One On-Premise Bridge for multiple tenants, or provider tenant share opb

Idea ID 1683637

One On-Premise Bridge for multiple tenants, or provider tenant share opb

Currently, if a smax tenant wants to utilize OPB, it is recommended to have a dedicated server just for the opb.

When handling mulitple customers in one environment, each instance of the OPB can only connect to one tenant. Which means if you are running a provider tenant with many managed tenants, it is recommended that each opb has its own dedicated server.

This can be a lot of resources to ask for, given that opb is usually running periodically. Why not allow multiple tenants to be able to utilize one opb (maybe max 3).

or if the provider tenant has an opb setup, why not let the managed tenants utilize the same opb agent.


You have to specify different credentials anyway, so why not allow multiples.


Tags (2)
Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes

Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team. 

Contributor.. Contributor..

The SMAX guide says that OPB should be dedicated on one machine. But never mentioned anything about any multiple tenant deployment limitation.

A way to achieve this could be with the following steps:

1. Install new OPB instance under a different folder on the dedicated OPB.

2. After installation completed, it's important to specify its own RMI port (other than default) for the particular instance.
3. Proceed with the configuration as described.

Waiting for your comments.


Micro Focus Expert
Micro Focus Expert

Hi TotevT


I think this is not possible even if you change the port . When you try to install the second OPB you cannot have new services , so for 2 OPB there will be only one service (which will be of first OPB) . Your wrapper log will also mention the same 

Think this is because the shortcut folder will be always pointing to C:/Program Data .

If you have achieved this please can you let us know .


This is a good Idea and it would be really helpful if we can have multiple tenant for a single OPB




Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

I have done this in a sandbox environment with a windows OPB. As mentioned above, it does require separate install directories and a RMI port change. But it also required creating a different service and other subtle path tweeks. I would not recommend doing this for any environment that is expected to be supported until it is officially blessed.

If this idea is officially pursued, I'd like to see revised sizing recommendations when multiple OPB instances are run on the same machine.



Micro Focus Contributor
Micro Focus Contributor

Hi igirvan,

interesting approach to run multiple OPB agents on one machine. I am interersted in doing the same, also on a Windows server.

How exactly did you manage to rename the service (config file?)? Did you then rename the first service before installing the 2nd?

What is meant by 'subtle path tweeks'?

Is it from your point of view a stable solution, worth to loose the official support?


Thanks and BR

Acclaimed Contributor.
Acclaimed Contributor.

If  port choice could be given at install time and environment variables could be tweaked instead of having constants like "wrapper" to "wrapper_1". This could be done. But should be officially supported.

In comparison service-now  "mid-server" (similar functionality)  out of the box can have multiple instances on same machine(services, ports and logs included from install separation).  This limitation is a problem when using multi-tenants.

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.