WebLogic 12c JMS Bridge to connect to WildFly 8.2 HornetQ Broker.

Hi,

As part of this article we will see how to configure a JMS Message bridge on WebLogic 12c side so that any message sent to the JMS Queue present on WebLogic will be automatically transfered to WildFly 8.2 Instance. The WebLogic Messaging Bridge is a forwarding mechanism that provides interoperability between WebLogic JMS implementations, and between JMS and other messaging products. We are going to use the Messaging Bridge to integrate WildFly 8.2 offered HornetQ messaging broker communication. A messaging bridge instance forwards messages between a pair of bridge source and target destinations. These destinations are mapped to a pair of bridge source and target destinations. The messaging bridge reads messages from the source bridge destination and forwards those messages to the target bridge destination.

In order to know how to create a WebLogic Message bridge between WebLogic and JBoss 5 please refer to : http://middlewaremagic.com/weblogic/?p=6066

As part of this article we will learn:

1). How to create a WebLogic Message Bridge using WLST.
2). How to create a JMS Queue on WildFly 8.2 side.
NOTE: These steps will remain almost same for JBoss AS7 or JBoss EAP6, the only change will be in the Connection URL of WildFly or JBossAS. In WildFly we use “http-remoting://localhost:8080” where as in JBossAS7/EAP6 we use “remote://localhost:4447”).
3). Then we will send some messages to WebLogic JMS Queues and will receive them from WildFly 8.2 JMS Queues.

Creating A Simple JMS Queue on WildFLy 8.2 side

Step-1). Start the WildFly 8.2 (or JBoss EAP6/JBossAS7) full profile (which has messaging) as following:

   $ cd /PATH/TO/wildfly-8.2.1.Final/bin
   $ ./standalone.sh -c standalone-full.xml

I am running Weblogic 12c and WildFLy on the same host hence i am running both on “localhost” users can change it based on their need.

Step-2). Create a simple JMS user on WildFly 8.2 side and this user must belong to “guest” role. Please see the “messaging subsystem” configuration of “standalone-full.xml” to know more about “guest” role.
username: jmsuser
password: jmsuser@123
user role: guest
Realm: ApplicationRealm

   $ cd /PATH/TO/wildfly-8.2.1.Final/bin
   $ ./add-user.sh 

What type of user do you wish to add? 
 a) Management User (mgmt-users.properties) 
 b) Application User (application-users.properties)
(a): b

Enter the details of the new user to add.
Using realm 'ApplicationRealm' as discovered from the existing property files.
Username : jmsuser
Password recommendations are listed below. To modify these restrictions edit the add-user.properties configuration file.
 - The password should not be one of the following restricted values {root, admin, administrator}
 - The password should contain at least 8 characters, 1 alphabetic character(s), 1 digit(s), 1 non-alphanumeric symbol(s)
 - The password should be different from the username
Password :  jmsuser@123
Re-enter Password :  jmsuser@123
What groups do you want this user to belong to? (Please enter a comma separated list, or leave blank for none)[  ]: guest
About to add user 'jmsuser' for realm 'ApplicationRealm'
Is this correct yes/no? yes
Added user 'jmsuser' to file '/PATH/TO/wildfly-8.2.1.Final/standalone/configuration/application-users.properties'
Added user 'jmsuser' to file '/PATH/TO/wildfly-8.2.1.Final/domain/configuration/application-users.properties'
Added user 'jmsuser' with groups guest to file '/PATH/TO/wildfly-8.2.1.Final/standalone/configuration/application-roles.properties'
Added user 'jmsuser' with groups guest to file '/PATH/TO/wildfly-8.2.1.Final/domain/configuration/application-roles.properties'
Is this new user going to be used for one AS process to connect to another AS process? 
e.g. for a slave host controller connecting to the master or for a Remoting connection for server to server EJB calls.
yes/no? yes
To represent the user add the following to the server-identities definition <secret value="am1zdXNlckAxMjM=" />

Step-3). Creating a simple JMS Queue using the WildFly CLI command line utility. NOTE the JNDI name should contain “java:/jboss/exported” prefix or else the JMS queue will can not be looked up remotely.

   $ cd /PATH/TO/wildfly-8.2.1.Final/bin
   $ ./jboss-cli.sh -c
   
   [standalone@localhost:9990 /] /subsystem=messaging/hornetq-server=default/jms-queue=TestQ/:add(entries=["java:/jboss/exported/jms/queue/TestQ"],durable=false)
     {"outcome" => "success"}
     
   [standalone@localhost:9990 /] :reload
     {
       "outcome" => "success",
       "result" => undefined
     }

