Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Configuration : Configuration Tool Wizards and Screens

Configuration Tool Wizards and Screens
When you run TIBCO Configuration Tool in GUI mode or in console mode, you are prompted for information about the component or components you selected for configuration.
Create Express Developer Environment
The Create Express Developer Environment wizard prompts for minimal configuration information and creates a host, a node, and an Administrator server running on the host. If you want more control over configuration details, run the Create Administrator Server wizard.
 
When you select Create Express Developer Environment, a wizard prompts you for information about the Administrator server and information about the Enterprise Message Service to be used. When you complete the wizard, it creates an Administrator server, a host named SystemHost, and a node named SystemNode. At runtime, these components communicate using the Enterprise Message Service server you specify. The following table summarizes the information you need when running the wizard.
Administers TIBCO ActiveMatrix applications and infrastructure.
Provide the name of the communication group within which status messages are exchanged and the name of the Administrator server. Provide communication properties for the Administrator server.
Propagates status messages between hosts, nodes, and the ActiveMatrix Administrator server and messages between applications.
Provide configuration details for the Enterprise Message Service server.
Administrator Server
When you create an Express Developer Environment, you specify the enterprise name you want to use and the name of the Administrator server you want to create in the Administrator Server screen.
Communication group for status messages that are sent between Administrator server, the hosts that are bound to the server, and the nodes that are managed by those hosts.
Name of the Administrator server.
Administrator Server Notification and Messaging Bus Server
The Administrator Server Notification and Messaging Bus Server screen prompts you for the connection information for one or more TIBCO Enterprise Message Service server instances. The Notification and Messaging Bus servers in your express developer environment are then associated with that server.
 
You must have access to a running instance of TIBCO Enterprise Message Service Server before you can complete this screen. See TIBCO Configuration Tool Requirements. If you intend to enable SSL communications, see Secure Communication Channels.
Comma-separated list of machinename:port addresses for a TIBCO Enterprise Message Service server.
Default: machinename:port, where machinename is the machine on which TIBCO Configuration Tool is being executed and port is 7222.
Username for the TIBCO Enterprise Message Service server. The user must have administrator privileges in the TIBCO Enterprise Message Service server. If the user does not have administrator privileges, configure your TIBCO Enterprise Message Service server as described in Configuring TIBCO Enterprise Message Service Servers for Non-Admin Users.
Password for the TIBCO Enterprise Message Service user.
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.
If an Administrator server was configured in the wizard, a link to the URL of the Administrator server.
Create TIBCO ActiveMatrix Administrator Server
 
The Create TIBCO ActiveMatrix Administrator Server wizard allows you to configure many aspects of your server including the database, authentication method, monitoring, log service, and more. You can review this wizard documentation before you start configuration to decide how you want to set up the server.
* The wizard takes 15 minutes or more to complete depending on the configuration options.
Database Requirements
When you run the wizard, you specify a database for ActiveMatrix Administrator server and for several system services. If you are using an external database (and do not use HSQLDB as an external database), set up the external database before you run the wizard.
1.
2.
3.
* If you use an HSQLDB external database, concurrent user access to Administrator server is not supported.
 
Database Requirements For DDL Generator Users
ActiveMatrix 3.2 supports a DDL generator utility that you use before you run TIBCO Configuration Tool. When you use DDL scripts produced by the DDL generator, you need different database permissions than if you do not use DDL scripts. The database user must have connect and resource privileges, and cannot have DBA privileges. The database user must be assigned to the default schema.
 
