The initial setup is not complex, and it is easy to maintain.

It's pretty straightforward as long as you know how the tool is designed to work and the architecture behind how you need to implement it for your environment.

The initial installation is quite simple. The experienced team can take around 1-2 days to complete the installment. I also can do it by myself.

It takes only one person to do the setup but it is good to have a support team for some time infrastructure inaccessibility.

I'm not normally involved in the setup. We usually have a process in place, where we follow the enterprise architect cycle.

It is not like I just go and get the product. I have to make sure that the product is stable. I have to ask if it has the ability to design a prototype and whether or not it fits.

I was involved in that. I ran a cycle and I identified a product. It took a long time to explain to people how to create assets and build up the communication collaboration.

We had to go through an eight to twelve month cycle to make them understand how to set up the actual tools and learn where they needed to use them.

It was probably a two year plan, or roadmap, to educate our staff, but we succeeded. It is one of the most successful projects that give us millions of dollars in ROI. There was a lot of integration, so it was great fun to work on, to learn, and it is a very good teaching tool as well.

It's a complex system and eventually it becomes straightforward. It's simple for an individual to use, but complex when you have the entire organization adopting it.

I didn’t really have any hiccups with the installation, it’s pretty straightforward. There are a few things, if you want to use some of the new features that are in that beta mode that you have to go in and you have to be very familiar with how to modify specific config files. I’m just naturally inquisitive so I just started digging through the config files on my own. I don’t recommend that unless you’re just that kind of person but other than that just out of the box set-up is so easy to stand up. Maybe the most challenging thing that we had was, overcoming an issue with SQL server implementation because I didn’t realize that each user that accesses service virtualization has to have their own development database instance inside SQL server. So we all shared the same instance and kept overriding everyone’s work. I found it in the documentation, it was there. I’m one of those guys that kind of implements first and reads documents later, and once I found it my temper level went down with the vendor. Even though, I think there’s something that, I think that’s something that can be improved upon. You should be able to share databases, but outside of that everything else went pretty smooth.

Initial setup was extremely easy; just a typical Windows installation wizard and it took me no time to get this deployed.

Initial setup was straightforward. It was easy to implement.

Initial setup was straightforward.

I was involved in the initial setup, and not just the software set up, but I was also involved in getting the right hardware configuration for that kind of workload. Our Patson USA team worked closely with HPE R&D (now Micro Focus R&D) to even figure out the CPU processor speed that would be needed to support 3,000 transactions per second, and HPE helped us out with that.

The initial setup was very straightforward. It is complex, but it is straightforward if you know what you're doing. There are various different ways you can set up the tool and that's where the complexity is. But, if you just want to do the traditional setup, it's very easy to do.

There was a learning curve, but that was several years ago, almost eight or nine years ago when we set initially. It was a learning curve for my infrastructure team. They were used to doing physical hardware deployments on an app server instead of virtualization of the server. Once they got behind them and the technology started running, we have virtualized 99% of all our data centers worldwide.

Initial setup was simple and straightforward.

Straightforward for the most part. There are limitations. For example in the virtualization engine of the J80, the Instant On, which is a OneView Instant On product line. It does work great, as long as you have your infrastructure. Our clients give us all the necessary requirements, such as the AD and IP address, the DNS, the subnets and stuff. As long as all that works seamlessly, then we can usually bind that HP 380, the Instant On into the infrastructure seamlessly. Does it always work smooth? No. But that's not necessarily HP's fault, it's because the infrastructure doesn't always lend itself to easy integration.

The initial setup is simple.

I wasn’t involved in the setup, but I heard from my colleagues who said the first setup was a bit challenging. However, with support from the HPE team, it was good. We were able to sort out the issues that came up.

It's easy to install and easy to use.