

Connecting to ESB MB¶

This section describes how to configure ESB Micro Integrator to connect with ESB Message Broker.

Setting up the Micro Integrator with ESB MB¶

Copy the following jars to /lib folder from /client-lib folder.
- andes-client-3.2.19.jar
- org.wso2.securevault-1.0.0-wso2v2.jar
- geronimo-jms_1.1_spec-1.1.0.wso2v1.jar

If you want the Micro Integrator to receive messages from a ESB MB instance, or to send messages to a ESB MB instance, you need to update the deployment.toml file with the relevant connection parameters.

Add the following configurations to enable the JMS listener with ESB MB connection parameters.

[[transport.jms.listener]]
name = "myQueueListener"
parameter.initial_naming_factory = "org.wso2.andes.jndi.PropertiesFileInitialContextFactory"
parameter.provider_url = "conf/jndi.properties"
parameter.connection_factory_name = "QueueConnectionFactory"
parameter.connection_factory_type = "queue"
parameter.cache_level = "consumer"

Add the following configurations to enable the JMS sender with ESB MB connection parameters.

[[transport.jms.sender]]
name = "myQueueSender"
parameter.initial_naming_factory = "org.wso2.andes.jndi.PropertiesFileInitialContextFactory"
parameter.provider_url = "conf/jndi.properties"
parameter.connection_factory_name = "QueueConnectionFactory"
parameter.connection_factory_type = "queue"
parameter.cache_level = "producer"

Add the following configurations to specify the jndi connection factory details:

[transport.jndi.connection_factories]
'connectionfactory.QueueConnectionFactory' = "amqp://admin:admin@clientID/carbon?brokerlist='tcp://localhost:5675'"
'connectionfactory.TopicConnectionFactory' = "amqp://admin:admin@clientID/carbon?brokerlist='tcp://localhost:5675'"

[transport.jndi.queue]
queue_jndi_name = "queue_name"

[transport.jndi.topic]
topic_jndi_name = "topic_name"

Start ESB Message Broker before starting the Micro Integrator.
Start ESB Micro Integrator.

Now, you have both ESB Message Broker and the Micro Integrator configured and running.

Securing the ESB MB server¶

JMS is an integral part of enterprise integration solutions that are highly-reliable, loosely-coupled, and asynchronous. As a result, implementing proper security to your JMS deployments is vital. The below sections discuss some of the best practices of an effective JMS security implementation when used in combination with ESB Micro Integrator.

Let's see how some of the key concepts of system security such as authentication, authorization, and availability are implemented in different types of brokers. Given below is an overview of how some common security concepts are implemented in ESB MB.

Note

You can apply the same information mentioned in this section when configuring JMS with Apache QPid.

Given below is an overview of how some common security concepts are implemented in the ESB MB runtime.

Security Concept	How it is Implemented in EI-Broker
Authentication	Andes Authenticator connected entities to authenticate.
Authorization	Creation and use of role-based permissions.
Availability	Clustering using Apache Zookeeper.
Integrity	Message-level encryption using WS-Security.

Let's see how each concept in the table above is implemented in ESB MB.

After setting up ESB MB with the Micro Integrator, open MI_HOME/wso2/broker/conf/advanced/qpid-config.xml file and add the following line as a child element of <tuning\>.

<messageBatchSizeForBrowserSubscriptions>100000</messageBatchSizeForBrowserSubscriptions>

Authentication: Plain Text¶

ESB MB requires all its incoming connections to be authenticated. The MI_HOME/conf/deployment.toml file contains lines similar to the following. They contain the username and password credentials used to authenticate connections made to the ESB MB runtime. This is plain text authentication.

[transport.jndi.connection_factories]
'connectionfactory.TopicConnectionFactory' = "amqp://admin:admin@clientID/carbon?brokerlist='tcp://localhost:5675'"
'connectionfactory.QueueConnectionFactory' = "amqp://admin:admin@clientID/carbon?brokerlist='tcp://localhost:5675'"

In the ESB Micro Integrator authentication example below, we send a request to the proxy service named testJMSProxy, which adds a message to the example.MyQueue queue.

  <proxy xmlns="http://ws.apache.org/ns/synapse" name="testJMSProxy"
         transports="https http"
         startOnLoad="true"
         trace="disable">
     <target>
        <inSequence>
           <property name="FORCE_SC_ACCEPTED" value="true" scope="axis2"/>
           <property name="target.endpoint" value="jmsEP" scope="default"/>
           <store messageStore="testMsgStore"/>
        </inSequence>
     </target>
  </proxy>

  <endpoint xmlns="http://ws.apache.org/ns/synapse" name="jmsEP">
     <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
  </endpoint>

  <messageStore xmlns="http://ws.apache.org/ns/synapse" class="org.wso2.carbon.message.store.persistence.jms.JMSMessageStore"
                name="testMsgStore">
     <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">MyQueue</parameter>
  </messageStore>

If you change the authentication credentials of the jndi.properties file, the connection will not be authenticated. You will see an error similar to:

ERROR - AMQConnection Throwable Received but no listener set: org.wso2.andes.AMQDisconnectedException: Server closed connection and reconnection not permitted.

Authentication: Encrypted¶

In the previous authentication example, the user names and passwords are stored in plain text inside the Micro Integrator's jndi.properties file. These credentials can be stored in an encrypted manner for added security.

Authorization¶

The ESB MB runtime allows user-based authorization as seen in the example on ESB MB Authentication. To set up users, follow the instructions in the Admin Guide.

The ESB MB runtime allows role-based authorization for topics, where public/subscribe access can be assigned to user groups. For more information on setting up role-based authorization for topics, see Managing Topics and Subscriptions.

Integrity¶

Integrity is part of message-level security, and can be implemented using a standard like WS-Security.

Top