Creating RA JMS Agent Connection Objects
You will need to create an RA JMS Agent Connection object by selecting an Agent and provider type. Next you define the JNDI properties. JNDI properties create the initial context of the JMS messages.
To create an RA JMS Agent Connection object:
- Add a Connection object of type JMS > JMSCONNECTION.
- Select the JMS Connection page.
- Respond to the following fields in the Agent Settings and General JNDI Properties sections.
- Agent
- Provider Type
- JMS Version
- Context Factory
- Provider URL
- Connection Factory
- Principal
- Credentials
- Optionally add other properties to the Custom JNDI Properties table.
- If your RA JMS Agent connection requires a user name and password to be passed at the implementation level, you can optionally add them in the User and Password fields in the Security section.
- Optionally set headers and add properties using the Headers & Properties page. For more information, see Defining Headers and Properties for RA JMS Agent Connection Objects.
- Optionally add queues, topics and/or subscribers using the Queues, Topics, Subscribers page. For more information, see Defining Queues, Topics, and Subscribers for RA JMS Agent Connection Objects.
- Click Save to save the Connection object.
Select an RA JMS Agent solution Agent object. This field is only used to populate the provider information in the Job.
Select a provider type defined for the Agent as documented in topic Specifying General RA JMS Agent Solution Agent Object Settings.
A read-only field that displays the JMS version.
Select the context factory from the selected provider type.
Enter the endpoint to the JMS provider in the format the vendor accepts.
Enter the registration name defined with JNDI (default ConnectionFactory).
The login name to the provider for the JNDI connection.
To pass a user name at the implementation level, you use the User field in the Security section of this page.
The password to the provider for the JNDI connection.
To pass a user name at the implementation level, you use the Password field in the Security section of this page.
These fields can include object variables in the format &<variable name>. The values of these object variables will be replaced at runtime.
The Login field on the Attributes