If changes in the CMMS are not being reflected in AssetWise, you may want to follow one of the messages through the whole message lifecycle to see what's happening.

Normal message flow 

• Incoming messages from CMMS are posted by the CMMS adapters to the Service Bus. 
• Are the components for this integration running? Check the engines via the Service Bus web pages.
• Assuming your Service Bus instance is healthy... The messages are queued in the corresponding Sync Topic to be consumed by AssetWise. PAUSE Message Consumption so you can see messages arrive. If the service bus shows the expected messages
  • arriving successfully, then continue to the next step. 
  • not arriving, then the issue is with the CMMS or the CMMS adapter. If you use BECS, visit here to investigate.
  • If you paused message consumption start it again when you are done this troubleshooting!
• Service bus messages are then processed. If AssetWise's processing is
  • successful, the message is removed permanently from the Sync subscription. To find it in APM... 
  • unsuccessful, the message is put into the dead letter queue for future review by an administrator
  • If there are multiple AssetWise products in this integration, each will have its own subscription and dead letter queue.

If this initial flowchart hasn't pinpointed your problem...

Prepare to troubleshoot

First, turn on Interop's Debug Logging.  If this is production, you should turn this back off when you're done troubleshooting.

Prepare to confirm message delivery

• Pause the specific connection,
• or set up a permanent message archive.
  • Note: there is a maximum combined size for all of a topic's subscriptions!
  • Do not leave a debug subscription active in the production environment.
  • If this is a very-active pre-production environment, monitor and purge this debug subscription regularly.

Start the process

Now that you have done the basic troubleshooting prep, trigger a data event that should be published!

• Make a change to an asset or work order in the CMMS
• Create an APM RequestForWork and mark it Ready to Send
• Etc

Depending on your desired message, the message might be sent immediately, or might be triggered based on a schedule.  See this article about ProcessRequestsForWork for more details.

Once you know the message has been sent, follow it in Interop.

Tracking the message

Did the message arrive? If not, check the exchange's configuration. Messages are posted to the exchanges, and from there go to the topics If the exchange is not bound to a queue, the messages won't go there.  

If it did arrive, was processing successful or unsuccessful?

• If unsuccessful, look in the DLQ. Where's the DLQ?   Also check the interop logs as well as APM and BECS logs.
• If successful, look for error messages in APM.  Here's where they are.