Saturday, 1 October 2016

WebLogic 12c 12.1.3 JMS Distributed Queues and Topics Configuration


Pre-requisite



Distributed JMS Queues and Topics Creation

  • Create Server: JMSManagedServer-1 
    • Select from left tree "base_domain-> Enviornment -> Servers" and click "New"
    • Provide Server name as "JMSManagedServer-1", Listen address as "<HOST-NAME-1ST-NODE", Port as "8001", select "No, this is a stand-alone server.", and Click "Finish"
    • Navigate to the JMSManagedServer-1 management page by clicking the JMSManagedServer-1 name entry in the Summary of Servers table.
    • In the general tab, select "<HOST-NAME-1ST-NODE>" in the Machine drop-down box, disable "SSL Listen Port Enabled" and Click Save.
    • In the Server Start tab, ether the following information and click save
    • Java Home as "/usr/java/jdk1.8.0_102/"
    • Java Vendor as "Oracle "
    • Arguments as 
    • -Djava.library.path=/app/Oracle/Middleware/Oracle_Home/wlserver/server/native/linux/x86_64/
  • Create Server: JMSManagedServer-2
    • Select from left tree "base_domain-> Enviornment -> Servers" and click "New"
    • Provide Server name as "JMSManagedServer-2", Listen address as "<HOST-NAME-1ST-NODE", Port as "8001", select "No, this is a stand-alone server.", and Click "Finish"
    • Navigate to the JMSManagedServer-2 management page by clicking the JMSManagedServer-2 name entry in the Summary of Servers table.
    • In the general tab, select "<HOST-NAME-2ND-NODE>" in the Machine drop-down box, disable "SSL Listen Port Enabled" and Click Save.
    • In the Server Start tab, ether the following information and click save
    • Java Home as "/usr/java/jdk1.8.0_102/"
    • Java Vendor as "Oracle "
    • Arguments as 
    • -Djava.library.path=/app/Oracle/Middleware/Oracle_Home/wlserver/server/native/linux/x86_64/
  • Create JMS Clusters 
    • Select from left tree "base_domain-> Enviornment -> Clusters" and click "New"
    • Provide name as "JMSCluster" and click "Finish"
    • Navigate to the JMSCluster management page by clicking theJMSCluster name entry in the Summary of Clusters table
    • In the "Servers" tab, add Servers "JMSManagedServer-1" and "JMSManagedServer-2" into the cluster
  • Create the JMS Servers 
    • Login to WebLogic Admin Console
    • Open web browser and hit the URL "http://<HOST-NAME>:7001/console/login/LoginForm.jsp" and enter credentials as "weblogic/Weblogic123"
    • On the left menu/navigation area, select the appropriate server domain and click to expand the Services - Messaging – JMS Servers node.
    • Click the Lock & Edit button, located near the top of the left menu.
    • On the following page, click the New button.
    • This will take you to a page where you can select a name for the JMS server. In the text box, name the server JMSServer-1.
    • Click Next.
    • Under the Select targets heading, use the drop-down box to select the name of the server where you wish to deploy the JMS server. ManagedJMSServer-1 should be the target for JMSServer-1. Click Finish.
    • To commit the change and create the JMS server, you must then click the Activate Changes button. This should create a new JMS server.
    • Complete steps above to create JMSServer-2, which should target ManagedJMSServer-2.
  • Create the JMS Module 
    • On the left menu/navigation area, select the appropriate server domain and click to expand the Services – Messaging – JMS Modules node.
    • Click the Lock & Edit button, located near the top of the left menu.
    • On the following page, click the New button.
    • This will take you to a page where you can select a name for the JMS module. In the Name text box, give the module an appropriate name.
    • Click Next.
    • Under the Targets heading, select ManagedJMSServer-1 and ManagedJMSServer-2. Click Next.
    • Click Finish.
    • Select SystemModule-1 from the JMS Modules table and select the Subdeployments tab and click the New button
    • Enter Default for the Subdeployment Name. Click Next.
    • On the Targets page, select JMSServer-1 and JMSServer-2. Click Finish
  • Create Queues and Topics
    • On the Create a New JMS System Module Resource page, Queue or Topic resource as appropriate and click Next.
    • Accept the default “round-robin” handling of the distributed JMS resources. You will enter the JMS Destination Properties on the following page. Give the distributed queue or topic an appropriate Name and JNDI Name. Following is an example: 
    • ticketRequest, ticketRequest, DistributedQueue
    • ticketResponse, ticketResponse, DistributedTopic
    • Click Next.
    • Accept the default targeting suggested by the admin console and click Finish.
    • Click the green “Activate Changes” button to ensure that the JMS resource definition is accepted and deployed by the Web Logic Server.
    • Test
    • You can verify that the JMS resources were successfully deployed by trying to connect to them with a JMS client such as Hermes JMS.


Thank You!