Deployment is totally my responsibility. I never had any issues with LoadRunner's deployment and installation. Just two years ago, there was some issue with licensing a utility on the controller. Other than that, it has been fine.

We have LoadRunner Professional in Canada, and we have LoadRunner Enterprise in Kansas City. We might combine them later into LoadRunner Cloud or LoadRunner Enterprise. We have not done it yet because the companies have joined. We have a network problem. We have to create a network access and trust policy.

The setup is pretty straightforward. The only scenario we see a complexity is when we have single-page applications where JavaScript is talking to the server and coming back. That's the only scenario where we find some difficulties.

The initial setup is very straightforward. You get the executables.  You just need to get your hardware lined up, like which machine will be a controller and which machine will be a generator, whether you need two or three generators with whatever the requirement is. 

You install the controller analysis on one machine, and then you have low generator agents, and different machines, and you just install the software, and the machine talks to each other.

The initial deployment is quite simple. It's not complex and can be done in one or two days.

LoadRunner Professional is easy to maintain.

The SaaS version is quick and easy to set up. The on-premises version has a lot of challenges, especially related to the DB. You need to have a particular DB version to store the user data. Also, you have to depend on additional licensing from a database side. For instance, if you have Oracle, then you would need an additional license for the Oracle user.

The setup is not difficult. You just click, click, click, but there are prerequisites. They have a link to download it and get it installed. If someone is experienced with IT, they should be able to install it themselves.

But if an organization has a lot of hardening policies to block to execution, that makes it difficult for an admin to deliver.

The initial setup was fairly easy. I would rate it eight out of ten.

The initial deployment is straightforward, requiring only basic knowledge of the application and operating system. A detailed manual is available on the OpenText website for reference.

The ease of LoadRunner Professional's setup process is one of its strengths - it's straightforward and takes a day or two to deploy.

The initial setup is not that straightforward. It requires specialists to train LoadRunner users. We used integrators to assist with implementation. The solution doesn't really require any maintenance. 

Downloading LoadRunner Professional was straightforward via the portal, and the installation process was relatively easy, especially with a quick and standard setup. Overall, the initial deployment was user-friendly. It takes about 15 minutes to install it. LoadRunner Professional doesn't require much initial configuration. However, to test applications, it is necessary to open the firewall to accept traffic.

The initial setup is not straightforward. It should be enabled with some APM tools so that we don't have to rely on third-party tools.

Whenever a client wants to improve their application, they will procure the licenses. It's simple to install. it will take hardly 20 to 30 minutes of time to install and we will get 50 user licenses free of cost.

It only takes 30 minutes to deploy on our application. It's on a private cloud that we use whenever we're working on a particular project. One person is enough to install it.

It's a fairly straightforward setup. I'd rate it seven out of ten. It's a plug-and-play tool. There is a bit of a learner curve, however. You could also do some workarounds if you need to, however, that might make it more complex to set up. 

The initial setup was straightforward. 

I would rate the initial setup a four out of five, it was simple.

The initial setup is straightforward.

I would rate the initial setup a five out of five.

I would rate the product's setup a nine out of ten. It's easy and straightforward. The tool's deployment took one hour to complete. 

The initial setup and configuration is pretty complex. 

I'd rate the solution a three out of five in terms of ease of setup.

The initial setup is a complex process that is not too straightforward. However, with some expertise, it is not a big problem.

It took a couple of days for us to deploy.

The setup is straightforward. We are a large company so I'm not sure how many are using this solution. In my department there are four users on our current project. 

This is a heavy-duty tool, so it's not a one-click installation. But I think it's comparatively easier with the documentation they provide.

I was involved in the initial setup. It's extremely straightforward. I've probably worked on about six or seven different versions, and it's extremely straightforward and fairly simple to setup.

The initial setup is not complex. We will be able to install it, but it will take a lot of steps. Open-source tools take two to three steps, while paid tools take eight to ten steps for deployment. The implementation is user-friendly.

I rate the initial setup a seven or eight on a scale of one to ten, where one is difficult and ten is easy. Considering my impressions of the product, I understand that it is a commercial tool, and it is very stable and of good quality. In general, it is very good. But, there are multiple factors where we can reject it because of its cost, support, and considering that anything that is very new can be done in the open-source tool. So rather than this particular thing, we need Micro Focus to put in extra effort. So, green screen applications are not supported by the solution. Also, ActiveMQ won't be supported in the solution. So for that, I need to write a custom code. I need to build different Java JAR files. Then, it doesn't support Java 64-bit, which is very poor. It supports only Java 32-bit version. For ActiveMQ and Kafka messaging queues, Java 64-bit is more dependable. So, that is completely redundant.

