Understanding Implementing Load Balancing Using Virtual Application Server Domains

You can configure one or more integration gateways for load balancing using virtual application server domains. This section provides an overview of implementing this process.

Synchronous Secondary Template Domains

To implement load balancing using virtual application server domains you must configure a synchronous secondary template domain in PSADMIN. When the application server boots, the secondary template registers application server information to all gateways defined for inbound processing. You can view the secondary templates that are registered to a gateway using the Inbound Gateways page in the Gateway component.

Note:

The terms secondary template domain and secondary template are used interchangeably in this section.

When the application server is booted, the secondary template domain appears in the Domain Status component in the Service Operations Monitor, where you perform additional configuration as well as manage dispatcher queues.

Load Balancing Application Server URLs

When you boot the secondary template domain, it appears in the Domain Status component in the Service Operations Monitor. Synchronous secondary templates are indicated in the system as Sync-Template.

You then use the Secondary Templates page to add the application server URL information (machine name: jolt port) in order for the gateway(s) to make a proper connection to that particular domain.

Gateway URLs and Inbound Gateway Processing

If you are using multiple gateways, you then use the Inbound Gateways page in the Gateways component to add gateway URLs for each physical gateway that you are using. The URL of the default local gateway is populated on the page by default.

You can also use the Inbound Gateways page to view current service URLs assigned to nodes.

Virtual Server Nodes

You can define a virtual server node so that in situations where an inbound request does not specify a “To” node, the system will send the request to a PeopleSoft node defined in the integration gateway properties file.

Secure Inbound Requests

The integration gateway properties file features a property, ig.SecureVirtualRequests, that enables you to require that all inbound requests be sent using SSL/TLS. When this property is set to True, the gateway accepts only those requests that are sent using SSL/TLS.