In this field... | Specify... |
Alias | A name for the provider web service endpoint alias. This also becomes the name of the SOAP-JMS trigger. The alias name cannot include the following illegal characters: # ©\ & @ ^ ! % * : $ . / \ \ ` ; , ~ + = ) ( | } { ] [ > < " |
Description | A description for the endpoint alias. |
Type | Provider |
Transport Type | JMS |
In this field... | Specify... | ||
SOAP-JMS Trigger Name | WS Endpoint Trigger. Integration Server populates this field automatically with all valid SOAP-JMS trigger names. | ||
Delivery Mode (optional) | Whether the JMS transport must be Persistent or Non_Persistent. | ||
Time to Live (optional) | The amount of time (in milliseconds) before a message expires. If set to zero, the message does not expire. | ||
Priority (optional) | The message's priority in the queue. You can specify a number from 0 to 9, where 0 is the lowest priority and 9 is the highest. | ||
Reply To Name (optional) | The name or lookup name of the JMS destination where a reply to the message must be sent. | ||
Reply To Type (optional) | The type of message to which containing an empty value. The options are Queue and Topic. Default to empty value.
| ||
Connection Count | The maximum number of connections that can be used to retrieve messages for the JMS trigger. Specifying multiple connections per concurrent JMS trigger affects the maximum number of messages the JMS trigger can process. The Max Execution Threads property specifies how many messages each connection can process. The total number of messages is the product of Max Execution Threads and Connection Count. For example, if the JMS trigger has a Max Execution Threads value of 5 and Connection Count is set to 2, the JMS trigger can process up to 10 messages at one time. Restrictions: The Connection Count property only applies to concurrent JMS triggers (that is, a JMS trigger in which the Processing mode is set to Concurrent). It does not apply to serial triggers. The Connection Count property only applies if the JMS connection alias allows an individual connection for each JMS trigger (that is, if the Create New Connection per Trigger parameter is set to true/selected/yes). The Connection Count property only applies if the JMS connection alias connects to the webMethods Broker. The Connection Count property cannot be used if the JMS trigger receives messages from a non-durable subscriber for a topic. |
In this field... | Specify... |
Include Connection Factory Name in JMS URI | Whether to include the connection factory name in the generated WSDL. |
Include JNDI Parameters in JMS URI | Whether to include the JNDI parameters in the generated WSDL. |
In this field... | Specify... | ||
Keystore Alias | Alias of the keystore containing the private key used to decrypt the inbound SOAP request or sign the outbound SOAP response.
| ||
Key Alias | Alias of the private key used to decrypt the request or sign the response. The key must be in the keystore specified in Keystore Alias. |
In this field... | Specify... |
Truststore Alias | The alias for the truststore that contains the list of CA certificates that Integration Server uses to validate the trust relationship. |