Making Planned Database Configuration Changes

This section lists the steps to update the database configuration in a planned manner when you have the ActiveMatrix Administrator running.

1. Edit the JDBC resource templates and reinstall resource instances using the following steps:
   1. In ActiveMatrix Administrator GUI, navigate to Shared Objects > Resource Templates.
   2. Select TIBCO ActiveMatrix PayloadService JDBC Resource.
      Note: If you upgraded from a prior release, select payloadJdbcSharedResource.
   3. In the Details section, update the database configuration and click Save. However, in the Apply Changes in Resource Template to Runtime window, click Cancel .
   4. In the Resource Instances tab of the Details section, verify that the resource instance shows Out of Sync.
   5. Click the Install button.
   6. Wait and refresh till the status of the resource instance switches to Running and In Sync.
2. Repeat step 1, but for the resource templates -TIBCO ActiveMatrix LogService JDBC Resource and TIBCO ActiveMatrix Governance JDBC Resource. The order is important, and the TIBCO ActiveMatrix Governance JDBC Resource must be the last one.
   Note: If you upgraded from a prior release, select cl_logservice_jdbc and GovernanceJDBCSharedResource.
3. Make the planned database configuration change on the database server. For example, changing the password.
4. Using TIBCO Configuration Tool, update the database configuration for the ActiveMatrix Administrator as follows:
   1. Select Edit TIBCO ActiveMatrix Administrator Server Configuration.
   2. From the Select Server Configuration drop-down list, select the enterprise name and server name.
   3. Check Edit Database Settings.
   4. If the users or groups are defined in the Administrator database and not in an LDAP server, select Edit Authentication Realm Settings .
   5. Click Test Connection to verify the settings.
   6. Click Configure to apply the changes. When the update is complete, TIBCO Configuration Tool restarts the system node.
   7. Wait for a few minutes for the system node to become available.