Assignment of Web Service Call as Destination of a Notification

Using the Web Service Destination System

You can now use the configured universal Web service destination system as the destination of a notification. You have the following options:

• You call the universal Web service destination system directly if you want to call the MII transaction synchronously.

• If you embed the Web service call with the MII transaction in a multiple call destination system, you can make error handling more flexible and allow the transaction to be called in the context of other process steps.

• By calling an asynchronous OPC UA method, you can configure the call of the MII transaction asynchronously. See: Configuring an Asynchronous Transaction Call.

Appropriate output expressions are now assigned to the variables of the input parameters of the destination system. At runtime, the parameters of the MII transaction are then supplied with the values of the output expressions.

Compatibility with Previous MII Transaction Calls

If you have already developed transactions in SAP MII that you previously called using the MII destination system, you can still call this transaction using PCo, without having to make changes to the transaction in MII.

The XML document sent from the MII destination system then supports inbound processing of the MII transaction. Parsing is performed to extract the transaction parameters from the XML message.

For the transaction call using the universal Web service destination system, you only have to maintain a single input variable in which the XML document is to be received. When assigning the notification output to the inbound parameters of the Web service destination system, you can select the special output value ~NotificationOutputInXMLFormat. At runtime, it contains the output of the notification in XML format, just as it is also generated by the MII destination system. Assign this expression to the only inbound parameter of the Web service destination system.

The special output expression ~NotificationOutputInXMLFormat is also available when you configure multiple call destination systems and OPC UA destination systems.