Components Configured by the Create TIBCO ActiveMatrix Administrator Server Wizard
The following table summarizes the components that are configured in the Create TIBCO ActiveMatrix Administrator Server wizard, their function, and the decisions you must make, the information you must gather, and actions you must perform before running the wizard.
Administers TIBCO ActiveMatrix applications and infrastructure.
Provide the name of the communication group within which status messages are exchanged and the name of the Administrator server. Provide communication properties for the Administrator server.
The TIBCO Host instance that manages the SystemNode node on which the Administrator server runs.
Provide the name and management port of the development node and the name of the environment that contains the node. If you intend to complete the tutorials in Administration Tutorials, you must create the development node, accept the default values for the environment and node names, and deploy all product applications on the development node.Customize the name and management port of the BPM node and the name of the environment that contains the node.
Propagates status messages between hosts, nodes, and the ActiveMatrix Administrator server and messages between applications.
Provide configuration details for the Enterprise Message Service server.
A database authentication realm stores user and group authentication data in a database. Users and groups in this realm can be edited within ActiveMatrix Administrator. You have the option to use the same database for authentication and administration data.
Provides credentials to enable secure interactions between ActiveMatrix Administrator servers, hosts, and nodes.
Choose the ActiveMatrix Administrator notification server and database or another notification server and database. If the latter, provide the notification server and database configuration details according to Database Requirements.
Choose the ActiveMatrix Administrator database or another database. If you are using a database different than the one the ActiveMatrix Administrator server uses, see Database Requirements.
Choose the ActiveMatrix Administrator database or another database. If you do not use the ActiveMatrix Administrator database, see Database Requirements.
Administrator Server
The Administrator Server screen allows you to specify the enterprise name and the name of the Administrator Server instance.
Communication group for status messages that are sent between Administrator server, the hosts that are bound to the server, and the nodes that are managed by those hosts.
Name of the Administrator server.
Administrator Server TIBCO Host Instance
Each Administrator server runs on a TIBCO Host instance. You can specify the instance on which the server will run, configure server characteristics such as a Windows shortcut, and specify the environment and the node.
Name of the machine on which the TIBCO Host instance runs. The value of this property must either be a hostname resolvable through DNS or 0.0.0.0; it cannot be an IP address.
Default: machineName, where machineName is the machine on which TIBCO Configuration Tool is being executed.
Management port of the TIBCO Host instance.
Check 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.
Check 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.
Administrator Server Connection Settings
The Administrator Server Connection Settings screen allows you to specify non-default adapters and ports and to enable and configure SSL for the external HTTP port. You can also choose to enable an HTTP load balancer.
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 will listen 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.
Port on which Administrator clients access the Administrator server.
Length of time before an inactive Administrator GUI login session times out.
Check to secure communication between Administrator server and clients with SSL. When checked, the Self-Signed Certificate and Imported Certificate radio buttons display.
IIndicate that Administrator server will identify itself to clients with a self-signed certificate When selected it uses the self signed certificate from the samples folder.
Indicate that Administrator server will identify itself to clients with a certificate imported into Administrator server. When selected, the Keystore fields and Fetch Keystore button are enabled.
Administrator Server Internal HTTP Port
Number of the internal Administrator HTTP port.
Check to secure communication between Administrator server and hosts with SSL.
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.
 
As part of configuration, you set up the notification and messaging bus server. If you are considering using SSL, see Secure Communication Channels. If you intend to enable SSL communications, see SSL Requirements.
Comma-separated list of machinename:port addresses for a TIBCO Enterprise Message Service server.
Default: machinename:port, where machinename is the machine on which TIBCO Configuration Tool is being executed and port is 7222.
Username for the TIBCO Enterprise Message Service server. The user must have administrator privileges in the TIBCO Enterprise Message Service server. If the user does not have administrator privileges, configure your TIBCO Enterprise Message Service server as described in Configuring TIBCO Enterprise Message Service Servers for Non-Admin Users.
Password for the TIBCO Enterprise Message Service user.
TIBCO Enterprise Message Service Server is SSL Enabled
Configure the Administrator server create SSL connections to an TIBCO Enterprise Message Service server that is enabled for SSL.
When this field is checked, the SSL Keystore Configuration fields are enabled. The TIBCO Enterprise Message Service server usually listens on port 7243 when SSL-enabled. You must update the port in the Machine Name Port List field before proceeding with SSL configuration.
 
Administrator Server Database Details
You can choose to use Administrator server with a default in-process database during development. In production systems, use an external database instead. This screen allows you to configure database details.
 
 
If you decide to use a non-default database, the wizard prompts you for database details.
* Use the default embedded database only during development.
If you are using an external database, see Database Requirements. If you intend to enable SSL communications, see Secure Communication Channels and SSL Requirements.
* The properties that the wizard sets in the build.properties file depend on the context in which the prompts are displayed. By default, you specify the properties for the Administrator Server database and the information is then used for the Notification Service database, the Log Service database, and the Payload Service database. You can, however, overwrite the values for the Notification Service, Log Service, and Payload Service, and you can change them in the build.properties file.
Driver for the external database: org.hsqldb.jdbcDriver, com.mysql.jdbc.Driver, or com.ibm.db2.jcc.DB2Driver.
Default: org.hsqldb.jdbcDriver.
 
