Hello,

We are setting up Spatial Integration in MAS, but any insight even if from Maximo 7.6 will be welcome.

We created a Map Manager, layers, inbound mapping and the GIS cron task is successfully updating assets in Maximo, and flagging the GIS record with MXCREATIONSTATE to whatever we tell it too.

However new assets come in with no MXASSETNUM to be mapped, Maximo creates a new asset but does not return any response back to GIS with the MXASSETNUM and MXSITEID, although there is a JSON mapping of outbound type defined on the layer.

Wonder what I am missing here

It looks like the outbound sync is not fully wired. Double-check that your outbound JSON mapping is correctly linked to the layer and that the GIS object structure includes MXASSETNUM and MXSITEID as response fields. Also, make sure that outbound processing is enabled in the GISUpdate cron task.

Hello,

We are setting up Spatial Integration in MAS, but any insight even if from Maximo 7.6 will be welcome.

We created a Map Manager, layers, inbound mapping and the GIS cron task is successfully updating assets in Maximo, and flagging the GIS record with MXCREATIONSTATE to whatever we tell it too.

However new assets come in with no MXASSETNUM to be mapped, Maximo creates a new asset but does not return any response back to GIS with the MXASSETNUM and MXSITEID, although there is a JSON mapping of outbound type defined on the layer.

Wonder what I am missing here

Thanks for the tip. I did recheck everything and I the event listener on the ARCGISASSET publish channel was not enabled. Don't know if it was needed, but I did that and a couple other things and I made some progress ; now when a record is updated I get a java error in the log clearly about something going out from the Publish Channel

The layer has the response mapping defined, that mapping is outbound, I've got the MXASSETNUM and MXSITEID in the mapping, not sure what is still wrong but will keep looking

Caused by: java.lang.NullPointerException	at com.ibm.tivoli.maximo.fdmbo.arcgis.ArcGISMapperExit.getMapNameOut(ArcGISMapperExit.java:358)	at com.ibm.tivoli.maximo.fdmbo.JSONMapperExit.setDataOut(JSONMapperExit.java:88)	at psdi.iface.migexits.ExternalExit.callExitsOut(ExternalExit.java:58)	at psdi.iface.migexits.ExitProcessor.executeOutExitLogic(ExitProcessor.java:543)	at psdi.iface.migexits.ExitProcessor.processExitsAndRulesOutForExtSys(ExitProcessor.java:492)	at psdi.iface.migexits.ExitProcessor.processExitsAndRulesOut(ExitProcessor.java:317)	at psdi.iface.mic.PublishChannel.processExitsOut(PublishChannel.java:679)	at psdi.iface.mic.PublishChannel.processStructure(PublishChannel.java:606)	at psdi.iface.mic.PublishChannel.publish(PublishChannel.java:161)	at psdi.iface.mic.MicListener.structureChanged(MicListener.java:144)

It looks like the outbound sync is not fully wired. Double-check that your outbound JSON mapping is correctly linked to the layer and that the GIS object structure includes MXASSETNUM and MXSITEID as response fields. Also, make sure that outbound processing is enabled in the GISUpdate cron task.

Hello,

We are setting up Spatial Integration in MAS, but any insight even if from Maximo 7.6 will be welcome.

We created a Map Manager, layers, inbound mapping and the GIS cron task is successfully updating assets in Maximo, and flagging the GIS record with MXCREATIONSTATE to whatever we tell it too.

However new assets come in with no MXASSETNUM to be mapped, Maximo creates a new asset but does not return any response back to GIS with the MXASSETNUM and MXSITEID, although there is a JSON mapping of outbound type defined on the layer.

Wonder what I am missing here

Personally I hate null pointer exceptions.... they are just no fun.. That said it usually means that you have an attribute somewhere that is required and empty.  So look at you JSON Outbound mapper and ensure that yo have the ASETTNUM populated there.  I ran into mind-numbing issue with spatial on the inbound creation side where I was not mapping the LOCATIONS.LOCATION attribute on the inbound side and it was failing with null pointer exception.  When I added LOCATION to mapper it worked.  So you may be facing similar issue?

Thanks for the tip. I did recheck everything and I the event listener on the ARCGISASSET publish channel was not enabled. Don't know if it was needed, but I did that and a couple other things and I made some progress ; now when a record is updated I get a java error in the log clearly about something going out from the Publish Channel

