Hi Steven,
This is solved now. There was a publish channel script which was inactive, but referenced in the PC. Once we remove that reference, the message looks correct although the reason behind this is not known now. But the same setting produced the correct message in 7612.
------------------------------
Subhransu Sekhar Sahoo
Tata Consultancy Services
------------------------------
Original Message:
Sent: 04-07-2023 09:12
From: Steven Shull
Subject: Outbound Integration Message Change in 7.6.1.3
I assume you are using an automation script and calling the exportData method of the MicService? I'm not sure if this is an intended change or not so you'd need to open a support case to get confirmation. The original structure doesn't make a lot of sense in a normal publish channel scenario so I'm thinking it is intended. This information is returned on REST API requests because you may have an interactive application using pagination and your application may need to see information like the number of records that match the criteria, what the next and previous page URLs are, etc. But on an integration where requests may be split into multiple transactions it doesn't make as much sense because this information is likely to just be discarded.
The bulk data export was added to support the initial sending of data to an external system in a controlled fashion with error handling. For example, in MAS we use this to send data from Manage into what we call the MAS Data Dictionary to be able to share asset, location, etc. information with Monitor. But it equally applies to a lot of integrations where you needed to get a one-time sync of all the data before depending on publish channels to maintain the data.
------------------------------
Steven Shull
IBM
Original Message:
Sent: 04-06-2023 09:46
From: Subhransu Sekhar Sahoo
Subject: Outbound Integration Message Change in 7.6.1.3
Hi Experts,
In Maximo 7.6.1.2, Maximo integration message used to start with a header member array and ends with (as shown below) while posting bulk JSON message to external system through Crontask.
Start:
{
"href": "https:\/\/localhost.com\/maximo\/oslc\/os\/testos",
"member":
End:
"responseInfo": {
"href": "https:\/\/tlocalhost.com\/maximo\/oslc\/os\/testos?inlinedoc=1&lean=1&oslc.select=*&addid=1",
"totalCount": 2
}
}
After 7.6.1.3 pack upgrade, looks like this start and end part is removed from the Integration message and the message starts with a "[" and ends with a "]".
Looks like IBM has added a all new bulk data export feature in the external system application for 7613 and that works similar to cron task based bulk export.
@Steven Shull Has the integration message been changed taking this new change (bulk data export) into account and is there a setting available in Maximo to post the integration message with the same member array again?
#Integrations
------------------------------
Subhransu Sekhar Sahoo
Tata Consultancy Services
------------------------------