Edit Administrator Server Database Details

The Edit Administrator Server Database Details screens is used to change the database details for your server. Using the wizard requires that you prepare your environment and that you perform some post-processing steps.

Changing Database Details

To change the database details, perform the following steps:
  1. From the TIBCO Administrator user interface, stop the following applications from the System environment:
    • com.tibco.amx.commonlogging.logservice.app
    • com.tibco.amx.commonlogging.payloadservice.app
  2. Perform the following steps to uninstall the resource instances:
    1. Make sure that you uninstall Log Service and Payload Service first. (TIBCO ActiveMatrix Payload Service Teneo Resource, TIBCO ActiveMatrix Log Service Teneo Resource).
    2. Uninstall the Teneo resource instances from the system node (TIBCO ActiveMatrix Governance Teneo Resource).
    3. Uninstall the Hibernate Resource Instance from the system node (TIBCO ActiveMatrix Governance Hibernate Resource).
    4. Uninstall in the following order : Log Service or Payload Service in any order followed by the Governance JDBC shared resource instances from the system node. Ensure that the Governance JDBC shared resource instance must be the last to be uninstalled. It is recommended to use the Force Uninstall option for JDBC Resource Instance.
    Note: If you skip steps 3 to 7, please restart TIBCO Host manually.
  3. If required, change the configuration of the user or database.
  4. Start TIBCO Configuration Tool and select Edit TIBCO ActiveMatrix Administrator Server Configuration - V3.4.
  5. Select the enterprise name and server name from the Server Configuration drop down menu, and select Edit Database settings.
  6. Edit the database configuration, and click Configure.

    When update is complete, TIBCO Configuration Tool restarts the SystemNode node.

  7. When the SystemNode node becomes available, log in to the TIBCO Administrator GUI and update the Governance JDBC resource with the new database configuration information. Cancel the pop-up to automatically synchronize the resource instances and applications.
  8. Install the following:
    1. JDBC Resource Instance for Governance JDBC Resource Instance. Make sure that Governance Service is installed before installing Log Service and Payload Service.
    2. Install the Hibernate Resource Instance (TIBCO ActiveMatrix Governance Hibernate Resource).
    3. Install the Teneo Resource Instances. Make sure Governance Service is done before installation of Log Service and Payload Service.
Note: If the data base URL is changed to point to a different database, make sure you migrate all the data from the old database location to the new database location. Editing the configuration alone does not migrate the data.
Field Description
Use Default In-Process Database

This will be checked if the current administrator uses an in-process database. TCT does not support editing the in-process database details.

Field Description
Database Driver Driver for the external database:
  • TIBCO enabled JDBC driver for IBM DB2 4.12.55
  • TIBCO enabled JDBC driver for IBM DB2 4.19.66
  • TIBCO enabled JDBC driver for IBM DB2 4.24.92
  • TIBCO enabled JDBC driver for Oracle 11.1.0
  • TIBCO enabled JDBC driver for Oracle 12.1.100
  • TIBCO enabled JDBC driver for Oracle 12.2.0
  • TIBCO enabled JDBC driver for Oracle 18.3.0
  • TIBCO enabled JDBC driver for Oracle 19.3.0
  • TIBCO enabled JDBC driver for Microsoft SQL Server 4.0.0
  • TIBCO enabled JDBC driver for Microsoft SQL Server 4.2.0
  • TIBCO enabled JDBC driver for Microsoft SQL Server 6.0.0
  • TIBCO enabled JDBC driver for Microsoft SQL Server 7.0.0
  • TIBCO enabled JDBC driver for PostgreSQL 10.7.0 (postgresql-42.2.8.jar is required)
  • TIBCO enabled JDBC driver for PostgreSQL 11.5.0 (postgresql-42.2.8.jar is required)

Default: JDBC driver provided for HSQL 1.8.400.

Database URL

URL of the external database.

Default: jdbc:hsqldb:hsql://localhost:1234/amx.

Note: For PostgreSQL database, you must add client machine IP address entry in the pg_hba.conf file. If the TIBCO ActiveMatrix Administrator is replicated, you must also add IP address of the machine on which ActiveMatrix Administrator is replicated in the pg_hba.conf file. For more information, see PostgreSQL documentation.
Username External database username.

Default: sa.

Password External database password.

Default: None.

Max Connections Maximum number of database connections to allocate.

Default: 10.

Database Server is SSL Enabled Check to enable the database server for SSL. When checked, the SSL Keystore Configuration fields are enabled.

Default: Cleared.

Note: PostgreSQL database with SSL enabled is not supported in TIBCO ActiveMatrix 3.4.0 Hotfix 002.
Field Description
Create a Trust Store... Invokes a wizard to import certificates from a server and create the trust store.
Browse Invokes a dialog to navigate to a keystore file.
Keystore Location Location of the keystore.
Keystore Type Type of the keystore: JKS or JCEKS.
Keystore Password Password that protects the keystore.
Caution: If ActiveMatrix Administrator is not starting due to database connection failure, refer to the resolution listed in the Troubleshooting section of the TIBCO ActiveMatrix Service Grid Installation guide.

Changing ActiveMatrix Policy Director Governance Database Details

Note: If you are using a common database for ActiveMatrix and ActiveMatrix Policy Director Governance, use the above procedure to change the database details.

If you are using a separate database for ActiveMatrix Policy Director Governance than the ActiveMatrix database, use the following steps to change the database details:

  1. From the TIBCO Administrator user interface, stop the following applications:
    • com.tibco.amx.commonlogging.logservice.app
    • com.tibco.amx.commonlogging.payloadservice.app
    • com.tibco.amx.mcr.aggregator
    • com.tibco.ampd.ogp.de
    • com.tibco.ampd.psm
  2. If required, change the configuration of the user or database.
  3. Make the appropriate changes to the TIBCO ActiveMatrix Governance JDBC Resource Shared Resource Template.
  4. Click Cancel on the pop-up.
  5. Install the JDBC Resource Instance for Governance JDBC Resource Instance. If the pop-up appears at this step, clear the selected applications. This automatically reinstalls Teneo and Hibernate Resource instances. If the pop-up does not appear, make sure that Teneo and Hibernate resource instances that were uninstalled in previous steps are installed now, and are in the Running state.
  6. Manually install the JDBC, Teneo, and Hibernate resource instances by navigating to the Resource Instance tab for the JDBC shared resource. It automatically re-installs the Teneo and Hibernate shared resources.
  7. After the resource installation is complete, restart TIBCO Host.
  8. Restart the applications stopped in Step 1.