Connecting to an Enterprise Service Bus or Message Broker

About Message Brokers or Enterprise Service Bus (ESB)

Enterprise Service Bus or a Message Broker (also called an Message Queue or MQ) is used to route messages from consumers to providers and vice versa. These applications usually have JMS support and use subscribe and publish mechanism to route the messages. JaxView, using JMS, subscribes to a topic to also get the messages for management purposes.

Integrating JaxView with ESB or Message Brokers

JaxView can be configured to connect to one or more ESBs or Message Brokers. You use the JMS connection functionality inside JaxView to connect to an ESB or Message Broker to get messages being routed to and from Web services. This can be used instead of installing agent stubs on remote containers or using JaxView as a proxy server to allow JaxView to get copies of service request messages for monitoring and reporting.

JaxView supports connectivity to the following ESB and Message Broker products:

You configure JaxView to connect to an Enterprise Service Bus or Message Broker by creating an ESB connection definition object in the JaxView Admin tab. You can connect to multiple service buses or brokers by adding another ESB connection definition object to the Admin object tree.

NOTE: To test a JMS connection to an ESB or MQ, use the JMS validation tool under Admin tab and Tool node. See the section on JMS Validation Tool for more information.

The details on how to connect JaxView the an Enterprise Service Bus or Message Broker will vary according to the ESB or MB vendor. Please consult the vendor's documentation for information on how to connect a third party application to the ESB using the JMS protocol. You will use the information to complete the Add ESB form for that product.

The following are typical properties used to define JMS connection to an ESB or MQ.

Title:
A unique name for the ESB to be added
Provider URL:
This is the URL for the ESB. This should include the port number and the protocol. For example t3://myhost:7001.
Connection Factory Name:
The name of the connection factory for JMS connection. For example cn=myConnectionFactory
Initial Context Factory:
The class for initial context factory. This class needs to be in the application classpath
Topic:
Comma delimited list of topics to subscribe to, which will get the messages needed. The root hierarchy for the topics is better suited to get all the messages
UserName:
The user name for connecting to the ESB
Password:
The password for connecting to the ESB
Message Type:
Either SOAP or Non-SOAP or REST. If the messages are SOAP then add here.