![]() |
![]() |
Creating and Deploying to WebLogic Server Clusters
Tutorial 4: Deploying the MedRec Package to a Cluster
This tutorial describes how to deploy the MedRec applications to a cluster for production. The tutorial includes the following sections:
|
Prerequisites
Before starting this tutorial:
|
Procedure
Now that your running cluster has the JDBC, JMS, and Mail resources required by the MedRec applications, you can deploy MedRec to the cluster.
Step 1: Deploy the MedRec Application
Step 2: Deploy the Physician Application
Step 3: Test the Deployment
To test whether the deployment was successful, open a browser window and enter the URL:
http://127.0.0.1:8001/start.jsp
You should receive the main login page where you can use the application from different roles.
Try accessing the same application using other server's in the cluster by entering the URLs:
http://127.0.0.1:8011/start.jsp
http://127.0.0.1:8021/start.jsp
Each URL should provide the main login page.
|
Best Practices
Deploy applications to all members of the cluster (homogeneous deployment) to avoid JNDI conflicts. See Communications in a Cluster in Using WebLogic Server Clusters.
|
The Big Picture
In this tutorial, you specify the different port numbers in separate URL requests to access different members of the cluster. A more sophisticated development environment might use a single DNS name that maps to all addresses in the cluster. DNS cycles through the configured addresses in a round-robin fashion to distribute multiple requests to different IP addresses.
Production environments generally use load balancing hardware with sophisticated load algorithms and load monitoring to ensure that large volumes of requests are distributed network requests to servers evenly (or according to each machine's processing capacity).
|
Related Reading
![]() |
![]() |
![]() |