First three modes can be load balanced by fronting a simple web server to virtualize the IP address/host name to one and route the requests to the managed servers in a round robin or weight based or any other supported algorithm. Oracle HTTP server is an example for such web server.

JMS uses a t3 protocol and it requires load balancer which can intercept the request at level 7 (TCP level) and route the request. Example is Oracle Traffic Director (OTD). Such load balancers can be used for first three type of requests as well.

For http/s protocols, there is no production level internal load balancing support from weblogic. This has to be handled using an external load balancer.

Weblogic supports JMS load balancing internally. For this, the client have to know the host name/ip address and port of all the managed servers in a cluster. In all the places where the Initial Context Provider URL is configured in OBPM application, specify the URL as:

t3://[HOST NAME 1]:[PORT 1],[HOST NAME 2]:[PORT 2]

HOST NAME – This is a DNS name of individual manager servers

PORT – Port number of individual managed servers.