Registering a JMS ConnectionFactory using Non-JNDI Provider

Use this procedure to register a JMS ConnectionFactory when your JMS provider does not provide a naming system (for example, SonicMQ). In this case, you must use an ObjectFactory to access the provider.

Using the administration tools that the J2EE Engine provides, you can create a standalone ConnectionFactory object. It is deployed on the server as an application that contains only the deployment descriptor for the JMS object.

1. In the Runtime tab of JMS Connector Service, choose Resources → Factories.
2. Choose  New on the toolbar.
3. In the right-hand tab complete the following fields:

   Field	Description	Example
   Application Name	Specify a name to which the ConnectionFactory is assigned. This name is used for the configuration that holds the object. Caution Do not enter the name of an application already deployed on the server. This leads to re-deployment of the application and data loss.	myApplication
   Factory Name	Enter a name for your ConnectionFactory. The system uses it to bind the factory in the naming system. You can look up the ConnectionFactory using this name.	myQueueConnFactory
   Client ID	Enter a unique client identifier. It is also assigned to the connection that is created with this ConnectionFactory. The Client ID is not a required field. If you leave it empty, it defaults to the client ID of the connection factory from the JMS provider.
   User	Enter a username for authentication to the JMS provider. The JMS system assigns it by default to the connections created by this ConnectionFactory unless you specify a different username for a connection.	Administrator
   Password	Enter a password corresponding to the username.
   Description	You can enter descriptive text about the ConnectionFactory. However, this is not required.	This is an example for a JMS ConnectionFactory.
   Provider Type	Choose Object Factory from the drop-down menu.
   Library	Choose a library that the JMS Connector uses to obtain a connection factory instance. This is a J2EE Engine library that contains the archive files of the JMS provider. Tip To use a JMS library, you must first deploy and define it on the J2EE Engine.
   Aliases	You can add unlimited number of aliases, which are alternative names of the connection factory. They enable multiple clients to use the factory and prevents you from having to create many equal connection factories only with different names.	myQCF myQCFactory

   Tip

   The type of the ConnectionFactory (Queue or Topic) is automatically determined after you start the application associated to the factory.

4. Choose the Provider tab. Fill in the following fields:

   Field	Description	Example
   Object Factory Class	Enter the Java fully qualified name of the class implementing the javax.naming.spi.ObjectFactory interface.	progress.message.jclient.AdministeredObjectFactory
   JMS Factory Class	Enter the Java fully qualified name of the class that implements javax.jms.QueueConnectionFactory or javax.jms.TopicConnectionFactory interface.	progress.message.jclient.xa.XATopicConnectionFactory

   Note

   You can add any Object Factory-specific properties using the Additional tab. Enter the name and the value of the additional parameter(s) in the Property and Value fields respectively, and then choose Add.

   Tip

   If you want to create a JMS ConnectionFactory similar to an existing one, choose  Copy on the toolbar to copy the properties of the existing ConnectionFactory. Then choose  New and  Paste to paste the properties. Modify the parameters and save the ConnectionFactory object with a new name or in another application.

5. To save the changes, choose  Save changes on the toolbar.

Console Administrator

Use deploy_jms_resource command from the JMSCONNECTOR command group. For more information, see JMSCONNECTOR .

See also:

Registering a JMS ConnectionFactory using JNDI-Based Provider

Editing JMS ConnectionFactory and Destination