Configuring JMS information

If your connection is to a JMS message queue or topic, enter the following information on the JMS Information page of the Create Connection wizard.

Choose the destination type:

Queue – to use point-to-point messaging.
Topic – to use publish and subscribe messaging.

See your JMS documentation for more information about destination type.

Enter the JMS provider URL. This URL is the host name and port number that will be used to connect to the JMS Server.

If you are using EAServer JMS, enter:

iiop://<host_name >:port_number

where:
- host_name is the name of the machine on which the server is running.
- port_number is the port number at which the server is listening.
For example: iiop://my_machine:2000
If you are using WebLogic Server JMS, the protocol type must be “t3”, which is the WebLogic multitier JDBC driver.

where:
- host_name is the name of the machine on which the server is running.
- port_number is the port number at which the server is listening:
```
t3://<host_name>:<port_number>
```
For example: t3://mymachine:7001
If you are using TIBCO JMS or SonicMQ JMS, enter:
```
tcp://<host name>:<port number>
```
where:
- host_name is the name of the machine on which the server is running.
- port_number is the port number at which the server is listening.
For example: tcp://localhost:7222

Enter or select the class name of the specific JMS provider’s initial naming context factory.

If you are using EAServer JMS:
```
com.sybase.jms.InitialContextFactory
```
If you are using WebLogic Server JMS:
```
weblogic.jndi.WLInitialContextFactory
```

If you are using TIBCO JMS:

com.tibco.tibjms.naming.
			TibjmsInitialContextFactory

For SonicMQ JMS, if the destination type is a queue:

progress.message.jclient.QueueConnectionFactory

If the destination type is a topic:

progress.message.jclient.TopicConnectionFactory

Enter or select the name of the connection factory administered object.

If you are using EAServer JMS and the destination type is a queue:
```
javax.jms.QueueConnectionFactory
```
If the destination type is a topic:
```
javax.jms.TopicConnectionFactory
```
If you are using WebLogic Server JMS and the destination type is a queue:
```
weblogic.jms.QueueConnectionFactory
```
If the destination type is a topic:
```
weblogic.jms.TopicConnectionFactory
```
Make sure that this connection factory administered object name exists in your WebLogic server, or change the value here to match the name of the connection factory-administered object you created in WebLogic Server.
For TIBCO JMS if the destination type is a queue:
- ```
com.tibco.tibjms.
				TibjmsQueueConnectionFactory
```
  If destination type is a topic:
```
	com.tibco.tibjms.
				TibjmsTopicConnectionFactory
```
  Make sure that this connection factory-administered object name exists in your TIBCO JMS Server or change the value here to match the name of the connection factory- administered object you created in TIBCO JMS Server.

For SonicMQ JMS, If the destination type is a queue:

progress.message.jclient.
				QueueConnectionFactory

If the destination type is a topic:

progress.message.jclient.TopicConnectionFactory

Enter the name of the destination; for example, if the destination is a JMS queue, enter:

JMS_Queue

Enter the user name and password for the queue or topic, for example, enter jagadmin with no password.

If you have selected Topic as the destination type, enter the name of one or more durable subscribers in the Topic Subscribers field, separated by commas, with no spaces in between.

Durable subscribers are subscribers who are interested in receiving messages from the selected published topic. For example, enter:

JMSTSub1,JMSTSub2,JMSSub1

If you are routing events from messaging to database, enter name of the destination in the Status Destination field.

The status destination queue or topic you define is used for a client application to listen for an error message (if any) that may result in the event sent to the database.

If you have just configured inbound information, return to step 10 in “Adding and configuring a new connection”.