Provision as SOAP web service

This article describes the technical provision of the SOAP web service.

Scope of supply

The definition of the Conigma web service and the implementation of the associated methods are included in the scope of delivery of Conigma CCM. However, the binding for the actual provision must be set up locally on the corresponding SAP system. The steps necessary for this are described below.

Activation of Services in ICF

In addition to the services required to execute transaction SOAMANAGER, the following services must be started in transaction SICF:

/default_host/sap/bc/soap/rfc

/default_host/sap/bc/srt/rfc/gal (recursive)

/default_host/sap/bc/srt/wsdl

Creating a Binding

For the external accessibility of the Conigma SOAP API, an appropriate binding must be created in transaction SOAMANAGER. The following description shows an example of the procedure based on SAP Release 7.31. Depending on the SAP Release used and the required security settings, the procedure may differ. If necessary, read the appropriate SAP documentation for your SAP release.

Starting the SOA Manager

Start the SOA Manager using the transaction code SOAMANAGER. The web interface of the SOA Manager is started in a separate browser window.

Creating a Service Binding

On the initial screen of the SOA Manager, choose "Web Service Configuration".

In the search mask that now appears, enter the pattern "/GAL/CCM*" for the object type and then click the "Search" button.

The search result now shows the web service /GALCCM_SOAP_API. A click on the entry changes to the configuration page. Click here on the button "Create Service" to start the wizard for creating a binding.

In the first step, specify the service name and the binding name. Then click on "Next".

In the next step you can configure the security settings. If you want to use the HTTPS protocol, please make sure that the required certificates are installed and that a corresponding server process has been configured. For more information, see the SAP documentation.
Make sure that the "User ID and Password" option is enabled in the Transport Level Authentication section. This setting activates authentication using Basic Authentication. You can use the user ID and password of an SAP user known on the current client.
Click on the "Next" button to go to the next step.

Next are some settings for the SOAP protocol. As a rule, these do not have to be changed. Click the "Next" button to go to the last step of the wizard.

Close the wizard by clicking the"Finish" button." off. You return to the configuration overview and the newly created binding is displayed.

Generating the WSDL

The generation of the WSDL for the Web service Consumer can be started using the following button:

In the following dialog box, you can specify the required options for WSDL generation. Then click on the button marked red in the following picture to generate and display the WSDL.

The generated WSDL is now displayed in its own browser tab and can be saved from there. The URL of the WSDL is also static and can be used to import the service definition into other systems. Please note, however, that support for the "Basic authentication" type is required.