Continuation to the earlier post : AppManage Commands - To deploy applications in TIBCO Administration domain
We can use AppManage utility to deploy the applications in batch mode. In real time, there might be a scenarios like to migrate/move all applications from one domain to other domain. So, we can use AppManage utility in batch mode to deploy, undeploy, start, stop and delete the applications.
To demonstrate, We have used the domain created in earlier post : TIBCO Administration Domain Creation using Domain Utility in GUI Mode and we consider below two applications i.e."TechsNibApp","TechsNibApp2" to perform batch mode deployments in an administration domain using AppManage utility.
As show above, we can build the ear either by using TIBCO Designer in GUI mode (or) we can use buildear utility in command line mode. |
To use the AppManage utility in batch mode you must first create an AppManage.batch file. This file lists the applications and their corresponding EAR and XML files. While you can create the file manually, the easiest way is to generate the file using -batchExport option. In addition to creating the AppManage.batch file, the option creates an EAR and XML file for each application in the given domain as below :
The AppManage utility and AppManage.tra file are installed in the <<TIBCO_HOME>>\tra\version\bin directory. Navigate to this location through command prompt and run below command by passing required parameters mentioned as below :
AppManage -batchExport -domain TechsNib_Domain -user TechsNib -pw TechsNib -dir F:\TIBCO\BW\Batch\
-batchExport --> To export all applications from specified TIBCO Domain AppManage.batch file : List of exported files: |
--> Now you can use below AppManage utility command to deploy both the applications specified in AppManage.batch file that is located in the directory specified for the '-dir' option.
AppManage -batchDeploy -domain TechsNib_Domain -user TechsNib -pw TechsNib -dir F:\TIBCO\BW\Batch\
-batchDeploy --> To batch deploy applications to the specified TIBCO Domain |
--> The following command is used to start both the applications specified in AppManage.batch file that is located in the directory specified for the '-dir' option.
AppManage -batchstart -domain TechsNib_Domain -user TechsNib -pw TechsNib -dir F:\TIBCO\BW\Batch\
-batchstart --> To start applications in batch mode |
--> The following command is used to stop both the applications specified in the AppManage.batch file that is located in the directory specified for the '-dir' option.
AppManage -batchstop -domain TechsNib_Domain -user TechsNib -pw TechsNib -dir F:\TIBCO\BW\Batch\
-batchstop --> To stop applications in batch mode |
--> AppManage utility is used to kill the applications in batch mode.The following command forces an immediate shutdown of each service instance or process engine specified in the AppManage.batch file that is located in the directory specified for the '-dir' option.
AppManage -batchkill -domain TechsNib_Domain -user TechsNib -pw TechsNib -dir F:\TIBCO\BW\Batch\
-batchkill --> To kill applications in batch mode |
--> AppManage utility is used to undeploy the applications in batch mode. The following command undeploy both the applications specified in the AppManage.batch file that is located in the directory specified for the '-dir' option.
AppManage -batchUnDeploy -domain TechsNib_Domain -user TechsNib -pw TechsNib -dir F:\TIBCO\BW\Batch\
-batchUnDeploy --> To batch undeploy applications in the specified TIBCO Domain |
--> The following command is used to delete all applications specified in the AppManage.batch file that is located in the directory specified for the '-dir' option. You can use '-force' option to undeploy and delete the application in one operation.
AppManage -batchDelete -domain TechsNib_Domain -user TechsNib -pw TechsNib -dir F:\TIBCO\BW\Batch\ -force
-batchDelete --> To delete applications in batch mode |
Please note we can check the logs of AppManage command executed in TIBCO administrative domain in <<TIBCO_HOME>>\tra\domain\<<Domain_Name>>\logs\ApplicationManagement.log file.
No comments:
Post a Comment