SOAP over JMS Binding Details (Provider)

The following table describes the binding details that are displayed for the selected SOAP over JMS binding, where the shared resource is acting as a provider.

Restriction: Topic destinations are not supported for SOAP/JMS bindings.
Property Description
Binding Name Defines the name used to identify this binding. The default value is SoapOverJms.
Style/Use Defines the style/use used by the SOAP binding. One of:
  • RPC/literal
  • Document/literal

Note: If a concrete WSDL document is being used to expose the service, the style/use used here should match the style/use defined in the WSDL document. If the two differ, at runtime the style/use defined in the WSDL document takes precedence and the style/use defined here will be ignored.

SOAP Version Defines the SOAP version used by this binding. SOAP versions 1.1 and 1.2 are supported.

The default value is 1.1.

Inbound: Connection Factory Configuration Logical name to identify a JMS Connection Factory Configuration resource instance in the BPM runtime. It creates an inbound connection to a JMS server to enable inbound receipt of JMS messages.

The default value is amx.bpm.userapp.jmsConnFactoryConf.

You can bind this logical name to the appropriate JMS Connection Factory Configuration resource instance using either of the following methods:

  • Early binding: Replace the name here with the name of a suitable JMS Connection Factory Configuration resource instance that already exists on the BPM runtime. (The mapping to the JMS Connection Factory Configuration resource instance will then be done automatically when you deploy the application to the BPM runtime.)
  • Late binding: Change or create the JMS Connection Factory Configuration resource instance to be used when you deploy the application to the BPM runtime. You do this by changing the value assigned to the JmsInboundConnectionFactory property on the Property Configuration page of the DAA Deployment Wizard. For more information, see Pageflow Processes and Business Services.

    If you instead export the project to a Distributed Application Archive for subsequent upload to the BPM runtime, a BPM administrator will need to configure the JMS Connection Factory Configuration resource instance to be used. For more information, see the Administrator interface documentation for your BPM runtime environment.

Inbound: Destination Configuration Logical name to identify a JMS Destination Configuration resource instance in the BPM runtime. It specifies what queue to listen to for inbound messages.

The default value is amx.bpm.userapp.jms.request.conf.

You can bind this logical name to the appropriate JMS Destination Configuration resource instance using either of the following methods:

  • Early binding: Replace the name here with the name of a suitable JMS Destination Configuration resource instance that already exists on the BPM runtime. (The mapping to the JMS Destination Configuration resource instance will then be done automatically when you deploy the application to the BPM runtime.)
  • Late binding: Change or create the JMS Destination Configuration resource instance to be used when you deploy the application to the BPM runtime. You do this by changing the value assigned to the JmsInboundDestination property on the Property Configuration page of the DAA Deployment Wizard. For more information, see Pageflow Processes and Business Services.

    If you instead export the project to a Distributed Application Archive for subsequent upload to the BPM runtime, a BPM administrator will need to configure the JMS Destination Configuration resource instance to be used. For more information, see the Administrator interface documentation for your BPM runtime environment.

Outbound: Connection Factory Logical name to identify a JMS Connection Factory resource instance in the BPM runtime. It is used to create an outbound connection to a JMS server.

The default value is amx.bpm.userapp.jmsConnFactory.

You can bind this logical name to the appropriate JMS Connection Factory resource instance using either of the following methods:

  • Early binding: Replace the name here with the name of a suitable JMS Connection Factory resource instance that already exists on the BPM runtime. (The mapping to the JMS Connection Factory resource instance will then be done automatically when you deploy the application to the BPM runtime.)
  • Late binding: Change or create the JMS Connection Factory resource instance to be used when you deploy the application to the BPM runtime. You do this by changing the value assigned to the JmsOutboundConnectionFactory property on the Property Configuration page of the DAA Deployment Wizard. For more information, see Pageflow Processes and Business Services.

    If you instead export the project to a Distributed Application Archive for subsequent upload to the BPM runtime, a BPM administrator will need to configure the JMS Connection Factory resource instance to be used. For more information, see the Administrator Interface documentation for your BPM runtime environment.