Starting WebLogic 12c and configuring it

First of all Copy the WildFly client jar “/PATH/TO/wildfly-8.2.1.Final/bin/client/jboss-client.jar” and place it inside the “$DOMAIN_HOME/lib” directory of WebLogic 12c.

Step-4). Start WebLogic 12c normally.

   $ cp -f /PATH/TO/wildfly-8.2.1.Final/bin/client/jboss-client.jar     /PATH/TO/wls12130/user_projects/domains/mydomain/lib

   $ cd /PATH/TO/wls12130/user_projects/domains/mydomain/bin
   $ ./startWebLogic.sh

Writing WLST script to configure JMS Bridge

Step-5). Now create a directory like “WebLogic_JMS_Bridge” where we will place our project artifacts.

   $ mkdir  WebLogic_JMS_Bridge
   $ cd WebLogic_JMS_Bridge

Step-6). Inside the “WebLogic_JMS_Bridge” directory write the following kind of file “domain.properties” which will contain all the configuration details.


############ WebLogic 12c JMS Queue and Connection Factory related Configuration #########

# 1 - Connecting details
server.url = t3://localhost:7001
username = weblogic
password = weblogic1
 
# 2 - JMSServer details
jms.server.name = My_JMSServer
store.name = MyJDBCStore
tragated.jms.server.name = myserver
 
# 3 - SystemModule Details
system.module.name = My_SystemModule
tragated.system.module.name = myserver
 
# 4 - ConnectionFactory Details
connection.factory.name = My_ConnectionFactory
connection.factory.jndi.name = My_CF
 
# 5 - Unit Of Order Details
unit.of.order.value = 1
 
# 6 - SubDeployment & Queue Details
queue.sub.deployment.name = Sub_My_Queue
queue.name = My_Queue
queue.jndi.name = My_Q


############ JMS Bridge related Configuration #########
weblogic.destination.bridge = WLS_Source_Bridge
weblogic.adapter.jndi.name = eis.jms.WLSConnectionFactoryJNDINoTX


wildfly.destination.bridge = WildFly_Destination_Bridge
wildfly.server.url = http-remoting://localhost:8080

# When using JBoss EAP6 or JBossAS7 then change the URL to following:
# wildfly.server.url =remote://localhost:4447

wildfly.initial.context.factory = org.jboss.naming.remote.client.InitialContextFactory
wildfly.remote.connection.factory.jndi.name = jms/RemoteConnectionFactory
wildfly.jms.destination.jndi.name = jms/queue/TestQ

wildfly.jms.username = jmsuser
wildfly.jms.password = jmsuser@123

Step-7). Now we will write simple WLST Script to configure the JMS Bridge , Create JMS Queue, JMS ConnectionFactory on WebLogic side. So write a file like “weblogicJMS_Setup.py” inside the same directory “WebLogic_JMS_Bridge” as following:

#############################################################################
#
# @author Copyright (c) 2010 - 2011 by Middleware Magic, All Rights Reserved.
#
#############################################################################
 
from java.io import FileInputStream
import java.lang
import os
import string
 
propInputStream = FileInputStream("domain.properties")
configProps = Properties()
configProps.load(propInputStream)
 
# 1 - Connecting details
serverUrl = configProps.get("server.url")
Username = configProps.get("username")
Password = configProps.get("password")
 
# 2 - JMSServer details
jmsServerName = configProps.get("jms.server.name")
storeName = configProps.get("store.name")
tragatedJMSServerName = configProps.get("tragated.jms.server.name")
 
# 3 - SystemModule Details
systemModuleName = configProps.get("system.module.name")
tragatedSystemModuleName = configProps.get("tragated.system.module.name")
 
# 4 - ConnectionFactory Details
connectionFactoryName = configProps.get("connection.factory.name")
ConnectionFactoryJNDIName = configProps.get("connection.factory.jndi.name")
 
# 5 - Unit Of Order Details
unitOfOrderValue = configProps.get("unit.of.order.value")
 
# 6 - SubDeployment & Queue Details
queueSubDeploymentName = configProps.get("queue.sub.deployment.name")
queueName = configProps.get("queue.name")
queueJNDIName = configProps.get("queue.jndi.name")
 
#7 - Weblogic Bridge Details:
weblogicDestinationBridge = configProps.get("weblogic.destination.bridge")
weblogicAdapterJNDINoTX = configProps.get("weblogic.adapter.jndi.name")

