The initial setup is easy.

The time taken for deployment depends on the components. For the agent space, we are managing the open systems agent. Then, it takes just minutes. I don't have the information about installing this product on the mainframe systems as well since it works there as well. I don't have any information about that site. But for the agent-based installation, it just takes a minute.

It seemed complex so we worked with a vendor called Sirius, and they helped us with the setup. Once they walked us through the process, it was fairly simple.

I think the product is generally easy-to-use and that includes my experience with the setup.  

Setup can be quite complex, especially when on-boarding workload that’s migrating from another solution. In those cases, extensive testing is required to ensure that all logical dependencies are properly defined, particularly where the legacy solution’s constructs do not have a like-for-like construct in TWS. JCLs and scripts also very likely require modification to meet TWS syntax requirements.

While the installation is fine, it requires the involvement of an IBM engineer. The solution is easier to install for those who are well versed in the IBM world, but this is a bit difficult for someone who has a background in application development. The process is easier for someone who has experience working with IBM tools. 

With any experience whatsoever, IWA is as simple to install and configure. You basically fill in some blanks and run the setup jobs. They create all of the STC, panels and skeletons that you require.

The application comes packaged from IBM. Once your Oracle db (or DB2 db) and network connections are configured, you are essentially set and running.

Initial setup for TWS 9.2, I find it complex, since there are number of components needed to be installed with no clear understanding of why those components are used and what is a pre-req for what.

However, I did find the installation for TWS 8.6 to be pretty straightforward.

Initial setup was complex; it involved automating huge complex business process models for (nowadays legacy) order, contract and invoice management applications, although limited to mainly workloads for the HP-UX operation system. Later on, the models became less complex, but the agent landscape became more heterogeneous (Solaris, RedHat Linux, SUSE Linux, HP-UX, Win 2003, Win 2008, SAP R/3, SAP BI).

If you have strong knowledge in TWS, then initial setup is just like bread and butter for you.

The scheduler is a little bit complex. They have different concepts, they use event mechanisms for their workforce. 

With Control-M you have a lot of server components. In the meantime, you can install them with Kubernetes as well which is a big improvement.

The setup was very complex. Our environment is very large. Setting up Workload Automation on our set of servers required the following:

• Setting up the agent
• Setting up the notification lists
• Filling out various forms for job stream scheduling. (It just goes on from there.)

Initial setup was somewhat complex, although it might be because we installed on Linux. Windows might have been a bit easier using the installation wizards.

It is simple to install.

Initial setup using the GUI was straightforward. However installing/upgrading a TWS master using the silent approach is a little bit tricky, as the details and the steps have to be collected from many other documents. There was no single document to help us to install the TWS, WAS, and IBM Installation Manager using the silent approach.

The initial setup is not very easy as IBM has multiple components integrated with the core product which are mandatory to setup and can be a bit tricky.

The initial setup is somewhat complex when taking into account the following factors:

• the supported\recommended database types are Oracle or DB2 for Windows shops
• deployment of agents across all batch processing servers
• security configuration
• load balancing and redundancy on the MASTER

Upgrades are also complex as all existing jobs, schedules, and other entities must be ported over and tested.

Initial setup was simple.

Individual access setup was relatively easy. But I think I would attribute this to the setup teams, to the on-boarding team at Chase. We had a specialized request procedure and an access team handled the request.

Initially, it was complex; during implementation, I faced many challenges.

Initial setup was a bit complex, as we did it without any consultant and the coding is not perfect or the same for different platforms (i.e. Windows, different Linux flavors, Solaris, AIX, etc.).

The configuration of IBM Workload Automation has some challenges. We have a difficult time customizing it, but it is similar to other solutions. However, it is easy to set up.

The setup was very complex and required on-site support, mostly due to the cross-product automation that we implemented.

Initial setup was fairly straightforward. However, configuring and setting up the TDWC was somewhat of a challenge; we had to consult with Level 3 support several times to get things working properly.