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...