XMS .NET creating administered objects

The ConnectionFactory and Destination object definitions that XMS applications require to make a connection to a messaging server must be created using the appropriate administrative tools.

Before you begin

For further details about the different types of administered object repository that XMS supports, see XMS .NET supported types of administered object repository.

About this task

To create the administered objects for IBM MQ use the IBM MQ Explorer or IBM MQ JMS administration (JMSAdmin) tool.

To create the administered objects for IBM MQ or IBM Integration Bus, use the IBM MQ JMS administration (JMSAdmin) tool.

To create administered objects for WebSphere Application Server service integration bus, use the WebSphere Application Server administrative console.

In the administrative tooling the property is known as APPLICATIONNAME or APPNAME for short.

Note: You cannot use JMSAdmin to set TRANSPORT(UNMANAGED). Therefore, in order to get an unmanaged XMS client using an administratively chosen application name, you need to enter the following command:

cf.SetIntProperty(XMSC.WMQ_CONNECTION_MODE, XMSC.WMQ_CM_CLIENT_UNMANAGED);

The following steps summarize what you do to create administered objects.

Procedure

Create a connection factory and define the necessary properties to create a connection from your application to your chosen server.
The minimum properties that XMS requires to make a connection are defined in XMS .NET required properties for administered ConnectionFactory objects.
Create the required destination on the messaging server, which your application connects to:
- For a connection to an IBM MQ queue manager, create a queue or topic.
- For a real-time connection to a broker, create a topic.
- For a connection to a WebSphere Application Server service integration bus, create a queue or a topic.
The minimum properties that XMS requires to make a connection are defined in XMS .NET required properties for administered Destination objects.