Destinations

An XMS application uses a Destination object to specify the destination of messages that are being sent, and the source of messages that are being received.

An XMS application can either create a Destination object at run time, or obtain a predefined destination from the repository of administered objects.

As with a ConnectionFactory, the most flexible way for an XMS application to specify a destination is to define it as an administered object. Using this approach, applications written in C, C++, and .NET languages, and Java, can share definitions of the destination. The properties of administered Destination objects can be changed without changing any code.

For .NET applications, you create a destination by using the CreateTopic or CreateQueue method. These two methods are available in both the ISession and XMSFactoryFactory objects in the .NET API. For more information, see Destinations in .NET and ../ref.dev/sapidest.htm#sapidest.

• Topic uniform resource identifiers
  The topic uniform resource identifier (URI) specifies the name of the topic; it can also specify one or more properties for it.
• Queue uniform resource identifiers
  The URI for a queue specifies the name of the queue; it can also specify one or more properties of the queue.
• Temporary destinations
  XMS applications can create and use temporary destinations.

Parent topic: Writing XMS applications