SOAP Service Binding
Use SOAP service binding to create a service provider.
Binding
This section has the following fields.
Field | Description |
---|---|
Name | The name of the service binding. |
Description | A short description of the service getting exposed. |
Target Namespace | The Target Namespace of the service. |
Expose Security Context | Selecting this option exposes the transport level security context in the message header, and places the information from the user's security context (either authentication or SSL certificate information) into the Context or SecurityContext output element.
Note: This is a fairly expensive operation and SSL certificates can consume memory resources. Select this option only if you require information from the user's security context for later use in your process.
|
Generate Concrete WSDL
The SOAP service binding helps you to create the concrete WSDL using Concrete WSDL Generation Wizard. For more information, see Generating Concrete WSDL.
SOAP Default Configuration
This section has the following fields.
Field | Description |
---|---|
SOAP Version | The version of the SOAP specification: 1.1 or 1.2. The default is 1.1. |
Style | The default SOAP binding style for all operations. Specify either Document or RPC style. |
Encoding | Encoding is literal. |
Attachment Style | Select the default attachment style for all the binding operations. Can be overidden at the operations level for each operation.
The following attachment styles are available:
|
Persistence Configuration
This section has the following fields.
Field | Literal Value/Module Property | Description |
---|---|---|
Persistence Type | None | Select either the NONE or File (Directory, Create Directories, and Threshold Size fields) persistence configuration types. |
Directory | Yes | This is the directory where attachments are serialized. |
Create Directories | Yes | Creates new directories if not present on the disk. |
Threshold Size | Yes | The maximum size of the attachment that can be kept in memory. Attachments larger than the specified size are written to the disk. The file name generated for serialization is random except when the Content-disposition header is available for the attachment. Here, the name is the same as the content-disposition header value.
Configure the size to Bytes, KB or MB. |
Threading Policy Details
The following are the details for the SOAP Service Binding threading policy.
Activity Type | Multi-Threaded? | Default Thread Count | Thread Count Configuration |
---|---|---|---|
Transport: HTTP | |||
ProcessStarter | Yes |
|
It can be configured on the
HTTP Connector shared resource using the following fields:
|
Add Binding
Click the
Add Binding icon to add a binding.
Delete Binding
Click the Delete Binding icon
to delete a binding.