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


Configuration : Configuration Setup and Overview

Configuration Setup and Overview
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.
* Silent mode and script mode are for advanced users.
Networking
Before you start configuration, check whether the default ports that TIBCO Configuration Tool expects to use are available. You must also decide whether you want to use SSL, and might have to set up keystores and trust stores.
Default Ports
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.
Figure 1. Default Ports
Table 4. TIBCO ActiveMatrix Runtime Object Default Ports
SystemHost TIBCO Host instance management
Standalone TIBCO Host instance management
TIBCO ActiveMatrix Administrator external HTTP
TIBCO ActiveMatrix Administrator internal HTTP
TIBCO Credential Server
Secure Communication Channels
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.
Figure 2. Communication Channels
By default, the communication channels are not secure. To secure them, you can configure the channels to use the Secure Sockets Layer (SSL) protocol. SSL is a cryptographic protocol that provides security and data integrity for communications over TCP/IP networks.
An SSL client and server negotiate a connection by using a handshaking procedure. During this handshake, the client and server agree on various parameters to establish the connection's security, as follows:
1.
2.
The certificate usually contains the server name, the trusted certificate authority (CA), and the server's public encryption key.
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.
Administrator server (external HTTP port) - web and CLI clients
When creating the Administrator server in TIBCO Configuration Tool.
Upgrade or downgrade: Administrator CLI
Administrator server (internal HTTP port) - hosts and nodes
When creating the Administrator server in TIBCO Configuration Tool.
Upgrade or downgrade: Administrator web UI or CLI
Change SSL configuration: Administrator web UI or CLI
Administrator server - Enterprise Message Service server
When creating the Administrator server in TIBCO Configuration Tool.
Upgrade or downgrade: Administrator web UI or CLI
Change SSL configuration: Administrator web UI or CLI
TIBCO Host instance - TIBCO Enterprise Message Service
When creating the Administrator server or TIBCO Host instance in TIBCO Configuration Tool.
Upgrade or downgrade: Administrator CLI
Administrator server - external database and LDAP servers
When creating the Administrator server in TIBCO Configuration Tool.
Administrator server - hosts and nodes (management)
When creating Administrator in TIBCO Configuration Tool.
Upgrade: Administrator web UI or CLI
Administrator -UDDI server
Manually import the UDDI server certificate into the Administrator server trust store using keytool.
Enable secure communication in Administrator web UI or CLI.
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.
Administrator Upgrade or downgrade: Administrator CLI
Administrator web UI or CLI
Administrator web UI or CLI
Keystores
If you set up your environment to use SSL, you have to set up keystores.
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.
 
Keystore Entries
A keystore has two types of entries:
Certificates of trusted entities are typically imported into a keystore as trusted certificates.
 
Keystore Entries and Aliases
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.
 
Keystore Passwords and Private Key Passwords
The private keys in a keystore are encrypted with a keystore password, which should be several words long.
You can also protect each private key with its individual password, which may or may not be the same as the keystore password.
If a password is lost, the associated keys cannot be recovered.
Keystore Provider
If you set up your environment for SSL, you have to set up a keystore. As part of the process, you configure a keystore provider.
 
Provides access to a keystore. Keystores can be stored internally in Administrator or externally.
 
