Software AG Products 10.7 | Integrating On-Premises and Cloud Applications | Integration Cloud | Applications | SOAP Applications
 
SOAP Applications
 
SOAP Applications - Account Configuration Details
SOAP Signature
The SOAP Application enables you to access third party Web Services hosted in the cloud. The SOAP Application uses a WSDL to create consumer operations.
The following features are supported for SOAP Applications:
*A SOAP Application implementation follows the WS-I Basic Profile 1.1 specification.
*SOAP Applications can be created by uploading a WSDL file or by using a valid WSDL URL that can be accessed over a network.
*SOAP Applications can be created with WSDLs that are annotated with WS-Security Policy/Policies.
*SOAP Applications with SOAP version 1.1 and 1.2 and Style/Use as Document/Literal and RPC/Literal (RPC/Encoded model is not supported for SOAP version 1.2).
*The following SOAP Binding types are supported:
*SOAP over HTTP.
*SOAP over HTTPS.
*Authentication type: HTTP Basic Token.
SOAP Applications have the following restrictions:
*The WSDL and associated schema(s) must be accessible through a publicly or locally accessible URL.
*Only WSDLs with WS-Security policies are supported. Any other policies, for example, WS-Addressing, WS-Reliable Messaging, and so on, are not supported. If you create SOAP Applications with WSDLs having non-WS-Security Policies, exceptions may appear while executing Integrations.
*Manual addition of WS-Security Policies in a SOAP Application is not supported. SOAP Applications with WS-Security can be created with only policy-annotated WSDLs, that is, WSDLs that already have WS-Security Policies annotated in them.
*SOAP over JMS is not supported.
*Only Basic Authentication is supported. Other authentication types such as Digest, NTLM, and Kerberos are not supported.
*You will not be able to attach or upload a file while executing an Integration.
*To add a SOAP Application
1. From the Integration Cloud navigation bar, click Projects > <Select a Project> > Applications > SOAP Applications > Add New Application.
2. Provide a name and description of your SOAP Application. The description you enter here will appear in the SOAP Applications page. Required fields are marked with an asterisk on the screen.
3. Click Browse next to the Application Icon if you want to select a different icon for your SOAP Application. The icon must be a PNG file and the size cannot exceed 50 KB, else the default image is displayed.
4. Click Next and specify the WSDL Source.
*Select URL if you want to specify the URL of the WSDL. The URL should begin with http:// or https://. The URL is used to retrieve the WSDL for the SOAP Application.
*Select File and then click Browse if you want to select the WSDL from your local file system. The size of the WSDL cannot exceed 5 MB. You can click the icon beside the Browse button if you want to add separate elements of a service definition after import, such as WSDLs or XSDs, to the primary WSDL.
Note:
Ensure that you add the primary WSDL as the first WSDL, and then add separate elements of the service definition, for example, dependent WSDLs and XSDs to the primary WSDL.
5. Enter the user name and password in the Authentication section if authentication is required to access the WSDL URL.
6. Click Next to review the details you have entered.
7. Click Finish to create the SOAP Application.
Editing SOAP Applications
From the SOAP Applications page, click the SOAP Application link, and then click Edit Application. You can change the Description and the Application Icon.
In the Application details page, Update WSDL section, select No, keep existing WSDL if you do not want to modify the WSDL URL or the WSDL file. Select Yes, override WSDL if you want to specify a new WSDL URL or upload a new WSDL file in the WSDL Source section.
Confirm the updated Application. After you click Finish, the Update SOAP Application window appears, which provides a summary of the impacted Accounts, Operations, and Integrations. Click Update to update the SOAP Application. Updating the WSDL may result in addition or removal of Operations or fields in the Input/Output signature of an Operation. This may lead to incorrect mappings if you have used that Operation in an Integration. To delete a SOAP Application, click Delete Application.