You can use a Web service interface in a transaction to do the following:
Allow third-party applications to call functions using Simple Object Access Protocol (SOAP) over HTTP.
Read inputs and outputs using the Web Service Definition Language (WSDL) that is automatically generated based on the transaction's configuration.
You can return the WSDL using a Uniform Resource Identifier (URI). The format of the URI is http://<servername>/XMII/WSDLGen/<TransactionFolder(s)>/<Transaction>. For example, if you have a transaction named Line1OEE in a KPI folder, and your server's name is Atlantis, the URI is http://Atlantis/XMII/WSDLGen/KPI/Line1OEE.
The WSDL includes a definition of the inputs to the transaction and the output from the transaction, which is in SAP Manufacturing Integration and Intelligence (SAP MII) XML format. This WSDL can be used in external applications such as Enterprise Application Integration (EAI) software or development tools like Visual Studio .NET, Java environments, and so on, to call functions in the SAP MII Workbench.
The input parameter data structure includes authentication credentials that must be provided with the inbound request. The user name and password must have runtime permission on the SAP MII server.
If a transaction has input parameters that are XML data types, you can specify an XSD and element to validate the structure when the system receives a transaction call. If the transaction is called from a Web service using the WSDLGen interface, the specified XSD exposes the XML structure in the WSDL. If the transaction is called from a Web service, you can also specify the XSD and element for output parameters to expose the output structure in the WSDL.
The system sends all SOAP requests to the SOAPRunner interface.