You can use TIBCO Configuration Tool to specify the properties of
ActiveMatrix Administrator servers and
TIBCO Host instances and the properties of third-party drivers you want to add to
ActiveMatrix Administrator servers.
You can run TIBCO Configuration Tool in GUI mode, console mode, silent mode, or script mode.
The default ports in a ActiveMatrix environment must be available before you can start configuration with the default values. You can specify a different port during configuration, or change the ports explicitly later.
Figure 1,
Table 4, and
Table 5 summarize the default values of the ports configured in
TIBCO Configuration Tool. You can change the defaults in
TIBCO Configuration Tool wizards. For information on how to change the ports after you have created runtime objects with
TIBCO Configuration Tool, see
Administration.
Table 4.
TIBCO ActiveMatrix Runtime Object Default Ports
|
|
|
|
|
|
|
|
|
|
TIBCO ActiveMatrix Administrator external HTTP
|
|
TIBCO ActiveMatrix Administrator internal HTTP
|
|
|
|
The ActiveMatrix platform is partitioned across many components. You can secure the corresponding communication channels during initial configuration or later.
ActiveMatrix components communicate with each other and with third-party applications over several communication protocols.
Figure 2 illustrates the components and communication protocols.
You can specify the SSL configuration of the communication channels at different times in the life cycle of a deployment. Table 6 lists how to perform the initial SSL configuration and how to upgrade, downgrade, and change the configuration of each channel. The Key column in the table points to the numbers in
Figure 2.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
TIBCO Host instance - TIBCO Enterprise Message Service
|
When creating the Administrator server or TIBCO Host instance in TIBCO Configuration Tool.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Administrator server (external HTTP port) - TIBCO Business Studio
|
Administrator - When creating Administrator server in TIBCO Configuration Tool.
TIBCO Business Studio - When you connect to Administrator.
|
|
|
|
|
|
SSL uses keys and certificates when it establishes the secure connection. A keystore is a database of keys and certificates. A keystore password is required to access or modify the keystore.
In ActiveMatrix, access to keystores is provided by a
Keystore Provider resource instance.
Each entry in a keystore is identified by an alias. In the case of private keys and their associated certificate chains, these aliases distinguish among the different ways in which the entity may authenticate itself. For example, the entity may authenticate itself using different certificate authorities, or using different public key algorithms. An alias might be named after the role in which the keystore owner uses the associated key, or might identify the purpose of the key.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(Administrator only) For superusers, passwords display encrypted. For non-superusers, the password doesn't display even if it was set when it was created. If you have permission to edit the password, you can specify a new value and save. If you edit other fields, the old value for the password field is retained. If you want to set an empty value as password, click the link Set Blank Password.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1.
|
Go to the CONFIG_HOME/admin/enterpriseName/samples/ directory.
|
2.
|
Open the keystore_data.xml data file and edit the following attributes of the CredentialEntry element:
|
3.
|
Open the keystore_build.xml build file and edit the following attributes of the AMXKeyStoreTask element in the addCredential target:
|
4.
|
Run ant -f keystore_build.xml addCredential.
|
Record the values of the keytool options because you must supply them when you upload the trust store keystore into
TIBCO Configuration Tool or
Administrator.
|
|
|
a.
|
Click Create a Trust Store.
|
|
|
b.
|
Click Browse and navigate to the location of the keystore you created.
|
|
2.
|
Click Test Connection to verify that the keystore enables an SSL connection.
|
•
|
Administrator and TIBCO Business Studio wizards and CLI property files
|
The default configuration of the Administrator server network adapter is the unspecified IP address (0.0.0.0), which means that it listens on IPv4 and IPv6 addresses. When clients access the
Administrator server by machine name, the name lookup resolves to both addresses. By default,
Administrator clients use the IPv4 address. To override this behavior and use the IPv6 address, set the value of the JVM system property
java.net.preferIPv6Addresses to true. For further information, see
Networking IPv6 User's Guide for JDK/JRE 5.0 . The Nodes chapter in
Administration explains how to set a JVM property for a node.
TIBCO Configuration Tool Requirements
You can run TIBCO Configuration Tool right after installation or at a later time. To run the tool successfully, you must first make sure your system meets the requirements.
Each product installation has a set of requirements. TIBCO Configuration Tool has additional requirements.
See the readme file for additional requirements.
To run successfully, TIBCO Configuration Tool must have access to a
TIBCO Enterprise Message Service that meets certain requirements.
A TIBCO Enterprise Message Service server acts as a notification server for the
ActiveMatrix Administrator servers and TIBCO Host instances within an enterprise. The enterprise is defined by the enterprise name and the
TIBCO Enterprise Message Service server that you specify when you run one of the configuration wizards. Ensure that the following requirements and prerequisites are satisfied:
•
|
The TIBCO Enterprise Message Service server must be running before you run the Create TIBCO ActiveMatrix Administrator Server and Create TIBCO Host Instance wizards or create these components in console mode or silent mode.
|
•
|
If you manually start the TIBCO Enterprise Message Service server, make sure you use the same configuration files as the Windows service. Use the following command
|
TIBCO_HOME/ems/version number/bin/tibemsd -config EMS_CONFIG_HOME/tibco/cfgmgmt/ems/data/tibemsd.conf
where EMS_CONFIG_HOME is the configuration folder for
TIBCO Enterprise Message Service.
By default, ActiveMatrix runs with SSL disabled. You can enable SSL for individual connections or for all connections in your environment.
See Secure Communication Channels for information on setting up SSL. If you intend to enable SSL, ensure the following prerequisites are satisfied.
•
|
TIBCO Enterprise Message Service Server - The TIBCO Enterprise Message Service server must be enabled with SSL and configured with a certificate file that contains both the server and issuer certificates before you run the Create TIBCO Administrator Server and Create TIBCO Host Instance wizards or before you create these components in console mode or silent mode.
|
•
|
Database and LDAP Servers - Database and LDAP servers must be enabled with SSL before you run the Create TIBCO Administrator Server wizard or before you create these components in console mode or silent mode.
|
Configuring TIBCO Enterprise Message Service Servers for Non-Admin Users
If you want to configure runtime objects and services, and you do not have administrator privileges on the TIBCO Enterprise Message Service server you want to use, you can configure the
TIBCO Enterprise Message Service server to allow configuration for non-admin users. The following steps presents the most restrictive permissions necessary.
1.
|
In the Enterprise Message Service server console, set permissions for the Administrator server users. In the following commands, replace username and password with the username and password values appropriate for each bus.
|
You can run TIBCO Configuration Tool using GUI wizards, using the console, or in silent mode.
Running TIBCO Configuration Tool in GUI Mode
When you run TIBCO Configuration Tool in GUI mode, you are prompted to select a configuration wizard. The wizard prompts you for information about that component.
1.
|
Execute TIBCO_HOME/tct/1.2/TIBCOConfigurationTool.
|
The TIBCO Configuration Folder dialog displays. A
TIBCO configuration folder stores configuration data generated by
TIBCO products. Configuration data can include sample scripts, session data, configured binaries, logs, and so on. The configuration folder is referred to as
CONFIG_HOME.
3.
|
TIBCO Configuration Tool displays with links to the following configuration wizards:
|
|
|
|
Specify the name and server properties of an ActiveMatrix Administrator server and the machine name, port, and credentials of the TIBCO Enterprise Message Service server used by the Administrator server. The TIBCO Host instance named SystemHost and the SystemNode node that runs ActiveMatrix Administrator server are started. The rest of the configuration properties are set to the default values described in the section Create TIBCO ActiveMatrix Administrator Server.
|
|
•
|
Specify the properties of an ActiveMatrix Administrator server and optionally create the server. The SystemHost TIBCO Host instance and the SystemNode node that runs ActiveMatrix Administrator server are started.
|
|
|
|
|
|
|
|
|
|
7.
|
On any screen, click Finish to accept default values for all the configuration properties and jump to the Summary screen.
|
Running TIBCO Configuration Tool in Console Mode
You can run TIBCO Configuration Tool from the command prompt on the platform of your choice.
You can run TIBCO Configuration Tool in GUI mode, console mode, or silent mode. The mode you used for running the installer does not affect the mode in which you run
TIBCO Configuration Tool.
3.
|
Type 1 or press Enter to configure all communications with SSL, or type N to continue.
|
Running TIBCO Configuration Tool in Silent Mode
Running TIBCO Configuration Tool in silent mode allows you to configure your system without user input. You can supply parameters that specify which wizard you want to run, and you can specify which configuration file you want to use.
Before you run in silent mode, you should run the tool in GUI mode to generate a configuration file (build.properties). You can then run in silent mode, pointing to the configuration file you generated.
Each build.properties file specifies the machine name and operating system. If you want to use that properties file to run in silent mode on a different machine, potentially with a different operating system, you can edit the properties file. You might have to change the following values in the configuration file.
The name of subfolder depends on the wizard you run in GUI or console mode.
2.
|
Edit the build.properties file and customize the configuration. In most cases, you specify a different machine name, Administrator server, and so on.
|
|
|
|
|
Edit Administrator Server
|
|
|
|
|
|
|
|
|
|
−
|
wizard_id can be one of the IDs listed in Step 3.
|
−
|
build.properties is a properties file for that wizard. You must customize most properties files before you run the wizard.
|
−
|
wizard_target is an optional parameter that allows you to set a non-default build target. By default, the build.xml file of the wizard you invoke is used.
|
Using TIBCO Configuration Tool Scripts and Property Files
When you run TIBCO Configuration Tool, the tool creates property files and Ant build script files and stores them in the following location:
CONFIG_HOME/tct/subfolder/date-time/scripts.
•
|
Table 8 lists the subfolders in CONFIG_HOME and includes information about the files in each folder.
|
•
|
Table 9 lists some of the properties that you might change in the properties file.
|
|
|
|
|
|
|
|
build.properties - Property settings and locations of configuration and property files
|
|
|
|
|
|
|
|
|
|
|
|
|
|
TIBCO Enterprise Message Service server URL for ActiveMatrix Administrator
|
|
|
|
TIBCO Host instance name for ActiveMatrix Administrator
|
|
|
|
TIBCO Host instance management port
|
|
TIBCO Enterprise Message Service server URL for standalone TIBCO Host instance
|
|
TIBCO Credential Server URL for standalone TIBCO Host instance
|
Saving a TIBCO Configuration Tool Configuration
You can run a TIBCO Configuration Tool wizard in GUI mode to configure a component, and save those settings as a configuration file with an associated script.
A script that TIBCO Configuration Tool generates only works for the same minor version, even if you install other versions later. For example, if you generate a script in 3.2.x, that script uses the 3.2.x features and cannot use 3.3.x features even if 3.3.x is installed.
1.
|
Run TIBCO Configuration Tool and select one of the wizards.
|
−
|
CONFIG_HOME is the folder you specify when you run the TIBCO Configuration Tool in one of the supported modes.
|
5.
|
Click OK to complete configuration.
|
Reusing a TIBCO Configuration Tool Configuration
You can run TIBCO Configuration Tool and reuse the configuration on a different machine and operating system if you edit the properties files to account for the following differences between the originating machine
A script that TIBCO Configuration Tool generates only works for the same minor version, even if you install other versions later. For example, if you generate a script in 3.2.x, that script uses the 3.2.x features and cannot use 3.3.x features even if 3.3.x is installed.
2.
|
If using SSL, edit integration_create_admin_data.xml and update the value of the keyStoreLocation attribute in the KeyStoreResource target element.
|
4.
|
Run ant [-logfile logfile] –f build.xml. The actions occur in the following subfolders:
|
|
|
|
|
|
Creates the tibcohost\hostName data folder, where hostName is the name you specified for the TIBCO Host instance.
|
|
Creates the admin\enterpriseName data folder and the tibcohost\hostName data folder, where hostName is the name you specified for the TIBCO Host instance and enterpriseName is the name you specified for the enterprise.
|
Create TIBCO Host Instance Properties
You can create a TIBCO instance by editing the appropriate properties in the appropriate files and running a script.
Use the scripts in the tibcohost folder to create a
TIBCO Host instance on a new machine or an additional
TIBCO Host instance on the machine where an ActiveMatrix Administrator server is running.
For creating an instance on a new ActiveMatrix machine, you update only the
build.properties file. Otherwise, you must modify configuration properties in the
tibcohost-instance.properties. For example, to create an additional
TIBCO Host instance on the same machine, change the value of the
amx.th.hpa.jmx.port property.
First TIBCO Host Instance
To create a standalone TIBCO Host instance, update the following properties before running the script:
|
|
|
|
|
|
|
TIBCO Host instance machine name
|
|
|
|
|
|
|
|
|
TIBCO Host instance management port
|
Update the following property when ActiveMatrix software is not installed onto the default location.
In addition to the changes listed in Additional TIBCO Host Instances, update the following properties to conform to target operating system path conventions:
Create ActiveMatrix Administrator Server Properties
You can create an ActiveMatrix Administrator server by editing the appropriate properties in the appropriate files and running a script.
Update the following property if the ActiveMatrix enterprise name has changed.
Update following property when ActiveMatrix software is installed in a different location.