Troubleshooting
Problem
An event for an object structure’s primary object is fired, however the object passed through to the associated Publish Channel is a different object name.
Cause
This situation occurs in the cases where one object is a VIEW of another object.
Diagnosing The Problem
Integration Framework Publish Channels rely on object events to trigger the sending of an outbound message to an external application. The primary (top) object of the channel’s object structure is the object that events are being monitored.
There is a current situation where an event for the object structure’s primary object is fired, however the object passed through to the publish channel is a different object name. This situation occurs in the cases where one object is a View of another object. The most common cases are:
· WOACTIVITY being a view of WORKORDER
· SR, INCIDENT, PROBLEM being a view of TICKET
· TOOLITEM being a view of ITEM
What occurs is that an event, for example for WORKORDER, is fired and that starts the processing of a WO-related Publish Channel, but the object passed through to the channel is a different one, for example WOACTIVITY. One way this situation occurs is if a user updates an Activity using the Wotrack application rather than the Activity application. Depending upon the configuration of processing rules in the channel or code within a custom java exit, the processing may hit an error because the MBO being processed (WOACTIVITY) does not match the one defined in the Channel’s object structure (WORKORDER).
Resolving The Problem
In the case your Publish Channel based integration scenario is hitting processing errors you can configure the provided Event Filter class on the channel. This class will perform a comparison of the object in the message versus the primary object in object structure and when the two values do not match, the message will be skipped (no message sent out through the channel).
To implement this new class, you will need to include this class file in the Maximo EAR file and restart the application using the application server console. You also need to configure the file name in the Event Filter Class field on those active publish channels that are listener enabled, and have this issue listening to events for different view based objects. The same class can be used on any channels where needed.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21649874