WebSphere Message Service Clients for C/C++ and .NET, Version 1.2 Operating Systems: Linux, Windows

Property mapping for administered objects

To enable applications to use WebSphere MQ JMS and WebSphere Application Server connection factory and destination object definitions, the properties retrieved from these definitions must be mapped on to the corresponding XMS properties that can be set on XMS connection factories and destinations.

In order to create, for example, an XMS connection factory with properties retrieved from a WebSphere MQ JMS connection factory, the properties must be mapped between the two.

All property mappings are performed automatically.

The following table demonstrates the mappings between some of the most common properties of connection factories and destinations. The properties shown in this table are just a small set of examples, and not all properties shown are relevant to all connection types and servers.

Table 1. Name mapping examples for connection factory and destination properties
WebSphere MQ JMS property name XMS property name WebSphere service integration bus property name
PERSISTENCE (PER) XMSC_DELIVERY_MODE  
EXPIRY (EXP) XMSC_TIME_TO_LIVE  
PRIORITY (PRI) XMSC_PRIORITY  
     
  XMSC_WPM_HOST_NAME serverName
  XMSC_WPM_BUS_NAME busName
  XMSC_WPM_TOPIC_SPACE topicName
Related concepts
Supported types of administered object repository
InitialContext properties
URI format for XMS initial contexts
JNDI Lookup web service
Retrieval of administered objects
Related tasks
Creating administered objects
Creating an InitialContext
Related reference
Required connection factory properties
Required destination properties

Concept topic

Terms of Use | Rate this page

Last updated: 7 Dec 2005

© Copyright IBM Corporation 2005. All Rights Reserved.