#8 - Widlfly bridge details:
wildflyDestinationBridge = configProps.get("wildfly.destination.bridge")
wildflyServerUrl = configProps.get("wildfly.server.url")
wildflyJMSUsername = configProps.get("wildfly.jms.username")
wildflyJMSUserPassword = configProps.get("wildfly.jms.password")
wildflyInitialContextFactory = configProps.get("wildfly.initial.context.factory")
wildflyJMSConnectionFactory = configProps.get("wildfly.remote.connection.factory.jndi.name")
wildflyJMSQueueJndi = configProps.get("wildfly.jms.destination.jndi.name")




redirect('wlst.log','false')
 
# 1 - Connecting to the Destination 
connect(Username,Password,serverUrl)
 
edit()
 
# 2 - JMSServer details
print "================== JMSSever ==================="
startEdit()
cmo.createJMSServer(jmsServerName)
print "Created a JMSServer !!"
cd('/Deployments/'+jmsServerName)
cmo.setPersistentStore(getMBean('/FileStores/'+storeName))
print "PersistentStore has been set for the JMSServer !!"
set('Targets',jarray.array([ObjectName('com.bea:Name='+tragatedJMSServerName+',Type=Server')], ObjectName))
print "Targeted the JMSServer !!"
activate()
print ""
 
# 3 - SystemModule Details
print "================== SystemModule ==================="
startEdit()
cd('/')
cmo.createJMSSystemResource(systemModuleName)
print "Created a SystemModule !!"
cd('/SystemResources/'+systemModuleName)
set('Targets',jarray.array([ObjectName('com.bea:Name='+tragatedSystemModuleName+',Type=Server')], ObjectName))
print "Targeted the SystemModule !!"
activate()
print ""
 
# 4 - ConnectionFactory Details
print "================== ConnectionFactory ==================="
startEdit()
cd('/JMSSystemResources/'+systemModuleName+'/JMSResource/'+systemModuleName)
cmo.createConnectionFactory(connectionFactoryName)
cd('/JMSSystemResources/'+systemModuleName+'/JMSResource/'+systemModuleName+'/ConnectionFactories/'+connectionFactoryName)
cmo.setJNDIName(ConnectionFactoryJNDIName)
print "Created a ConnectionFactory !!"
cd('/JMSSystemResources/'+systemModuleName+'/JMSResource/'+systemModuleName+'/ConnectionFactories/'+connectionFactoryName+'/SecurityParams/'+connectionFactoryName)
cmo.setAttachJMSXUserId(false)
cd('/JMSSystemResources/'+systemModuleName+'/JMSResource/'+systemModuleName+'/ConnectionFactories/'+connectionFactoryName)
cmo.setDefaultTargetingEnabled(true)
print "Targeted the ConnectionFactory !!"
activate()
print ""
 
# 5 - Unit Of Order Details
print "================== Unit Of Order ==================="
startEdit()
cd('/JMSSystemResources/'+systemModuleName+'/JMSResource/'+systemModuleName+'/ConnectionFactories/'+connectionFactoryName+'/DefaultDeliveryParams/'+connectionFactoryName)
cmo.setDefaultUnitOfOrder(unitOfOrderValue)
print "Changed Unit Of Order !!"
activate()
print ""
 
# 6 - SubDeployment & Queue Details
print "================== SubDeployment & Queue ==================="
startEdit()
cd('/SystemResources/'+systemModuleName)
cmo.createSubDeployment(queueSubDeploymentName)
print "Created a SubDeployment for Queue !!"
cd('/JMSSystemResources/'+systemModuleName+'/JMSResource/'+systemModuleName)
cmo.createQueue(queueName)
print "Created a Queue !!"
cd('/JMSSystemResources/'+systemModuleName+'/JMSResource/'+systemModuleName+'/Queues/'+queueName)
cmo.setJNDIName(queueJNDIName)
cmo.setSubDeploymentName(queueSubDeploymentName)
cd('/SystemResources/'+systemModuleName+'/SubDeployments/'+queueSubDeploymentName)
set('Targets',jarray.array([ObjectName('com.bea:Name='+jmsServerName+',Type=JMSServer')], ObjectName))
print "Targeted the Queue to the created subdeployment !!"
activate()
print ""



print "================== Creating  WebLogic Destination Bridge ==================="
startEdit()
cd('/')
cmo.createJMSBridgeDestination(weblogicDestinationBridge)
cd('/JMSBridgeDestinations/'+weblogicDestinationBridge)
cmo.setConnectionURL(serverUrl)
cmo.setAdapterJNDIName(weblogicAdapterJNDINoTX)
cmo.setConnectionFactoryJNDIName(ConnectionFactoryJNDIName)
cmo.setDestinationJNDIName(queueJNDIName)
activate()


