Archive for 2012

This guide is to configure WSO2 Message Broker 2.0.1 with WSO2 ESB 4.5.1 locally. WSO2 MB is configured to use inbuilt Cassandra Database in this example, and only one MB instance will be used (of course you can cluster it).

Configurations for Message Broker

1. Unzip WSO2 MB 2.0.1 pack. You can download it form here.
2. We will start WSO2 MB with a port offset of 1. For that open /repository/conf/carbon.xml file and define offset.

<Ports>
       <!-- Ports offset. This entry will set the value of the ports defined below to
        the define value + Offset.
        e.g. Offset=2 and HTTPS port=9443 will set the effective HTTPS port to 9445
        -->
       <Offset>1</Offset>

3. To start it with one node, we will use internal Cassandra bundled with WSO2 MB. As we have all port off-set by 1, we will have to point MB to correct Cassandra port. Go to /repository/conf/advanced/qpid-virtualhosts.xml and edit it to the correct port.

<carbon>
         <store>               
         <class>org.wso2.andes.server.store.CassandraMessageStore</class>
               <username>admin</username>
               <password>admin</password>
               <cluster>ClusterOne</cluster>               
 <idGenerator>org.wso2.andes.server.cluster.coordination.TimeStampBasedMessageI     dGenerator</idGenerator>
               <connectionString>localhost:9161</connectionString>
           </store>

Note: if you are using an external Cassandra instance you can point MB to it editing the connection string.

4. Whenever subscriptions are made or removed for queues, info level logs are printed. But when using MB 2.0.1 with Message processors it is always peeking for messages triggering subscription logs. To stop that edit log4j.properties file available at /repository/conf/log4j.properties file with the following line

#andes specific
log4j.logger.org.wso2.andes.server.cassandra.DefaultClusteringEnabledSubscriptionManager=WARN

5. Now navigate to /bin and run wso2server.bat file, and start WSO2 MB.

Configurations for WSO2 ESB

Unzip WSO2 ESB 4.5.1 pack. You can download it form here.

1. Unzip WSO2 ESB 4.5.1 pack. You can download it form here.

2. To setup backend (for demonstration of this example.)

2.1 Navigate to /samples/axis2Server/src/SimpleStockQuoteService and run ‘ant’ to build.

2.2 Come back to /samples/axis2Server folder and run axis2Server.bat file.

2.3 Point your browser to http://127.0.0.1:9000/services/SimpleStockQuoteService?wsdl and verify that the service is running.

3. Open JNDI.proerties file in /repository/conf folder and point to the MB broker being run. Also use ‘carbon’ as the virtualhost. Define a queue called ‘JMSMS’ there. No need of a topic here, so comment it out.

# register some connection factories

# connectionfactory.[jndiname] = [ConnectionURL]
connectionfactory.QueueConnectionFactory = amqp://admin:admin@clientID/carbon?brokerlist='tcp://localhost:5673'
# register some queues in JNDI using the form
# queue.[jndiName] = [physicalName]
queue.JMSMS=JMSMS

4. Start WSO2 ESB by running /bin/wso2Server.bat file.
5. Define a message Store by copy-pasting following config to the source view (Alternatively you can use message-store UI).

 <messageStore class="org.wso2.carbon.message.store.persistence.jms.JMSMessageStore"
                name="JMSMS">
     <parameter name="java.naming.factory.initial">org.wso2.andes.jndi.PropertiesFileInitialContextFactory</parameter>
     <parameter name="java.naming.provider.url">repository/conf/jndi.properties</parameter>
     <parameter name="store.jms.destination">JMSMS</parameter>
  </messageStore>

6. Define an end-point to send the message. In this example we use above backend we just set-up.

  <endpoint name="SimpleStockQuoteService">
     <address uri="http://127.0.0.1:9000/services/SimpleStockQuoteService"/>
  </endpoint>

7. Define a message forwarding processor as below (by copy-pasting or using the Management Console UI).

  <messageProcessor class="org.apache.synapse.message.processors.forward.ScheduledMessageForwardingProcessor"
                    name="Processor1"
                    messageStore="JMSMS">
     <parameter name="max.delivery.attempts">4</parameter>
     <parameter name="interval">4000</parameter>
  </messageProcessor>

