When we are working with TIBCO software, we only have one thing in mind: Zero coding. This is the best brand that explains what TIBCO Software is, but in some times or to do some task you have to go down all these GUI interfaces and face the scripting issue, and you must be able to handle that!
TIBCO has several command-line applications that allows us to perform some applications we can also do with all these TIBCO GUI. So, the first question is.. Why I want to learn that if I can do it with a GUI?
Ok, thats fair, I’m going to try to answer to this question. In my experiencie, I have been faced before to the mandatory rule that all the administration tasks must be doing through scripting. This rule has many valid reasons (batch procedures, automatic, easy to learn, easy to adapt to all the company enviroments and so on..). So, one more time, in some times you must have the command line and know all the posibilities TIBCO software gives to you.
We are going to start this serie of posts with one of the main applications that allows to perform tasks in TIBCO via scripting, and that is AppManage. AppManage is an application that allows to do several tasks in our BW developments, such as:
- 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 into an administration domain in one operation. The application is uploaded with its deployment options set, but is not deployed.
- 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 a domain, 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.
You can find the AppManage application inside your TIBCO Runtime Agent (a.k.a TRA) installation folder /<tibco_home>/tra/<version>/bin.
OK, that’s enoguh for a introduction of AppManager, so let’s start using it. In this post we are going to do a little task, but I promise we’ll be having a new post so we can take a deeper look of this great application.
We are trying to do the following: With have our app, we built it with TIBCO Designer and we are going to deploy it to the TIBCO Administration and start it.
So, our first task must be, extract the configuration file that we are going to use to do the upload into the TIBCO domain, so we are going to run the following command:
C:\tibco\tra\5.7\bin>AppManage.exe -export -ear “C:\Documents and Settings\Administrator\TIBCO_BW_AMQ.ear” -out config.xml
With this command, we generate our XML configuration file, and we are going to use to deploy it into our TIBCO domain, so we proceed with the next command:
C:\tibco\tra\5.7\bin>AppManage -deploy -ear “C:\Documents and Settings\Administrator\TIBCO_BW_AMQ.ear” -deployconfig config.xml -app TIBCO_BW_AMQ_APPMANAGE -domain tibco_domain -user tibco -pw tibco
In this case we are uploading to the ‘tibco_domain’ domain, and these domain credentails. The final task is to see in the Administrator the result of these tasks: