Redeploying an Application: Changes Made to EAR and Deployment Files

If you change both the TIBCO Designer project and the deployment configuration file, you must upload both when redeploying. For example, you may want to make the following changes:

• add new services or delete existing services (adapter, process or form flow archives)
• add or remove deployment level or service level variables (including Adapter SDK properties)
• change checkpoint storage from File to JDBC or JDBC to JDBC, where the new JDBC Shared Resource was not part of the Shared Archive in the original EAR file

If you have changed both the TIBCO Designer project and the deployment configuration file, complete the following steps to redeploy the changed application:

1. Build an EAR file using the buildear utility. For example:buildear -s -ear /filenotify.archive
2. Generate a new deployment configuration file using the EAR file created in the previous step, the deployment configuration file used when previously deploying the application and specify a new deployment configuration file.
3. After you have made the changes to your deployment configuration file, you are ready to deploy the application.

Read more...

Starting & Stopping Applications in Batch Mode

The following command starts all applications specified in the AppManage.batch file that is located in the directory specified for the -dir option. The directory must have been created earlier using the -batchExport option.

AppManage -batchstart -domain mydomain -user admin -pw admin -dir c:\adminbatch\mybatch\

The following command stops all applications specified in the AppManage.batch file that is located in the directory specified for the -dir option.

AppManage -batchstop -domain mydomain -user admin -pw admin -dir c:\adminbatch\mybatch\

Read more...

AppManage in Batch Mode

To use the AppManage utility in batch mode you must first create an AppManage.batch file. The file lists the applications and their corresponding EAR and XML files. You can create the file manually, but the files listed in the AppManage.batch file must be specified using relative file paths. The base of those relative paths is the directory specified by the –dir option that is given on the AppManage command line.

The easiest way is to generate the file using the -batchExport option. In addition to creating the AppManage.batch file, the option creates an enterprise archive file and XML file for each application in the given domain.

After creating the AppManage.batch file, you can use the AppManage utility to do the following operations in batch mode:

• Deploy applications
• Undeploy applications
• Start or stop applications
• Delete applications
• Kill applications
• Change the transport

Read more...

How to start the AppManage and buildear utilities

To start the AppManage utility, change directory to TIBCO_TRA_HOME\bin and type AppManage -action where options include -export, -upload, -config, -deploy, and -undeploy etc.

• The AppManage utility must be run on a machine that is part of the administration domain you are updating.

Starting Buildear:

To start the buildear utility, change directory to TIBCO_TRA_HOME\bin and type

buildear -options.

You should verify your project by loading it into TIBCO Designer before you use the project with the buildear utility. If the project doesn't load correctly in TIBCO Designer, the buildear utility doesn't support it.

Read more...

AppManage utility Log Files

The AppManage utility writes information to a log file. The log file location depends on whether you are accessing an administration domain or not.

• If you are not accessing an administration domain, the log is written to the TIBCO_TRA_HOME\logs\ApplicationManagement.log file.
• If you are accessing an administration domain, the log is written to the TIBCO_TRA_DOMAIN_HOME\domain-name\logs\ApplicationManagement.log file.

A comparison log file is generated if you export from an EAR file without specifying an administration domain. This information can help you decide whether you need to change the deployment configuration file after an EAR filechanges.

For example, using the following command line, the AppManage utility compare sthe oldconfiguration.xml file with the given EAR file. If any service, global variables, or both have been added, removed, or updated, a log file is created in the same directory where the oldconfiguration.xml file resides, using the file name, oldconfiguration.xml.log.

AppManage -export -ear c:\ears\timer_wait.ear -deployConfig oldconfiguration.xml -outnewconfiguration.xml

Read more...

Uses of AppManage utility in Scripting Deployment

• The AppManage utility creates an XML based deployment configuration file in which deployment options can be defined.
• The utility also uploads the deployment file and EAR file into a TIBCO Administrator administration domain.
• Create a deployment configuration file based on information in an EAR file, or from an application already configured in the TIBCO Administrator GUI.
• Upload an EAR file to an administration domain without specifying deployment configuration options. After the file is imported, it is ready to be configured with deployment options and deployed using the TIBCO Administrator GUI.
• Upload an EAR file and a deployment configuration file and deploy the application in one operation. Using this method, you can quickly deploy your applications in multiple domains.
• Export all application archives and deployment configuration files within adomain, so they can be batch deleted, started, stopped, undeployed, or deployed in another domain. For TIBCO Rendezvous administration domains, you can change the transport set for application to administration server communication, from rv (Rendezvous) to local, or the reverse.
• Undeploy a deployed application.
• Delete an application from an administration domain.
• Start a service instance of an application.
• Stop a successfully deployed service instance of an application.

Read more...

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.

Read more...