Proxy Service for WSO2 ESB to Test Setup

Now to test the scenario use a proxy service like below.

  <proxy name="InOnlyProxy"

         transports="https http"
         startOnLoad="true"
         trace="disable">
     <target>
        <inSequence>
           <property name="FORCE_SC_ACCEPTED" value="true" scope="axis2"/>
           <property name="OUT_ONLY" value="true"/>
           <property name="target.endpoint" value="SimpleStockQuoteService"/>
           <log level="full"/>
           <store messageStore="JMSMS"/>
        </inSequence>
     </target>
  </proxy>

Note the highlighted parts, which are related.
Now whenever a message comes to this proxy service, it will be stored in JMS message store (which is in MB, JMSMS queue. If you disable message processor and send messages you will notice in MB management console message count of JMSMS queue being increased.)

This is “In Only” service invocation with Message Forwarding Processor. Similarly, following this article you can implement the others.

To Test

With soap UI send the following soap message to the InOnlyProxy.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://services.samples" xmlns:xsd="http://services.samples/xsd">

  <soapenv:Header/>
  <soapenv:Body>
     <ser:getQuote>
        <!--Optional:-->
        <ser:request>
           <!--Optional:-->
           <xsd:symbol>IBM</xsd:symbol>
        </ser:request>
     </ser:getQuote>
  </soapenv:Body>
</soapenv:Envelope>

Message will be logged at ESB console, SOAP UI will get 202 Accepted message, and at axis2Server console following will be logged.

samples.services.SimpleStockQuoteService :: Generating quote for : IBM

Concept behind RefFSContextFactory

RefFSContextFactory uses a JNDI folder as the provider URL. That JNDI folder has .binding files which contains the mapping between JNDI name and actual IBM Websphere MQ objects, such as a queue manager, queue, topic, and so forth.

Configuring WebSphere MQ

The WebSphere installation directory will be reffered to as

Go to the /Java/bin directory and open the JSAdmin.config file with a text editor.

Comment out the existing INITIAL_CONTEXT_FACTORY and add a INITIAL_CONTEXT_FACTORY named com.sun.jndi.fscontext.RefFSContextFactory

Comment the default PROVIDER_URL and use a directory path instead. Make sure that directory is created in the file system (ex: C:/JNDI-Directory).

Note: If exists, delete any earlier versions of the .bindings files from that folder.

ex: After changing your JSAdmin.config file should look like this.

# appropriate one should be uncommented.
#
#INITIAL_CONTEXT_FACTORY=com.sun.jndi.ldap.LdapCtxFactory
INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
#INITIAL_CONTEXT_FACTORY=com.ibm.ejs.ns.jndi.CNInitialContextFactory
#INITIAL_CONTEXT_FACTORY=com.ibm.websphere.naming.WsnInitialContextFactory
#INITIAL_CONTEXT_FACTORY=com.ibm.websphere.naming.WMQInitialContextFactory
#
# The following line specifies the URL of the service provider's initial
# context. It currently refers to an LDAP root context. Examples of a
# file system URL and WebSphere's JNDI namespace are also shown, commented
# out.
#
#PROVIDER_URL=ldap://polaris/o=ibm,c=us
PROVIDER_URL=file:/C:/JNDI-Directory
#PROVIDER_URL=iiop://localhost/
#PROVIDER_URL=localhost:1414/SYSTEM.DEF.SVRCONN
......

4. Restart the IBM WebSphere service

Creating a queue on WebSphere MQ

Open the WebSphere MQ explorer and right click on Queue Manager and select New >Queue Manager.

Provide a name for the Queue Manager (myQueueManager) and Make it default. Press Next.

Select the options to Start Queue Manager, Autostart Queue Manager and Create server connection channel. Then press on Next.

Select the option to Create listener configuration for TCP/IP and provide a port number (1415).

Once the Queue Manager is created, right click on the Queues icon belonging to the queue manager (myQueueManager) and select New->Local Queue.

Provide a name for the Queue (myQueue) and press on Next. Go with the default configurations and press on Finish.

