Configuration

The Configuration tab has the following fields.

Field

Global Var?

Description

Name

No

The name to appear as the label for the resource.

Description

No

Short description of the resource.

Enable for AMX

No

Selecting this check box allows you to configure this Service resource in ActiveMatrix BusinessWorks. It also allows you to configure an ActiveMatrix BusinessWorks endpoint for the existing services.

Note: Select this check box only if you want to expose your Service to theActiveMatrix BusinessWorks world.
Warning: If this check box is selected and cleared, you loose the Partner Link Configuration information from the partner binding table.

Tabs visible after selecting the check box are:

  • Services

  • References

  • Properties

  • WSDL Source

  • Overview

Following tabs are visible when this check box is not selected (by default):

  • Configuration

  • Partner Binding

  • WSDL Source

  • Overview

Implementation

No

This field allows you to add abstract WSDL files that describe the service. Click the + button to add a WSDL file. Click the X button to remove a WSDL file. Click the Rename Current Service Port to change the name of the currently selected service port.

Service Port Sub-Tabs

Each service port have a sub-tab containing the configuration for the service port.

Interface Namespace

No

Namespace for the interface file of the service. You can click the Go To Referenced Resource to view the interface file.

Operations Sub-Tab

This sub-tab contains a table of all operations defined in the interface file. This table allows you to specify the resource that implements each operation.

Operation Name

No

Name of the operation. This column is a read-only list of operations contained in the interface file.

Operation Implementation

No

Double click on this field and use the Browse button to locate the resource that implements each operation. Process definitions that implement an operation must have an input, output, and error schemas that match the input, output, and fault messages of the operation.

You can leave the implementation for an operation unspecified. In this case, an exception is thrown when a client attempts to invoke the unimplemented operation.

Note: You can drag and drop a process definition from the project tree to the operation implementation cell. If the signature of the operation matches the process definition, the process be inserted. If the process definition or the WSDL changes, the icon for the process definition in the cell changes to a warning triangle indicating the operation and implementation signatures no longer match.

Endpoint Bindings Sub-Tab

This sub-tab allows you to specify one or more endpoints that expose the service as well as the transport bindings for each endpoint.

Use the + button to add endpoints, use the X button to delete endpoints, and use the arrow buttons to move the selected endpoint in the list.

Endpoint Name

No

Specify a name for the endpoint in this field.

Endpoint Type

No

Specify the type of endpoint by selecting from the list of types.

  • Local — A local endpoint is available to consumers within the same process engine. This type of endpoint provides a highly efficient way for local services to invoke each other without incurring the overhead of using a network transport.

  • SOAP — A SOAP endpoint is used to expose the service by way of the SOAP protocol to other partner services or web clients

Transport Sub-Tab

Transport

No

Use the Browse button to select a transport. In this release, HTTP Connection or JMS Connection resources can be used as transports.

Use Basic Authentication

Yes

This field is available when an HTTP transport is selected.

When checked, this field specifies that incoming SOAP requests must supply a valid username and password.

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).

Endpoint URI

No

This field is available when an HTTP transport is selected.

This field specifies the Endpoint URI that clients can use to access the service.

JMS Destination

Yes

This field is available when a JMS transport is selected.

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. For more information about destination names, see your JMS provider documentation.

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.

JMS Destination Type

No

This field is available when a JMS transport is selected.

This field specifies whether the JMS Destination is a Topic or a Queue.

JMS Message Type

No

This field is available when a JMS transport is selected.

This field specifies the type of incoming messages on the specified destination. It can be either Text Message or Bytes message.

Enable W3C SOAP JMS 1.0 Compliance

No

Select the check box to comply with the W3C SOAP Over JMS 1.0 specification.

By default, the check box is not selected and the service complies with the TIBCO specifications.

Target Service

 

This field is available when a JMS transport is selected.

This field is available only when the check box Enable W3C SOAP JMS 1.0 Compliance is selected.

Specify the target service value, if any.

Note: If Target Service is configured, the value is reflected in the WSDL as a query parameter.

Reply Using Incoming Delivery Mode

No

This field is available when a JMS transport is selected.

Select the check box if you want to send the reply using the incoming delivery mode.

By default, the check box is not selected.

JMS Delivery Mode (Response)

Yes

This field is available when the Reply using Incoming Delivery Mode field is not selected.

The delivery mode of the response message. Can be one of the following:

  • PERSISTENT: signifies the messages are stored and forwarded.

  • NON-PERSISTENT : messages are not stored and may be lost due to failures in transmission.

  • TIBCO EMS Reliable : this mode is only available when using TIBCO Enterprise Message Service. For more information about this mode, see the TIBCO Enterprise Message Service documentation.

By default, the field selection is PERSISTENT.

Acknowledge Mode

No

This field is available when a JMS transport is selected.

This field specifies the acknowledgment mode to be used for incoming messages. It can be one of the following:

  • Auto : the message is automatically acknowledged when it is received.

  • Client: the message is acknowledged when the process implementing the operation ends successfully.

  • Dups OK : the message is acknowledged automatically when it is received. JMS provides this mode for lazy acknowledgment, but ActiveMatrix BusinessWorks acknowledges messages upon receipt.

  • TIBCO EMS Explicit : (only available for TIBCO Enterprise Message Service) a message which is not acknowledged using the Confirm activity before the process instance ends, are redelivered instead of all messages in the session. The session is not blocked and one session handles all incoming messages for each process instance.

  • Note: In the ActiveMatrix BusinessWorks 5.10 release, a change occurs in the behavior of this feature. Now only the messages that are not confirmed, are redelivered.
  • TIBCO EMS Explicit Dups OK : (only available for TIBCO Enterprise Message Service) a message which is not acknowledged using the Confirm activity before the process instance ends, are redelivered instead of all messages in the session. The session is not blocked and one session handles all the incoming messages for each process instance. The messages however, would be lazily acknowledged.

JMS Application Properties

 

This field is available when a JMS transport is selected.

Any application-specific message properties that is part of the message. This is specified by the JMS Application Properties shared configuration object.

JMS Application Properties (Response)

 

This field is available when a JMS transport is selected.

Any application-specific message properties that is part of the response message. This is specified by the JMS Application Properties shared configuration object.

Max Sessions

No

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.

This field specifies the maximum number of JMS sessions to create for incoming queue messages.

When a JMS queue message is received, the session is blocked until the message is acknowledged. Because the acknowledgment can come at a later time when the process ends, this field allows you to specify a maximum number of new sessions to be created for handling 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.

Operations

No

The operation that this process definition implements.

The drop-down list in this field is populated with the operations contained in the specified port type in the specified WSDL.

You can choose one operation to implement per process definition. If you want to implement multiple operations, you must create a process definition for each.

SOAP Details Sub-Tab

Default Style

No

The SOAP binding style for operations that do not explicitly set their binding style. You can specify either Document or RPC style.

SOAP Version

No

Specify either SOAP 1.1 or SOAP 1.2 for the version of the SOAP specification to which incoming messages should comply.

For more information, see SOAP Specification Compliance.

Operations

No

Select each operation from the drop down list to specify the SOAP Action, Style, or Encoding for the operation.

SOAP Action

Yes

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.

For more information about soapAction, see the SOAP specification.

Style

No

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.

Encoding

No

The encoding type for the body of the SOAP input and output messages. This can be either literal or encoded.

Encoded messages support more complex datatypes such as SOAP arrays.

When encoded is specified, you can optionally specify the namespace for input, output, and fault messages.

Input Message Namespace

No

The namespace for input messages.

Output Message Namespace

No

The namespace for output messages.

Fault Message Namespace

No

The namespace for fault messages.