Using Centralized Configuration for EnterpriseOne HTML Servers (Release 9.2.7)

Starting with Tools Release 9.2.7, you can use Centralized Configuration in Management Console to configure default configuration settings across EnterpriseOne HTML servers. Centralized Configuration enables you to configure server settings from a single location that can be applied to all the HTML servers assigned to a server group.

You can use Centralized Configuration under Configure section in Management Console to create a centralized configuration file, e1central.properties, that will help Management Console and HTML server instance to connect with the database.

The configuration file will be distributed to all the applicable instances in the Server Manager Console, enabling Centralized Configuration. Management Console will use the values defined in the centralized configuration file to connect with the database. Each HTML server, that has Centralized Configuration enabled, will read the configuration files (such as jde.ini, jas.ini, jdbj.ini, jdelog.properties, etc.) from the database and create the .ini file before starting the instance.

After you enable the Centralized Configuration, the group level default configuration settings will be applicable to the server group as well as all the HTML server instances in that server group. Any changes made on the configuration of server groups will be applicable to HTML server instances as well. However, if you change the configuration settings at instance level, the system overrides the group level configuration settings and uses the instance level configuration. You have the option to restore the default group level configuration settings for such instances. See Understanding How to Restore Group Default Settings for HTML Server Instances for details.

When you add a new server to a server group, Management Console automatically applies the default configuration settings for that type of server to the newly added server. See Configuring Default Configuration Settings for details. Moving an existing server from a group to a different server group will use the settings of the server group it is moved to, if you have the Centralized Configuration enabled for a server instance. Server Manager automatically applies the default configuration settings of that server group to the newly added HTML server instance.

Below prerequisites should be fulfilled before you enable Centralized Configuration:

The Sever Manager Console and the HTML servers should be on Tools Release 9.2.7.
All the required drivers and certificates must be installed on both Server Manager Console and JAS for Server Manager Console to communicate with the database.
Latest Tools Rollup ESU must be installed.

Any changes to configuration settings on group or instance level requires you to synchronize the settings and restart the HTML server instance for to use the new settings. For such instances, the system displays a Warning message along with a Synchronize Configuration button. Click the Synchronize Configuration button to sync the changes and restart the instance.

For all cluster setup, you must manually copy the e1central.properties file, that has the database details, along with the e1Central_config folder, if available, to the node’s config folder.

Important: If you have more than one Sever Manager Console, you need to have different data sources for respective consoles. For each Server Manager Console, you must create different F98CCONF (E1 Centralized Configuration Table) table in different data sources. The table F98CCONF (E1 Centralized Configuration Table) in system data source will be created as part of latest Tools Rollup ESU.

In case there is a change in the data source, you need to manually migrate all the records from F98CCONF (E1 Centralized Configuration Table) table to the new data source.

Note: HTML servers that are on and above Tools Release 9.2.7, must be restarted after synchronization is complete with the new settings. When Centralized Configuration is enabled, any update that is made manually will not take effect after the server is restarted. The changes are lost as the changes will be downloaded from the database.

> obe:

Click here to view an OBE of this feature.