...
The Bridge also has a "Simple Object Access Protocol" (SOAP) adapter ready. SOAP is a lightweight protocol for the exchange of information in a decentralized, distributed environment. SOAP is an XML language, which is commonly transported in HTTP packages.
The SOAP adapter enables you to use any other Web Service as backend for the Bridge. Instead of getting data via SQL from a database, the SOAP adapter sends a request to the other Web Service and gets back a SOAP response message. This message is then mapped to data items, similar to the process described in the chapter on database adapters.
Today, there are already many services, which speak SOAP. You may also have several Bridge services that speak together via SOAP (for instance as part of a Software Oriented Architecture (SOA) environment).
| Noteinfo |
|---|
|
The Bridge supports SOAP version 1.1 . | Version |
|---|
| - Added in Builder 5.1.8.56
- Runtime 5.1.82.1
|
Support of for RPC encoded services and SOAP version 1.2 for document-literal encoded services. |
...
Component Diagram of a Service Using the SOAP Adapter
...
...
Added in Builder 6.0
...
The physical definition, meaning which Bridge will fulfill this operation, is done in the component diagram on the SOAP alias. To make a link from the SOAP-call in the activity diagram to the corresponding component diagram the tagged value alias has to be used.
...
| Multiexcerpt |
|---|
| MultiExcerptName | soap_tagged_values |
|---|
|
| Tagged Value | Description | Allowed Values |
|
|---|
| SOAP | | messageFormat | Defines the formatting of the SOAP message. | None | no linebreaks and no indentation | | Linebreaks (default) | linebreaks, but no indentation | | Indentation | linebreads and indentation | | sendTransactionID | Defines whether the transaction ID is sent in the a SOAP header element <TransactionID>...</TransactionID> with namespace http://e2e.ch/bridge.
If sent, the calling and the called service can be identified to belong to the same transaction. | false | transaction ID is not sent in the SOAP header element | | true (default) | transaction ID is sent in the SOAP Header element | | sendCorrelationID | Defines whether the correlation ID is sent in the a SOAP header element <CorrelationID>...</CorrelationID> with namespace http://e2e.ch/bridge .
The correlation ID is used to identify each SOAP call. | false | correlation ID is not sent in the SOAP header element | | true (default) | correlation ID is sent in the SOAP header element | | Advanced | | followRedirects | Maximum number of redirects to follow. | any integer | |
| timezone | | Multiexcerpt include |
|---|
| MultiExcerptName | timezone |
|---|
| nopanel | true |
|---|
| PageWithExcerpt | SOAP Service Components |
|---|
|
| Version |
|---|
| Added in Builder 5.1.8.38Runtime 5.1.77.0 | | Multiexcerpt include |
|---|
| MultiExcerptName | timezone_examples |
|---|
| nopanel | true |
|---|
| PageWithExcerpt | SOAP Service Components |
|---|
|
| | dateFormatString | | Multiexcerpt include |
|---|
| MultiExcerptName | dateFormatString |
|---|
| nopanel | true |
|---|
| PageWithExcerpt | SOAP Service Components |
|---|
|
| Version |
|---|
| Added in Builder 5.1.8.38Runtime 5.1.77.0 | | Multiexcerpt include |
|---|
| MultiExcerptName | dateFormatString_examples |
|---|
| nopanel | true |
|---|
| PageWithExcerpt | SOAP Service Components |
|---|
|
| | options | Specify native cURL options as listed in Setting cURL Options on the URL Adapter.
Also refer to this page for more details on how to set these options. | Example: CURLOPT_TIMEOUT=20 | soapVersion
| Specify the SOAP version used with this SOAP call | Version |
|---|
Added in Builder 6. 0 | 1.1 (default) | use SOAP version 1.1 | | 1.2 | use SOAP version 1.2 | |
...
| Multiexcerpt include |
|---|
| MultiExcerptName | soapUseSecureHelloWorldAdvancedExample |
|---|
| nopanel | true |
|---|
| PageWithExcerpt | INTERNAL:_examples_BRIDGE |
|---|
|
| Noteinfo |
|---|
|
The Bridge uses in his services SOAP RPC encoding for operations of a SOAP port type interface. The SOAP document-style encoding (also known as document-literal encoding) is also supported and can be chosen by selecting the stereotype <<DocumentEncoding>> on these port type operations. You can find more information about SOAP encodings in Encoding of SOAP Operations. |
SOAP Adapter Components and Deployment of
...
Builder Version 5.1
...
...
Deprecated since Builder 6.0
| Expand |
|---|
| title | Click here to read the documentation of the component and deployment diagram used in E2E Builder releases before 6.0 ... |
|---|
|
The operation defined in the WSDL file is specified in the operation property in the SOAP adapter node.
The physical definition, meaning which Bridge will fulfill this operation, is done in the deployment diagram. To make a link from the SOAP-call in the activity diagram ... 
... to the corresponding component diagram the tagged value alias has to be used. 
The alias-linked backend service artifact from the component diagram hold in the deployment diagram the location to the web service server, which supplies the "getExchangeRate" service. 
|