Maximo Integration

  • 1.  Publish channel - Cannot manage more than 99 transactions ?

    Posted Mon March 29, 2021 11:56 AM
    Hi,


    I'm using an interface which uses a publish channel to send transactions to an external system when assets are changed in Maximo.

    The listening port is activated and as soon as a change on an asset is made, a transaction is generated. When changing a specification value for a rotating item, all assets associated with that item are updated. It works well when there are less than 100 modified assets. I see all of the transactions messages showing. But when there is 100 or more associated assets, no transaction is generated at all.

    Is there a setup (websphere, property or other) that would prevent more than 99 modifications via a publish channel?

    Thank you !

    ------------------------------
    Sylvain Bourgeois
    ------------------------------


  • 2.  RE: Publish channel - Cannot manage more than 99 transactions ?

    Posted Tue March 30, 2021 08:32 AM
    This isn't related to the integration itself (it can handle significantly more than that at a time) but with the functionality in Maximo to update the rotating asset specs. The itemspec class has a hardcoded limit of 100 where it switches from utilizing MBOs to performing SQL updates. Since it's not going through the MBO framework, it won't trigger publish channels (nor scripts, e-audit, etc.). Switches like this are on a lot of the specification related settings to improve performance when making bulk changes.

    You could potentially open a case with IBM to make this setting a system property to control. Arbitrary limits like this should have a property (IMO) to control it so that if you wanted to use MBOs for 500 records as an example you could.

    ------------------------------
    Steven Shull
    Director of Development
    Projetech Inc
    Cincinnati OH
    ------------------------------



  • 3.  RE: Publish channel - Cannot manage more than 99 transactions ?

    Posted Tue March 30, 2021 08:51 AM
    Hi,

    Thanks for your response, it is appreciated.

    So If I understand, below 100 assets, it uses MBO so it generates transaction for each modified asset. When we have 100 assets or more to update, the update is made directly via an sql query explaining why no transactions are generated.

    Is that right ?

    I created a script with a launchpoint on item (on update after save) and I've been able to generate more than 100 transactions but it is time consuming so I was hoping this could be done directly from Maximo.

    I will look to maybe trigger my script only if there are more than 99 assets to update to avoid duplicate transaction.

    Thank you for your help !

    ------------------------------
    Sylvain Bourgeois
    ------------------------------



  • 4.  RE: Publish channel - Cannot manage more than 99 transactions ?

    Posted Tue March 30, 2021 08:58 AM
    Correct. I would make your launch point on ITEMSPEC instead of ITEM since you're only trying to handle this specific scenario updating specs. In addition, you can use their function to get the number of rotating assets (mbo.getNumberOfRotatingAssets()) to determine if you're >=100 or not.

    ------------------------------
    Steven Shull
    Director of Development
    Projetech Inc
    Cincinnati OH
    ------------------------------