General
Administrator - Upload Keystore From
Path to the keystore to be uploaded into Administrator. After the keystore is uploaded, a link displays from which the keystore can be downloaded.
(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.
Creating a Keystore Containing a Username and Password
You can create a keystore that contains a username and password by editing data and build files and running an Ant script.
Procedure 
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.
Example 
<?xml version="1.0" encoding="UTF-8"?>
<amxdata_base:Enterprise
xmlns:amxdata="http://tibco.com/amxadministrator/command/line/types"
xmlns:amxdata_base="http://tibco.com/amxadministrator/command/line/types_base"
xmlns:amxdata_reference="http://tibco.com/amxadministrator/command/line/types_reference"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://tibco.com/amxadministrator/command/line/types_base ../schemas/amxdata_base.xsd http://tibco.com/amxadministrator/command/line/types ../schemas/amxdata.xsd">

<AMXKeyStore xsi:type="amxdata:AMXKeyStore">
<CredentialEntry alias="myDatabase" protectionParam="databaseKeyAliasPassword" username="scott" secret="tiger" />
<CredentialEntry alias="myLDAP" protectionParam="ldapKeyAliasPassword" username="cn=Manager,dc=example,dc=com" secret="password" />
</AMXKeyStore>

</amxdata_base:Enterprise>

<target name="addCredential">
<AMXKeyStoreTask
dataFile="keystore_data.xml"
adminKeyStorelocation = "my_keystore.jceks"
adminKeyStorePassword = "password"
action="add"/>
</target>
>ant -f keystore_build.xml addCredential
Buildfile: C:\amx320data\admin\amxadmin\samples\keystore_build.xml

addCredential:
[AMXKeyStoreTask] INFO - Keystore file C:\amx320data\admin\amxadmin\samples\my_keystore.jceks does not exist; creat
ing a new keystore file
[AMXKeyStoreTask] Adding entry for alias 'myDatabase'...
[AMXKeyStoreTask] Adding entry for alias 'myLDAP'...
[AMXKeyStoreTask] Saving to keystore file C:\amx320data\admin\amxadmin\samples\my_keystore.jceks

BUILD SUCCESSFUL
Total time: 12 seconds
Trust Stores
A trust store is a keystore that contains trusted certificates. Each time you configure an external server connection for SSL, you create and configure a trust store for that connection.
You can create a trust store by using certificates imported from trusted servers or by uploading a keystore file.
Creating a Trust Store Keystore
You can create a trust store with keytool if you have a trusted public certificate.
Procedure 
1.
A root CA is an entity like VeriSign that digitally signs your certificate. The certificate will be in a file with a special extension such as .pem extension.
2.
Use the JDK keytool utility to create a keystore containing the certificate from step 1.
JAVA_HOME\bin\keytool -import -v -trustcacerts -alias MyCert
-file server.cer -keystore MyTrustStore.jks -keypass secret -storepass keystorePassword
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.
Configuring a Trust Store
To configure a trust store, you can either upload certificates and have TIBCO Configuration Tool create the trust store, or you upload a keystore file that contains certificates.
About this task 
If you configure a trust store for use with an SSL-enabled Microsoft SQL Server, you must upload a keystore. For Microsoft SQL databases, the Configure a Trust Store button does not work.
Procedure 
1.
a.
Click Create a Trust Store.
a.
Create a keystore containing the certificates from the trusted server.
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.
IPv6 Support
If an object has a property that can contain an IP address, the address is usually set to the unspecified IP address (0.0.0.0). That means the object listens on IPv4 and IPv6 addresses. By default clients use the IPv4 address. You can override this behavior so that clients use the IPv6 address.
 
Prerequisites
Before using an IPv6 supported network perform the following tasks:
1.
2.
3.
4.
a.
b.
 
IPv6 Address Support
IPv6 addresses are supported by machine names and URLs in the following tools and objects:
TIBCO Configuration Tool
Administrator and TIBCO Business Studio wizards and CLI property files
 
IPv6 Address Representation
IPv6 address representation is described in the IPv6 Addressing Architecture and Format for Literal IPv6 Addressing in URLs specifications, and summarized in Table 7.
Enclose the address in square brackets ([]). For example, the URL of an Administrator server running on a machine at the address FEDC:BA98:7654:3210:FEDC:BA98:7654:3210 is http://[FEDC:BA98:7654:3210:FEDC:BA98:7654:3210]:8120/amxadministrator.
 
IP Address Use and Resolution
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.
If you do not have administrator privileges for the Enterprise Message Service server, you must set you Enterprise Message Service for a non-administrator user. See Configuring TIBCO Enterprise Message Service Servers for Non-Admin Users.
* See the readme file for additional requirements.
Enterprise Messaging Server 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:
Each enterprise must use a different TIBCO Enterprise Message Service server.
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.
If you do not have administrator privileges for TIBCO Enterprise Message Service, you can request privileges or configure the service for a non-admin user from the TIBCO Enterprise Message Service server console. See Configuring TIBCO Enterprise Message Service Servers for Non-Admin Users.
SSL Requirements
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.
See Secure Communication Channels.
Configuring TIBCO Enterprise Message Service Servers for Non-Admin Users
Configuration of runtime objects and services is easiest if you have administrative privileges on the TIBCO Enterprise Message Service server you want to use. If you do not have administrative privileges, you can set up the TIBCO Enterprise Message Service server to allow configuration for non-admin users.
About this task 
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.
Procedure 
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.
delete queue >
delete topic >
create user
username "Description of the user" password=password
create queue AMX_SV.>
grant queue AMX_SV.> user=username create, delete, modify, send, receive
delete queue >
delete topic >
create user
username "Description of the user" password=password
create topic EMSGMS.>
grant topic EMSGMS.> user=username create, modify, subscribe, publish
grant topic $sys.monitor.connection.* user=username subscribe
grant admin user=username view-connection,view-server
create topic AMX_MGMT.>
grant topic AMX_MGMT.> user=username create, modify, subscribe, publish
delete queue >
delete topic >
create user
username "Description of the user" password=password
create queue com.tibco.amf.admin.deploymentServerQueue.>
grant queue com.tibco.amf.admin.deploymentServerQueue.> user=username create, delete, send, receive
delete queue >
delete topic >
create user
username "Description of the user" password=password
create queue cl_logservice_queue.physical
create queue cl_payload_queue.physical
grant queue cl_logservice_queue.physical user=username send, receive
grant queue cl_payload_queue.physical user=username send, receive
create jndiname cl_logservice_queue queue cl_logservice_queue.physical
create jndiname cl_payload_queue queue cl_payload_queue.physical
delete queue >
delete topic >
create user
username "Description of the user" password=password
create queue amx.governance.stats
grant queue amx.governance.stats user=username send, receive
create queue amx.governance.internal.stats
grant queue amx.governance.internal.stats user=username send, receive
2.
The Notification, Management, and Messaging buses are initially grouped together as are the Monitoring, Logging, and Payload buses.
delete queue >
delete topic >
create user
username "Description of the user" password=password
create queue AMX_SV.>
grant queue AMX_SV.> user=username create, delete, modify, send, receive
create topic EMSGMS.>
grant topic EMSGMS.> user=username create, modify, subscribe, publish
grant topic $sys.monitor.connection.* user=username subscribe
create queue com.tibco.amf.admin.deploymentServerQueue.>
grant admin user=username view-connection,view-server
grant queue com.tibco.amf.admin.deploymentServerQueue.> user=username create, delete, send, receive
delete queue >
delete topic >
create user
username "Description of the user" password=password
create queue cl_logservice_queue.physical
create queue cl_payload_queue.physical
create queue amx.governance.stats
create queue amx.governance.internal.stats
grant queue cl_logservice_queue.physical user=username send, receive
grant queue cl_payload_queue.physical user=username send, receive
grant queue amx.governance.stats user=username send, receive
grant queue amx.governance.internal.stats user=username send, receive
create jndiname cl_logservice_queue queue cl_logservice_queue.physical
create jndiname cl_payload_queue queue cl_payload_queue.physical
3.
Configure and create the Administrator server and TIBCO Host instances as described in Create TIBCO ActiveMatrix Administrator Server and Create TIBCO Host Instance.
Running TIBCO Configuration Tool
You can run TIBCO Configuration Tool using GUI wizards, using the console, or in silent mode.
About this task 
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.
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.
Before you begin 
Make sure your system meets all requirements. See TIBCO Configuration Tool Requirements.
Procedure 
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.
2.
Accept the default folder for CONFIG_HOME, type a folder name, or click Browse to select a folder, and click OK.
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.
Specify the database that serves as a persistent store for ActiveMatrix Administrator server and the monitoring, logging, and payload services.
Specify the communication and management properties of a standalone TIBCO Host instance and optionally create and launch the TIBCO Host instance.
Edit an existing ActiveMatrix Administrator server configuration.
4.
The wizard reference, also available as online help, can help guide your decisions.
5.
Optionally, check the Configure to Secure All Communication with SSL checkbox.
When you enable SSL, the wizards containing communication channels display SSL configuration fields. For information on the supported communication channels, see Secure Communication Channels.
6.
Optionally, click Load to load the values saved from a previous configuration session. See Saving a TIBCO Configuration Tool Configuration.
7.
On any screen, click Finish to accept default values for all the configuration properties and jump to the Summary screen.
8.
9.
Click Configure.
Running TIBCO Configuration Tool in Console Mode
You can run TIBCO Configuration Tool from the command prompt on the platform of your choice.
Before you begin 
Make sure your system meets all requirements. See TIBCO Configuration Tool Requirements.
About this task 
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.
Procedure 
1.
In a console window, go to the TIBCO_HOME\tct\version directory and run the following command.
* On Windows, the name ends with a c; do not type TIBCOConfigurationTool -consoleMode.
2.
3.
Type 1 or press Enter to configure all communications with SSL, or type N to continue.
For information on the supported communication channels, see Secure Communication Channels.
4.
When configuration completes, you can select a second configuration option or type q to quit.
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.
About this task 
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.
ActiveMatrix installation location
ActiveMatrix runtime configuration data location
ActiveMatrix enterprise name
* You must be an advanced user with an in-depth understanding of the configuration process to successfully run TIBCO Configuration Tool in silent mode.
Procedure 
1.
build.properties file is stored in CONFIG_HOME/tct/subfolder/date-time/scripts.
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.
See Using TIBCO Configuration Tool Scripts and Property Files.
3.
Create Administrator Server
Edit Administrator Server
Create TIBCO Host Instance
4.
From a console window, run TIBCO Configuration Tool in silent mode.
TIBCOConfigurationTool -silentMode -wizard.id wizard_id wizard.props build_properties [wizard.target ant_target-name]
TIBCOConfigurationToolc.exe -silentMode -wizard.id wizard_id wizard.props build_properties [wizard.target ant_target-name]
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.
Example 
Example 1. Running in Silent Mode
TIBCOConfigurationToolc.exe -silentMode -wizard.id com.tibco.tct -wizard.props C:/build.properties -wizard.target end-to-end
Using TIBCO Configuration Tool Scripts and Property Files
You save and edit property files that TIBCO Configuration Tool generates, and perform configuration with those files by using an Ant script.
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.xml - Ant build file
build.properties - Driver specification and JAR file location
build.xml - Ant build file
build.properties - Property settings and locations of configuration files
tibcohost-instance.properties - TIBCO Host instance configuration
build.xml - Ant build file
build.properties - Property settings and locations of configuration and property files
integration_create_admin.xml - ActiveMatrix Administrator server bootstrap configuration
admin-instance.properties - ActiveMatrix Administrator server configuration
admin-tibcohost-instance.properties - TIBCO Host instance configuration that manages the node running the ActiveMatrix Administrator server
admin-envt-data.xml - ActiveMatrix development environment configuration
cl_logservice_data.xml - Log service configuration file
cl_payloadservice_data.xml - Payload service configuration file
governance_integration_data.xml - Monitoring service configuration file
ActiveMatrix installation location
ActiveMatrix runtime configuration data folder
ActiveMatrix Administrator machine name
ActiveMatrix Administrator server base URL
ActiveMatrix Administrator enterprise name
TIBCO Enterprise Message Service server URL for ActiveMatrix Administrator
ActiveMatrix Administrator database URL
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.
About this task 
* 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.
Procedure 
1.
Run TIBCO Configuration Tool and select one of the wizards.
2.
3.
4.
Click Save.
The configuration properties file and script is saved in the specified folder. The default folder is CONFIG_HOME/data/tct/subfolder/date-time/scripts, where
CONFIG_HOME is the folder you specify when you run the TIBCO Configuration Tool in one of the supported modes.
subfolder depends on the wizard you run.
5.
Click OK to complete configuration.
Reusing a TIBCO Configuration Tool Configuration
After you have saved a configuration file, you can run an Ant script to reuse the configuration.
Before you begin 
Install and configure Ant on the target machine.
About this task 
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
ActiveMatrix installation location
ActiveMatrix runtime configuration data location
ActiveMatrix enterprise name
Because all the property files specify the machine name, you must always replace the source machine name with the target machine name.
* 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.
Procedure 
1.
2.
If using SSL, edit integration_create_admin_data.xml and update the value of the keyStoreLocation attribute in the KeyStoreResource target element.
3.
4.
Run ant [-logfile logfile] –f build.xml. The actions occur in the following subfolders:
Adds plug-ins to TIBCO_HOME\components\shared\1.0.0\plugins.
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.
See Using TIBCO Configuration Tool Scripts and Property Files.
Configure Third-Party Driver Properties
You can configure third-party drivers by setting properties in a build.properties file and running a script.
 
To configure drivers, set the following properties in tpclshells/build.properties:
ActiveMatrix installation location.
In most cases, you modify the folder locations in the following properties.
Update the following properties to conform to target operating system path conventions:
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 name
TIBCO Host instance machine name
 
Additional TIBCO Host Instances
TIBCO Host instance name
TIBCO Host instance management port
 
Enterprise Name
ActiveMatrix enterprise name
 
Installation Location
Update the following property when ActiveMatrix software is not installed onto the default location.
ActiveMatrix installation location.
 
Configuration Folder Location
Update following property when using a different configuration data folder location.
ActiveMatrix runtime state configuration location.
 
In addition to the changes listed in Additional TIBCO Host Instances, update the following properties to conform to target operating system path conventions:
ActiveMatrix installation location.
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.
 
Machine Name
Update the following properties with the correct machine name:
Machine on which ActiveMatrix Administrator runs.
ActiveMatrix Administrator server URL.
 
Enterprise Name
Update the following property if the ActiveMatrix enterprise name has changed.
ActiveMatrix enterprise name
 
Installation Location
Update following property when ActiveMatrix software is installed in a different location.
ActiveMatrix installation location.
 
Configuration Folder Location
Update following property when using a different configuration data folder location.
ActiveMatrix runtime state configuration location.
 
Update the following properties in addition to the changes required for machine name to conform to target operating system path conventions.
ActiveMatrix installation location.
ActiveMatrix runtime state configuration location.

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