Using BTMdeploy
btmdeploy is used to extract the deployment files from the TMTM Application Service so that they can be transferred to the manual deployment directory configured when you installed the TMTM Configuration Agent. btmdeploy is located in the InstallDir on the services machine.
Use btmdeploy as soon as possible after deployments are activated and/or deactivated so that the TMTM Configuration Agent can act on the operation promptly.
To use BTMdeploy to deploy BTM configurations
Use the BTMdeploy command with the parameters described in the following table.
Parameter
Use to...
--as-host hostname
TMTM Application Service host. Default is localhost.
--as-port portnumber
TMTM Application Service port number. The default port number is used if this option is not used.
--deployhost pattern
Deployment host regular expression pattern. All hosts, if not provided.
--dir dirName
Directory where the deployment files are to be extracted. Defaults to the current directory.
--model pattern
Model name regular expression pattern. Use in conjunction with --profile.
--profile pattern
Profile Name Pattern. Defaults to all profiles.
--statusDisplay the current deployment status.
-? or -hList this command help summary.
-bRun in batch mode. Parameters are not confirmed.
-p password
Password.
-sSpecify password via stdin. This is mutually exclusive with -p.
The BTM Config Service must be running in manual deployment mode in order to process the deployment jar files.
Extract the deployment files for all profiles and models on the host myDeployHost.
btmdeploy --dir deploy --deployHost myDeployHost SA
where:
deploy is the name of the local directory.
myDeployHost is the name of the host.
SA is a TMTM user ID.
The resulting local extraction directory has the following structure:
deploy
---myDeployHost
JMSProfile_WasModel_1.jar
Profile0_Model0_1.jar
where:
JMSProfile_WasModel_1.jar and Profile0_Model0_1.jar are model and profile jar files. These names are samples only.
After btmdeploy has run, the jar files must be distributed to the host machines running the extensions. The distributed files must be made available to the TMTM Agent/BTMConfig Service.