Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your developerWorks profile is displayed to the public, but you may edit the information at any time. Your first name, last name (unless you choose to hide them), and display name will accompany the content that you post.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

Select a language:

  • Close [x]
  • Close [x]

Connecting WebSphere Partner Gateway Version 6.0 to SonicMQ

How to configure a JMS target and a JMS gateway in WebSphere Partner Gateway V6.0 that connect to SonicMQ

Henning Burgmann (henning.burgmann@de.ibm.com), IT Specialist, IBM
Henning Burgmann is an IT Specialist and a member of IBM Software Services for WebSphere in Cologne, Germany. Henning has focused on J2EE development especially in connection WebSphere Application Server, WebSphere Process Server, and WebSphere Partner Gateway products. He has worked for IBM since 1996.

Summary:  This tutorial describes how to set up a JMS (Java Messaging Service) target and a JMS gateway in WebSphere Partner Gateway that connect to SonicMQ queues. It also shows you how to create the corresponding objects in SonicMQ.

Date:  04 Apr 2007
Level:  Intermediate
PDF:  A4 and Letter (1094 KB | 29 pages)Get Adobe® Reader®

Activity:  5535 views
Comments:  

Introduction to Java Message Service (JMS)

JMS describes a common API for messaging products. It offers a unified way of sending and receiving asynchronous messages for Java™ programs. JMS distinguishes the point-to-point and publish and subscribe messaging model. In this article, you concentrate on the point-to-point model. The current version of the JMS API is 1.1.

JMS architecture

The JMS provider is the messaging system that implements the JMS API. A JMS client is a Java program that uses the JMS API to send or receive messages via the JMS provider. The JMS messages are the exchanged message objects. They consist of a standard header, optional properties that can be added to the header and the body. The following message types are defined:

  • TextMessage
  • StreamMessage
  • BytesMessage

The ConnectionFactory and Destinations are the standard JMS objects that are provided to the JMS client. References to these administered objects are stored in the JNDI namespace. The ConnectionFactory is needed for setting up a connection from a JMS client to a JMS provider. In the point-to-point model a destination is a references to one of the provider's message queues.


Figure 1. The JMS architecture
The JMS architecture

For further details about the JMS architecture, please refer to the JMS specification V1.1 and the J2EE 1.4 tutorial (see Resources).

JMS messages in WebSphere Partner Gateway

For the IBM® WebSphere® Partner Gateway's integration with other back-end systems via JMS, two packaging types are recommended:

  • None
  • Backend Integration

None package sends and receives only the raw messages without any further header information beside the standard JMS headers. The Backend Integration package adds JMS properties to the header of outbound messages. For inbound messages, the seven important properties are defined as mandatory by the Backend Integration package. The following table lists these required properties that are useful for the further processing by another backend system:


Table 1. The required JMS properties in the Backend Integration package
JMS property nameDescription
x_aux_sender_idIdentification of the message sender (in most cases the DUNS number).
x_aux_receiver_idIdentification of the message receiver (in most cases the DUNS number).
x_aux_protocolMessage content protocol.
x_aux_protocol_versionVersion of the message content protocol.
x_aux_process_typeMessage type
x_aux_process_versionVersion of the message type
x_aux_system_msg_idUnique identifier for duplicate checking

For further details about the WebSphere Partner Gateway's backend integration via JMS, please refer to the IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Integration Guide (see Resources).

1 of 7 | Next

Comments

Back to top

Close [x]

Help: Update or add to My dW interests

What's this?

This little timesaver lets you update your My developerWorks profile with just one click! The general subject of this content (AIX and UNIX, Information Management, Lotus, Rational, Tivoli, WebSphere, Java, Linux, Open source, SOA and Web services, Web development, or XML) will be added to the interests section of your profile, if it's not there already. You only need to be logged in to My developerWorks.

And what's the point of adding your interests to your profile? That's how you find other users with the same interests as yours, and see what they're reading and contributing to the community. Your interests also help us recommend relevant developerWorks content to you.

View your My developerWorks profile

Return from help

Close [x]

Help: Remove from My dW interests

What's this?

Removing this interest does not alter your profile, but rather removes this piece of content from a list of all content for which you've indicated interest. In a future enhancement to My developerWorks, you'll be able to see a record of that content.

View your My developerWorks profile

Return from help

static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere, Java technology
ArticleID=205660
TutorialTitle=Connecting WebSphere Partner Gateway Version 6.0 to SonicMQ
publish-date=04042007
author1-email=henning.burgmann@de.ibm.com
author1-email-cc=

Table of contents

1 of 7 | Next

Local resources

Tags

Help
Use the search field to find all types of content in My developerWorks with that tag.

Use the slider bar to see more or fewer tags.

Popular tags shows the top tags for this particular content zone (for example, Java technology, Linux, WebSphere).

My tags shows your tags for this particular content zone (for example, Java technology, Linux, WebSphere).

Use the search field to find all types of content in My developerWorks with that tag. Popular tags shows the top tags for this particular content zone (for example, Java technology, Linux, WebSphere). My tags shows your tags for this particular content zone (for example, Java technology, Linux, WebSphere).

 

Dig deeper into WebSphere on developerWorks

Try IBM PureSystems. No charge.

IBM PureSystems on a kaleideoscope background

Experience today!

Get started with the cloud-based trial and pattern development kit.

Share this page:

  • Close [x]

Follow developerWorks:

  • Close [x]