print "================== Creating  WildFly Destination Bridge ==================="
startEdit()
cd('/')
cmo.createJMSBridgeDestination(wildflyDestinationBridge)
cd('/JMSBridgeDestinations/'+wildflyDestinationBridge)
cmo.setConnectionURL(wildflyServerUrl)
cmo.setAdapterJNDIName(weblogicAdapterJNDINoTX)
cmo.setConnectionFactoryJNDIName(wildflyJMSConnectionFactory)
cmo.setDestinationJNDIName(wildflyJMSQueueJndi)
activate()

startEdit()
cd('/JMSBridgeDestinations/'+weblogicDestinationBridge)
cmo.setUserName(Username)
cmo.setUserPassword(Password)
activate()

startEdit()
cd('/JMSBridgeDestinations/'+wildflyDestinationBridge)
cmo.setUserName(wildflyJMSUsername)
cmo.setUserPassword(wildflyJMSUserPassword)
cmo.setInitialContextFactory(wildflyInitialContextFactory);
activate()

print "================== Creating  JMS Bridge on WebLogic12c ==================="
startEdit()
cd('/')
cmo.createMessagingBridge('WLS12c_to_WildFly8_Bridge')
cd('/MessagingBridges/WLS12c_to_WildFly8_Bridge')
set('Targets',jarray.array([ObjectName('com.bea:Name=myserver,Type=Server')], ObjectName))
cmo.setSourceDestination(getMBean('/JMSBridgeDestinations/'+weblogicDestinationBridge))
cmo.setTargetDestination(getMBean('/JMSBridgeDestinations/'+wildflyDestinationBridge))
cmo.setStarted(true)
cmo.setSelector('')
cmo.setQualityOfService('Atmost-once')
activate()

cmd = "rm -f wlst.log"
os.system(cmd)

Step-8). Now we will run the WLST script. As following:

   $ cd /PATH/TO/wls12130/user_projects/domains/mydomain/bin
   $ . ./setDomainEnv.sh
   $ cd /PATH/TO/WebLogic_JMS_Bridge
   $  java  weblogic.WLST  webLogicJMS_Setup.py
   
   
   
   OUTPUT:
   
Initializing WebLogic Scripting Tool (WLST) ...

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands


================== JMSSever ===================
Created a JMSServer !!
PersistentStore has been set for the JMSServer !!
Targeted the JMSServer !!

================== SystemModule ===================
Created a SystemModule !!
Targeted the SystemModule !!

================== ConnectionFactory ===================
Created a ConnectionFactory !!
Targeted the ConnectionFactory !!

================== Unit Of Order ===================
Changed Unit Of Order !!

================== SubDeployment & Queue ===================
Created a SubDeployment for Queue !!
Created a Queue !!
Targeted the Queue to the created subdeployment !!

================== Creating  WebLogic Destination Bridge ===================
================== Creating  WildFly Destination Bridge ===================
================== Creating  JMS Bridge on WebLogic12c ===================

Writing Java Code to send messages to WebLogic JMS Queue

Step-9). Now In the “WebLogic_JMS_Bridge” create a sub directory with name “src” where we will create file “QueueSend.java”:

import java.io.IOException;
import java.util.Hashtable;
import javax.jms.JMSException;
import javax.jms.Queue;
import javax.jms.QueueConnection;
import javax.jms.QueueConnectionFactory;
import javax.jms.QueueSender;
import javax.jms.QueueSession;
import javax.jms.Session;
import javax.jms.TextMessage;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;

public class QueueSend {
  public final static String JNDI_FACTORY="weblogic.jndi.WLInitialContextFactory";
  public final static String JMS_FACTORY="My_CF";
  public final static String QUEUE="My_Q";

  private QueueConnectionFactory qconFactory;
  private QueueConnection qcon;
  private QueueSession qsession;
  private QueueSender qsender;
  private Queue queue;
  private TextMessage msg;

  public void init(Context ctx, String queueName) throws NamingException, JMSException {
    qconFactory = (QueueConnectionFactory) ctx.lookup(JMS_FACTORY);
    qcon = qconFactory.createQueueConnection();
    qsession = qcon.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
    queue = (Queue) ctx.lookup(queueName);
    qsender = qsession.createSender(queue);
    msg = qsession.createTextMessage();
    qcon.start();
  }

