Using TIBCO Configuration Tool Scripts and Property Files
You save and edit property files that TIBCO Configuration Tool (TCT) generates, and perform configuration with those files by using an ANT script.
When you run TCT, the tool creates property files and ANT build script files and stores them in the following location: CONFIG_HOME/tct/<subfolder>/<date-time>/scripts.
Each wizard creates its own sub folder under CONFIG_HOME/tct. Each sub folder contains the configuration scripts under the TIMESTAMP folder.
The following table lists the sub folder names created corresponding to each wizard.
Wizard | Sub Folder Name |
---|---|
Create TIBCO ActiveMatrix Administrator Server | admin |
Edit TIBCO ActiveMatrix Administrator Server | admin.editor |
Create Express Developer Environment | ede |
Create TIBCO Host Instance | tibcohost |
Configure Third-Party Driver | tpclshell |
Create TIBCO ActiveMatrix Policy Director Governance Administrator Server | pd |
Create TIBCO ActiveMatrix Policy Director Governance Proxy Host | pd.proxy |
Replicate TIBCO ActiveMatrix Administrator Server | admin.replicate |
Upgrade or Downgrade TIBCO ActiveMatrix | tct.upgrade.downgrade |
Update JRE used by TIBCO ActiveMatrix | tct.update.jre |
Each wizard creates build.xml, build.properties, and a templates folder under the scripts directory.
- build.xml: Ant build file used to configure based on the saved data.
- build.properties: Contains properties that are configured for the wizard.
- templates: Contains wizard-specific template files that are used to generate the actual build and data files for use during configuration. These files are different for each wizard.
- A tmp folder is created when the build file is used. This tmp file contains the actual files created from the templates. These files are generated every time when configured through TIBCO Configuration Tool or Ant. If you change files in the tmp folder, they are overwritten because the files are regenerated when you run the build file again.
- The build.properties can be edited based on your needs. For example, when scripts are migrated to a new machine, all the machine-specific details and other relevant properties can be updated. Depending on the wizard type, you can select the properties that you want to edit.
deploy-mcr
target fails. So it is not recommended to change the name of SystemEnvironment, SystemNode and SystemHost.