Hello everyone,
We are currently working on integrating Maximo with two external systems using MIF. This is an XML based integration.
Recently we migrated integration code into the Production environment. It included some 12 outbound Publish Channels and around 10 Enterprise Services(for inbound). The publish channels are based on custom object structures.
Around 3 such publish channels use JOBPLAN as one of the objects in their Object Structure. We have included 6 attributes on the JOBPLAN object in the object structure viz. EXCODE, WKCODE,JPNUM,PLUSCREVNUM,ORGID,SITEID. Out of these attributes, EXCODE and WKCODE are custom attributes.
When we enabled the Publish channel listeners as well as the associated External System in Prod, users started getting " Attribute does not exist" error on doing transactions like changing Work Order status, generating PM Workorders, etc.
The system first throws an error for EXCODE attribute. If I exclude this from all the three publish channels where JOBPLAN object is used in the corresponding object structure, the system throws an error for the WKCODE attribute. On excluding this as well, it then throws an error for OOB field PLUSCREVNUM and so on.
We had to disable all the 3 publish channel listeners and then bounce the JVMs for this error to go off in Prod. The entire code is working fine in our internal development and test environments. For your reference, we are on Maximo 7.5 and our Prod environment is clustered with 10 servers, each having separate JVMs for UI, Cron, MEA, etc.
Please suggest how can we fix this issue?
#Integrations------------------------------
Atul Kumar
------------------------------