  public void send(String message,int counter) throws JMSException {
    msg.setText(message);
    msg.setIntProperty("counter", counter);
    qsender.send(msg);
  }

  public void close() throws JMSException {
    qsender.close();
    qsession.close();
    qcon.close();
  }

  public static void main(String[] args) throws Exception {
    if (args.length != 1) {
      System.out.println("Usage: java QueueSend WebLogicURL");
      return;
    }
    InitialContext ic = getInitialContext(args[0]);
    QueueSend qs = new QueueSend();
    qs.init(ic, QUEUE);
    readAndSend(qs);
    qs.close();
  }

  private static void readAndSend(QueueSend qs) throws IOException, JMSException {
    String line="Test Message Body with counter = ";
    for(int i=0;i<10;i++) {
          qs.send(line+i,i);
          System.out.println("JMS Message Sent: "+line+i+"\n");
       }
  }

  private static InitialContext getInitialContext(String url) throws NamingException {
    Hashtable env = new Hashtable();
    env.put(Context.INITIAL_CONTEXT_FACTORY, JNDI_FACTORY);
    env.put(Context.PROVIDER_URL, url);
    return new InitialContext(env);
  }
}

Step-10). Now we will write a simple ANT “build.xml” file inside the “WebLogic_JMS_Bridge” as following:

<project name="ApplicationLevelJMSDemo" default="run">
<property name="wls.home" value="/Users/jsensharma/NotBackedUp/Installed/wls12130" /> <!-- CHANGE ME!! -->
<property name="basedir" value="." />
<property name="tmp.dir" value="tmp" />
<property name="output.dir" value="build" />
<property name="src.dir" value="src" />
<property name="client.jar.name" value="jms_WLS_Client.jar" />

        <path id="wls.classpath">
             <fileset dir="${wls.home}">
                 <include name="**/*.jar"/>
             </fileset>
        </path>
        <target name="init">
           <delete dir="${output.dir}" />
           <mkdir dir="${output.dir}" />
           <delete dir="${tmp.dir}" />
           <mkdir dir="${tmp.dir}" />
        </target>

        <target name="run">
           <delete dir="${tmp.dir}" />
           <mkdir dir="${tmp.dir}" />
           <javac srcdir="${src.dir}" destdir="${tmp.dir}"  includes="QueueSend.java" classpathref="wls.classpath"/>
           <jar jarfile="${output.dir}/${client.jar.name}" basedir="${tmp.dir}" compress="true" />
           <java classname="QueueSend" fork="true">
               <classpath>
                  <pathelement location="${tmp.dir}"/>
                  <path refid="wls.classpath"/>
               </classpath>
               <arg value="t3://localhost:7001"/>
           </java>
           <delete dir="${tmp.dir}" />
        </target>  
</project>

Make sure to change the “wls.home” to point to your own WebLogic installation in this file.

Step-11). Now lets run the ANT project to send some messages to WLS “My_Q”

     $ cd /PATH/TO/WebLogic_JMS_Bridge
     $ export ANT_HOME=/PATH/TO/apache_ant_1.9.2
     $ export JAVA_HOME=/PATH/TO/jdk1.8.0_60
     $ export PATH=$JAVA_HOME/bin:$ANT_HOME/bin:$PATH
     
     $ ant
     
     
     OUTPUT:
     Buildfile: /Users/jsensharma/NotBackedUp/MM_Tests/WLS/JMS_Bridge/build.xml

run:
    [mkdir] Created dir: /PATH/TO/WebLogic_JMS_Bridge/tmp
    [javac] /Users/jsensharma/NotBackedUp/MM_Tests/WLS/JMS_Bridge/build.xml:28: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds
    [javac] Compiling 1 source file to /PATH/TO/WebLogic_JMS_Bridge/tmp
    [javac] warning: Supported source version 'RELEASE_6' from annotation processor 'org.eclipse.persistence.internal.jpa.modelgen.CanonicalModelProcessor' less than -source '1.8'
    [javac] warning: Supported source version 'RELEASE_6' from annotation processor 'org.sonatype.guice.bean.scanners.index.SisuIndexAPT6' less than -source '1.8'
    [javac] Note: /PATH/TO/WebLogic_JMS_Bridge/src/QueueSend.java uses unchecked or unsafe operations.
    [javac] Note: Recompile with -Xlint:unchecked for details.
    [javac] 2 warnings
      [jar] Building jar: /PATH/TO/WebLogic_JMS_Bridge/build/jms_WLS_Client.jar
      JMS Message Sent: Test Message Body with counter = 0
      
      JMS Message Sent: Test Message Body with counter = 1
      
      JMS Message Sent: Test Message Body with counter = 2
      
      JMS Message Sent: Test Message Body with counter = 3
      
      JMS Message Sent: Test Message Body with counter = 4
      
      JMS Message Sent: Test Message Body with counter = 5
      
      JMS Message Sent: Test Message Body with counter = 6
      
      JMS Message Sent: Test Message Body with counter = 7
      
      JMS Message Sent: Test Message Body with counter = 8
      
      JMS Message Sent: Test Message Body with counter = 9
      
   [delete] Deleting directory /PATH/TO/WebLogic_JMS_Bridge/tmp

