For production purposes, always create physical destinations. During the development and testing phase, however, this step is not required.
The first time an application accesses a destination resource, Message Queue automatically creates the physical destination specified by the Name property of the destination resource. The physical destination is temporary and expires after a period specified by a Message Queue configuration property. Physical destinations are attached to Message Queue instances and not to Application Server instances. Any Application Server instance can talk to any Message Queue instance because there is no tight coupling between Message Queue and Application Server.
In the Admin Console, select Configuration >Physical Destinations.
In the Create Physical Destinations page, specify a name for the physical destination.
Choose the type of destination, which can be topic or queue.
To manage JMS physical destinations with the asadmin command-line utility, use the create-jmsdest, flush-jmsdest, or delete-jmsdest subcommands.
For more details about the fields and properties of the Physical Destinations page, see the Admin Console online help.
By default, all the instances in Application Server share the same Default JMS Host which is used by the domain administration server (DAS). In other words, all physical destinations are the same. If your environment requires configuration-specific physical destinations, you must create a separate JMS host for each instance or cluster as described in the following steps:
In the Edit JMS Hosts page of the Admin Console, create a new JMS host with its own port.
In the JMS Service page, create a JMS Host as follows:
Set the Type to LOCAL.
In the Default JMS Host field, specify the host that you created in Step 1.
You can also set other options on this page if needed.
Save the changes and restart the instance or cluster.
Now you are ready to create configuration-specific physical destinations.