Installation can be conventional or container (Docker) based. This gives the potential for auto-scaling and resilience; however, the last version I used (2019) was not able to exploit the full benefits of containerization. In either case, installation needs very careful planning - which is good as it focuses the mind on what needs to be monitored.

Consider OpsBridge as being the "SAP of ITOM". It requires dedicated resources to configure and administer.

The initial setup is pretty straightforward. It's not complex at all.

The solution is easy to install, which is wonderful.

The initial setup for Micro Focus Operations Bridge was complex. You have to plan it before you deploy it because it's an extensive product, and for its deployment, my company used a big team.

The full deployment of the Micro Focus Operations Bridge took nearly three weeks, and the integration for operations and monitoring took nearly two months.

On a scale of one to five, setting up the solution is a four out of five for me.

The initial setup is a bit more complex than straightforward. I'd rate it a three out of five in terms of ease of setup.

I was not here for the latest deployment. However, based on my experience, usually, it takes at least one month to more to plan, prepare, deploy, and configure.

We have five people who can handle deployment and maintenance. 

It's very complex, but that is reflective of our network design and local delivery. The product could be simpler, but the complexity we experienced was our problem.

I was not part of the original installment. 

The initial setup is not exactly straightforward. It's complex as it's not just one product. It has to integrate with many other products. A standalone product can be simple, however, when you have an integrated environment, definitely the complexity is increased. How you design it and whether it is standalone dictates the process. Every setup is unique and different according to each individual company.

The initial setup is simple.

The setup is straightforward. Depending of the architecture/integration, it can take from one to 10 days.

Highly recommend to go for CDF (Containerized Deployment Foundation)

Well, the whole installation was a nightmare. They have the evolution guide and the evolution guide is very incomplete. Like I said, that's the biggest thing. It says, well go do this, but it doesn't tell you how to go find the documentation on how to do that or it doesn't exist at all. It's amazing, one of the biggest answers that you get from the supports folks of that is that, boy I wish the developers would document it. Thanks for letting us know how it works. That's not a mature product. They also don't have training from an administrator perspective, only from an operator perspective. How can you release a product and there's no training for administrators?

Initial setup was straightforward and integration was easy. 

The installation instructions are a mess to the point where the advice given to us by other HPE people has been to not follow the instructions, but to follow the VMEs instead.

The installation for an enterprise IIS solution, rather than just an out-of-the-box one, doesn't work very well. We ended up needing to troubleshoot the installation to get it to work. Installing the IIS filters was a big headache. We installed them, but we couldn’t do anything until we went in and adjusted them. When I left, there was still a problem creating users. We couldn't do any of that, so I don't know if they fixed that yet.

It was pretty straightforward.

We did the initial implementation of the environments together with HPE; we built the production environment, they built the test and development environments as references. It was OK. In hindsight, there were more things that we should have taken into account before we started building, some of which we understood, some of which we didn't. All in all, there are a lot of components.

I think the changes they're proposing now to the product in the next year or two, those might help. We'll see. Or, at least we'll have new problems. But there are a lot of components to install on a lot of virtual machines, if that's your architecture.

I was involved in the initial setup. The initial version, that was still BSM 9, was more difficult to deploy than it is nowadays. It has definitely improved in that department. With containerization it would definitely further improve the deployment of the solution.

Well, implementation is straightforward. It's a reason to implement the dashboard. The more complex things are the numbers that will be produced, but that's not a problem of the product. That's a problem of how to consolidate these numbers.

For greenfield implementation, which still happens, fundamentally I think Ops Bridge provides a deeper level of understanding of what's going on in the infrastructure. If it's a complex environment, it's difficult to find toolsets that will address it correctly. If you look at the entire offering of Ops Bridge, it's one component in the suite that is relevant for monitoring your environment; detection of what's going in that environment.

If you look at Live and more holistically, all those components that include a BSM, OMi, and other products that I forget, that by itself offers multiple layers in the different technical areas of infrastructure. They work well together for some data modelling challenges, I guess, but overall it works well together and it provides a many-layered insight into what's going on in the infrastructure. You have different levels of how you can see what's going and analyze what you should be doing to address that.

The setup takes a lot of planning and preparation, like any upgrade. You just have to make sure you have a basic plan. I think it goes like the old adage, “If you fail to plan, then plan to fail.”

I took over once the product was already running. It's now handled by my team, but I have only recent joined the team.

Initial setup and deployment has been fairly complex. There are specialized skills and expertise required to run deployments. Once deployed, I think the solution is fairly robust for us to go ahead and use.

It wasn't complex, but, the DB behind it was the toughest part.

It took approximately one week to complete the installation and setup. I would say that the setup process is painful.

The initial setup was straightforward. I had no problems with it.

Initial setup was fairly straightforward. The documentation is good, so we didn't have a problem with that. There are lots of different ways you can set it up and lots of different architectures. So choosing the one that was right for us was challenging. The documentation was valuable in that it enabled us to choose what we needed to choose.

For various customers, I deployed it and helped them run it. It has its complexities because IT has its complexities. When you're monitoring IT, you're going to inherit those complexities, but HPE did make pretty good strides to pull in the data sources and make out-of-the-box integrations, both for their products and for third-party products. Making it the most seamless product possible.

Setting it up is very simple, but you need to design your architecture properly.

The HPE setup is very straightforward. However, once you go into scalability and grow larger, that requires expertise and needs some hard work.

We performed the initial setup, which I'd rate as 3/5.

The initial setup had some challenges; but since it was completed, it has been very stable.

The initial installation document didn't have some of the prerequisites we needed to install the software; but we looked at the installation document again recently and they added all that information. So, in our particular case, it was good.

I was not involved in the initial setup, but I've been involved in migration to a later product. The migration was very complex. It is a very complex product. It probably took me a year before I really felt I understood the product at all. It wasn't something that you can learn in two or three weeks.

It's just a vast complex product and it has also evolved. That's the downside of the product evolving, because there's lots of things that come from its origins and there are some things which have been added, and you can tell the difference. You can tell that it's not brand new because it keeps changing names. It used to be called OpenView and all those commands are OV this and OV that, so I it wasn't updated on that part of it.

I didn't participate in the original setup, so I'm unsure as to if it was straightforward or not.

The setup was very complex.

The initial setup went quite well. It was smooth.

The initial setup is complex. It is not easy to understand how to correctly implement it for the first time. Subsequent implementations were much easier because we had some experience. You have to understand what you want to monitor before you start with the implementation, and a technical person is required.

The deployment takes approximately three to five months for a medium-sized implementation.

The first setup was complex. That is why we asked for a partner's help.

It's very easy to install.

Setups are complex, not straightforward. First of all, there are all the checks that you have to do. You have to see if it does not interfere with other integrated products. There are some parameters that might get lost.

There's a whole bunch of eventual hot fixes and patches that should be installed first. This requires down time, so you bring down the entire system. That's a very bad situation.