Scalability-wise, it can be a little bit challenging. However, it changes and depends on the perspective because it just needs to execute the job, and sometimes the capability depends on the application itself, not TWS. So, if I look at scalability from that perspective, I can give a little bit low, but for the product itself, we don't have any problems so far. So, I rate the product's scalability an eight out of ten.

More than 1,000 people in my organization are using the solution.

I think scalability could be improved. We are moving to cloud and plan to increase the number of users.

This is a scalable solution and they have documentation on how to scale the product. We're running thousands of jobs per day across many agents in the cloud, as well as in the data center. 

The scalability is actually quite fine. I think that right now we have around 100 to 150 users that have jobs running on it.  

The offshore team is made up of about five guys that mainly take care of the maintenance tasks. At this moment, we do not actually have any plans to scale our usage. Maybe in the coming two years, we might have to. We are planning to upgrade or migrate to another tool depending on what is best for our situation at that time.  

Our clients for the solution are mostly enterprise businesses.

IBM Workload Automation is a scalable solution. I would recommend the solution for bigger companies.

Scalability also is relatively good. Our firm also supports TWS/d schedules, which by comparison are significantly less scalable.

None! I have supported this product in literally 100s of different environments and its unmatched in its ability to scale to any size.

IBM TDWC makes scalability and functionality easy and fast.

One drawback would be the mail server IDs are maxed out at 6-7 servers per ID (IDs are classified as per the alpha-numeric characters A-Z and 0-9).

No.

I have not encountered any scalability issues at all.

We did not need to scale this solution. We had close to ten people who used it.

We do not have plans to increase the number of users of the solution.

We never encountered any issues with scalability.

We had to write a scripted solution to be able to change jobs behind the scenes. The solution runs with a specific command fed into it. We fed it this script: “CSCRIPT

None; we’ve had no issues with scalability other than time zone management, which requires some creative scheduling scenarios to account for the hard-coded plan start/end time and time differences between master server and remote agents.

There were no scalability issues.

We have not encountered any scalability issues.

We have had no issues with scalability. However, we have less than 100 batch servers across all environments, so our environment is not very large.

There were no scalability issues using DM.

It is extremely scalable. We run more than 80,000 jobs a day across multiple platforms.

There were no scalability issues.

We encountered scalability issues. There are some parameters that need to be tuned once you reach a certain level, and it is not clearly stated / explained in the product documentation.

There were no scalability issues; we managed to deploy over 85,000 server with no issues.

We have not had any scalability issues.

We did not encounter any scalability issues.

I have not encountered any stability issues.