# Operations Bridge Manager (OBM)

### What is OBM Integration in ZigiOps?

Operations Bridge Manager (OBM) is an IT operations management platform used for event correlation, topology-aware monitoring, and service-centric operations across hybrid IT environments.

ZigiOps enables secure, API-based integration between OBM and ITSM, DevOps, and other monitoring platforms. Using ZigiOps, events, topology data, and operational alerts from OBM can be synchronized with external systems to support automated incident management and cross-platform operations workflows.

With ZigiOps, OBM can:

* Forward correlated events to ITSM platforms such as ServiceNow, Jira, Remedy, and Cherwell
* Receive topology and infrastructure data from monitoring tools for enrichment
* Participate in bi-directional event and incident workflows with ITSM systems
* Support downtime and RTSM-based configuration management integrations

The integration is fully customizable and does not require custom scripts or plugins.

### Which OBM Versions Are Supported?

Please note that using a supported version is mandatory.

| Product                         | Supported Deployment Types | Supported Versions |
| ------------------------------- | -------------------------- | ------------------ |
| Operations Bridge Manager (OBM) | Server                     | 10.x (or newer)    |

{% hint style="info" %}
Confirm the prerequisites of the corresponding integration template before continuing, as some templates may not require all environmental prerequisites.
{% endhint %}

### How Do I Create a Connected Server in OBM?

A Connected Server must be created in OBM before ZigiOps can receive events from it.

{% stepper %}
{% step %}
Access the Connected Servers page

Access the OBM web console and navigate to: **Administration > Setup and Maintenance > Connected Servers**
{% endstep %}

{% step %}
Create an External Event Processing Connected Server

Create a new Connected Server of type **External Event Processing** and configure the following:

**General:**

* **Display Label** - Enter a display label to identify this connected server.
* **Identifier** - The Connected Server username ZigiOps uses to authenticate against OBM. Accept the default or enter a valid value.

**Server Properties:**

* **Fully Qualified Domain Name** - The FQDN or IP of the ZigiOps server, which OBM uses to send event data.
* **CI Type** - The CI Type OBM creates in RTSM for this connected server. Select **Management System** if unsure.
* **Delivery Options** - Accept the default unless advised otherwise by an OBM administrator.

**Integration Type:**

* **Type** - Select **Call External Event Web Service**.
* **URL Path** - Enter `/listener/omi` unless specified otherwise in the ZigiOps template settings.
* **Supports Bulk Transfer** - Enable if bulk transfer of events is required. Check the ZigiOps template for a BULK action name before enabling.

**Outgoing Connection:**

* **Username** - Enter `notused` (OBM requires a value but ZigiOps does not use it).
* **Password** - Enter `notused` (same reason as above).
* **Port** - Enter the ZigiOps listener port as specified in the corresponding ZigiOps template.
* **Transfer Control** - Enable this option to allow event transfer through this connected server.

**Incoming Connection:**

* **Password** - The password ZigiOps uses to authenticate against OBM for backward synchronization.
  {% endstep %}
  {% endstepper %}

### How Do I Create an Event Forwarding Rule in OBM?

Event Forwarding rules define which OBM events are automatically sent to ZigiOps and connected ITSM platforms.

{% stepper %}
{% step %}
Log in and open Event Forwarding

Log in to the OBM web console. Navigate to: **Administration > Event Processing > Automation > Event Forwarding** and click **New**.
{% endstep %}

{% step %}
Configure the forwarding rule

Configure the forwarding rule:

* **Display Name** - A descriptive name to identify this rule.
* **Event Filter** - The condition criteria that events must match to be forwarded.
* **Target Servers** - The connected server to which the rule forwards events. Set the forwarding type to **Synchronize and Transfer Control**.
  {% endstep %}

{% step %}
Save the rule

Click **Create** to save the Event Forwarding rule.
{% endstep %}
{% endstepper %}

### How Do I Connect OBM to ZigiOps?

#### OBM - Connected System Configuration

Follow the steps below to add your OBM instance as a connected system.

{% stepper %}
{% step %}
Open the OpsBridge system setup

Log into your ZigiOps instance. Navigate to: **Connected Systems > Add New System > OpsBridge**
{% endstep %}

{% step %}
Configure the connection parameters

Configure the following parameters:

* **Server URL** - Input the URL of your OBM instance. For example, `https://obm.example.com`
* **Username** - Input your Connected Server username (required for event integrations).
* **Password** - Input the password for the above user (required for event integrations).
* **Downtime Service Username** - Input an OBM Downtime Service username (required for downtime integrations).
* **Downtime Service Password** - Input the password for the Downtime Service username (required for downtime integrations).
* **RTSM Username** - Input an OBM RTSM username (required for downtime or uCMDB integrations).
* **RTSM Password** - Input the password for the RTSM username (required for downtime or uCMDB integrations).
* **Proxy Settings** - Enables the usage of a proxy server.
  {% endstep %}

{% step %}
Save the system

Examine the settings and if they are correct, click the **Save** button to store the system.
{% endstep %}
{% endstepper %}

Once saved, OBM becomes available for use in ZigiOps integration templates.

### What Are the Most Common OBM Integration Use Cases?

#### Use Case 1: OBM Event Forwarding to ITSM

Correlated OBM events can be automatically forwarded to ITSM platforms including ServiceNow, Jira, Remedy, Cherwell, Ivanti, and Zendesk. ZigiOps maps event fields to the target system's incident schema, ensuring full context is preserved.

#### Use Case 2: Bi-Directional ITSM and OBM Synchronization

When an ITSM incident linked to an OBM event is updated or resolved, ZigiOps synchronizes the status change back to OBM, keeping event ownership and lifecycle state consistent across both platforms.

#### Use Case 3: Topology Data Ingestion from Monitoring Tools

ZigiOps can forward topology and infrastructure data from monitoring tools such as SAP SolMan into OBM, keeping the OBM topology model up to date without manual configuration.

### What Integration Templates Are Available for OBM?

ZigiOps provides the following integration templates for OBM:

* OBM events to Cherwell incidents
* OBM events to Ivanti incidents
* OBM events to Jira tasks
* OBM events to Remedy incidents
* OBM events to Remedy problems
* OBM events to ServiceNow incidents
* OBM events to ServiceNow incidents (Staging Table)
* OBM events to Zendesk tickets
* SAP SolMan Alerts to OBM Events Backsync

*See the Integration Catalog for all OBM templates.*

Templates are documented individually in the Integration Catalog.

### Summary

The OBM integration in ZigiOps enables:

* Secure, Connected Server-based event integration
* Support for OBM 10.x and newer (Server deployment)
* Integration with ITSM, DevOps, and other monitoring platforms
* Event forwarding, bi-directional sync, and topology data exchange
* Configurable downtime and RTSM-based integration options
* Optional proxy configuration
* Fully customizable synchronization workflows

ZigiOps allows OBM to participate in enterprise-grade ITSM, ITOM, and automation ecosystems without requiring custom development.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.zigiwave.com/available-systems/operations-bridge-manager-obm.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.