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, as well as Java, can share the same definition of the destination. The properties of administered Destination objects can be changed without changing any code.
You can create a destination for a C or C++ application in either of the following ways:
For further information, see Destination for C or Destination for C++.
For further information about creating a URI, see Topic uniform resource identifiers and Queue uniform resource identifiers.
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 further information, see Destinations in .NET and IDestination.