Integrate > HPE Operations Manager i (OMi) > Incident Exchange (OMi - SM) integration > Synchronization of incident changes back to Operations Manager i (OMi)

Synchronization of incident changes back to Operations Manager i (OMi)

After OMi opens an incident in HPE Service Manager, Service Manager will synchronize the incident changes back to OMi.

Operations Manager i (OMi) can forward an event record to Service Manager as an incident by calling a Service Manager Web Service. The incident ID is then stored in the event record.

When a user has updated the incident opened from OMi, Service Manager calls an OMi server RESTful Web Service to update the incident changes to the OMi event record.

If Service Manager fails to synchronize the incident changes back to OMi for some reasons (for example, because of a network problem), Service Manager behaves as follows:

  • Displays a warning message, indicating that the incident failed to be synchronized to OMi.
  • Saves the failed task in the SMIS task queue, and retries the task to re-synchronize the changes to OMi based on an interval time and a maximum retry times configured when adding the Incident Exchange (OMi - SM) integration in SMIS. When the re-synchronization is successfully completed, the failed task is removed from the task queue.

System Administrators can monitor failed tasks, and reset their retry times or rerun expired tasks. For more information, see Monitor failover tasks.