IBM Support

Data is not exported by the publish channel even if the listener is enabled.

Troubleshooting


Problem

If the listener is enabled for the publish channel, the data is exported when a record for the corresponding object is updated. However, if an automation script is also triggered by the same event, the data is not exported sometimes.

Symptom

You can reproduce the issue with the following steps.
1) From [Object Structures] application, create the following object structure.
Object Structure: TESTOS01
Consumed By: Integration
Support Flat Structure: checked
-Source Objects for TESTOS01
Object: RELATEDRECORD
Parent Object: blank
Object Location Path: RELATEDRECORD
Relationship: blank
Exclude Attributes Mode: unchecked
Object: WORKORDER
Parent Object: RELATEDRECORD
Object Location Path: RELATEDRECORD/WORKORDER
Relationship: RELATEDRECWO
Exclude Attributes Mode: checked
2) Select [Exclude/Include Fields] from More Actions and check the following attributes for WORKORDER object to include.
DESCRIPTION
STATUS
CHANGEDATE
3) Select [Advanced Configuration] from More Actions and check [Propagate Event] for the child object.
4) Create another object structure with the following values.
Object Structure: TESTOS02
Consumed By: Integration
Support Flat Structure: checked
-Source Objects for TESTOS02
Object: WORKORDER
Parent Object: blank
Object Location Path: WORKORDER
Relationship: blank
Exclude Attributes Mode: checked
Object: RELATEDRECORD
Parent Object: WORKORDER
Object Location Path: WORKORDER/RELATEDRECORD
Relationship: RELATEDWO
Exclude Attributes Mode: unchecked
5) Select [Exclude/Include Fields] from More Actions and check the following attributes for WORKORDER object to include.
DESCRIPTION
STATUS
CHANGEDATE
6) Select [Advanced Configuration] from More Actions and check [Propagate Event] for the child object.
7) From [Publish Channels] application, create the publish channel.
Publish Channel: TESTPC01
Operation: Publish
Object Structure: TESTOS01
Adapter: MAXIMO
Interface Table: (BLANK)
Enable Listener: checked
-Object Structure Sub-Records
"Object" "Object Location Path" "Processing Order"
"RELATEDRECORD" "RELATEDRECORD" "1"
"WORKORDER" "RELATEDRECORD/WORKORDER" "2"
8) Create another publish channel with the following values
Publish Channel: TESTPC02
Operation: Publish
Object Structure: TESTOS02
Adapter: MAXIMO
Interface Table: (BLANK)
Enable Listener: checked
-Object Structure Sub-Records
"Object" "Object Location Path" "Processing Order"
"WORKORDER" "WORKORDER" "1"
"RELATEDRECORD" "WORKORDER/RELATEDRECORD" "2"
9) From [External Systems], create the following external system.
External System: EXTSYS
Endpoint: MXFLATFILE
Enabled: checked
Outbound Sequential Queue: jms/maximo/int/queues/sqout
Inbound Sequential Queue: jms/maximo/int/queues/sqin
Inbound Continuous Queue: jms/maximo/int/queues/cqin
10) Add the following publish channels to the external system "EXTSYS".
TESTPC01
TESTPC02
11) From [Automation Scripts], select [Create]-[Create Script with Object Launch Point] and specify the following values.
Launch Point: TESTLP01
Script: TESTSC01
Script Language: jython
Object: RELATEDRECORD
Active: checked
Events: Save
Save: Add/After Save
If the transaction is saved and committed in it by save() or something, the source code can be anything.
12) From [Work Order Tracking], open a Work Order [TESTA].
13) On [Related Records] tab, click [Select Work Orders] and select [TESTB].
14) Confirm the record is exported to a file under FILEDIR directory for the endpoint MXFLATFILE by the publish channel TESTPC01.
15) Confirm the automation script TESTSC01 runs.
16) However, another publish channel TESTPC02 does not fire any events.
Note this issue does not always happen. If it is not reproduced, you can disable and enable the listener for one of the publish channels and try again.

Document Location

Worldwide

[{"Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"ARM Category":[{"code":"a8m50000000CbQzAAK","label":"System Administration-\u003EAutomation Script"}],"ARM Case Number":"TS003677232","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.6.0;7.6.1"},{"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":" ","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}},{"Product":{"code":"SSWT9A","label":"IBM Control Desk"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":" ","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
18 September 2025

UID

ibm16337477

Page Feedback