Kepserverex v6 example
In destination, we attach MCall and map the inputs. These are then mapped to WSCall and WSCall2 respectively.įor our showcase, we created a Tag Based Notification- TurnNotif with Trigger Expression as ‘DontTurn’ and output as TurnLeft and TurnRight. We assign the constant value of 2 to output variable outVar1 and constant value of 5 to temporary variable tempVar1. In next steps 20 and 30, we add WSCall and WSCall2 destination system to it (and assign input variables to it). The assignment is done for Tags (TurnLeft, TurnRight). In first step, step 10, TagStore destination is setup. Later, Create Request Message is setup and Service is tested.Īt last, the Multiple Call Destination System (MCall) is setup. WSDL URL and Basic Authentication is set. Web Service Destination System WSCall and WSCall2 are created. Hence, two different destination type /different services are created. Intention of using two different destinations is to showcase that based on branching condition call in SAP PCo, different destinations can be called. Through these, we send constant value back to SAP MII for further processing as per the use case. Second and Third Destination Type are Web Service Destination System. We define the Agent Instance to it and write back tag values to Kepware Tags (TurnLeft, TurnRight) via this.
KEPSERVEREX V6 EXAMPLE HOW TO
In each case, MII transaction is called and constant is passed to it.Īssuming how to create Source (Kepware – OPC DA Source) is known by everyone, we just highlight it and don’t go into its details.Īssuming how to create an Agent Instance is known by everyone, we just highlight it and don’t go into its details.Īgent Instance called KepIns (Kepware Instance) is created and subscription Items are added as below.įor our showcase, we created four destination systems.įirst one is Query Destination System called TagStore. If true, execution goes to step 20 else to step 30. Then, we define a branching condition to check for condition if TurnLeft value is greater than 7. In multiple call destination, we first make TagStore call which passes the value 0 to Kepware Tags TurnLeft and TurnRight. Also, we push the constant value (say last displacement value for our use case ahead) to SAP MII via web service call. In our example, as soon as DontTurn is turned ON (value is 1, under Notification Type OnTrue), we make the TurnLeft and TurnRight OFF (value to 0). For the same, we have setup three tags such as DontTurn, TurnLeft, TurnRight which define the device movement. Universal Web service destination systemįor our showcase example, we have setup our Source as Kepware which has a Channel called Plant and a device called RotatorArm within it.You can call the following types of destination systems from a multiple call destination system: Additionally, you can add exceptional handling and branching condition in each step. You can create a sequence in which different destination systems can be called. For this, a new destination system type is added within PCo called Multiple Call Destination system. This feature helps us to configure multiple PCo Destination systems in a configurable sequence within SAP PCo.
Introduction to Plant Connectivity – Multiple Call Destination System Introduction to Plant Connectivity Multiple Call Destination System The document takes us step by step showing how to use the Plant Connectivity Multiple Call Destination System to connect to Kepware and MII for our showcase. This document showcases the new capability of Plant Connectivity – Multiple Call Destination System. Showcased Example Tested via SAP PCo 15.1 (15.), SAP MII 15.1 SP6, Kepware v6.1 Showcase a Feature SAP PCo – Multiple Call Destination System