Understanding How to Enable Centralized Configuration for EnterpriseOne HTML Servers

After you save the settings in the Centralized Configuration for the first time, it is applied to the server group’s HTML server configuration and all the HTML server instances within that group. Upon a successful save, Centralized Configuration inserts a group level configuration to the database. An instance level override, for those instances where the level configuration settings are different from the server group it belongs to, is also inserted.

Centralized Configuration is also enabled for HTML servers that are on Tools Release 9.2.7 while you create a new instance. Alternatively, with Tools Release 9.2.7, you can perform a Change Component operation on the existing server instances which enables Centralized Configuration. Change component will make all the current configuration entries in database as instance level configuration.

To enable Centralized Configuration:

  1. Log in to Server Manager Console.

  2. Click Centralized Configuration to access the database details.
    Note: Make sure you have required drivers and certificates installed to allow the JAS instances and the Server Manager Console to connect with the database.
  3. Complete the below fields:
    • Username

      Enter the username to use for centralized configuration when connecting to the configured database.

    • Password

      Enter the password to use for centralized configuration when connecting to the configured database.

    • Database Type

      Use the dropdown to select a database where the centralized configuration table is stored. Tnsname.ora field is populated when you select Oracle Database and the Use TLS field is populated when you select either IBM UDB, AS/400 or SQL.

    • Owner

      Enter the database object owner where the centralized configuration table is stored.

    • Server

      Enter the server name where the centralized configuration table is stored.

    • Database Name

      Enter the database name where the centralized configuration table is stored.

    • Physical Database

      Enter the physical database name where the centralized configuration table is stored.

    • Server Port

      Enter the database server port where the centralized configuration table is stored.

    • Data Source Name

      Enter the database server port where the centralized configuration table is stored.

    • Use TLS

      The Use TLS option appears for selection after you select either IBM UDB, AS/400, or SQL. Select the checkbox if you want a secure TLS connection to either of the databases.

    • Tnsname.ora

      The Tnsname.ora field appears for modification after you select Oracle Database in Database Type. Enter the Tnsname.ora connection details.

  4. Click Save.

The system will continue to apply the settings and it will take between 5 to 15 minutes to complete the action depending on the number of server instances in the group. Do not refresh your web browser until the system prompts that the operation is successful.

If the database details are incorrect, the system displays an error message. You must rectify the incorrect details to enable Centralized Configuration.
Note: The data migration is a one-time event. If the database already has the records, the migration will not initiate after you click Save. The system only performs the database connection validation.