BUILD SUCCESSFUL
Total time: 4 seconds

Step-12). Now login to WildFly 8.2 console and then check the JMS Queue “TestQ” runtime stats whether those messages reached to it or not.
http://localhost:9990/console/App.html#jms-metrics

Reference

I am just pasting the WebLogic side JMS Bridge configuration XML snippet here from “config.xml”

  <messaging-bridge>
    <name>WLS12c_to_WildFly8_Bridge</name>
    <target>myserver</target>
    <source-destination>WLS_Source_Bridge</source-destination>
    <target-destination>WildFly_Destination_Bridge</target-destination>
    <selector></selector>
    <quality-of-service>Atmost-once</quality-of-service>
    <started>true</started>
  </messaging-bridge>
  .
  .
  .
  <jms-server>
    <name>My_JMSServer</name>
    <target>myserver</target>
    <persistent-store xsi:nil="true"></persistent-store>
  </jms-server>
  
  <jms-bridge-destination>
    <name>WLS_Source_Bridge</name>
    <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDINoTX</adapter-jndi-name>
    <user-name>weblogic</user-name>
    <user-password-encrypted>{AES}MZthQtsuT4GH55R5es9TQFUOU8dK8tvLy5xJl5DcN1E=</user-password-encrypted>
    <connection-factory-jndi-name>My_CF</connection-factory-jndi-name>
    <connection-url>t3://localhost:7001</connection-url>
    <destination-jndi-name>My_Q</destination-jndi-name>
  </jms-bridge-destination>
  
  <jms-bridge-destination>
    <name>WildFly_Destination_Bridge</name>
    <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDINoTX</adapter-jndi-name>
    <user-name>jmsuser</user-name>
    <user-password-encrypted>{AES}0hlGNKwgZkSw+YxjxJSAbkPJm0EnV5tn5Czd5CLTJgk=</user-password-encrypted>
    <connection-factory-jndi-name>jms/RemoteConnectionFactory</connection-factory-jndi-name>
    <initial-context-factory>org.jboss.naming.remote.client.InitialContextFactory</initial-context-factory>
    <connection-url>http-remoting://localhost:8080</connection-url>
    <destination-jndi-name>jms/queue/TestQ</destination-jndi-name>
  </jms-bridge-destination>
  
  <jms-system-resource>
    <name>My_SystemModule</name>
    <target>myserver</target>
    <sub-deployment>
      <name>Sub_My_Queue</name>
      <target>My_JMSServer</target>
    </sub-deployment>
    <descriptor-file-name>jms/my_systemmodule-jms.xml</descriptor-file-name>
  </jms-system-resource>

Source Code: All the relative contents can be found in the following link:
https://github.com/jaysensharma/MiddlewareMagicDemos/tree/master/WebLogic/JMS/WebLogic_JMS_Bridge

Regards
Jay SenSharma


Using weblogic 12c specific new wls-maven-plugin

Hi,

As part of this example we will talk about the new “wls-maven-plugin” which is added as part of WebLogic 12c installation. This plugin provides a lots of additional facilities compared to the older “weblogic-maven-plugin” plugin. With the help of “wls-maven-plugin” plugin we can install, start and stop servers, create domains, execute WLST scripts, and compile and deploy applications.

The wls-maven-plugin requires a local WebLogic Server installation. For more information on this please refer to the following link: https://docs.oracle.com/cd/E24329_01/web.1211/e24368/maven.htm#WLPRG692

Update:10-Nov-2015 Unfortunately this plugin is removed in WebLogic 12.2.1, See the review: https://community.oracle.com/message/13400268

Installing “wls-maven-plugin”

Step-1). Open a terminal and run the following command:

$ export M2_HOME=/PATH/TO/apache_maven_3.2.3
$ export JAVA_HOME=/PATH/TO/jdk1.8.0_60
$ export PATH=$JAVA_HOME/bin:/PATH/TO/apache_maven_3.2.3/bin:$PATH


