You open the JMS Collector agent configuration dialog from a workflow configuration: you can right-click the agent icon and select Configuration..., or double-click the agent icon.
JMS Collector agent configuration - JMS_Collector tab
| Setting | Description |
|---|---|
| Profile | Enter the JMS profile that you want used to establish the connection. For further information see 9.47.3 JMS Profile. |
| Username | Enter 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: For password, use: |
| 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. |
| Name | Enter a unique name that identifies the topic endpoint of the client. Provide this to use a durable subscription. |
| ID | Enter a unique client ID. This is an optional parameter as it can be set in the configured ConnectionFactory object. |
| Enable Pre-Acknowledge Routing | To have the content of the incoming message routed to the next specified Route before an acknowledgement is sent back to the JMS server, select this check box. 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. The content that is sent as output is generated in the |
| Route | The route where the message is sent to before an acknowledgment is sent back to the server. |