HTTP Load Balancer for a BusinessEvents Stack

In a private cloud, when you run TIBCO BusinessEvents, you do not know in advance the address of the machine or where it can run unless you set resource preferences in the rules.

The URL to invoke the BusinessEvents endpoint when used with an Administrator domain (a web service using SOAP over HTTP transport or an HTTP Receiver activity) is in the following form:

http://BrokerMachineName:BrokerPort/TIBCO_ADMIN_DOMAIN/BE-APPLICATION-PATH.NAME/ARCHIVE_ID/BE_HttpPortName

Where all the italicized parts are concatenated to form this HTTP URL.

• BrokerMachineName: machine name or IP Address where you installed TIBCO Silver® Fabric.
• BrokerPort: port of the Silver® Fabric Administrator GUI. The default value is 8080.
• TIBCO_ADMIN_DOMAIN: value of the Domain name you entered when you configured TIBCO Administrator component.
• BE-APPLICATION-PATH.NAME: deployment directory and name of the BusinessEvents application. The folder and application name is delimited by a period. For example if the BusinessEvents application is named AppName and was deployed in the TIBCO Admin directory say: aaa/bbb/ccc/ then the {BE-APPLICATION-PATH.NAME} would be: aaa.bbb.ccc.AppName. The {BE-APPLICATION-PATH.NAME} can be copied from the TIBCO Silver Fabric Administrator and then Dashboard, Scaled Archives page.
• ARCHIVE_ID: name of the archive as specified by the project archive name and the runtime directory in which it is published.
• BE_HttpPortName: global variable, endpoint URI, is defined at archive design-time as the HTTP port created to accept requests. Use TIBCO Studio to create the variable (the name is arbitrary) in the global variable group. It should be set as modifiable at the service level so that the value can be changed at run time.
  The base port value for HTTP request activity and SOAP/HTTP Web service activity can be changed at the component level as shown in preceding section.

  • If deployed from TIBCO Administrator UI or AppManage, the default value is set in designer.
  • If deployed from BE Enabler Component (REST, .ear file uploaded), the HTTP port is calculated to avoid port conflict.

For example:

http://10.107.172.95:8080/MyDomain/HTTPChannel/HTTPChannel.bar/httpport1/Channels/HTTP/PostEmpl

If your BusinessEvents stack invokes other BusinessEvents components, you can set the HTTP load balancer value as a global variable.