The layer has the response mapping defined, that mapping is outbound, I've got the MXASSETNUM and MXSITEID in the mapping, not sure what is still wrong but will keep looking

Caused by: java.lang.NullPointerException	at com.ibm.tivoli.maximo.fdmbo.arcgis.ArcGISMapperExit.getMapNameOut(ArcGISMapperExit.java:358)	at com.ibm.tivoli.maximo.fdmbo.JSONMapperExit.setDataOut(JSONMapperExit.java:88)	at psdi.iface.migexits.ExternalExit.callExitsOut(ExternalExit.java:58)	at psdi.iface.migexits.ExitProcessor.executeOutExitLogic(ExitProcessor.java:543)	at psdi.iface.migexits.ExitProcessor.processExitsAndRulesOutForExtSys(ExitProcessor.java:492)	at psdi.iface.migexits.ExitProcessor.processExitsAndRulesOut(ExitProcessor.java:317)	at psdi.iface.mic.PublishChannel.processExitsOut(PublishChannel.java:679)	at psdi.iface.mic.PublishChannel.processStructure(PublishChannel.java:606)	at psdi.iface.mic.PublishChannel.publish(PublishChannel.java:161)	at psdi.iface.mic.MicListener.structureChanged(MicListener.java:144)

It looks like the outbound sync is not fully wired. Double-check that your outbound JSON mapping is correctly linked to the layer and that the GIS object structure includes MXASSETNUM and MXSITEID as response fields. Also, make sure that outbound processing is enabled in the GISUpdate cron task.

Hello,

We are setting up Spatial Integration in MAS, but any insight even if from Maximo 7.6 will be welcome.

We created a Map Manager, layers, inbound mapping and the GIS cron task is successfully updating assets in Maximo, and flagging the GIS record with MXCREATIONSTATE to whatever we tell it too.

However new assets come in with no MXASSETNUM to be mapped, Maximo creates a new asset but does not return any response back to GIS with the MXASSETNUM and MXSITEID, although there is a JSON mapping of outbound type defined on the layer.

Wonder what I am missing here

The issue was that at the same time I enabled the Event Listener on the ARCGISASSET Publish Channel I set the "Publish JSON" flag to true.

When I un-flagged it, I see from the log a response is being generated... but skipped. I see the SKIPTRANSACTION entry in the log file meaning the response will not be sent out.

I don't see any processing rules on the Publish Channel at any level, I guess something from the Event filter, or some other Spatial configuration is preventing the transaction from being sent out...

Personally I hate null pointer exceptions.... they are just no fun.. That said it usually means that you have an attribute somewhere that is required and empty.  So look at you JSON Outbound mapper and ensure that yo have the ASETTNUM populated there.  I ran into mind-numbing issue with spatial on the inbound creation side where I was not mapping the LOCATIONS.LOCATION attribute on the inbound side and it was failing with null pointer exception.  When I added LOCATION to mapper it worked.  So you may be facing similar issue?

Thanks for the tip. I did recheck everything and I the event listener on the ARCGISASSET publish channel was not enabled. Don't know if it was needed, but I did that and a couple other things and I made some progress ; now when a record is updated I get a java error in the log clearly about something going out from the Publish Channel

The layer has the response mapping defined, that mapping is outbound, I've got the MXASSETNUM and MXSITEID in the mapping, not sure what is still wrong but will keep looking

Caused by: java.lang.NullPointerException	at com.ibm.tivoli.maximo.fdmbo.arcgis.ArcGISMapperExit.getMapNameOut(ArcGISMapperExit.java:358)	at com.ibm.tivoli.maximo.fdmbo.JSONMapperExit.setDataOut(JSONMapperExit.java:88)	at psdi.iface.migexits.ExternalExit.callExitsOut(ExternalExit.java:58)	at psdi.iface.migexits.ExitProcessor.executeOutExitLogic(ExitProcessor.java:543)	at psdi.iface.migexits.ExitProcessor.processExitsAndRulesOutForExtSys(ExitProcessor.java:492)	at psdi.iface.migexits.ExitProcessor.processExitsAndRulesOut(ExitProcessor.java:317)	at psdi.iface.mic.PublishChannel.processExitsOut(PublishChannel.java:679)	at psdi.iface.mic.PublishChannel.processStructure(PublishChannel.java:606)	at psdi.iface.mic.PublishChannel.publish(PublishChannel.java:161)	at psdi.iface.mic.MicListener.structureChanged(MicListener.java:144)

