Replicate TIBCO ActiveMatrix Administrator Server
Machine 2 - Replicate the Administrator server on
5. When TIBCO Configuration Tool returns to the wizard selection screen, click Replicate TIBCO ActiveMatrix Administrator Server and configure the replica server by responding to the wizard
prompts.
a. In the Remote Administrator Details screen, enter the information to connect to the first Administrator server. This information is used to fetch the current configuration.
b. When you click Next, Machine 2 settings are validated. As part of validation, the wizard checks that.
● Both machines use the same CONFIG_HOME.
● The shared folder is accessible and contains valid data.
● The first administrator server is using an external database.
c. When validation is successful, you can provide a unique host name and node name for the replica server on the next screen.
The wizard displays the current Administrator server configuration. You cannot edit the
d. Enter passwords when prompted.
e. After entering the configuration details, click Configure to replicate the Administrator server.
After clicking Configure in TCT, in case any error occurs, user need to delete the partially installed replicated instance before starting over.
The TIBCO Configuration Tool Replicate TIBCO ActiveMatrix Administrator Server wizard does not show the configuration details for Monitoring, Logging, and Payload services. If those services are configured and deployed on the first Administrator server, they are automatically deployed on the replica server as part of the replication process.
While planning replication, ensure that both the Administrator servers have the same set of software versions including the hotfixes that were applied before upgrading to ActiveMatrix 3.3.1.
When you log in to one of the Administrator servers (or access the load balancing URL), you see the following system setup:
● Two hosts exist in the Infrastructure > Hosts screen.
● Two nodes exist in the SystemEnvironment environment in the Infrastructure > Nodes screen.
After completing the setup, requests can be processed by either server. If one server is unavailable, the other server can process requests.
Remote Administrator Server Details
The Remote Administrator Server Details screen is used to specify the machine name and port for the primary server. You must also specify the username and password. If you configured the primary server with SSL, you must perform SSL configuration for the replica server as well.
Field Description
Machine Name Name of the machine on which the primary Administrator server runs.
The value of this property must a hostname resolvable through DNS or an IP address.
Port Management port that the primary Administrator server is using.
Default: 8120
Username User name of the administrator of the primary Administrator server. This user must be a super user. This credential is used to access the first admin server to get the current configuration. Only super user is allowed to query the current configuration.
Default: root
Password Specify the password of the administrator of the primary Administrator server.
Administrator server
is SSL enabled If the primary Administrator server is SSL enabled, select this check box so that TIBCO Configuration Tool uses SSL to connect to the primary
Administrator server. If you select the check box, you are prompted for keystore configuration information.
Test Connection Click this button to verify that TIBCO Configuration Tool can access the server you specified using the username and password you specified.
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.
Default: JKS.
Keystore
Password Password that protects the keystore.
Create Replicated Instance Validation Info
The Create Replicated Instance Wizard Validation Info screen appears only if your system setup meets all requirements.
The requirements are listed in Setting Up Your Environment for Replication on page 83.
Administrator Server Configuration Details
You must specify a host name and node name for your replica server.
Field Description
Enterprise Name Displays the enterprise name of the remote Administrator server. You cannot change the enterprise name; the remote server and the replica server must be in the same enterprise.
Host Name Name of the SystemHost instance that will be associated with the replica server. The host name must be unique. You cannot use the name you used for the host associated with the remote Administrator server.
Default: SystemHostReplica
Node Name Name of the SystemNode instance to be associated with the replica server.
The node name must be unique. You cannot use the name you used for the node associated with the remote Administrator server.
Default: SystemNodeReplica
Administrator Server TIBCO Host Configuration
As part of the replica server setup, specify the machine and port for the TIBCO host on which the replica server runs. This information is for the local machine, not the remote machine.
Field Description
Machine Machine on which the TIBCO Host instance runs.
Field Description
Port Port for the TIBCO Host instance to communicate with other services in the environment.
Register as Windows
Service Select to register the TIBCO Host instance as a Windows service named TIBCO ActiveMatrix Admin-enterpriseName-serverName with startup type Automatic. The service is not started.
Default: Cleared.
Create Windows
Shortcut Select to add a shortcut named TIBCO ActiveMatrix Admin
-enterpriseName -serverName that points to CONFIG_HOME\tibcohost
\Admin-enterpriseName-serverName\host\bin\tibcohost.exe to the Windows desktop.
Default: Cleared.
Administrator Server Connection Settings
Field Description
Network Adapter Address of the network adapter on the machine on which the Administrator server runs. The default is set to 0.0.0.0 so that
Administrator listens on all network adapters (including http://localhost and http://hostname). If you leave the default, clients can connect to the Administrator server using any of the conventions (localhost, IP address, hostname). The value of this property must either be a hostname
resolvable through DNS or 0.0.0.0; it cannot be an IP address.
Management Port Management port of the node that runs Administrator server.
Default: 6021.
External HTTP Port Port on which Administrator clients access the Administrator server.
Default: 8120.
Enable SSL for
External HTTP Port Select to secure communication between the Administrator server and clients with SSL. When selected, the Self-Signed Certificate and Imported Certificate radio buttons display.
Default: Same as for remote server.
Self-Signed Certificate Indicates that the Administrator server identifies itself to clients with a self-signed certificate generated by TIBCO Credential Server.
Do not use a self-signed certificate in production environments.
Default: Same as for remote server.
Imported Certificate Indicates that the Administrator server identifies itself to clients with a certificate imported into the Administrator server. When selected, the Keystore fields and Fetch Keystore button are enabled.
Keystore Location Location of the keystore to import.
Field Description Keystore Type Type of keystore.
Keystore Password Password that protects the keystore.
Fetch Keystore When you click this button, you can select one of the available key aliases, specify the keystore password, and click Verify Keystore to verify that the password you entered is valid.
Administrator Server Notification and Messaging Bus Server
The notification server is an Enterprise Message Service server that delivers status messages sent by hosts and nodes to the Administrator server.
This screen displays the Enterprise Messaging Service server details used by the first Administrator server. You cannot edit the configuration, except for the Password field. If SSL is enabled in the first admin server the SSL settings are displayed as well, but are not editable.
Click Test Connection to make sure that they can connect to EMS from the replica administrator machine.
Administration Server Database Details
The administrator server that you are replicating must be set up to use an external database. This screen displays the information about the external database used by the first admin server. You cannot change this information for the replica server.
Click Test Connection to make sure you can connect to the database from the replica machine.
Field Description
Database Driver Driver for the external database:
● TIBCO enabled JDBC driver for Oracle 12.1.100
● TIBCO enabled JDBC driver for Oracle 11.1.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 IBM DB2 4.19.66
● TIBCO enabled JDBC driver for IBM DB2 4.12.55 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.
Field Description
Max Connections Maximum number of database connections to allocate.
Default: 10.
Database Server is
SSL Enabled Select to enable the database server for SSL. When selected, the SSL Keystore Configuration fields are enabled.
Default: Cleared.
Administrator Server Database Authentication Realm Details
If you selected a database authentication realm on the remote server, both Administrator server instances will store information about users and groups in a database. This screen displays connection information for the database you set up from the remote server.
You can review connection information in this screen, then enter the password for the specified database and click Test Connection.
Administrator Server Configuration LDAP Authentication Realm
If you select an LDAP authentication realm when you configure the remote Administrator server, Administrator retrieves information about users and groups from LDAP. This screen shows the LDAP configuration used by the first administrator server.
Click the Test Connection button to make sure the connection between LDAP server and the replica server works properly.
Administrator Server Configuration Summary
Each TIBCO Configuration Tool wizard's summary screen allows you to check the configuration that you specified and see the effects of that configuration. You can click Back to make changes, save the configuration for use by the silent installer, or click Configure to start the configuration. If you are using the console configuration tool, you can perform the same actions by typing single-letter commands, as prompted.
The Administrator Server Configuration Summary screen displays information about the session scripts and log folder and about the Administrator URL. For this wizard, you can only choose to replicate the remote server, or cancel the replication.
Deleting an Administrator Server
If you are using a replica Administrator server, the TIBCO Configuration Tool wizard does not allow you to delete a replica instance, if you want to. You can delete from the command line.
Prerequisites
Make sure that the super user specified in the remote_props.properties has force_delete
permission. Only users with explicit force_delete and super user permission are allowed to delete the Administrator server instance.
Do not run the deletion script on the machine on which the Administrator instance you want to delete is running. For example, assume your cluster consists of Administrator instance A running on machine X and Administrator instance B running on machine Y. To delete instance B, run the script from
instance A running on machine X.
Procedure
1. Open a command window.
2. Go to the following directory.
CONFIG_HOME/admin/enterprise_name/samples
3. Edit the deleteAdminInstance_data.xml file to update the node and host name properties.
4. Run the following command.
ant -f deleteAdminInstance_build.xml
When you run this command, the replica node is deleted from the environment and the replica host will be unregistered. If the replica host has any runtime nodes, the replica host is not unregistered.
5. If the replica host is unregistered, got to the machine on which the administrator instance was running and terminate the TIBCO Host process.