Copyright © TIBCO Software Inc. All Rights Reserved

Redeploying an Application

You can use the scripting utilities to redeploy an already deployed application. The AppManage utility does not include a redeploy command; the -deploy command is used to redeploy an application. The options to use with the -deploy command vary depending on where changes were made. The -force option provided for AppManage is equivalent to the Force redeployment of all services in the TIBCO Administrator GUI. This section shows these options.

Changes Made to EAR file Only

If you have only changed the application’s configuration in TIBCO Designer, you must upload the changed EAR file into the affected administration domains. For example, you might modify a TIBCO Designer project by:

•	changing an existing adapter service or form flow service

•	changing an existing process within a process service by adding or deleting new activities or changing existing activities

•	adding, deleting or changing existing sub-processes

•	adding, deleting or changing shared resources

In scenarios where just the application’s project has changed, build the new EAR file using the buildear utility and use AppManage -deploy with the -ear option to redeploy the application.

For example, the following command lines build an EAR file and redeploy the filenotify application with the changed filenotify.ear archive file.

buildear -s -ear /filenotify.archive

         -o c:\ears\deployment\filenotify.ear

         -p c:\tibco\projects\filenotify

AppManage -deploy -ear c:\ears\deployment\filenotify.ear

          -app filenotify -domain tp003 -user admin -pw admim

Changes Made to Deployment File Only

If you have only changed the deployment file, you must upload the changed deployment file. For example, you might modify the deployment file by:

•	changing deployment level or service level variables

•	adding or removing machines to which services are bound

•	adding, deleting or changing service monitoring configurations

•	changing fault-tolerance settings for process services deployed in fault-tolerant mode

•	changing checkpoint storage from JDBC to File, or from File to JDBC ,or JDBC to JDBC, where the new JDBC resource exists in the original shared archive

•	changing process settings such as Active or Inactive State, MaxJobs, or Activation Limit

•	changing service instance configuration settings such as NT Service, Java parameters, or log files

•	changing deployment transport settings such as to Rendezvous, HTTP, HTTPS or related parameters

In scenarios where just the deployment configuration file has changed, use AppManage -deploy with the -deployconfig option to redeploy the application.

For example, the following command redeploys the filenotify application with the changed filenotify_tp003.xml file.

AppManage -deploy

          -deployconfig c:\ears\deployment\filenotify_tp003.xml           -app filenotify -domain tp003 -user admin -pw admin

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

            -o c:\ears\deployment\filenotify.ear

            -p c:\tibco\projects\filenotify

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.

For example, when the following command is run, a log file is generated in the same folder where the new deployment configuration file is created. The log file lists all changes that were made to the deployment configuration file, as a result of changes to the EAR file.

   AppManage -export -ear c:\ears\deployment\filenotify.ear

             -deployconfig c:\ears\deployments\filenotify.xml

             -out c:\ears\deployments\filenotify-changed.xml

The new deployment configuration file may need to be further modified, for example, by replacing machine binding substitution variables with actual machine names for new services, modifying deployment or service level variable values, picking up the right checkpoint repository from the list of checkpoint repositories, and so.

3.	After you have made the changes to your deployment configuration file, you are ready to deploy the application. For example:

   AppManage -deploy -ear c:\ears\deployment\filenotify.ear

           -deployconfig c:\ears\deployment\filenotify-changed.xml

           -app filenotify -domain tp003 -user admin -pw admin

Copyright © TIBCO Software Inc. All Rights Reserved