Deploying of (BusinessWorks) ear files in Administrator is often easier using a script calling AppManage (in the TRA distribution) than doing it manually in the Administrator web frontend. With scripted deployments the ear file and the deployment xml file containing the process and global variable settings is usually extracted from a version control system. So a working scripted deployment guarantees that these settings will not be lost.
The following ant target deploys an ear file using AppManage:
Note also several ant properties. These can be supplied from the command line or from Jenkins/Hudson:
- Server credentials: tibco.admin.host, ssh.user and ssh.password.
- Tibco Administrator credentials: tibco.admin.domain, tibco.admin.user
- Appmanage location and Administrator domain: ${serverTibcoTraDir}/5.6/bin, ${tibco.admin.domain}
- Ear file and global variables: ${tibco.app.earfile}.ear, ${tibco.app.config}.xml.
- Name and directory of the deployment in Administrator: tibco.admin.dir and tibco.app.name.
- Deployment description, overwrites the description in the global variables xml: appmanage.deployment.description
- Other parameters for AppManage, boolean values: appmanage.nostart, appmanage.nostop, appmanage.forceDeployment.
For training on TIBCO Administrator mail us at virtualnuggets@gmail.com