Creating and deploying clusters in WebLogic Server

In WebLogic Server, you deploy the remote method invocation (RMI), create the clusters, configure Java™ Message Service (JMS), and deploy the EAR files.

  1. Deploying the remote method invocation registry file for WebLogic Server
    When you build the remote method invocation (RMI) registry file, the file must be deployed each physical server. Deployment includes creating an RMI registry service and, creating a batch file to start RMI. To run the process correctly, you must update the start sequence for all servers so that all product ervers start after the RMI server starts.
  2. Creating clusters in WebLogic Server
    You can create as many clusters as your deployment requires.
  3. Configuring the Java Message Service for WebLogic Server
    Java Message Service (JMS) is used as the messaging standard to create, send, receive, and read messages from queues. This process enables distributed communication with external systems in a loosely coupled, reliable, and asynchronous manner.
  4. Deploying EAR files for clusters in WebLogic Server
    When you deploy the EAR files in WebLogic Server, the changes that you made for the different clusters, such as the configuration of message-driven beans, are deployed.
Parent topic: Configuring clustered systems
Related concepts:
Application server documentation

Feedback