Sunday, August 15, 2010

About AppManage Utility- Script deployment

The scripting tools allow you to build an EAR file for an application configured in TIBCO Designer, then load the application into one or more TIBCO Administrator administration domains. Deployment options can be specified in a deployment configuration file that is created using the AppManage utility.
  • If your application is not complex and needs only machine bindings defined for each domain, you can use the AppManage utility to create the deployment configuration file from information in the EAR file, then edit the configuration file with the machine names where the applications will be deployed. In this scenario, the TIBCO Administrator GUI is not used.
  • If your application is complex and needs more than machine bindings defined, you can import an EAR file into the TIBCO Administrator GUI and specify deployment configuration options for the application. This method is preferred if your application includes complex mappings, such as fault tolerance, runtime variables, alerts and so on.
In this scenario, the TIBCO Administrator GUI is used to initially set the application’s deployment configuration options. After the options are set, the TIBCO Administrator GUI is no longer used. The AppManage utility updates the deployment configuration file from the application configured in the TIBCO Administrator GUI. The file is edited for each administration domain by changing machine bindings and so on, then deployed into each administration domain.

0 comments:

Popular Posts

  © Blogger templates The Professional Template by Ourblogtemplates.com 2008

Back to TOP