Right click on the Channels icon under the Advanced icon and select New > Server-connection Channel. Provide a name for the channel (myChannel) and press on Next. Set the transmission protocol as TCP and press on Finish.

Once these steps are completed, a listener will be created running on port 1415 and you should be able to view it by clicking on the listeners icon.

Generating .bindings file

RefFSContextFactory uses a file system url as the provider url. We are going to create a .bindings file inside C:/JNDI-Directory folder using JSAdmin.config file we prepared. Navigate to /Java/bin directory and run JMSAdmin.bat file.

create bindings as appropriate. You have to use the names of resources you have defined. You can choose JNDI names as you want.

//define a context factory. If in same machine you can use "define qcf(MYCF) //qmgr(CUSTOMER_QUEUE_MANAGER) transport(BIND)" as well.

define qcf(MYCF) qmgr(CUSTOMER_QUEUE_MANAGER) host() port() CHANNEL(SYSTEM.DEF.SVRCONN) transport(CLIENT)

//define a queue

define q(JMS_QUEUE) qmgr(CUSTOMER_QUEUE_MANAGER) queue(MY_QUEUE)

Following is an example commands that goes with configs we have made under “Creating a queue on WebSphere MQ”. You can check created objects by display ctx command.

Welcome to the Admin Tool's command-line interface

InitCtx> def qcf(MQ_JMS_MANAGER) qmgr(myQueueManager) tran(client) chan(myChannel) host(175.157.120.102) port(1415)

InitCtx> def q(JMS_QUEUE) qmgr(myQueueManager) queue(myQueue)

InitCtx> display ctx

Contents of InitCtx

     .bindings                 java.io.File

  a JMS_QUEUE                 com.ibm.mq.jms.MQQueue

  a MQ_JMS_MANAGER            com.ibm.mq.jms.MQQueueConnectionFactory

3 Object(s)

   0 Context(s)

   3 Binding(s), 2 Administered

InitCtx> end

Stopping Websphere MQ classes for Java(tm) Message Service Administration

C:\IBM\WebSphere MQ\Java\bin>

Now go to C:/JNDI-Directory . You should be able to view .bindings file there.

Configure an ESB instance running on a different machine

The following configuration changes were made on the ESB for it to be able to remotely
communicate with WebSphere MQ.
The ESB installation directory will be reffered to as .

Copy C:/JNDI-Directory from above machine to a suitable place in new machine. We will consider this place in Ubuntu machine as /home/user/JNDI-Directory.

Copy all the jars found in the jar_files.zip attachment to the /repository/ components/lib directory. In addition, you have to copy fscontext.jar file found in /Java/lib directory as well.

Add the following jms transport receiver configuration to the /repository/ conf/axis2.xml file.

<transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener">
<parameter name="myQueueConnectionFactory" locked="false">
<parameter name="java.naming.factory.initial" locked = "false">com.sun.jndi.fscontext.RefFSContextFactory</parameter>
<parameter name="java.naming.provider.url" locked="false">file:/home/user/JNDI-Directory</parameter>
<parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">MQ_JMS_MANAGER</parameter>
<parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
<parameter name="transport.jms.Destination">JMS_QUEUE</parameter>
<parameter name="transport.jms.JMSSpecVersion">1.0</parameter>
</parameter>

<parameter name="default" locked="false">
<parameter name="java.naming.factory.initial" locked = "false">com.sun.jndi.fscontext.RefFSContextFactory</parameter>
<parameter name="java.naming.provider.url" locked="false">file:/home/user/JNDI-Directory</parameter>
<parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">MQ_JMS_MANAGER</parameter>
<parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
<parameter name="transport.jms.Destination">JMS_QUEUE</parameter>
<parameter name="transport.jms.JMSSpecVersion">1.0</parameter>
</parameter>
</transportReceiver>

Note the changed values.

Enable transport sender

Start the ESB by providing the -Duser.name=SYSTEM jvm parameter. ex: ./wso2server.sh -Duser.name=SYSTEM

On a successful connection, an INFO level log message similar to the following is printed on the esb startup.

