See Chapter 7, Services and Partners for more information about defining services.
|
|
|
|
|
|
|
This field specifies which type of Service this resource uses. The configuration of TIBCO ActiveMatrix BusinessWorks services is slightly different from ActiveMatrix BusinessWorks BPEL Extension services. If you are configuring a ActiveMatrix BusinessWorks BPEL Extension service, select ActiveMatrix BusinessWorks BPEL Extension in this field. If you are configuring a TIBCO ActiveMatrix BusinessWorks service, select ActiveMatrix BusinessWorks Process Definition in this field.
See TIBCO ActiveMatrix BusinessWorks Palette Reference for more information on configuring TIBCO ActiveMatrix BusinessWorks services.
|
|
This field contains a set of tabs, one for each interface of the service. Use the + or X button to add or remove interfaces from this field. Adding an interface brings up the Select a Resource dialog where you can select the WSDL resource that describes the correct interface. Use the Rename Current Interface button to rename the currently selected interface.
|
|
|
Namespace for the WSDL file of the interface. You can click the Go To Refinanced Resource button to view the WSDL file.
|
This sub-tab contains a table of all operations defined in the interface. This table allows you to specify the orchestration process that implements each operation. Use the Adjust for WSDL Updates button when the WSDL resource changes.
|
|
|
|
Timeout (in seconds) for incoming messages that are not consumed. For example, an incoming message may be for an existing orchestration process, but the orchestration process has not yet reached the point where it is ready to receive the message. Also, you may have incoming unsolicited messages that do not match any existing orchestration process. You can handle unsolicited messages by creating a TIBCO ActiveMatrix BusinessWorks automated process definition to handle them.
|
|
Double click on this field and use the Browse button to locate the orchestration process that implements each operation. Only orchestration processes whose Input Partners match the operation can be selected.
|
|
|
|
|
|
|
|
Use the Browse button to select a transport. HTTP Connection or JMS Connection resources can be used as transports.
|
|
The user name and password specified in the incoming request must exist in the domain (users are created and managed in the domain using TIBCO Administrator).
|
|
|
|
This field specifies the name of the destination for incoming JMS messages for this service. The syntax of the destination name is specific to the JMS provider you are using. See your JMS provider documentation for more information about destination names.
Note: If you are using TIBCO Enterprise Message Service as your JMS provider, you can use the Browse button next to this field after specifying a valid connection in the JMS Connection field. The Browse button displays a list of configured destinations in the JMS server that are appropriate for this activity.
|
|
|
|
This field specifies the type of incoming messages on the specified destination. Can be either Text Message or Bytes message.
|
|
•
|
Dups OK — the message is acknowledged automatically when it is received. JMS provides this mode for lazy acknowledgement, but TIBCO ActiveMatrix BusinessWorks acknowledges messages upon receipt.
|
•
|
TIBCO EMS Explicit Client Acknowledge — (only available for TIBCO EMS) the message will be acknowledged at a later point by using the Confirm activity. The session is not blocked and one session handles all incoming messages for each process instance. If a message is not confirmed before the process instance ends, all messages received in the same session are redelivered.
|
|
|
This field is available when a JMS transport is selected and Client is selected as the Acknowledge Mode. If the JMS Destination Type is Topic, this field is read-only. If the JMS Destination Type is Queue, the value of this field can be altered.
When a JMS queue message is received, the session is blocked until the message is acknowledged. Because the acknowledgement can comes at a later time when the process ends, this field allows you to specify a maximum number of new sessions to create to handle incoming messages.
Once the maximum number of sessions is reached, no new incoming messages can be processed. Once an incoming message is confirmed, the total number of active sessions is decreased and another incoming message can be processed.
|
|
|
|
|
The SOAP binding style for operations that do not explicitly set their binding style. You can specify either Document or RPC style.
|
|
Specify either SOAP 1.1 or SOAP 1.2 for the version of the SOAP specification to which incoming messages should comply.
|
|
The Advanced button allows advanced configuration of SOAP headers on BPEL endpoints for inbound service request. These headers can be mapped into a context object which is made available as service context in the orchestration through the Get Context activity.
|
|
The soapAction that is expected from incoming SOAP requests. This field is required, and by default, the operation name is used as the soapAction. Each operation in an interface must have a unique value for SOAP Action.
|
|
The SOAP binding style for the selected operation. You can specify either Document or RPC style, or you can specify that the value in the Default Style field should be used.
|
|
The encoding type for the body of the SOAP input and output messages. This can be either literal or encoded.
|
|
|
|
|
|
|
The Advanced SOAP Settings dialog appears. The tabs on the Advanced SOAP Settings dialog are the same as the dialog in TIBCO ActiveMatrix BusinessWorks. Refer to Chapter 16, "Service Palette" of the
TIBCO ActiveMatrix BusinessWorks Palette Reference for more information on the tabs of this dialog.
The WSDL Source tab displays the concrete WSDL interface file that is generated based on the information specified on the Configuration tab of this resource. This tab has the following fields.