$ export MW_HOME=/PATH/TO/wls12130
$ cd $MW_HOME/wlserver/server/lib
$ mvn install -Dfile=wls-maven-plugin.jar -DpomFile=pom.xml

Step-2). Now install the wls-maven-plugin inside the local maven repository which is by default “~/.m2/repository”. In this case it will be placed inside the following dir “~/.m2/repository/com/oracle/weblogic/wls-maven-plugin”

$ mvn install:install-file  -Dfile=wls-maven-plugin.jar -DpomFile=pom.xml

[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building WebLogic Server Maven Plugin 12.1.3.0
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-install-plugin:2.4:install-file (default-cli) @ wls-maven-plugin ---
[INFO] Installing /PATH/TO/wls12130/wlserver/server/lib/wls-maven-plugin.jar to /Users/jsensharma/.m2/repository/com/oracle/weblogic/wls-maven-plugin/12.1.3.0/wls-maven-plugin-12.1.3.0.jar
[INFO] Installing /PATH/TO/wls12130/wlserver/server/lib/pom.xml to /Users/jsensharma/.m2/repository/com/oracle/weblogic/wls-maven-plugin/12.1.3.0/wls-maven-plugin-12.1.3.0.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.289 s
[INFO] Finished at: 2015-10-20T09:51:47+05:30
[INFO] Final Memory: 7M/245M
[INFO] ------------------------------------------------------------------------

Defining “pluginGroup” via global “settings.xml” file.

Step-3). Make sure to add the following “com.oracle.weblogic” in your “~/.m2/settings.xml” file:

<?xml version="1.0" encoding="UTF-8"?> 
<settings xmlns="http://maven.apache.org/settings/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> 

  <pluginGroups> 
    <pluginGroup>com.oracle.weblogic</pluginGroup>
  </pluginGroups>  
</settings>

Running the “mvn wls:help” command

Step-4). Once the “pluginGroup” is configured then from now on in this machine any time and from any directory we will be able to run the following wls maven task (For Example “mvn wls:help“):

$ cd /ANY/Directory/Of/Your/Choice
$ export M2_HOME=/PATH/TO/apache_maven_3.2.3
$ export JAVA_HOME=/PATH/TO/jdk1.8.0_60
$ export PATH=$JAVA_HOME/bin:/PATH/TO/apache_maven_3.2.3/bin:$PATH

$ mvn wls:help

Output of the above command should be something like following:

[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building WebLogic Server Maven Plugin 12.1.3.0
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- wls-maven-plugin:12.1.3.0:help (default-cli) @ wls-maven-plugin ---
[INFO] 
WebLogic Server Maven Plugin
The following goals are supported by wls-maven-plugin:

appc:
  Generates and compiles the classes needed to deploy EJBs and JSPs to 
  WebLogic Server. Also validates the deployment descriptors for compliance 
  with the current specifications at both the individual module level and 
  the application level. 

deploy:
  Deploys WebLogic Server applications and modules. Supports all deployment 
  formats, such as WAR, JAR, etc. 

create-domain:
  Create a domain for WebLogic Server using the default domain template. 
  For more complex domain creation use the WLST goal. 

help:
  Lists all the goals supported by the <code>wls-maven-plugin</code>. 

install:
  Installs WebLogic Server. 

list-apps:
  Lists the deployment names for applications and standalone modules 
  deployed, distributed, or installed in the domain. 

redeploy:
  Redeploys a running application or part of a running application. 

start-app:
  Starts an application deployed on WebLogic Server. 

start-server:
  Starts WebLogic Server. 

stop-app:
  Stops an application. 

stop-server:
  Stops WebLogic Server. 

undeploy:
  Undeploys the application from WebLogic Server. Stops the deployment unit 
  and removes staged files from target servers. 

update-app:
  Updates an application's deployment plan by redistributing the plan files 
  and reconfiguring the application based on the new plan contents. 

wlst:
  WLST wrapper for Maven. 

ws-clientgen:
  A Maven goal to generate client web service artifacts from a WSDL 

ws-wsdlc:
  A Maven goal to generate a set of artifacts and a partial Java 
  implementation of the Web service from a WSDL. 

ws-jwsc:
  A Maven goal to build a JAX-WS web service 


For detailed help on a goal, use -Dgoal=<goal-name> -Ddetail=true options.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS

Creating a Simple WebApp and Deploy using plugin

Now we will go one step ahead and deploy a simple web application to WebLogic 12c using this plugin.

Step-5). Create a directory structure like following in anywhere your file system :