Administrator Server Authentication Realm
Administrator stores information about users and groups in an authentication realm. You can choose to let Administrator store the information in a database or in LDAP. TIBCO Configuration Tool will then prompt you for more information about the authentication realm.
Administrator Server Database Authentication Realm
If you select a database authentication realm, Administrator stores information about users and groups in a database. You can choose the same database as the Administrator server, or choose to configure a different database.
Use ActiveMatrix Administrator Server Database
Check if the database authentication realm should use the same database as the Administrator server. If unchecked, the database configuration fields display.
 
If you decide to use a non-default database, the wizard prompts you for database details.
* Use the default embedded database only during development.
If you are using an external database, see Database Requirements. If you intend to enable SSL communications, see Secure Communication Channels and SSL Requirements.
* The properties that the wizard sets in the build.properties file depend on the context in which the prompts are displayed. By default, you specify the properties for the Administrator Server database and the information is then used for the Notification Service database, the Log Service database, and the Payload Service database. You can, however, overwrite the values for the Notification Service, Log Service, and Payload Service, and you can change them in the build.properties file.
Driver for the external database: org.hsqldb.jdbcDriver, com.mysql.jdbc.Driver, or com.ibm.db2.jcc.DB2Driver.
Default: org.hsqldb.jdbcDriver.
 
Administrator Server LDAP Authentication Realm
If you select an LDAP authentication realm, Administrator stores information about users and groups in LDAP. You are prompted for the user and password, name resolution context, and server URLs. You can also specify the user search configuration and optional group information.
 
If you intend to enable SSL communications, see Secure Communication Channelsand SSL Requirements.
Default: com.sun.jndi.ldap.LdapCtxFactory
Default: machinename:389, where machinename is the machine on which TIBCO Configuration Tool is being executed.
Specifies how a user’s group memberships are found. Administrator uses group information when a user, once authenticated, performs other activities in the system. Options:
Group has users - List of users that belong to the group. When selected, the Group Attribute with User Names field is enabled.
User has groups - List of groups to which the user belongs. When selected, the User Attribute with Group Names field is enabled.
 
