Advanced SOAP Settings
For each operation, you can specify advanced configuration options. To access the advanced configuration options, perform the following:
-
Select Partner Link.
-
Select the operation.
The Advanced SOAP Settings dialog appears. The following sections describe the tabs on this dialog.
Input Headers
The Input Headers tab allows you to specify a SOAP message parts used for any SOAP Undescribed headers expected in the Outgoing Request.
Use the +, X, and arrow keys to add, delete and move the input header messages in the list.
The Input Headers tab has the following fields.
Field |
Description |
Part Name |
This field contains a drop-down list with all parts of the specified SOAP message. You can specify a cardinality for the part, if applicable. |
Message Name |
The message in a WSDL file to use as the Undescribed input header for the outgoing 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. |
Undescribed |
Select this check box to declare the header as Undescribed header. |
Cardinality |
This field contains a drop-down list with two options: Repeating and Optional. |
Output Headers
The Output Headers tab allows you to specify a SOAP message part used for any SOAP undescribed headers expected in the Incoming Response.
Use the +, X, and arrow keys to add, delete and move the input header messages in the list.
The Output Headers tab has the following fields.
Field |
Description |
Part Name |
This field contains a drop-down list with all parts of the specified SOAP message. You can specify a cardinality for the part, if applicable. |
Message Name |
The message in a WSDL file to use as the undescribed output header for the SOAP incoming response. 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. |
Undescribed |
Select this check box to declare the header as Undescribed header. |
Cardinality |
This field contains a drop-down list with two options: Repeating and Optional. |
Input Context
The Input Context tab allows you to specify a Context Resource that contains transport-specific data. The data you provide to the context resource is available to the process definition that implements the operation.
The Input Context tab has the following fields.
Field |
Description |
Context |
The Context Resource that specifies the schema you want to use. The schema of this resource should include elements for each data element you want to provide to the output Headers for the message. |
Mapping Panel |
The mapping panel is similar to the mapping panel provided in the Input tab of activities. This panel allows you to map transport-specific information. Using this you can send the information as part of the Undescribed header in a SOAP Request message to the Service. The mapping panel appears only when a Context resource is specified in the Context field. |
inputMessage |
The root class for the input of the SOAP Request Reply activity. This class contains all input items for the activity. If this is a document request, the input is named inputMessage. If the request is an RPC, the input is the name of the operation. |
Transport Properties - HTTP |
|
Headers |
|
Accept |
This field specifies media types that are acceptable for response messages for the incoming request. For example, If no Accept header field is present, then it is assumed that the client accepts all media types. |
Accept-Charset |
This field specifies the character sets that are acceptable for response messages for the incoming request. For example, iso-8859-5, unicode-1-1. Character sets are described in the HTTP specification. If no Accpet-Charset header is present, then it is assumed that the client accepts any character set. |
Accept-Encoding |
This field specifies the content-coding values that are acceptable for response messages. For example compress, gzip. For more information about this header field, see the HTTP specification. |
Cookie |
For more information about this field, see the HTTP specification. |
Pragma |
This field is used to include implementation-specific directives that might apply to the receiver. For more information about using this field, see the HTTP specification. |
undescribed Headers |
|
Authentication Credentials |
|
user name |
Username for logging into the HTTP server. This overrides the value specified in the Identity resource. Note: You can override the user name only if the activity is configured for Basic or NTLM authentication.
|
password |
Password for logging into the HTTP server. This overrides the value specified in the Identity resource. Note: You can override the password only if the activity is configured for Basic or NTLM authentication.
|
domain |
Domain for logging into the HTTP server. This overrides the value specified in the configuration. Note: You can override the domain name only if the activity is configured for NTLM authentication.
|
Output Context
The Output Context tab allows you to specify a Context Resource that contains data the process definition implementing the operation has provided. The data can then be mapped to Undescribed Headers of the output message returned to the client.
The Output Context tab has the following fields.
Field |
Description |
Shared Context |
The Context Resource that specifies the schema you want to use. The schema of this resource should include elements for each data element you want to provide to the output Undescribed Headers for the message. |
Expose Security Check box |
Selecting this check box meant for Security Context Propagation and Security Context, makes it available as a transport data in the mapping panel. |
Mapping Panel |
The mapping panel is similar to the mapping panel provided in the Input tab of activities. This panel allows you to map Input Context data provided by the implementation of the operation to the transport-specific Undescribed headers of the reply message sent to the client. The mapping panel appears only when a Context resource is specified in the Context field. |
outputMessage |
The root class for the output of the SOAP Request Reply activity. This class contains all output items for the activity. If this is a document request, the output is names outputMessages. If the request is an RPC, the output is the name of the operation with "Response" appended. |
mimeEnvelopeElement |
This element contains the reply message attachments when mime attachments are used. This element contains a repeating element named mimePart that contains each mime attachment. |
mimeHeaders |
This element contains the mime header for each mimePart. Mime headers can contain the following information:
Note: When the content type is specified as "text/*" (for example, "text/xml"), the attachment content is expected to be in either the textContent input element or the file name storing the attachment is expected to be in the fileName input element. When the content type is anything other than "text/*", the attachment content is expected to be in either the binaryContent input element or the file name storing the attachment is expected to be in the fileName input element.
|
binaryContent |textContent |fileName |
This element contains the mime attachment. The element can be one of the following:
|
Transport Properties - HTTP |
|
Headers |
|
Allow |
This field lists the set of methods supported by the resource identified by Request URI. |
Content-Type |
This field indicates the media type of the entity body for the outgoing message and the incoming response. Media types are described in the HTTP specification. An example of the media type is |
Content-Length |
This field indicates the size of the entity body (in decimal number of OCTETs) of the response message. |
Content-Encoding |
This field is used as a modifier to the content-type. When present, its value indicates what additional content encodings have been applied to the entity-body, and thus what decoding mechanisms must be applied in order to obtain the media-type referenced by the Content-Type header field. Content-Encoding is primarily used to allow a document to be compressed without losing the identity of its underlying media type. For more information about this field, see the HTTP specification. |
Date |
The date and time when the response message was sent. |
Location |
This field is used to redirect the receiver to a location other than the Request-URI for completion of the request or for identification of a new resource. |
Set-Cookie |
For more information about this field, see the HTTP specification. |
Pragma |
This field is used to include implementation-specific directives that might apply to the receiver. For more information about using this field, see the HTTP the HTTP Specification. |
Fault Context
The Fault Context tab allows you to select a shared Context Resource that is set with SOAP fault attributes. The data can then be mapped to Fault elements of the Fault message returned to the client.
The Fault Context tab has the following fields.
Field |
Description |
Context |
The Context Resource that specifies the SOAP fault schema you want to use. The schema of this resource should include elements for each data element you want to provide the Fault elements for the fault message. Note: For Fault Context propagation you must map Fault elements to the Context data.
|
Expose Security Context |
Selecting this check box meant for Security Context Propagation and Security Context, makes it available as a transport data in the mapping panel. |
Mapping Panel |
The mapping panel is similar to the mapping panel provided in the Input Context tab of activities. This panel allows you to map data provided by the implementation of the operation to the transport-specific Undescribed headers of the reply message sent to the client. The mapping panel appears only when a Context resource is specified in the Shared Context field. The Transport Data shows the Global Variables and the Context Data shows the Context resource element. |