Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 Getting Started : Exporting an Application

Exporting an Application
You can use the appManage -export option to create and export an application’s deployment configuration file and archive (EAR) file. You can also use the appManage -batchExport option to create and export the deployment configuration files and EAR files for all applications in an administration domain.
Exporting an EAR File and Configuring for an Application
The next command exports the deployment configuration file and creates an EAR file for an application named myApp. The deployment configuration file and EAR file are created in the c:\test folder. The application is embedded in folder1/folder2/, which is relative to the Application Management root in the TIBCO Administrator GUI. See Specifying Application Names for more information.
AppManage -export -out c:\test\myApp.xml -genEar -ear c:\test\myApp.ear -app folder1/folder2/myApp -user user1 -pw user1 -domain test
Exporting EAR Files and Configuring for all Applications
You can export all applications in an administration domain using the appManage -batchExport option. For example, the next command exports a deployment configuration file and EAR file for each application found in the test domain.
AppManage -batchExport -user user1 -pw user1 -domain test -dir c:\temp\test
When performing batch jobs with AppManage in a database-based domain, make sure that your database server is configured with a sufficiently large connection pool so that you do not run out of JDBC connections. For more information, see Configuring Connection Pool Size for the Database Serverin TIBCO Administrator Server Configuration Guide.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved