HTTP Port Management (optional)

The HTTP port management is done for the following BusinessEvents process starter:

  • SOAP/HTTP Event Source
  • SOAP/HTTP Service
  • HTTP Receiver Activity

To avoid port conflicts on the TIBCO Silver Fabric engines where TIBCO BusinessEvents™ is running, TIBCO Silver Fabric Enabler for TIBCO BusinessEvents provides a field named: "HTTP Base value for the HTTP request Activity and SOAP/HTTP Web Service Activity" to set the HTTP base value.

Warning: This defines a reserved range of ports that should not be used elsewhere.

If the application that is to be scaled includes an HTTP Port Variable, you must set the HTTP Port Variable to be settable at the service level using TIBCO BusinessEvents® Studio. To make the HTTP Port Variable "service settable" select the Service Settable check box in the Global Variable Editor.

Refer to the section on "Working with Global Variables" in the TIBCO BusinessEvents Developers Guide for more information.

Edit the base values of the "HTTP Base Value..." and "HTTP Port Increase Value..." variables on the HTTP Port Management page, as shown in the HTTP Port Management figure.

HTTP Port Management

The HTTP base port value is used to calculate derived port values for Web Services using SOAP over HTTP transport and other HTTP activities as required by your BusinessEvents project.

HTTP Port = "HTTP Base Value..." + "HTTP Port Increase Value..."* (HttpActivityNumber(1,2,3,or more)-1) + EngineInstanceValue

For example, you have a BusinessEvents project configured using two HTTP activities. The HTTP activities are running on the engine instance whose number is 2. The "HTTP Base Value..." is the default value: 8200. The "HTTP Port IncreaseValue..." is the default value: 50.

The first port is set to 8202 which was derived from:   8200 + 50 *(1-1) + 2

The second port is set to 8252, derived from:   8200 + 50 *(2-1) + 2

Note: You should not put different base values on different BusinessEvents components running on the same Silver® Fabric private cloud. If the values are different, you might encounter port conflicts.

If your project uses more than 50 HTTP ports, the "HTTP Port Increase Value..." variable must be greater than the number of HTTP ports.

Tip: If you choose to deploy TIBCO BusinessEvents as a standalone component on Silver Fabric engines, ensure that you have set ports be sure to avoid conflicts. In standalone mode, global variables such as those for ports (that is port1=1234 and port2=5678) can be set in a file ending in *.cfg suffix in the uploaded compressed archive file.

For more information, refer to the TIBCO BusinessEvents Administration Guide - "Building and Deploying EAR Files at the Command Line" : Starting a TIBCO BusinessEvents Engine at the Command Line.