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
    • com.tibco.amx.mcr.aggregator
  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.3.
  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 installating 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 first 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 Oracle 10.2.0
  • TIBCO enabled JDBC driver for Oracle 11.1.0
  • TIBCO enabled JDBC driver for Microsoft SQL Server 2.0.0
  • TIBCO enabled JDBC driver for Microsoft SQL Server 3.0.0
  • TIBCO enabled JDBC driver for Microsoft SQL Server 4.0.0
  • TIBCO enable JDBC driver for IBM DB2 4.12.55
  • TIBCO enabled JDBC driver for IBM DB2 2.3.63

Default: JDBC driver provided for HSQL 1.8.400.

Database URL

URL of the external database.

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

Username External database username.

Default: sa.

Password External database password.

Default: None.

Max Connections Maximum number of database connections to allocate.

Default: 30.

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

Default: Cleared.

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.
Contents
Search Results