We have talked already about the mix of capabilities that we have available in the TIBCO BW 6.x series. Some of them are coming from the previous BusinessWorks version (the 5.x series) and others are coming from the last version of the AMX platform and its product, TIBCO AMX Service Grid. Today we are going to talk about one of these features that we are inheriting from the TIBCO AMX world and it is the Deployment Server tab.
When we are using our TIBCO BW 5.x processes if we want to deploy our software we have to do it from an external application. This applicacion could be an instance of TIBCO Administrator, a custom one using the CLI available from TIBCO BW and/or TIBCO Administrator, but there is no way to do a deployment from the TIBCO Designer tool. That’s right, no? Ok, so we are going to see how this is changing in this new version.
In this version, when we are using an complete Eclipse platform we are going to be in touch with many Views and Perspectives concepts from Eclipse. Ok, One of these default views is the Delpoyment Servers view:
In this view we are going to get a connection to the Server (or servers) that you want to do your deployments. This time you are not connection with the TEA (the equivalent of the TIBCO Administrator) but you are connection to a BW agent and you are going to be asked for the connection settings of this agent to establish a connection.
To create a connection, you only have to use the contextual menu in this view and select the option “Add Network”. You are going to be asked information using this form:
Ok, that’s it! You are going to have your connection establed. And what now? What are the thing that you could do with this tab?
First of all, you could take a look of the application uploaded and deployed in this network. You could check the state of the AppSpaces and AppNodes managed by the agent. You could take control of this elements, you could stop and start AppSpaces, AppNodes and Applications. And you could upload your Archives using the drag & drop technique from the Project Explorer view to the “Archives” section inside the tab:
And thats it! You cannot deploy the uploaded archive, only upload the archive to the server. I expect that you find this interesting because it’s saving you time and space from generating the EAR file and any efficiency in the deployment process is an advace!