Showcase New Feature SAP MII v 15 SP 03 – Plant Connectivity Integration

Applies to- 15.0 SP3 Patch 7

Summary

This document showcases the new feature of Plant Connectivity Integration in MII v15.0

The document takes us step by step showing how to use the Plant Connectivity Integration Functionality Introduced recently.


Table of Content

Introduction to Plant connectivity Integration

Creating/Managing the Notification

Complete Process Flow

Conclusion

Introduction to Plant Connectivity Integration

This feature helps us to configure PCo remotely via MII. SAP MII Administration Menu provides us a new component named Plant Connectivity Integration which contains a notification management tab wherein we can create and manage lifecycle of notification.  This new screen is Fiori based HTML5 client for maintaining PCo notification from MII.

When we click on Notification Management, a new screen opens up showing us tiles for Manage Notification and Browse Notification.


/wp-content/uploads/2015/06/s1_731852.png


Browse Notification helps us to search through various parameters like PCo Data Server, Notification Name, and Status etc. The search functionality is a big help specially when you have created number of notification and you want a quick easy way to reach out to one of notification and edit it. You can even Export/Import, Edit, Pause a notification – all from within MII without even opening PCo console.


Sample Browse Notification Screen

/wp-content/uploads/2015/06/s1_731852.png

Sample Manage Notification Screen


/wp-content/uploads/2015/06/s1_731852.png


Create/Manage the Notification

We will now showcase how to create a notification by clicking Manage Notification (initial screen display as above).

Prerequisite:

  1. We have a PCo DataServer configured and in running status within SAP MII.
  2. PCo Tag Alias already created within PIC for our example.
  3. PCo Notification Destination type should already exist in SAP PCo.
  4. Activate the version-ed notification setting within SAP PCo console. We can find this setting under Tools->Options (Global Properties->Enhancements).

Upon opening the Manage Notification Screen, we will choose a PCo Data Server for which we intend to create a notification. On choosing a Data Server, Create Notification button is enabled on below right side of screen.

*Alternatively, we can click Plant Catalog, choose a tag and click Create Notification.

On click of Create Notification, a pop up asks for a Name and Description of Notification. For our example, we named it TemperatureTag. On providing the same, new screen opens up with tabs like Trigger, Output, Message Delivery, Destination, and Description.


Next, we provide a Trigger Expression for our Notification. For the same, we click on Manage Expression and provide an expression coming from PIC (Plant Information Catalog). For our example, we have mapped a PCo tag to a PIC Tag Alias named Newtag1. We enter an expression as greater than 4000 which is as displayed in screen below.


/wp-content/uploads/2015/06/s1_731852.png


Then we click on Output tab, to provide an Output Expression. We provide an expression mapping it to PIC Alias name Newtag1 and naming expression as NewtagOutput.

Next, we click on Message Delivery, in case we want to change any parameters for Reliability, Failed Messages, Lifetime or bundling of any messages. For our example, we keep everything as default.


Then we click on Destination, for our example we have created a MII destination which we want to map it to out Notification.



/wp-content/uploads/2015/06/s1_731852.png


On click of Add Destination, pop up screen comes up and we define MII Destination as MII_Destination as below.


/wp-content/uploads/2015/06/s1_731852.png


On clicking OK, we map the Transaction Name, Input Parameter and save the notification.


/wp-content/uploads/2015/06/s1_731852.png

As seen in snapshot above, we have various buttons on below right side of screen. Upon click of save – The notification is saved in a Draft state.


Various other buttons include:

Publish to PCo- It will send this notification to PCo which creates it in draft state.

Activate- It will make it activate and start sending the notification.

Pause/Resume- User can pause/resume on any of current notification.


Complete Process Flow

We demonstrated above, how we create a notification from Notification Management from within MII.

Later, we publish it to PCo and it is visible from SAP PCo console as well. Now, we can manage the entire lifecycle ofnotification from MII. We can edit it, activate it so that we can send notifications through, we can pause it, resume it and even delete it. Once we activate it, it starts sending notification to MII which is chosen destination for our example.


PCo Console snapshot showing the Notification which we created from MII screen (in Pause state)


/wp-content/uploads/2015/06/s1_731852.png


If we try to edit it (from within MII), it creates a new version and entire lifecycle of publishing it, activating it, needs to be followed before we receive the notification again.

And now if we search through the notification under Browse Notification tile, it shows our notification which is created from MII as below.



/wp-content/uploads/2015/06/s1_731852.png




Conclusion

The above steps show us how we can create and manage the notification lifecycle all from within MII. And above that, we can even search through all the notifications created and edit them at easy using the latest functionality of Plant Connectivity Integration through Notification Management tab.


Please note:

  1. Only Notification which are created within MII, are visible and available under search functionality.


To report this post you need to login first.

13 Comments