In the organization part, we have it deployed on-prem. But most of the tool licensing that we use is on the client side itself since the client purchases the tool, and so in their environment, we do the test.

The initial setup of Micro Focus LoadRunner Professional is simple for me. However, I understand new people have to learn, and I would still rate it simple. The deployment took approximately 30 to 45 minutes. Micro Focus LoadRunner Professional is straightforward but the Enterprise version is complicated.

The initial setup for the standalone version is very simple and very easy compared to a solution like Apache JMeter. If you have the licenses then you can get started very soon.

It takes perhaps 20 minutes to deploy, depending on the machine configuration. Only one person is required because it has an auto-install package.

The initial setup is pretty easy. This product is Java-based and you just have to add the independent libraries and dependencies. It is more of a client-server based architecture

The setup for LoadRunner is straightforward as the installations are via wizards, and this makes them quick and easy. Make sure though, that the instructions are followed as written, and be aware that virus detection software can adversely affect the installation. The most complex area is in ensuring connectivity between the load generators and the controller, which may involve firewall changes as load generator machines should be located where the users are situated or externally on the cloud. The complexity is often getting permissions from the IT support teams and explaining what you are doing rather than changing the firewall itself and setting it up. It requires good communication skills.

The installation took around 20 to 30 minutes.

It's not straightforward because for us it was because it was an upgrade of the infrastructure as well. So at the same time we changed the server, we also changed the infrastructure. It was not because of the product itself, it was more linked to what we needed to do at that time.

Previous versions were easy to install but we struggled with the LoadRunner Enterprise to get it to work. It was a bit challenging.

The initial setup of the solution was very straightforward, as I recall. It wasn't too complex.

The cloud has allowed for deployments to happen fairly fast. You need one URL and within 15-20 minutes you can have it installed on your local machine.

The two Micro Focus products are interesting to compare. LoadRunner is very easy to set up. Performance Center needs an expert. I can install LoadRunner in minutes by myself. To do the installation properly with Performance Center needs a specialist and takes weeks.  

Plenty of people seem to have installed Performance Center in a couple of days, but when they use it they usually have problems. You really need to do it properly. I do plan to have a look at the newer versions, and maybe those implementations will be smoother.  

The initial setup is not that difficult. When it comes to distribution systems then it will be somewhat difficult, and you need to have a proper network to work on. Another consideration is that at the distribution level and onward we need to put different controllers, unions, and claims at different locations to have a product as accurate as this.

The initial setup was quite straightforward and it's quite easy to install the standard version. Everything takes less than an hour.

It's not exactly straightforward. Their instructions were not all they could have been, but we still got it installed.

It is straightforward. You just have to go through the read-me document and installation guide provided along with the software.

The initial setup was quite easy, and the deployment took one to two days.

Initial setup is straightforward as LoadRunner is pretty much standalone and just needs connectivity to the system under test.

Setup was very straightforward. We installed, applied the licenses, and started using it.

Initial setup was not that difficult.

The setup of LoadRunner is very straightforward. It comes with one retro file which installs all the applications which handle the individual applications also. It's a very easy setup, just that the sizing of the tools is much less. Other than that, the setup is pretty easy.

It was a very long time ago. It was complicated only because of the age of the technology then and the infrastructure we had.

Updating, it's something you just have to plan for, but otherwise it was fairly straightforward.

The tool's deployment is easy and can be completed in one to two days.

Five to six engineers are required to maintain this solution.

The initial setup and installation of the software were very easy and straightforward. 

It was rather easy and you can do it yourself.

The initial setup is easy; HPE Documentation is one of the biggest benefits.

I have been involved with the initial setup at multiple organizations. Because we are a consulting firm, we go and talk to different bigger organizations and we do their setups as well.

The setup of LoadRunner itself is very straightforward. It's just that different clients provide different hardwares, and that's the hardest part.

The initial setup is easy. It's not difficult.

Little complex

I'm quite experienced with the solution, so I haven't had any issues with the initial setup.

It was a long time ago that we installed it.

The initial setup was really straightforward. You just install, make a couple of tests, and everything is connected.

It was straightforward.