JMS Collector Agent Configuration

Owned by Jenni Wallin
Last updated: Apr 04, 2023 by Former user (Deleted)

To open the JMS Collector agent configuration dialog from a workflow configuration, you can do either one of the following:

  • double-click the agent icon
  • select the agent icon and click the  Edit button


The Agent Configuration contains configurations to establish connections with the JMS server and subscription sessions.


JMS Collector agent configuration

SettingDescription
ProfileEnter the JMS profile that you want used to establish the connection. For further information see JMS Profile.
UsernameEnter a user name to apply when initiating the connection with the JMS server. This field is optional.
Password

Enter a password to use when initiating the connection with the JMS server. This field is optional.

Note!

There may be instances where setting the username and password for the JNDI server will result in an error where the agent will not be able to access the server. When this happens, you will have to set the username and password in the properties list in the JMS Profile, using the following security context:

For username, use: java.naming.security.principal

For password, use: java.naming.security.credentials

Durable Subscription
Enable Durable Subscription

To enable the agent to create a durable topic subscription, select this check box. 

If the Destination is of type queue, the agent will fail to initiate.

NameEnter a unique name that identifies the topic endpoint of the client. Provide this to use a durable subscription.
IDEnter a unique client ID. This is an optional parameter as it can be set in the configured ConnectionFactory object.
Pre-Acknowledge Routing
Enable Pre-Acknowledge Routing

, select this check box.

Select this option to have the content of incoming message routed to the next specified Route before an acknowledgement is sent back to the JMS server. 

When enabled, to route the UDR, the JMS Collector agent uses the same thread that it used when the JMS message was collected. This way, the agent can use another agent, e g Inter Workflow, to store incoming messages before they are acknowledged. This routing will send the bytearray UDR type, and encoded using the MZ Tag encoder. For further information on MZ Tagged Formats, see Format Management Overview in the Ultra Reference Guide.

RouteThe route where the message is sent to before an acknowledgment is sent back to the server.