{"id":49332,"date":"2023-01-15T11:05:07","date_gmt":"2023-01-15T03:05:07","guid":{"rendered":"https:\/\/oihelp.corporate.ifs.com\/help\/?page_id=49332"},"modified":"2024-07-08T09:43:59","modified_gmt":"2024-07-08T01:43:59","slug":"configuration-utility","status":"publish","type":"page","link":"https:\/\/oihelp.corporate.ifs.com\/help\/field-explorer\/field-operator-administration\/configuration-utility\/","title":{"rendered":"Configuration Utility"},"content":{"rendered":"\n

This article applies to IFS OI Field Operator: Explorer Edition version 4.11 and later. For more, see Release History<\/a>.<\/p>\n

This application allows you to define instances of the Field Operator Server and configure various settings for each instance. The settings dictate how users connect to an instance and certain behaviours of the application. The configuration application is a windows application, run on the computer where the Field Operator Server components were installed. Much of the information edited with this application is stored in files on the server.<\/p>\n

Open the configuration application by launching IFS OI.FieldOperator.Config.exe as administrator<\/em><\/strong>. If you chose to do so, the setup program will have created a shortcut on the desktop of the server computer.<\/p>\n

Instance definition<\/h2>\n

1. Launch the Field Operator Configuration Utility (if not already open).<\/p>\n

Note<\/strong>: Always run the Configuration Utility as an Administrator<\/strong> because it needs to update configuration files on the server computer.<\/p>\n

\"Graphical<\/a><\/p>\n

When you first open the Configuration Utility, there will be no instances in the list.<\/p>\n

\"Graphical<\/a><\/p>\n

2. Click the Add<\/strong> button to set up the first instance or select an instance in the list and click Edit<\/strong>.<\/p>\n

3. Complete the Define a Field Operator Instance<\/strong> page with the credentials necessary to connect to your IFS OI Merrick and IFS OI Explorer implementations.<\/p>\n

\"Graphical<\/a><\/p>\n

Instance Name<\/strong>: Give the instance a name that will help you recognize it later in the Enterprise Manager. Most companies define Instances to match organizational units or regions of users within their company.<\/p>\n

IP Address<\/strong>: This should default to the first IP Address available on the machine. If you see an IPV6 address in this drop-down, please refer to Appendix A: Disabling IPV6.<\/p>\n

Port Number<\/strong>: This is necessary for the Route Setup application. Route Setup communicates with the Field Operator server via TCPIP sockets. Typically use the default port number but note that you\u2019ll need this later when configuring the Route Setup app for users.<\/p>\n

Automatic or Manual<\/strong>: This setting specifies whether the instance will be started automatically when the machine is rebooted. The default is Automatic<\/strong>. Manual can be helpful for temporary test instances that you only want to run occasionally. Remember, each instance is watching the source data for changes that need to be downloaded to user devices. See Field Operator Sync Process<\/a>.<\/p>\n

Set time to Restart Field Operator instances<\/strong>: The Instance bounces each night at this specified time to restart counters such as the number of connections today, etc. The default time is midnight.<\/p>\n

Run from this folder<\/strong>: This is how you run multiple versions of the Field Operator server software on one computer. See Running multiple versions of the Field Operator Server on one computer<\/a><\/p>\n

Connect to IFS OI Explorer<\/strong>: Input the credentials for the IFS OI Explorer Forms account with Administrator privileges that you\u2019ve collected before the installation (see the Field Operator\u00a0<\/strong>Server 4 Installation Guide<\/em><\/strong> which was downloaded from the IFS OI Store when you downloaded the software.)<\/p>\n

Enable Shiftlog Workbooks<\/strong>: As of version 4.7, please leave this deselected<\/em> unless your company is working directly with IFS OI development on this beta functionality.<\/p>\n

Connect to IFS OI Merrick<\/strong>: Input the information for the ProCount database that you\u2019ve collected before the installation. The ProCount database must be SQL Server database and must be upgraded to the version of Field Operator being configured. Note: Typically, you can update the ProCount database even if you\u2019re still using a previous version of the Merrick software. For example, Merrick 3.16 will continue to run if the database is upgraded to 4.x. Please check with P2 support for exact compatibility with the versions you\u2019re working with.<\/p>\n

Production System<\/strong>: You must select ProCount Version 3x+, 4x or later <\/strong>to support Field Operator devices. As defined in the Field Operator Installation Guide, the ProCount database must be updated to the version of Field Operator Server that you are installing, using the Database Upgrade process in the Merrick setup program.<\/p>\n

Field Operator Metadata Set<\/strong>: Screens for ProCount, Carte and Field Operator are all defined in the Merrick Metadata configuration utility. Within that utility, you can define multiple sets<\/em> of metadata. Many companies will only have one set of screens in production but may want to define different sets for test. The Field Operator instance is instructed to use a given set with this configuration. If in doubt, choose the default.<\/p>\n

Allocation Engine<\/strong>:<\/p>\n

Important<\/strong>: Select the version of the Merrick Allocations engine that is processing your ProCount data. Setting this incorrectly will cause the allocation engine to miss data that needs to be processed.<\/p>\n

4. Click OK<\/strong>.<\/p>\n

The database connection will be validated and then the instance will show in the Instances list.<\/p>\n

Note:<\/strong> for testing purposes, the Connect to IFS OI Explorer<\/strong> setting can be deferred, but commentary will be disabled in the application. If you\u2019re still in the process of setting up IFS OI Explorer, you can deselect this setting and get the system running for IFS OI Merrick first and then return to this setting later when IFS OI Explorer is running.<\/p>\n

Note:<\/strong> The Connect to IFS OI Explorer<\/strong> setting has changed from earlier versions. Before v4.6, ProCount, Carte and Field Operator all used the same connection setting which was stored in the ProCount database. Now, the setting in the Field Operator Configuration Utility only applies to Field Operator. To see commentary in ProCount and Carte you also<\/em><\/strong> need to enter this information in the Merrick Metadata Configuration Utility. (this allows you to start using commentary in Field Operator without affecting ProCount and Carte, and bring ProCount and Carte commentary on-line later.)<\/p>\n

Field Operator Options<\/h2>\n

Once the instance has been defined, select it from the instance list and select Field Operator Options<\/strong> to configure the various settings that control the application\u2019s behaviour. Depending on the instance definition, different tabs of information may appear here. For example, if you have not yet connected to IFS OI Explorer, the IFS OI Explorer and Commentary tabs will not be present.<\/p>\n

Environment \/ Authentication<\/h3>\n

Note:<\/strong> Settings on this tab must be completed before attempting to start an instance for the first time.<\/p>\n

\"Graphical<\/a><\/p>\n

Server ID<\/strong>: This ID uniquely identifies your Field Operator Server instance within the user community. Choose an ID that will be unique to your company and identify the instance within your company. If your company is XYZ petroleum and you\u2019re defining an instance for the Bakken region, an appropriate id might be XYZ-BAKKEN01.<\/p>\n

Important<\/strong>: Each server instance must have its own unique<\/em><\/strong> Server ID. Do not attempt to start two instances with the same ID.<\/p>\n

Your users will need to know this ID (along with valid credentials to your domain). The users will need to type the Server ID into their devices. Before deciding on a Server ID, it\u2019s a good idea to try typing it into a phone\u2019s keypad to see if it\u2019ll be difficult for your users.<\/p>\n

Upload log files to P2 Support once per day<\/strong>: If this option is selected, your Field Operator Server will communicate via the standard fo.p2energysolutions conduit to an Field Operator Server running at IFS OI. The process will upload the eVINmmyy.log files, any eVINServerErrors.txt file, SyncLogmmddyy.csv files and any files in the UploadsErrors folder. When working with P2 Support, our personnel may ask you to invoke this process one time by selecting Server<\/strong> \u2013 Upload Logs to IFS OI<\/strong>\u00a0in the Field Operator Instance Manager<\/strong>. IFS OI would appreciate you turning this option on even if you\u2019re not actively working with P2 support, as a collection of this data will help IFS OI serve you better.<\/p>\n

Conduit URL<\/strong>: Typically, you\u2019ll leave the default value of fo.p2energysolutions.com. Some customers may be working with IFS OI directly to define a company specific conduit URL.<\/p>\n

Environment Type: <\/strong>The word \u201cEnvironment\u201d is almost synonymous with \u201cinstance\u201d in the Field Operator world. (Almost, but not quite\u2026. it\u2019s possible to have two environments that access one instance)<\/p>\n

Users will sign into an Environment <\/strong>which connects to the instance. The main attribute of an Environment is how users are authenticated. This is a new concept in Field Operator version 4.7 as we\u2019ve added the ability to authenticate using the IFS OI Central portal. See Authentication and Authorization in Field Operator<\/a>. If you\u2019re installing Field Operator on your company\u2019s server, then the environment type will likely be On-Prem Domain.<\/strong><\/p>\n