Administrator Server TIBCO Credential Server Details
You can specify credential server details to identify the TIBCO Credential Server that you want to use with your Administrator server installation.
Address of the network adapter on the machine on which TIBCO Credential Server runs. The default is set to 0.0.0.0 so that TIBCO Credential Server will listen on all network adapters (including http://localhost and http://hostname). With the default setting, clients can connect to TIBCO Credential 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.
User identifier for TIBCO Credential Server clients.
Administrator Server TIBCO Credential Server Keystore
If you enable SSL, you can use Administrator server with an auto-generated keystore or specify keystore information.
Default: TIBCO_HOME/tibcohost/1.2/templates/admin.default.ssl.trust.store.ts.
Administrator Server Monitoring Service Notification Server
The monitoring service is an ActiveMatrix application that aggregates performance data from runtime object, that is, TIBCO Host instances and nodes. TIBCO Configuration Tool deploys the monitoring service application on the SystemNode node, which is the node that runs the Administrator server.
Use ActiveMatrix Administrator Notification Server
Check if you want the monitoring service to use the same notification server as the Administrator server. If unchecked, the wizard allows you to configure the monitoring service explicitly.
 
As part of configuration, you set up the notification and messaging bus server. If you are considering using SSL, see Secure Communication Channels. If you intend to enable SSL communications, see SSL Requirements.
Comma-separated list of machinename:port addresses for a TIBCO Enterprise Message Service server.
Default: machinename:port, where machinename is the machine on which TIBCO Configuration Tool is being executed and port is 7222.
Username for the TIBCO Enterprise Message Service server. The user must have administrator privileges in the TIBCO Enterprise Message Service server. If the user does not have administrator privileges, configure your TIBCO Enterprise Message Service server as described in Configuring TIBCO Enterprise Message Service Servers for Non-Admin Users.
Password for the TIBCO Enterprise Message Service user.
TIBCO Enterprise Message Service Server is SSL Enabled
Configure the Administrator server create SSL connections to an TIBCO Enterprise Message Service server that is enabled for SSL.
When this field is checked, the SSL Keystore Configuration fields are enabled. The TIBCO Enterprise Message Service server usually listens on port 7243 when SSL-enabled. You must update the port in the Machine Name Port List field before proceeding with SSL configuration.
 
Administrator Server Monitoring Service Database
The monitoring service is an ActiveMatrix application that aggregates performance data from runtime objects. The monitoring service application is deployed on SystemNode, the node that runs the Administrator server.
Use ActiveMatrix Administrator Server Database
Check to have the monitoring service use the same database as the Administrator server. If unchecked, the database fields display and let you configure a non-default database.
 
If you decide to use a non-default database, the wizard prompts you for database details.
* Use the default embedded database only during development.
If you are using an external database, see Database Requirements. If you intend to enable SSL communications, see Secure Communication Channels and SSL Requirements.
* The properties that the wizard sets in the build.properties file depend on the context in which the prompts are displayed. By default, you specify the properties for the Administrator Server database and the information is then used for the Notification Service database, the Log Service database, and the Payload Service database. You can, however, overwrite the values for the Notification Service, Log Service, and Payload Service, and you can change them in the build.properties file.
Driver for the external database: org.hsqldb.jdbcDriver, com.mysql.jdbc.Driver, or com.ibm.db2.jcc.DB2Driver.
Default: org.hsqldb.jdbcDriver.
 
Administrator Server Monitoring Service Configuration
You can enable extended monitoring for the monitoring service to capture extended statistics for the service.
 
You can enable extended monitoring for the monitoring service to capture extended statistics for the service.
Administrator Server Log Service Database
A log service is a TIBCO ActiveMatrix application that offers logging services. The log service application is deployed in the environment SystemEnvironment on SystemNode, the node that runs the Administrator server. A log service receives log entries sent to a JMS destination and stores the entries in a database.
 
If you did not deploy the logging and payload services when you created the Administrator server using the TIBCO Configuration Tool, see TIBCO_HOME\administrator\version\scripts\logging\readme.txt.
Use ActiveMatrix Administrator Server Database
Check to have the log service use the same database as the Administrator server. If unchecked, the database fields display.
 
If you decide to use a non-default database, the wizard prompts you for database details.
* Use the default embedded database only during development.
If you are using an external database, see Database Requirements. If you intend to enable SSL communications, see Secure Communication Channels and SSL Requirements.
* The properties that the wizard sets in the build.properties file depend on the context in which the prompts are displayed. By default, you specify the properties for the Administrator Server database and the information is then used for the Notification Service database, the Log Service database, and the Payload Service database. You can, however, overwrite the values for the Notification Service, Log Service, and Payload Service, and you can change them in the build.properties file.
Driver for the external database: org.hsqldb.jdbcDriver, com.mysql.jdbc.Driver, or com.ibm.db2.jcc.DB2Driver.
Default: org.hsqldb.jdbcDriver.
 
Administrator Server Payload Service Database
A payload service supports archiving, persisting and retrieving large size payload data. It is an independent service and does not depend on a log service. However, a log record sent to a log service can include a payload URL field to link a log message and payload data. You can choose to store payload data in the same database used by Administrator server or use another database.
 
If you did not deploy the logging and payload services when you created the Administrator server using the TIBCO Configuration Tool, see TIBCO_HOME\administrator\version\scripts\logging\readme.txt.
Use ActiveMatrix Administrator Server Database
Check to have the payload service use the same database as the Administrator server. If unchecked, the database configuration fields display to let you specify database information.
 
If you decide to use a non-default database, the wizard prompts you for database details.
* Use the default embedded database only during development.
If you are using an external database, see Database Requirements. If you intend to enable SSL communications, see Secure Communication Channels and SSL Requirements.
* The properties that the wizard sets in the build.properties file depend on the context in which the prompts are displayed. By default, you specify the properties for the Administrator Server database and the information is then used for the Notification Service database, the Log Service database, and the Payload Service database. You can, however, overwrite the values for the Notification Service, Log Service, and Payload Service, and you can change them in the build.properties file.
Driver for the external database: org.hsqldb.jdbcDriver, com.mysql.jdbc.Driver, or com.ibm.db2.jcc.DB2Driver.
Default: org.hsqldb.jdbcDriver.
 
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.
 
If an Administrator server was configured in the wizard, a link to the URL of the Administrator server.
Create TIBCO Host Instance
A TIBCO Host instance is one of the central components of any product in the TIBCO ActiveMatrix family of products. You can create an instance explicitly and give custom information about the instance, associated notification server, and associated Administrator server.
 
* If you create a TIBCO Host instance, you cannot use that instance with an older version of the Administrator server.
 
TIBCO Host Instance
When you create a TIBCO Host instance, you are first prompted for the basic information that includes the name, enterprise and machine name, and behavior as a Windows application.
Name of the TIBCO Host instance. The name must be unique within the enterprise.
Name that defines a communication group for status messages sent between ActiveMatrix Administrator server and the hosts that are bound to the server.
Name of the machine on which the TIBCO Host instance runs.
Default: hostname, where hostname is the machine on which TIBCO Configuration Tool is being executed.
Management port of the TIBCO Host instance.
Check to register the TIBCO Host instance as a Windows service named TIBCO ActiveMatrix instanceName, where instanceName is the name you specified in the Name field, with startup type Automatic. The service is not started.
Check to create a shortcut named instanceName on the Windows desktop that points to CONFIG_HOME\tibcohost\instanceName\host\bin\tibcohost.exe and launches the TIBCO Host instance.
TIBCO Host Instance Notification Server
When you create a standalone TIBCO Host instance, you can specify an associated notification server. This notification server can be the same server as that used by the Administrator, or you can define a different notification server.
 
The Notification Server is an Enterprise Message Service server that performs two essential system functions within the TIBCO ActiveMatrix platform. It delivers status messages sent by hosts and nodes to the Administrator server.
See TIBCO Configuration Tool Requirements. If you intend to enable SSL communications, see Secure Communication Channels.
Comma-separated list of machinename:port addresses for a TIBCO Enterprise Message Service server.
Default: machinename:port, where machinename is the machine on which TIBCO Configuration Tool is being executed and port is 7222.
Username for the TIBCO Enterprise Message Service server. The user must have administrator privileges in the TIBCO Enterprise Message Service server. If the user does not have administrator privileges, configure your TIBCO Enterprise Message Service server as described in Configuring TIBCO Enterprise Message Service Servers for Non-Admin Users.
Password for the TIBCO Enterprise Message Service user.
TIBCO Enterprise Message Service Server is SSL Enabled
Configure the Administrator server create SSL connections to an TIBCO Enterprise Message Service server that is enabled for SSL.
When this field is checked, the SSL Keystore Configuration fields are enabled. The TIBCO Enterprise Message Service server usually listens on port 7243 when SSL-enabled. You must update the port in the Machine Name Port List field before proceeding with SSL configuration.
 
TIBCO Host Instance Administrator Server
When you create a TIBCO Host instance, you can immediately bind it to an Administrator server and specify connection information for that server, or choose not to bind the TIBCO Host instance to an Administrator server. You can enable the connection for SSL.
Bind to Administrator Server
Check to bind the TIBCO Host instance to an Administrator server. When checked, the Administrator server configuration fields are enabled.
Name of the machine on which the Administrator server is running. The value of this property must either be a hostname resolvable through DNS or 0.0.0.0; it cannot be an IP address.
Administrator Server is SSL Enabled
Check to enable the Administrator server internal port (see Administrator Server Internal HTTP Port) for SSL. When checked, the SSL Keystore Configuration fields are enabled.
 
Summary
If an Administrator server was configured in the wizard, a link to the URL of the Administrator server.
Configure Third-Party Driver
You can package a third-party driver into a feature and upload the feature with the Configure Third-Party Driver wizard. After the feature has been uploaded, you can add it to a node. See Administration.
 
When you select the Configure Third-Party Driver wizard, you are prompted for information about the driver itself and for the driver JAR files.
Third-Party Driver Details
The third-party driver details screen allows you to give detailed information about the driver you want to add to Administrator and install on nodes in your environment.
TIBCO enabled JDBC driver for Microsoft SQL Server 3.0
TIBCO enabled JDBC driver for Microsoft SQL Server 2.0.0
TIBCO enabled JDBC driver for Oracle 10.2.0
TIBCO enabled JDBC driver for Oracle 11.1.0
TIBCO enabled JDBC driver for IBM DB2 2.3.63 Not supported for ActiveMatrix Administrator and ActiveMatrix JDBC resource templates.
TIBCO enabled JDBC driver for IBM DB2 4.12.55
TIBCO enabled JMS client for Sonic 6.1.0
TIBCO enabled JMS client for WebSphere 7.0.0. Support for WebSphere MQ 6.0 is based on the backward compatibility of the WebSphere MQ 7.0 client library. When a JMS binding is configured with JMS topics and needs to work with WebSphere MQ 6.0, you must provide the 7.0.1.3 version of the client library.
Third-Party Driver JAR Folder
When you configure a third-party driver or other feature, you are prompted for the folder that contains the JARs to deploy to the Administrator server.
Summary
If an Administrator server was configured in the wizard, a link to the URL of the Administrator server.
Replicate TIBCO ActiveMatrix Administrator Server
In a production environment, you can set up your system to include a replica Administrator server on a second machine. Requests can be processed by either server. If one server is unavailable, the other server can process requests.
 
Overview
In TIBCO ActiveMatrix 3.2, you can replicate an Administrator server on a second machine by running TIBCO Configuration Tool. Before you can run the TIBCO Configuration Tool wizard that performs replication, you must set up the source environment and the destination requirement.
 
Shared File System Requirements and Overview
TIBCO Configuration Tool needs only read/write access for the shared filesystem. However, you should use a highly available filesystem in production environments. Consider using a SAN (storage area network) solution for shared folders and files. Place the TIBCO Administrator database on the SAN as well. Your storage needs depend on the number of DAA files you upload, on the number of application instances in use, and on the number of nodes you deploy the applications to.
After setup of the replica server, TIBCO Administrator reads from or writes to the shared file system each time it performs one of the following tasks:
In a steady state, when no deployment is being performed and the applications are running, TIBCO Administrator does not read from or write to the shared filesystem.
If the shared file system is not available when deployment is being performed, the deployment task fails. To recover, you retry the task. If you are using a SAN solution, this problem does not occur; only a highly available storage solution supports high availability for replicated TIBCO Administrator server setups.
 
Setting Up Your Environment for Replication
Before you can run TIBCO Configuration Tool for replication, you must set up your environment.
1.
2.
3.
Machine 1 - Set up the first Administrator server on machine 1 by using the Create TIBCO ActiveMatrix Administrator Server wizard.
1.
Install and configure your Administrator server and note down the following information.
TIBCO_HOME location
CONFIG_HOME location
2.
a.
Copy the folder CONFIG_HOME/admin/enterprise_name/shared to a location accessible from Machine 2.
b.
To let the Administrator server on Machine 1 know about the new location of the shared folder, Open a command prompt at TIBCO_Home\administrator\3.2\scripts.
c.
ant -f sharedWorkFolder_build.xml -Dadmin.shared.folder="NEW SHARED FOLDER LOCATION"
-Dconfig.home="CONFIG_HOME" -Denterprise.name="ENTERPRISE_NAME"
d.
Restart the SystemNode node. From CONFIG_HOME/tibcohost/Admin-enterprise_name-instance_name/host/bin, run the following commands.
tibcohost.exe stopNodes -nodeName SystemNode
tibcohost.exe startNodes -nodeName SystemNode
Machine 2 - Replicate the Administrator server on Machine 2.
1.
Run the installer, specifying the same TIBCO_HOME location as Machine 1 is using.
2.
On Machine 1, copy the content of CONFIG_HOME/tct/keystore and put it in the same folder on Machine 2. Create the folder if it does not exist.
3.
Launch TIBCO Configuration Tool and select the same CONFIG_HOME as was used on Machine 1.
4.
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.
b.
When you click Next, Machine 2 settings are validated. As part of validation, the wizard checks that.
c.
The wizard displays the current Administrator server configuration. You cannot edit the configuration.
d.
e.
* 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.
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.
After you have completed 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 allows you 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.
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.
Administrator Server Configuration Details
You must specify a host name and node name for your replica server.
Administrator Server TIBCO Host Configuration
As part of the replica server setup, you 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.
Check 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.
Check 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.
Administrator Server Connection Settings
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 will listen 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.
Port on which Administrator clients access the Administrator server.
Check to secure communication between Administrator server and clients with SSL. When checked, the Self-Signed Certificate and Imported Certificate radio buttons display.
Indicate that Administrator server will identify itself to clients with a self-signed certificate generated by TIBCO Credential Server.
Indicate that Administrator server will identify itself to clients with a certificate imported into Administrator server. When selected, the Keystore fields and Fetch Keystore button are enabled.
Administrator Server Notification and Messaging Bus Server
The notification server is an Enterprise Message Service server delivers status messages sent by hosts and nodes to the Administrator server.
 
This screen displays the Enterprise Messaging Serer details used by the first Administrator server. With the exception of the Password field, you cannot edit the configuration. 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 to make sure you can connect to the database from the replica machine.
Driver for the external database: org.hsqldb.jdbcDriver, com.mysql.jdbc.Driver, or com.ibm.db2.jcc.DB2Driver.
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, you might want to delete a replica instance and create a new one. You perform this task from the command-line, the TIBCO Configuration Tool wizard does not allow you to delete an instance.
Before you begin 
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.
About this task 
* 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.
2.
CONFIG_HOME/admin/enterprise_name/samples
3.
Edit the deleteAdminInstance_data.xml file to update the node and host name properties.
4.
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.
Edit ActiveMatrix Administrator Server Configuration
You can edit some aspects of the configuration for an existing Administrator server with TIBCO Configuration Tool.
 
This section describes the process of updating configuration settings that were initially specified when creating the Administrator server using TIBCO Configuration Tool.
To edit an existing configuration, follow these steps:
1.
2.
Select a CONFIG_HOME location for the Administrator server that you wish to change.
3.
Click Edit TIBCO ActiveMatrix Administrator Server Configuration - V3.2
Select an Administrator server configuration from the drop-down list.
Edit Administrator Server Configuration
You can edit the connection settings, database settings, or authentication realm settings for your Administrator server.
 
Edit the connection settings for the ActiveMatrix Administrator server.
Edit the configuration details for the ActiveMatrix Administrator database.
Edit the configuration details for the Administrator authentication realm.
Administrator Server Connection Settings
When you edit the connection settings, you can specify the network adapter and external port or enable SSL for HTTP communications. If you enable SSL, you are prompted to specify the certificate information. The defaults this screen displays show the current configuration settings.
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 will listen 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.
Port on which Administrator clients access the Administrator server.
Check to secure communication between Administrator server and clients with SSL. When checked, the Self-Signed Certificate and Imported Certificate radio buttons display.
Indicate that Administrator server will identify itself to clients with a self-signed certificate. When selected it uses the self signed certificate from the samples folder.
Indicate that Administrator server will identify itself to clients with a certificate imported into Administrator server. When selected, the Keystore fields and Fetch Keystore button are enabled.
Edit Administrator Server Database Details
The Edit Administrator Server Database Details screens allow you 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
Changing database details requires that you perform the following steps.
1.
2.
3.
4.
Start TIBCO Configuration Tool and select Edit TIBCO ActiveMatrix Administrator Server Configuration - V3.2.
5.
6.
When update is complete, TIBCO Configuration Tool restarts the SystemNode node.
7.
8.
9.
10.
* 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.
 
Driver for the external database: org.hsqldb.jdbcDriver, com.mysql.jdbc.Driver, or com.ibm.db2.jcc.DB2Driver.
Edit Administrator Server Authentication Realm
Administrator stores information about users and groups in an authentication realm. When you edit the Authentication realm, you can change the settings of the current realm, switch from a database to LDAP, or switch from LDAP to a database. TIBCO Configuration Tool will then prompt you for more information about the authentication realm.
 
Changing from a Database Realm to LDAP
Before you can change from a database realm to LDAP realm, you have to add a new user in the current DB realm and assign the user as superuser. This new user must already a user in the LDAP realm you want to use. See the Administration document for more information.
If you are changing from a Database realm to an LDAP realm, super user credentials are displayed. You need to enter the super user credentials you just created.
Enter the information about the authentication realm in the wizard screen.
 
Changing from LDAP to a Database Realm
What happens when you change from LDAP to a database realm depends on whether the database realm is empty or not.
For this case, use the tibco_user superuser to log in to TIBCO Administrator after you have changed to a database realm and change the password. Consider creating a new superuser and deleting the default tibco_user user.
For this case, use the tibco_user superuser to log in to TIBCO Administrator after you have changed to a database realm and change the password. Consider creating a new superuser and deleting the default tibco_user user.
Enter the information about the authentication realm in the wizard screen.
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.
 
When you edit the server configuration, the tasks you can perform depend entirely on the selections you made during configuration.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved