Administering Mediator : Mediator Configurations : Configuring SOAP Over JMS Protocol : Creating SOAP-JMS Web Service Endpoint Aliases : Creating a SOAP-JMS Provider Web Service Endpoint Alias and Trigger
Creating a SOAP-JMS Provider Web Service Endpoint Alias and Trigger
 
Viewing Thread Usage for SOAP-JMS Triggers
Increasing or Decreasing Thread Usage for All Triggers
Enabling, Disabling, and Suspending SOAP-JMS Triggers
If a virtual service's Entry Protocol Step is set to JMS, you must create the following:
*A SOAP-JMS provider Web service endpoint alias.
This alias stores the configuration used to generate the web service's endpoint reference (the JMS URI), the JMS bindings, or both, in a WSDL file. The primary information used to build the JMS URI is retrieved from the SOAP-JMS trigger.
*A SOAP-JMS trigger.
A trigger specifies the JMS provider destination from which the trigger receives messages, and the name of the JMS connection alias that the trigger uses to connect to the JMS provider.
To create a SOAP-JMS provider Web service endpoint alias and a SOAP-JMS trigger
1. Open Integration Server Administrator if it is not already open.
2. In the Navigation panel, select Settings > Web Services.
3. Click Create Web Service Endpoint Alias.
4. Under Web Service Endpoint Alias Properties, provide the following information:
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
5. Under JMS Transport Properties, provide the following information:
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.
Note:  
This parameter is only applicable when performing request-reply.
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.
6. Under JMS WSDL Options, provide the following information:
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.
7. Under WS Security Properties, if the inbound SOAP request must be decrypted and the outbound SOAP request must be signed, do the following:
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.
Important:  
The provider must have already given the consumer the corresponding public key.
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.
8. Under WS Security Properties, if the signing certificate chain of an inbound signed SOAP message has to be validated, specify the following:
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.
9. Click Save Changes.
Integration Server saves your changes and creates the SOAP-JMS trigger.
Copyright © 2015- 2017 Software AG, Darmstadt, Germany. (Innovation Release)

Product LogoContact Support   |   Community   |   Feedback