KB 069 – PowerConnect JAVA Disabling PI Message collection

KB 069 – Disabling PI message collection

Symptom:

NW is caching the UI component so when upgrading from .24 to .26 the UI is still expecting 18 operations from the WSDL but we’ve added a further 4 in the new version so there’s a mismatch. Forcing the service group to be re-processed fixes this because it seems to invalidate whatever cache is storing the UI config

Solution:

  1. Open the PowerConnect java control panel http://<server>:<port>/webdynpro/resources/com.powerconnect5/spcj_wd/SapPowerConnectJava#
  2. Uncheck the PI Monitoring Enabled

    3. KB 069 - PowerConnect JAVA Disabling PI Message collection 1

  3. Restart the java agent and this will stop the collection of PI message payload and processing logs
  4. Uncheck the Channel Monitoring Enabled

    5. KB 069 - PowerConnect JAVA Disabling PI Message collection 2

  5. Restart the java agent and this will stop the monitoring of the channel status
  6. If you want to keep the message monitoring enabled but disable the collection of the payload or processing logs this can be achieved in the

    7. KB 069 - PowerConnect JAVA Disabling PI Message collection 3

  7. Uncheck the Collect message logs will disable the collection of all message logs.
  8. Uncheck the Collect message payload to disable the collection of all PI message payload (the actuall PI message contents).
  9. If you wish to setup a filter for specific messages

    10. KB 069 - PowerConnect JAVA Disabling PI Message collection 4

  10. Setting the filters to NOT_CONFIGURED is the equivalent of ‘*’ or match all patterns.
  11. If there is an Advanced filter set then it overrides the Simple Filter settings

    12. KB 069 - PowerConnect JAVA Disabling PI Message collection 5

  12. To set the Advanced Filter then create an .xml file with the following structure and upload it using the [upload] button then activate it using the [import] button.

    <?xml version=”1.0″ encoding=”UTF-8″?>

    <PIFilters>

    <PIFilter>

    <direction>INBOUND</direction>
    <interfacename></interfacename>
    <namespace></namespace>
    <messagetype></messagetype>
    <onlyfaultymessages>false</onlyfaultymessages>
    <receivername>TESTREC</receivername>
    <receiverparty>TESTPARTY</receiverparty>
    <sendername></sendername>
    <senderparty></senderparty>
    <status></status>

    </PIFilter>

    </PIFilters>

  13. If you want multiple filters then duplicate the </PIFilter> </PIFilter>section like this

    <?xml version=”1.0″ encoding=”UTF-8″?>

    <PIFilters>

    <PIFilter>

    <direction>INBOUND</direction>
    <interfacename></interfacename>
    <namespace></namespace>
    <messagetype></messagetype>
    <onlyfaultymessages>false</onlyfaultymessages>
    <receivername>TESTREC</receivername>
    <receiverparty>TESTPARTY</receiverparty>
    <sendername></sendername>
    <senderparty><senderparty>
    <status></status>

    </PIFilter>

    <PIFilter>

    <direction>OUTBOUND</direction>
    <interfacename></interfacename>
    <namespace></namespace>
    <messagetype></messagetype>
    <onlyfaultymessages>true</onlyfaultymessages>
    <receivername>TESTREC2</receivername>
    <receiverparty></receiverparty>
    <sendername>TESTSEND</sendername>
    <senderparty><senderparty>
    <status></status>

    </PIFilter>

    </PIFilters>

    Download PDF version here