
Use this procedure to register a JMS Topic or Queue Destination object.
The J2EE Engine administration tools enable you to register a standalone JMS Destination. It is deployed on the server as an application that contains only the deployment descriptor for the Destination object.
You can register a standalone JMS Destination using the:
Visual Administrator
| Field | Description | Example |
|---|---|---|
|
Application Name |
Specify a name to which the Destination is assigned. This name is used for the configuration that holds the object. Caution
Do not enter the name of an application that is already deployed on the server. This leads to re-deployment of the application and data loss. |
myApplication |
|
Destination Name |
Specify a name for the object that you create. |
myTopicDestination |
|
Factory Name |
Specify the name of a Queue- or TopicConnectionFactory. Tip
If the ConnectionFactory that you specify does not exist on the J2EE Engine, you cannot start the JMS Destination. After you deploy a ConnectionFactory with the specified name on the J2EE Engine, the JMS Destination is automatically started. |
myTopicConnectionFactory |
|
Description |
You can enter a short description for the object you create. |
This is a Topic JMS Destination for <X> provider. |
|
User |
Enter a username for authentication to the JMS provider. This must be an existing user. If you leave this field empty, the user and password for the used ConnectionFactory are assigned to the Destination object. |
Administrator |
|
Password |
Enter a password that corresponds to the specified username. |
|
If you want to create a JMS Destination similar to an already existing one, use Copy on the toolbar to copy the properties of the existing JMS Destination. Then choose
New and
Paste to paste the properties. Modify the parameters and save the JMS Destination object with a new name or in another application.
Console Administrator
To create a JMS Destination, use the deploy_destination command from the JMSCONNECTOR command group. For more information, see JMSCONNECTOR .
The J2EE Engine supports registration of a JMS Destination when deploying a J2EE application. You have to include a relevant XML definition of the JMS object in the application archive file (EAR). For more information about the format of the XML file, see jms-destinations.dtd .
See also: