Advanced

The Advanced tab contains the following fields:

Field

Description

General Sub-Tab

Service URI

The Service URI portion of the URL that can be used to retrieve the WSDL file. For clients to retrieve WSDL files from ActiveMatrix BusinessWorks, you must define a process definition that accepts HTTP requests and uses the Retrieve Resources activity to generate the WSDL file. For more information, see Using Retrieve Resources on page 628.

The URL to retrieve WSDL files is the following:

http://<host>:<port>/<serviceURI>?wsdl

where <serviceURI> is the value in this field.

SOAP Action

The soapAction that is expected from incoming SOAP requests. For more information about soapAction, see the SOAP specification.

WSDL Namespace

The namespace for the concrete WSDL file specified by this activity.

Style

The SOAP binding style. You can specify either Document or RPC style.

Encoding

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

The namespace for input messages.

Output Message Namespace

The namespace for output messages.

Fault Message Namespace

The namespace for fault messages.

Embed Interface

When checked, specifies that all referenced WSDL files should be included inline in the concrete WSDL file. Otherwise, all referenced WSDL files are imported.

Embed Types

When checked, specifies that all referenced XSD files should be included inline in the concrete WSDL file. Otherwise, all referenced XSD files are imported.

Embed JNDI Properties

When checked, specifies that JDNI properties should be included inline in the service specification in the WSDL Source tab.

Input Attachments Binding Sub-Tab

Mime Content Type

The table containing this column allows you to specify the mime content type of each message part. This is especially useful for describing parts that contain attachments. For more information on the valid syntax of the content type, see the mime specification.

If specified, the content type appears in the WSDL for the specified part.

Use the X, +, and arrow keys to delete, add, and move parts in the list.

Message Part

The message part that you would like to specify the content type for. This field is a drop down list of message parts.

Write to File

Checking this field specifies that incoming messages whose attachments exceed the specified threshold size should be written to a file instead of stored in memory. This allows you to accept large incoming attachments without consuming a great deal of memory. When this field is checked, the Directory and Threshold Size fields appear.

Leaving this field unchecked specifies that attachments of incoming messages should be kept in memory.

Once written, the files created by using this option are not deleted automatically. You must manage the storage used by these files and delete them when they are no longer used.

Although Write to File exists for SwA and MTOM, Soap over JMS completely depends on the heap size configuration as JMS specifications do not support writing JMS messages in parts as is the case with Soap over HTTP, which can be written over wire in parts. Hence, writing large JMS messages to JMS after configuring Write to File, completey depends on the Heap size.

Directory

The directory to write attachments that are above the specified threshold. The process engine does not attempt to create the directory if the specified directory does not exist. Therefore, create the directory before starting the process engine.

Create Non-Existing Directories

When checked, all directories in the path specified in the Directory field are created, if they do not already exist.

If this field is unchecked and there are one or more directories in the specified path in the Directory field that do not exist, an exception is raised.

Threshold Data Size (bytes)

The maximum size (in bytes) of an incoming message attachment that can be kept in memory. Attachments larger than the specified size are written to a file in the specified directory. The file’s name is output so that subsequent activities in the process definition can access the file and read its contents.

Specifying zero (0) in this field causes all incoming messages to be saved to a file.

Output Attachments Binding Sub-Tab

Attachment Style

This field allows you to choose the attachment style for the outbound/response messages. Two attachment styles are available: SwA and MTOM.

Mime Content Type

The table containing this column allows you to specify the mime content type of each message part. This is especially useful for parts that contain attachments. For more information on the valid syntax of the content type, see the mime specification.

If specified, the content type appears in the WSDL for the specified part.

Use the X, +, and arrow keys to delete, add, and move parts in the list.

Message Part

The message part that you would like to specify the content type for. This field is a drop down list of message parts.

Input Headers Sub-Tab

The Input Headers sub-tab allows you to specify a SOAP message parts used for any SOAP headers expected in the incoming request. The specified input headers are also included in the concrete bindings in the generated WSDL file.

When an incoming request supplies a header, the SOAP Event Source process starter places the information contained in the header into the output process variables for the SOAP Event Source. The header information is then available to subsequent activities in the process definition.

Use the +, X, and arrow keys to add, delete and move the input header messages in the list.

Message Name

The message in a WSDL file to use as the input header for the incoming SOAP request. This WSDL file does not have to be the same as the file used for output headers or the file used to configure the port type and operation of the incoming request.

Use the Browse button in this field to search for valid WSDL File resources and to select the desired message in the WSDL File.

Part Name

This field contains a drop down list with all parts of the specified SOAP message. You can specify a namespace or encoding for the part, if applicable.

Binding

Binding used for the part. This field must be "soap".

Ouput Headers Sub-Tab

The Output Headers sub-tab allows you to specify a SOAP message parts used for any SOAP headers expected in the outgoing reply. The specified output headers are also included in the concrete bindings in the generated WSDL file.

Use the +, X, and arrow keys to add, delete and move the input header messages in the list.

Message Name

The message in a WSDL file to use as the output header for the SOAP request. This WSDL file does not have to be the same as the file used for input headers or the file used to configure the port type and operation of the incoming request.

Use the Browse button in this field to search for valid WSDL File resources and to select the desired message in the WSDL File.

Part Name

This field contains a drop down list with all parts of the specified SOAP message. You can specify a namespace or encoding for the part, if applicable.

Binding

Binding used for the part. This field must be "soap".