Network
Ensure that all the ports required by components of TIBCO Order Management - Long Running are configured with the same port number. This software supports distributing components across network. All the components excluding Order Management Server UI, communicated with other component using TIBCO Enterprise Message Service. Order Management Server UI communicates with Order Management Server using HTTP. If layer 7 load balancer is used within a site, Order Management Server UI must always be configured to point to the local site load balancer, even if geo-targeted global load balancer is used to dynamically update the DNS entry and activate the standby site. You must use hostnames instead of IP address when specifying location of services. The IP address scheme at the recovery site could be different from primary site. If IP address is specified, there is a possibility that it might refer to node that is not available.
The following table lists the property name and host and port number used by Order Management Server UI and Order Management Server components of TIBCO Order Management - Long Running for HTTP communication:
| Property Name | Description |
|---|---|
| com.tibco.af.omsServer.proxyHost | Host address of the Order Management Server |
| com.tibco.af.omsServer.proxyPort | Port number of the Order Management Server |
If TIBCO Fulfillment Provisioning is integrated with TIBCO Order Management - Long Running, the following additional properties must point to local site load balancer: