The initial setup was straightforward.

Initial setup was understandable. It wasn't that complex. The complexity was setting up the infrastructure. That was one of the challenging things where we had to acquire a few machines so we could set up the coordinators and simulators. We wanted beefier machines so we could get very similar production load. But, other than that, getting it on the users machine is a straightforward process.

The deployment is simple.

I was not involved in the initial setup of this solution.

It should have been straightforward, and it could have been better. I've given this feedback a couple of times previously. The focus is on getting the technology in, but it's less focus on the how do I change my organization to adopt the software? I think from other feedback I've heard, a lot of people have the same thing. It's not the, what it can do; it's the, how do I make it work in my organization? We had to focus a bit more on that. Once CA heard that message, I got all the support I needed, but it wasn't there as part of the service delivery for bringing it in. There are things on both sides.

This is what I'm primarily doing. It's been straightforward with no issues.

I wouldn't say initial setup is straightforward. You have to have a little background, engineering knowledge, about how it operates. I know my team accomplished it working with CA in relatively short order.

We have completed the PoC, so I would say since we haven't completely set it up. So far, whatever the setup has done, we're satisfied with it.

Initial setup was complex, as we were new to the tool and to reach the current scenario, a learning curve in terms of the tool was required.

I was involved in the initial setup at a different client. It was pretty straightforward, I never faced any issues, and in fact I purchased myself a license from CA, spending a lot of money on this. I was a good investment for me. I'm very passionate about technology. I have bought a lot of software, but it is worthwhile spending money on this.

It was very complex initially, once you have one or two people on board that gain experience setting up environments, you will eventually be self sufficient. Expect to use outside professional services for the initial implementation though. Don't let the vendor's sales people convince you to buy just the software, some training and "starter pack" services. The services and training will not be enough. A more realistic approach is to rent qualified engineers for the first project or two where you are going to leverage CA Service Virtualization. Send your own staff to training and have them work alongside the consultants for these initial projects. after a project or two, your team will become self sufficient.

Initial setup for service testing was easy, but setup of virtualization server was bit complex and needed help from an expert.

I think it's a little more technically involved to get it started, but once you get the hang of it you can pretty much do even internal knowledge transfer to any other team. We rely on CA-provided training to a really small group of our team, and then after that we first do our internal training and knowledge transfer to other teams to scale it up.

It was straightforward from CA's setup, but it was probably somewhere in between in terms of our internal process.

We set up on a Linux server which was complex due to internal security in our company that pose a challenge. Not a tool specific problem, but an internal process security issue.

My team did the initial setup, and it's pretty straightforward.

I was not involved in the initial setup.

I was not involved in the initial setup process, since we have a setup team that takes care of this.

There was no problem. We did our own setup just for our POC and it was no problem.

The most recent version is not simple.

It's not easy and especially when you want to set up a distributed architecture, it gets a bit complex. For that, also, when we need something complex then true expertise is needed.

I am the specialist and a part of the team for managing this solution.

I was a part of the setup. However, I have the other group who carried out the process. It was quite straightforward because I was with them at the time.

Setup/installation is straightforward. The product installation guide helps lot.

I was the product manager that rolled it out to our enterprise. It was very complex.

CA was learning the product at the same time we were learning the product. CA had just bought the product from ITKO LISA (or acquired ITKO LISA). At the time, it did not have enterprise characteristics, since then CA has been able to bring to a large company as far as management capability, security, and things of that nature. When we were implementing it, it did not have that, but it does now. 

Upgrades are straightforward from a CA perspective. They are complex from our company perspective, and that is mostly self-inflicted. 

I was involved in the initial setup of the service virtualization. We stood up our own Linux server. The setup was pretty out of the box. It wasn’t difficult. Our developers, though, want it to be easier. They don't like to use it. they want it to be easy to set up.

With version 6, everything needed to be centralized. Now with 9.5, it can be decentralized. It is pretty complex, because it violates all kinds of security regulations at the network datacenter level.

The initial setup was easy and occurred within 1 full day, including configuration and full setup.

It was very complex, since it is a tool that is integrated with lots of software parts: all the servers, the middleware, the UI, etc. Integrating it in the development environment was really not straightforward. It took us several weeks to stand on our feet.

Getting it working in our particular environment was complex.

The initial setup was straightforward. It required training, but it was straightforward after the training. The training helped get us off the ground.

One of the reasons we picked the product was it was easy to set up. We signed our contract at the end of May, and we had our production instance up and running in the second week of June, so it was very easy to set up and it's been running solid since.

The initial setup was straightforward.

The initial setup was straightforward.

I was not involved initially, but I am involved in upgrades with enterprise dashboard and writing instructions on upgrading client dashboards. I haven’t heard anything bad about initial setup, though.

This initial setup of this solution is not straightforward at all. The installation is unnecessarily complex. Again, user-friendliness is not an area that CA DevTest can boast about.

There's definitely a learning curve, but they're there with you on site, helping you get set up. At least in our case they were with us, so that removed a lot of the problems.

I was not involved in the initial setup, but there was somebody in my team that was involved. I don't think we encountered a lot of issues or challenges as such. We had to, of course, pull some experts from CA as well just to get their ideas on how we're supposed to set up, how things work, and what are best practices. Other than that, the first couple of sprints we had to learn and tweak a little bit as part of our retrospectives. Otherwise it's been pretty much okay.

The setup was straightforward. The development of the harnesses was more challenging.

It takes some time, but after one or two tries it becomes easy.

It was very straightforward.

Initial setup was pretty straightforward in terms of installation and configuration. Later, as we encountered a few challenges, we built a couple of utilities.

The initial setup was quite straightforward because the steps to install and configure were clear.

Installation and setup was very easy. It is easiest tool in the market to learn and implement.

The initial setup was straightforward, but the settings procedure, like providing the correct domain name, server name, username and password, did not work the first time they were provided from LISA.

The product is relatively simple to install and use. The complexities generally relate to system connectivity restrictions within the organization.

It's easy to install as there's lots of documentation. Whether it's a small installation, a single server, or multiple servers, it's pretty easy. Again, American Airlines has it deployed on 60 servers. We have only 5.

It was not simple nor was is complex. To set up CA DevTest, you should know the tool and architecture very well along with his installation skills on the particular server you choose - like Unix or Linux. Firewalls and other areas are also very important.

Initial setup for Workstation is straightforward although setting an agent and broker for pathfinder to use recording is bit complex.

CA came in and installed it. It seemed like it was a straightforward installation as long as you know what you're doing. I couldn't just do it out-of-the-box, but it seemed like it was pretty straightforward.

I would say it was complex.

The initial set up, if you look at the basic functions, it's quite straightforward. But for the scale that we were planning to implement it at, we did not get a lot of support from CA. So a lot of it had to be done in-house. We had to bring in our own architects and do a lot of environment setup and the like. We did not get a lot of support from CA. That's one area where I would say CA could have helped out better.

It's a bit complex as far as creating the model and then improvising it. Also maintaining the model is cumbersome.

Initial setup was straight forward. It was an easy install.

The initial set-up was not complicated thanks to the detailed documentation available.

Initial setup was pretty straightforward.

The setup was straightforward and there are many supporting documents available on the CA site that guide you through the process.

If it's your first time using it you will face difficulties but afterwords everything is just few clicks away.

Initial setup was straightforward. Read the agreement and close your eyes, next... next...

Initial setup was simple.

It was already in production when I joined.

The setup was straightforward as a result of having good documentation and a great community to reach out to for help.

I'm not aware of any issues we faced during the implementation. We have a separate environments team which did the setup for us.

The initial setup was straightforward. We did have some problems with the one of the upgrades. CA actually releases a new version every year, so we try to catch up with it. We have had issues with the prior to last upgrade. This one was okay, the latest one.

Initial setup was OK.

Initial setup was both straightforward and complex. We had some configuration issues, such as conflicts with our firewall. They helped with what they were able to help with. For some of the issues, we needed our security desk and network teams to open up ports and other things like that.

The server-side configuration and the start of activities at our customer required the intervention of expert staff of CA because we did not have the necessary experience. I am of the opinion that it is better to follow the advice of experts where things are not specified in a simple manual.

The initial setup was a little complex.

We were the pilot team for the solution. It was fairly straightforward; install a package on a server, start up some services, and go.

I was not involved in the initial setup. I have also not been involved the setup of any new releases.

I've been using CA Service Virtualization for the last 6 years, I am quite happy with the performance and how it developed over the years. Unlike other tools, the set up of CA Service Virtualization is quite easy and self-explanatory.

Setup is straightforward, you just need to follow the installation guide.

The complexity of an install totally depends on what you are trying to virtualize. Sometimes configuring the security settings for recording is a pain but that’s not because of the product, it’s just a pain.

Initial set up might be a bit complex, especially when you are going with an enterprise level setup. However it is a one time effort and is very smooth afterwords.

It was simple

I wasn't involved in the initial setup but I heard we had some issues with building SSL services initially.

Initial setup was complex. CA SV scripting has an initial learning curve.

Initial setup was straightforward.

The setup was a little complex, but it is ongoing. When we get into the tool, we feel it's easy to proceed with it.

Setup was straightforward. The instructions in the specification document were crisp and clear.

It's straightforward, just follow the user manual provided on the CA website.

Simple and straightforward. Anyone with basic knowledge can do it.