It’s very important that all of the database servers reside within the same VLAN as the application servers; otherwise, there will be numerous performance issues. Additionally, it’s important to work with CA in order to determine the proper application configuration based on the number of requests you expect to process, the size of those requests, and the number of process instances required to satisfy the objectives of those requests.

It’s been very stable. At one time we had some issues in a load-balanced environment, but those have since been corrected.

The way we have to interact with Linux machines has been a challenge, but that’s mainly due to how we’ve configured our environment rather than a limitation of the solution.

If you would like to do automation, stability is key. We need a reliable product and that is what we got with CA.

We have an advanced environment that is tolerant to failures. I think it holds up very well considering all the processing and all the challenges it has to deal with day to day.

Lately, this product has been very stable. However, we have faced two major problems in the past. The first one is related to the database’s XA feature, which is mandatory to run CA PAM. Due to an unknown reason, XA stopped working, which caused us to launch a huge investigation. In the end, the root cause of the issue remained a mystery, and our solution was to re-configure XA from scratch. The second big issue was that the email connector suddenly stopped working, and we were unable to get emails from a mailbox. After a lot of time, we found out that the connection sometimes worked and sometimes didn’t. The solution was to implement a workaround to try again if the first attempt fails.

Very satisfied. Mostly database issues – periodically locked transaction, and then the product goes down and processes don’t run. We haven’t seen that in seven or eight months which might be a result of upgrading to 4.2.1.

I've had no issues with stability.

Very stable. So far, perfect.

CA Process Automation is the one of most stable and scalable solutions, and it's completely fit for the purpose. If we are talking about stability, it is one of the applications that has few errors in the logging files. I would advise you to host the solution on a dedicated server in order to benefit from the full power and system resources.

Every so often the service needs to be restarted otherwise it runs slower and slower. I think this may be due to a memory leak.