INFO - JMSConnectionFactory JMS ConnectionFactory : myQueueConnectionFactory initialized

Test the setup

Copy paste the following proxy service to ESB synapse configuration. This will listen to messages coming from created queue at Websphere MQ (myQueue) then log it and drop the message.

<proxy name="SimpleStockQuoteService" transports="jms" startOnLoad="true">
<target>
<inSequence>
<property name="OUT_ONLY" value="true"/>
<log level="full"/>
<drop/>
</inSequence>
<outSequence/>
</target>
<parameter name="transport.jms.ContentType">
<rules>
<jmsProperty>contentType</jmsProperty>
<default>application/xml</default>
</rules>
</parameter>
<parameter name="transport.jms.ConnectionFactory">myQueueConnectionFactory</parameter>
<parameter name="transport.jms.DestinationType">queue</parameter>
<parameter name="transport.jms.Destination">JMS_QUEUE</parameter>
</proxy>

Right click queue in MQ explorer and put a test message to the queue (should be a xml). At that instance you will see that your message is consumed by the queue and logged at ESB running on remote machine.

WSO2 Stratos is the most complete, enterprise-grade, open PaaS, with support for more core services. WSO2 Stratos provides the core cloud services and essential building blocks for example federated identity and single sign-on, data-as-a-service and messaging-as-a-service and more, required for developing SaaS and cloud applications.

WSO2 Stratos enables organizations to combine the cost savings of cloud with the security, control and SLAs of enterprise data centers. WSO2 Stratos enables:

Unprecedented data center utilization and lower IT infrastructure costs
Tenant self-provisioning and agile app development
Tenant usage metering and billing
Easy access to SQL and noSQL data stores
Messaging, business and presentation services
Automated governance and centralized identity and security controls
Accelerated adoption of internal clouds and gradual migration into public clouds

This post is about deploying WSO2 products locally with Stratos.

First build the products you want to deploy and put the zip files that are in /carbon/products/(product)/modules/distribution/service/target into a one folder. Say home/ToRunWithStratos
Create a folder called 'deploy' in ToRunWithStratos. Now you have all the zip files of products plus the deploy folder in ToRunWithStratos folder.
Install "perl" to your machine. Use following commands.

sudo apt-get install libfile-copy-recursive-perl
sudo apt-get install libfile-path-perl
sudo apt-get install libfile-basedir-perl
sudo apt-get install libxml-libxml-perl (You many need to install libxml2-dev first- sudo apt-get install libxml2-dev)
sudo apt-get install libarchive-zip-perl
sudo apt-get install libgetopt-declare-perl
sudo apt-get install liblist-moreutils-perl

Install mySQL database using package manager. Use the following command to assign the password "root" to root.

mysqladmin -u root -p password root

Following are the general parameters that is needed to have in order to run stratos. In brackets I have shown my configuation values.

-p : Packs dir where services archive files resides(home/ToRunWithStratos)
-t : directory where changed configuration files are stored(home/ToRunWithStratos/deploy)
-v : version(1.1.0-SNAPSHOT)
-s : whether to enable sso (true)
-d : whether to create database (true)
-l : service list to enable ("mb is mnager")
-c : configuration file name (stratos_config_min.xml)
-u : database user name(root)
-w : database password(root)

cd to carbon/build
In my case following is the command I used to run mb on stratos

./stratos-setup.pl -p /home/hasitha/ToRunWithStratos -t /home/hasitha/ToRunWithStratos/deploy -v "1.1.0-SNAPSHOT" -d true -l "manager is mb" -c stratos_config_min.xml -u root -w root -s true

After the script is run, add following lines to /etc/hosts file after opening it as administrator, as you will be instructed in the command prompt after above command is run.

127.0.0.1 cloud-test.wso2.com

127.0.0.1 identity.cloud-test.wso2.com

127.0.0.1 governance.cloud-test.wso2.com

127.0.0.1 appserver.cloud-test.wso2.com

127.0.0.1 montor.cloud-test.wso2.com

127.0.0.1 data.cloud-test.wso2.com

127.0.0.1 process.cloud-test.wso2.com

127.0.0.1 rule.cloud-test.wso2.com

