Defining SOAP Message Pipelines
The TDV SOAP data source has a Message Pipeline panel that can be used to configure how request and response messages are handled.
What Happens When a SOAP Message Pipeline is Run
|
1. Create a SOAP request by executing the operation. |
6. The SOAP response message is received from the service side. |
|
2. Message pipelines that are defined as request. |
7. Message pipelines that are defined as response. |
|
3. The SOAP request message is handled according to the SOAP specifications that are defined in the contract. |
8. The SOAP response message is handled according to the SOAP specifications that are defined in the contract. |
|
4. Message pipelines that are defined as request.. |
9. Message pipelines that are defined as response. |
|
5. The SOAP request message is sent to the service side. |
10. The SOAP message is received. |
To define a SOAP Message Pipeline
| 1. | Select the Message Pipeline tab. |
| 2. | Use the green plus buttons to add steps to the Request Message Pipeline or Response Message Pipeline. The following types can be added: |
|
Request Message Step Types |
Response Message Step Types |
|
Add Username Token |
Create Element |
|
Create Element |
Custom |
|
Custom |
Delete Element |
|
Delete Element |
Log Message to File |
|
Encrypt Element |
Process Security Header |
|
Log Message to File |
Set Environment From Node |
|
Set Environment From Node |
Set Node From Environment |
|
Set Node From Environment |
|
|
Sign Element |
|
| 3. | Follow the prompts on the screens for what is required for each of the different step types. |
| 4. | You can delete, edit, and reorder the steps at anytime after adding them. |