The present document is an overview of the process of configuration upload to the Eubrewnet. There are some steps that users have to follow before introducing a configuration for working with the system:
- The Operators have to contact admin (firstname.lastname@example.org) for registration. They need to provide the list of Brewers that they are responsible for and contact information.
- The administrator carries out the registration in the system.
- The operators have to log in the website of Eubrewnet (Eubrewnet).
- Then the operators can upload configuration for their brewers.
- Configuration in the Database
The set of parameters and values that are needed to process Raw data and calculate the different products.
- Configuration Files
Files that store the values that are needed to fill the Configuration: now ICF and/or O3Brewer.ini, ( ZSF, DCF, UVR … will be added in next steps).
- Eubrewnet Client
Software that has to be installed and run periodically in computers that can access the Brewer files which sends the files to Eubrewnet.
The Data Upload Procedure
There are several ways to upload configurations to the database:
- Use the values that are already stored in the database corresponding to Configuration Files (ICF are automatically stored at the database if they have been sent by the client).
- Upload the Configuration Files and filling the values that are common to the Configuration.
- Fill the form by hand.
It’s an IP responsibility to add the configuration. You have several options available to perform this task. All the process that are going to be described below are usable at any time.
1. Use values already on Database
The process begins selecting a Brewer and a Date. When the Form (Figure 1) is loaded, several buttons will appear for the Configuration Files that have been submitted previously. It will display the configuration parameter actives for this date (minor nearest date) the valuable Configuration files could be ICF and O3Brewer.
Figure 1: Configuration upload form
The operators can select the values from the Configuration Files that have been submitted to the database in two ways: using all the values that are common to the configuration from a file (Figure 2) or selecting them individually (Figure 3).
Figure 2: Using all configuration file content
Figure 3: Using single values
2. Upload the configuration by files
The operators can use values that belong to Configuration Files during upload time. There is a tab with the admitted Configuration Files (Figure 4). After uploading a file, all the values that are common to the Configuration are going to be replaced with the values in the Configuration File.
Figure 4: Using configuration file contentThere is an option for store the content of these files in the database: Replace Content Check (Figure 5). Selecting it involves the replacement of the data in the database for the file. It is potentially dangerous.
Figure 5: Replacing configuration files in databaseFor security purposes, the Replace Content Check can only be selected once for a configuration and a type of file. It means that if the operators want to upload two or more configuration files, she has to use this functionality after inserting the configuration into the database.
3. Upload the configuration by hand
The operators can write the values at any time. They have to respect the format: integers, doubles or dates as “Year-Month-Day” (<Year, four digits>-<Month, two digits>-<Day, two digits>).
After the form is filled, the operator can stored its content in two different ways, to create a new configuration or to replace the existing one:
- If the operator wants to create a new Configuration (Figure 6). The system will try to upload the values. The process will fail if there’s other Configuration for the same date.
Figure 6: Create a new configuration
- If the operator decides to modify an existing Configuration, all the values will be rewritten (Figure 7).
Figure 7: Modify existing configuration
- Process Level 2.0 Data Logic is now working. Setting the Process checkbox will force to recalculate data from last configuration until the day before the configuration’s date (Figure 8).
Figure 8: Process Level 2.0 Data
The Operators can see the list of available configurations in Configuration History (Figure 9).
Figure 9: History tableThe configuration constants are divided into different sets. To see the values it’s only needed a click on the Set Name (as seen in the Figure 10).
To see the values of all the stored configurations at a glance, there’s the table view (Figure 11).