127.0.0.1 cep.cloud-test.wso2.com

127.0.0.1 esb.cloud-test.wso2.com

127.0.0.1 gadget.cloud-test.wso2.com

127.0.0.1 messaging.cloud-test.wso2.com

127.0.0.1 mashup.cloud-test.wso2.com

Now cd to /home/hasitha/ToRunWithStratos/deploy/wso2stratos-mb-1.1.0-SNAPSHOT/bin directory and run wso2Server.sh in order to start MB server. Now it is running in stratos.

Concept

On WSO2 carbon platform front end and back-end of a particular component is decoupled using service and stub concept.

In the core of a component backend is written and certain functionality is exposed as service using WSDL (Web Service Definition Language).

Using Java2WSDL tool, WSDL is generated during maven installation.

The front-end of the component should use a stub instance which is made according to the above WSDL. Then it can call the methods in the stub to access the back-end functionality.

Here I will explain how front-end of carbon/components/messagebox component can be modified to access the backend functionality of carbon/components/qpid in order to demonstrate the above scenario. As all the components are written in a consistent way same can be applied to other components as well.

Modification to the service

Open the qpid component using idea (or preferred IDE). For example to create an idea project using that component cd to carbon/components/qpid and type mvn idea:idea. Then mevan will create an idea project (.ipr) for you. Or else newer versions of idea can build the project using pom file in that component (just open the pom file or .ipr file).
Uder org.wso2.carbon.qpid/service/ws there is a file called qpidAdminService.
In that file you can access the backend functionality of the component and expose only relevant information.

Public String getDetails();

Getting the WSDL

Cd to qpid component and type "mvn clean install". This will build the component.
In the same way build the features which use qpid component out of the features that are installed to the product you wish to run (example: carbon/features/qpid)
Build the product (example: carbon/products/mb)
After successful build unzip the product/module/distribution/product/target/SNAPSHOT.zip
Copy /carbon/components/qpid//target/ to unzipFolder/repository/components/plugins replacing the existing file in the same name.
Open unzipFolder/repository/conf/carbon.xml file and set HideAdminServiceWSDLs to false

Then cd to bin folder there and run WSO2Sever.sh script.
After starting the server successfully open the client in the browser (using MGT console URL displayed in command prt).
For example

https://10.216.157.167:9443/carbon/services/QpidAdminService

Now the WSDL of the specified service will appear on the browser.

Generating the new stub

Right click and get the source and copy the entire code and paste it replacing all he code in the relevant stub under carbon/service-stubs//src/main/resources. (example: carbon/service stubs/org.wso2.carbon.qpid.stub/src/main/resources/QpidAdminService.wsdl)
Now cd to carbon/service-stubs/ and build using "mvn clean install". Then the new stun class would be generated.

The Front-end

Open carbon/components/ (example: carbon/components/messageBox)
Under /carbon/components/messagebox/org.wso2.carbon.messagebox.ui JSP (Java Server Pages) are located.
In JSP pages you can create an instance of the stub (example: qpidAdminServiceStub) and access the methods you have exposed in the backend of the other (example: qpid) component. You will need to import it as well.

<%@ page import="org.wso2.carbon.qpid.stub.service.QpidAdminServiceStub" %>

QpidAdminServiceStub qpidAdminServiceStub = UIUtils.getQpidAdminServiceStub(config, session, request);

String detail = qpidAdminServiceStub.getDetails();

Note that phases in <> should be replaced with relevant terms according to your scenario

Hasitha's Tech Blessings

Configurations for Message Broker

Configurations for WSO2 ESB

Proxy Service for WSO2 ESB to Test Setup

Concept behind RefFSContextFactory

Configuring WebSphere MQ

Creating a queue on WebSphere MQ

Generating .bindings file

Configure an ESB instance running on a different machine

Test the setup

Why Apache Cassandra?

Why Apache Zookeeper?

High level Architecture with Cassandra

Zookeeper Cluster Synchronizing Architecture

About Me

About

Popular Posts

Labels Cloud

Total Pageviews

Blog Archive

My Favorite Tech Blogs

Featured

Most Popular

About me

Featured

Instagram