Its initial setup has moderate complexity. It required some coordination with the vendor because their system also needs to be ready. We also get maintenance support from them.

I did not directly set up the solution. 

Right now, we have the product on-premises.

It is an IBM tool, and there are a lot of steps to deploy it. It's not straightforward. You need to have experience. You need to create replication objects, and you need to learn the commands and scripts. It can be quite complex. 

The installation is pretty fast. It doesn't take too long. We did a deployment a few years ago, and it only took maybe two to three days. We updated it to version 11 at that point. The length of time depends on the architecture. It can vary a bit. 

First, we have to install it on the web server. After that, we have to set up the repository with Oracle or DB2. That takes a lot of time. When you are a big organization, it takes a lot of people. There are configurations and prerequisites that have to be considered. 

Only one person is needed to manage the maintenance. 

The initial setup is quite easy.

In terms of intermediate storage, we have some challenges, especially with customers who store data in intermediate locations. 

Also, when we migrated from standard DataStage to Cloud Pak for Data, we faced a lot of challenges surrounding data latency. 

One client is located at two different locations, about 900 miles away, and they have strict expectations for low latency between systems. The initial infrastructure setup was fine, but we had intermittent storage issues. 

We relied on other service providers to assist in that situation.

The deployment time depends. Sometimes, it's just a few hours, depending on the applications involved. When I did a large migration from one version to another, it took almost a month to migrate about 20,000 processes. 

If there are no code changes in the system, the migration might take about a day. In some cases, where there are code changes, it could take even longer.

The initial setup of DataStage, implemented through an IBM partner in Mexico, faced challenges due to partner skill gaps, leading to some complications. Deployment took around one to two years until the system became more stable, and currently, a team of three handles maintenance and support, with two individuals at level two communicating with IBM for assistance.

I would rate my experience with the initial setup a seven out of ten, where one is difficult and ten is easy. I have worked both on-premises and deployed it on a private cloud.

The deployment process usually takes a day.

Setting up IBM InfoSphere DataStage was easy.

How long the deployment takes would depend on certain factors, but it usually takes just two to three hours.

The solution's initial setup is straightforward. Also, it's a one-time activity. It is better to have a competent person for deployment since newbies cannot do it themselves.

When I started using IBM InfoSphere DataStage, it was already deployed on the server. So I did not have to go through the installation phase.

We didn't need to do anything because the customer, with whom we are working on the project, had already set everything up for us. The initial setup was not in our preview.

Setting up the system is difficult and requires a lot of technical expertise. It demands a high level of experience during the setup process. 

However, despite the difficulty, our team, possibly the only one in Mexico, is good at quickly completing the setup.

Most of our implementations or installations are on-premises, accounting for approximately 90% of the total. The remaining 10% of our implementations are on the cloud.

The initial setup of the product is straightforward. The first deployment may be more complex in one case than another. It depends on the complexity of the processes an organization is building and what they need to consider in future planning. Normally you can install it without much trouble and have your first processes live within a few days.

After that, the project is ongoing and it becomes more complex as you build it out. Normally everything does not have to be in place from the beginning as the solution may be deployed to solve new or future issues. In other words it is not replacing something that is already functioning, it is providing something new. As you build out, you get more processes going and the setup becomes more complex. But the initial setup is quite simple.

The initial setup is easy for the DataStage, but for billing and metadata, it gets more complicated. In our case, before installing the metadata, the proper documentation was not there, which complicated things a bit.

You install IBM InfoSphere DataStage once you've set it up properly. It's robust and reliable, but initially configuring it can be challenging.

IBM has good installation documents. The tool's deployment took a day to complete. 

The infrastructure and the software configuration part was done by one of my teammates. We were able to complete it in two working days. This was only for the installation of DataStage. 

The initial setup can be challenging. It's harder to set up than, for example, SSIS.

I'm not sure how long it took to set up, as it was already in place when I joined the team. However, I would say it took a week to deploy.

We have five people on hand that can handle deployment and maintenance tasks. They are all engineers. 

Depends on type of environment that is being installed. I have seen fairly simple to overly complex initial setups due to the environment, not due to the tool.

The installation was not straightforward and I would rate it at medium complexity.

For the on-prem solution, it was moderately complex. I'm not sure about the hybrid version.

I don't do the setup, but I think that they have many challenges.

Initially, we had challenges with the configuration. We were trying to use the comparison for Excel, and reading the Excel files from the source, but the files were not readable.

The initial setup is quite simple. It didn't take more than half an hour to set it up on my laptop.

The initial setup is not easy. You have to be an expert to install DataStage.

Sometimes I get calls from clients who ask me to install this solution because their Unix administrator is not able to do it. You have to configure your OS, Database, Web server, and more. There are a lot of things to install.  

If you are not experienced then it is not possible to install.

The product is easy to deploy. I rate the process an eight or nine. The deployment time depends on the specific requirements of customers. It takes approximately three months to complete. It requires a team of five to 100 people to execute it, depending on the company size.

It's a straightforward process. In terms of deployment from the data stage, it takes about a week.

The initial setup was straightforward. We did not have issues.

The solution has one of the most straightforward setups. It's even easier than Office.

We outsourced deployment to IBM and didn't have any issues. Implementation took about two weeks. We have between 20 and 30 users in the company and our maintenance is carried out by IBM.

I recall that the setup was quite difficult. We had to call in some IBM people. It's possible that they have improved that aspect. I know there's a difference in installation depending on whether it's on-prem or cloud. It's possible that the cloud version is easier to install but I don't have experience with that. 

It was straightforward technically.

It is quite a complex tool to set up properly in any environment. It requires someone who has experience with the product.  

I've never done an installation but I believe it's relatively complex, IBM usually is. 

The initial setup is quite complex. Actually, it is probably very quick to deploy, but a difficult project. Typical projects about ETL or extracting some information take dozens of days.

It was complex.

The initial setup is easy as it's done through a web installation process with an HA setup option.