mkdir TestWLS_PluginProject
cd  TestWLS_PluginProject
mkdir -p src/main/webapp

Step-6). Now create a simple JSP “index.jsp” inside the “TestWLS_PluginProject/src/main/webapp” as following:

<HTML>
	<HEAD>
		<TITLE> Sample Web Application </TITLE>
	</HEAD>
	<BODY>
		<%
			out.println("
<h2>Hello World!!! , Date/Time: "+ new java.util.Date()+"
<h2>");
		%>
	</BODY>
</HTML>

Step-7). The most important part, Create the following kind of “TestWLS_PluginProject/pom.xml” file, Which will use the “wls-maven-plugin”. In the following pom.xml make sure to change the “CHANGE ME !!!” section with your own environment specific data.

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
         
  <modelVersion>4.0.0</modelVersion>
  <groupId>middleware.magic</groupId>
  <artifactId>TestWebApp</artifactId>
  <version>1.0</version>
  <packaging>war</packaging>
  <name>TestWebApp</name>
  
  <properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <middleware.home>/Users/jsensharma/NotBackedUp/Installed/wls12130</middleware.home>  <!-- CHANGE ME !!! -->
    <admin.server.url>t3://localhost:7001</admin.server.url>  <!-- CHANGE ME !!! -->
    <admin.username>weblogic</admin.username>  <!-- CHANGE ME !!! -->
    <admin.password>weblogic1</admin.password>  <!-- CHANGE ME !!! -->
  </properties>  
  
  
  <dependencies>
    <dependency>
      <groupId>javax</groupId>
      <artifactId>javaee-web-api</artifactId>
      <version>6.0</version>
      <scope>provided</scope>
    </dependency>
  </dependencies>
  
  <build>
   <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
        <version>2.3.2</version>
        <configuration>
          <source>1.7</source>
          <target>1.7</target>
        </configuration>
      </plugin>

      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-war-plugin</artifactId>
        <version>2.1.1</version>
        <configuration>
          <failOnMissingWebXml>false</failOnMissingWebXml>
        </configuration>
      </plugin>
      
      <plugin>
        <groupId>com.oracle.weblogic</groupId> 
        <artifactId>wls-maven-plugin</artifactId> 
        <version>12.1.3.0</version> 
        <configuration> 
          <middlewareHome>${middleware.home}</middlewareHome>
          <adminurl>${admin.server.url}</adminurl>
          <user>${admin.username}</user>
          <password>${admin.password}</password>
          <name>${project.build.finalName}</name>
          <source>${project.build.directory}/${project.build.finalName}.${project.packaging}</source>          
        </configuration> 
      </plugin>
      
   </plugins>
  </build>
</project>

Step-8). Now build and deploy the application using the following command:

$ export M2_HOME=/PATH/TO/apache_maven_3.2.3
$ export JAVA_HOME=/PATH/TO/jdk1.8.0_60
$ export PATH=$JAVA_HOME/bin:/PATH/TO/apache_maven_3.2.3/bin:$PATH
cd  TestWLS_PluginProject

### To deploy application
mvn clean install wls:deploy

### To undeploy application
mvn wls:undeploy

This demo is available in the following link:
https://github.com/jaysensharma/MiddlewareMagicDemos/tree/master/WebLogic/Maven/TestWLS_PluginProject

Regards
Jay SenSharma

1 Comment more...

Middleware Magic Completes 2 year of spreading its Magic

It’s a pleasure to announce that Middleware Magic is celebrating it’s second anniversary today. We are now two years old today.

For new readers, we started Middleware Magic 2 years back and started as a tech blog for only Weblogic and with time we found that lot of new stuff is going on JBoss which caught our eyes, hence a year back exactly this day we had started tech blogging on JBoss as well and with it we really started making magic in the world of middleware.

Weblogic

JBoss

We always have a keen eye on our growing numbers and it’s really good to see we are growing with time and we are spreading the news like always in the world of middleware technology. This year for the total page views hit [i.e. JBoss + Weblogic] and total social network followers [i.e. Facebook + Twitter + Google] are

Pages Views 1,88,000+
Social Network followers 1140+

And special thanks to all the guys who took interests in joining our team and we are eagerly waiting for your articles to get them published on middleware magic with your name on it. We would also like to thank our subscribers from for supporting us and our teams [René van Wijk, Ravish Mody and Jay SenSharma] hard work as well as for bringing us to this stage and making middleware magic such a huge platform for everyone else.


Copyright © 2010-2012 Middleware Magic. All rights reserved. |