Application AppNodes using different ports in the same host

In the today post we are going to learn how to deploy a Web service in two AppNodes using different ports to receiving requests. When I named a “Web Service” I’m referring to a Process that expose an HTTP connection to receive requests.

You may think this is not a problem if I want to deploy an application using the TIBCO BW 6.x series I upload the Application Archive to the TEA and I start the Application deployment in the different nodes. Ok, first of all you should know that the configuration values are the same, at first, for every AppNode you deploy. Another important thing is that if you create an HTTP Resource with the default configuration the port is not configured used a property (this is not occurring with the hostname value, for example), so you have to do the following tasks:

  • Configure your HTTP Resource inside your application to specify the port number using a Module Property.
  • Change the initial configuration at least in one AppNode.

Continue reading


Deployment Server tab in TIBCO BW 6.X

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.

Continue reading