It looks like the outbound sync is not fully wired. Double-check that your outbound JSON mapping is correctly linked to the layer and that the GIS object structure includes MXASSETNUM and MXSITEID as response fields. Also, make sure that outbound processing is enabled in the GISUpdate cron task.

Hello,

We are setting up Spatial Integration in MAS, but any insight even if from Maximo 7.6 will be welcome.

We created a Map Manager, layers, inbound mapping and the GIS cron task is successfully updating assets in Maximo, and flagging the GIS record with MXCREATIONSTATE to whatever we tell it too.

However new assets come in with no MXASSETNUM to be mapped, Maximo creates a new asset but does not return any response back to GIS with the MXASSETNUM and MXSITEID, although there is a JSON mapping of outbound type defined on the layer.

Wonder what I am missing here

The issue was that at the same time I enabled the Event Listener on the ARCGISASSET Publish Channel I set the "Publish JSON" flag to true.

When I un-flagged it, I see from the log a response is being generated... but skipped. I see the SKIPTRANSACTION entry in the log file meaning the response will not be sent out.

I don't see any processing rules on the Publish Channel at any level, I guess something from the Event filter, or some other Spatial configuration is preventing the transaction from being sent out...

Personally I hate null pointer exceptions.... they are just no fun.. That said it usually means that you have an attribute somewhere that is required and empty.  So look at you JSON Outbound mapper and ensure that yo have the ASETTNUM populated there.  I ran into mind-numbing issue with spatial on the inbound creation side where I was not mapping the LOCATIONS.LOCATION attribute on the inbound side and it was failing with null pointer exception.  When I added LOCATION to mapper it worked.  So you may be facing similar issue?

Thanks for the tip. I did recheck everything and I the event listener on the ARCGISASSET publish channel was not enabled. Don't know if it was needed, but I did that and a couple other things and I made some progress ; now when a record is updated I get a java error in the log clearly about something going out from the Publish Channel

The layer has the response mapping defined, that mapping is outbound, I've got the MXASSETNUM and MXSITEID in the mapping, not sure what is still wrong but will keep looking

Caused by: java.lang.NullPointerException	at com.ibm.tivoli.maximo.fdmbo.arcgis.ArcGISMapperExit.getMapNameOut(ArcGISMapperExit.java:358)	at com.ibm.tivoli.maximo.fdmbo.JSONMapperExit.setDataOut(JSONMapperExit.java:88)	at psdi.iface.migexits.ExternalExit.callExitsOut(ExternalExit.java:58)	at psdi.iface.migexits.ExitProcessor.executeOutExitLogic(ExitProcessor.java:543)	at psdi.iface.migexits.ExitProcessor.processExitsAndRulesOutForExtSys(ExitProcessor.java:492)	at psdi.iface.migexits.ExitProcessor.processExitsAndRulesOut(ExitProcessor.java:317)	at psdi.iface.mic.PublishChannel.processExitsOut(PublishChannel.java:679)	at psdi.iface.mic.PublishChannel.processStructure(PublishChannel.java:606)	at psdi.iface.mic.PublishChannel.publish(PublishChannel.java:161)	at psdi.iface.mic.MicListener.structureChanged(MicListener.java:144)

It looks like the outbound sync is not fully wired. Double-check that your outbound JSON mapping is correctly linked to the layer and that the GIS object structure includes MXASSETNUM and MXSITEID as response fields. Also, make sure that outbound processing is enabled in the GISUpdate cron task.

Hello,

We are setting up Spatial Integration in MAS, but any insight even if from Maximo 7.6 will be welcome.

We created a Map Manager, layers, inbound mapping and the GIS cron task is successfully updating assets in Maximo, and flagging the GIS record with MXCREATIONSTATE to whatever we tell it too.

However new assets come in with no MXASSETNUM to be mapped, Maximo creates a new asset but does not return any response back to GIS with the MXASSETNUM and MXSITEID, although there is a JSON mapping of outbound type defined on the layer.

Wonder what I am missing here