You must be Logged on to comment or reply to a post.

  1. P. de Wilde

    Hi Ruchir,

    I am trying to do the setup you described but i am running into the problem that destination defined in PCO is not appearing in MII. When i query PCo by using the PCo Management Host service webservices i notice that my destination is showing as a system destination, not a MII system destination:

    [INFO] [Tracer_1]<?xml version=”1.0″ encoding=”UTF-8″?><GetDestinationSystemsResponse xmlns=”urn:sap.com:pco.management”>

        <GetDestinationSystemsResult xmlns:a=”urn:sap.com:pco.contracts” xmlns:i=”http://www.w3.org/2001/XMLSchema-instance“>

            <a:DestinationSystemName>

                <a:Description>MII TCX Quality Server</a:Description>

                <a:Name>MII_QAS_QJ2</a:Name>

            </a:DestinationSystemName>

        </GetDestinationSystemsResult>

    </GetDestinationSystemsResponse>

    [INFO] [Tracer_0]<?xml version=”1.0″ encoding=”UTF-8″?><GetMiiDestinationSystemsResponse xmlns=”urn:sap.com:pco.management”>

        <GetMiiDestinationSystemsResult xmlns:a=”urn:sap.com:pco.contracts” xmlns:i=”http://www.w3.org/2001/XMLSchema-instance“/>

    </GetMiiDestinationSystemsResponse>

    Do you have any idea why this is. We are using PCO 15.0 SP05 Patch 6 and MII 15.0 SP05 Patch 3. I do not know where to change this in PCO.

    (0) 
    1. Ruchir Batra

      Hi Wilde,

      If i understood the issue, you are stating that MII destination is not visible during Add Destination …(as below) ,.. then add a simulation destination first (create in PCo and check visibility here) and then try to look for MII Destination.. I remember some issue around it.. not sure on PCo /MII version..and if corrected.. just try it .. it may solve your issue..

      Issue.png

      (0) 
    2. Ria Elezabeth Ninan

      Hi Wilde,

      To be able to add MII destinations using MII Plant connectivity feature, the MII destination pointing to this same MII instance should be created in PCo. This means only the MII destination pointing to the same MII instance will appear in MII Plant connectivity management. Hence, please check if the MII destination(MII_QAS_QJ2) points to the same MII instance from where you are trying to create notifications remotely. If it is, then you should check if you are able to add Simulation Systems.

      Thanks and Best Regards,

      Ria

      (0) 
  2. P. de Wilde

    The initial problem is solved.

    It was not the simulation bug. Ria pointed me in the right direction. Beside needing to have a connection to the correct MII system, it seem i have to use the IP address of the server instead of the hostname.

    But i am running into a new problem when creating a Notification Agent. When i try to publish i get the following error. I am unable to find where i need to set the subscription.

    /wp-content/uploads/2016/02/2016_02_09_101734_883984.jpg

    (0) 
    1. Ria Elezabeth Ninan

      Hi Wilde,

      You donot have to set the subscription item manually. It gets populated by the application based on the tags that you have used in the expression.

      Hence please make sure, that you have an output/Trigger expression which uses a valid PCo tag. Do let us know if you still have issues.

      Thanks and Best Regards,

      Ria

      (0) 
      1. P. de Wilde

        The problem is that we are using PCO for file transfers, to and from a server. And in this case we do not have a tag to subscribe to.

        Normally i would create a source system of type File Monitor Agent, and then create an Agent instance with an underlying notification where i set the destination.

        The original subscription is on AddressRoot / ReceiveDataFileContent (using the browse option under subscription items). The question is whether this is also possible using the SAP MII Page?

        (0) 
        1. Ria Elezabeth Ninan

          Hi Wilde,

          I think in this scenario you could create a PCo data server pointing to the agent instance that you have created in PCo. Then you should be able to use the Tag: AddressRoot/ReceiveDataFileContent in an expression while creating the notification in MII PCoManagement application.

          Based on the datatype of this tag, you could model the expression.

          Thanks and Best Regards,

          Ria

          (0) 
          1. P. de Wilde

            Hi Ria,

            I have tried your suggestion but it is still not working. I am still getting the same error:

            /wp-content/uploads/2016/02/2016_02_10_111921_884781.jpg

            I have tried generating a versioned agents from within PCo but there i get the following error:

            /wp-content/uploads/2016/02/2016_02_10_112149_884810.jpg

            Therefore i am starting to doubt whether or not it is even possible to create the File based notification using the SAP MII PCoManagement application.

            Peter

            (0) 
            1. Ria Elezabeth Ninan

              Hi Wilde,

              From the first screenshot that you have put I think you typed in the OutputExpression and hence it is not in the expected format.. could you please edit the expression and enclose it within [] square brackets like this:

              [AddressRoot / ReceiveDataFileContent]

              I think with this it should work.. If issue still persists you could open a support ticket.


              Thanks and Best Regards,

              Ria

              (0) 
                1. Ria Elezabeth Ninan

                  Hi Wilde,

                  If I understand this correctly, you are getting this error as you have not mapped the PCo tag in MII PIC hierarchy.

                  The Tag that you have used is a valid PCo tag, however you need to map that tag in MII Plant Information Catalog and then use it in the expression editor.

                  If upgrading to MII 15.1 is an option, then you could use PCo tags directly in the output expression without using MII PIC.

                  Thanks and Best Regards,

                  Ria

                  (0) 

Leave a Reply