Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..
91 views

OMI <-> OBM sync

Jump to solution

Hi,

Has anyone set up integration between OMI using HTTP with OBM using HTTPS?
Setting up manager-to-manager integration is normally easy, but I cannot find doc for the scenario above.

I want to have the possibility of having OMI send events and topo to OBM, and have OBM backsync event status to OMI. Have done that before between BSM and OMI, but then both used HTTP.
When setting up Connected Server on both sides there is an exchange of certificates, but I guess topo sync also needs a certificate for ssl comm. 

If anyone knows and/or have a link to doc it is appreciated.

 

0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Expert
Micro Focus Expert

Hello Dasomm,

First, the answer to your question:
>> Has anyone set up integration between OMI using HTTP with OBM using HTTPS?

Yes, and it works well.

We have to distinguish between the communication used for event forwarding (BBC which is always HTTPS) and the web server configuration.

The event forwarding works regardless if your server is HTTP or HTTPS.

One thing that does not work with a mix of https and http is drill down. But unlike BSM integration, that is probably not what you would use or need for OMi - OBM integration.
The reason for this is, that the web browser won't allow a less secure http frame being opened in a https window.

 

Like CheeseTriangle wrote, for topology you usually would use the Data Flow Probe (just like with a BSM to OBM integration). And the DFP can connect to either http or https targets.

I've never used the forward topology option. I would assume it's using BBC, and thus will work regardless, but I'm not positive.

Best regards,
Tobias

View solution in original post

3 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Hello,

When configuring connected servers, I don't think you can select one server to use HTTPS and another server to use HTTP.  My understanding is that the topology sync also uses the same connection to WDE - which is why you have to resatrt WDE if you start forwarding topology.

Topology forwarding is only recommended if you ultimately want to forward your data to an OM server acting as the MoM server.  

If you want to synchronize the topology of two OBM systems instead, use a Data Flow Probe - which sounds like the option you might want to use. 

See https://docs.microfocus.com/itom/Operations_Bridge_Manager:2018.05.001/OMi/AdminGuide/ConnectedServers/connecting_servers_about for more details.

Enjoy.

Highlighted
Micro Focus Expert
Micro Focus Expert

Hello Dasomm,

First, the answer to your question:
>> Has anyone set up integration between OMI using HTTP with OBM using HTTPS?

Yes, and it works well.

We have to distinguish between the communication used for event forwarding (BBC which is always HTTPS) and the web server configuration.

The event forwarding works regardless if your server is HTTP or HTTPS.

One thing that does not work with a mix of https and http is drill down. But unlike BSM integration, that is probably not what you would use or need for OMi - OBM integration.
The reason for this is, that the web browser won't allow a less secure http frame being opened in a https window.

 

Like CheeseTriangle wrote, for topology you usually would use the Data Flow Probe (just like with a BSM to OBM integration). And the DFP can connect to either http or https targets.

I've never used the forward topology option. I would assume it's using BBC, and thus will work regardless, but I'm not positive.

Best regards,
Tobias

View solution in original post

Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..

Thanks for useful info!

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.