The initial setup for Oracle Data Integrator (ODI) was straightforward, and Oracle has good documentation.

The initial setup is neither easy nor complex; rather, it is moderate. We need to set up the complete system and its topology. First, we have to install and configure the ODI repository. Next, we need to prepare the appropriate topology, develop the necessary components, and deploy them. Typically, we separate the work of designing the repository from the execution phase. Afterward, we import it into production, where only the execution repository is present.

The initial setup of ODI is not simple. We need to install Oracle BI applications to use ODI to access the tables that are built in or provided by Oracle. It is an on-premise system and it would help to make the process easier.

The setup is straightforward but designed for professional use rather than beginners. It's at a normal level of complexity for such a product.

In 12c, they have made the setup so much more simple then what it used to be. The interface to do the setup walks you through every setup step.

The initial deployment is very simple and we carried out the implementation in-house.

The initial setup is complex, especially if you also have to install a console. Deployment takes a day or two. 

The initial setup is simple. There are several things to check with ODI. Prerequisites include space, database memory, CPU allocation, and so forth.

The initial setup for Oracle Data Integrator (ODI) is straightforward.

In terms of the initial setup, at first, it was a bit hard for me. That said, it is pretty straightforward once you are done with this data source connection tool and once you are done with this on the repository side. Setting up a reporting server was easy, however, doing the middleware, especially on the application server, was a bit tedious for me.

I'd rate the setup process a four out of five in terms of ease of implementation.

The initial setup of ODI was straightforward. The full implementation took us approximately two months because of our architecture, it was not the fault of the tool.

ODI has one of the easiest implementations out of all the others for a database.

The solution's initial setup is straightforward, especially compared to Mule, which our team has worked with before and found to be a bit more complex in terms of setup. Pentaho Data Integration and Hitachi Data Integration are also good.

Since the deployment of Oracle Data Integrator has already been done, the customer provides the platform or software. Another team is responsible for maintaining the solution while we have published some of its services. It takes around three months to deploy the solution.

It was straightforward and very easy. Almost the same as setup>next> next>next.

Although the initial setup was straightforward, you must decide if you will create one schema for the master and work repository or separate schemas. However, the product provides a step-by-step menu-driven UI, which makes the installation a breeze.

The initial setup is easy. It took about two and a half months to deploy.

The deployment takes at least 30 minutes. The tool has a lot of prerequisites. If we don't have a consultant or expert to help with the deployment, we won’t be able to complete it within 30 minutes. It would take longer. We must install JDK and the OBIEE repository that contains ODI packets. The software setup is confusing. The installation can be done in-house if the SOP is clear with the prerequisites and steps to follow.

The bigger the environment, the bigger the challenge is you need to face. Maybe one day Oracle will integrate all their tools. It'll be easier, and the good thing is that I saw a lot of improvements over the years.

The initial setup is complex, it took us three months.

Getting the right JDK during agent config on Solaris was challenging on one occasion. It needs a Solaris expert to do this but in general when one knows the bits and pieces of the tool it should be straight forward .

The initial setup is a bit complex as it needs some repo schema setup and agent setup.

The initial setup of the solution is not complex. It's very straightforward. We found it to be easy.

For simple mapping, deployment only takes about half an hour.

We handle the maintenance ourselves. Occasionally, we may reach out to Oracle for certain tasks, however, largely, we deal with everything maintenance related internally.

Set up of ODI Studio and the ODI repository is relatively simple, it is all done through a single JAR file executable. The complexity comes when you need to create ODI agents - there are three flavors of agent and the best choice of agent will depend on your agent management needs and infrastructure. The ODI agent executes ODI code and interacts with the host OS, typically one agent is sufficient, but more may be needed.

Initial setup for version 11.1.1.7 of ODI was a little difficult, but installing 12c was really easy.

It was straightforward as the installation is fairly easy and well documented.

The initial setup was a little complex because the architecture of the product was blurred, so I needed some weeks to understand it.

As a customer to a consultant team, I was involved in the installation and deployment of ODI. There were some challenges, which was probably due to the relative inexperience of the team that handled it. Eventually, they were able to get through it. Fortunately, my internal team as costumers were also able to do our research and participate in that discovery, too.

It was straightforward. I used an application server for the initial setup and I did not find any challenges.

Initial setup is straightforward. If you are from a technical background, it's pretty straightforward.

The initial setup is not really easy. To use ODI you must:

• Install the ODI studio (client)
• Create and configure a master and a work repository to develop on them, being sure that they can reach the database schemas you’ll work on (relational structures involved in the integration)
• Install and configure an agent (if you need to communicate with more than a server and to schedule integration tasks), choosing properly where you need it and opening all the communication doors to allow it to reach all the parts of your architecture

The initial setup is extremely easy and straightforward.

The initial setup is not that straightforward, you have to know how it works to deploy and implementation takes several months. We use managers or admins for deployment. 

The initial setup was rather complex but I knew what I needed to do to achieve the end result. There are also allot of reading material on these products if you get stuck

Well, it is certainly not the "Run the installer, click Next Next Next Next and have it up and running" kind of an install. There are many types of ODI agents that need to be installed and tweaked on uncountable number of servers so it does take a while to get the whole thing functional. It is all well documented though. Don't expect any major issues here but make sure you book enough time for the initial setup.

For me, it was straightforward if installing it on a desktop. There is more complexity when installing it on a server. Agents are involved and in v10, it was not easy to install even the agents.

All ODI, all the ETL tools, they have mappings and knowledge bases and the like. Based on that, I don't think it is too complicated. It is fine. There is a learning curve, but this is going to be orchestrated by IT, not by business users, so I think it's fine.

The initial setup is really not straightforward. You really have to think about the architecture in which you want to use ODI (i.e., agent(s), repository setup, topology). But this makes the software as flexible as it can be.

I wasn't involved in the implementation, but I haven't heard that it was particularly complex.

The initial implementation was simple, and there are no issues to report.

I can say that the level of complexity of the initial setup is medium. It is not straightforward because each customer may need specific logic on ETL approaches, so this means that your Knowledge Modules are mostly customized. Although except after the first installation and environment definitions, it is pretty easy to do after that.

It was quite straightfoward.

We did a migration for Oracle Warehouse Builder to Oracle Data Integrator 12c using the migration tool provided by Oracle. And I've to say I'm surprised to see a migration tool working so well!

It's straightforward to set up.

Straighforward except for DBA involvement during installation for schema creation.

The initial setup really depends on the situation so it can sometimes be more complicated. When it comes to implementation, a deployment will usually take around 40 days and up to six engineers. 

I think that the initial setup is amazing.

The installation of the client tool: ODI studio is easy.

The installation is rather straightforward, with the available documentation it must be possible to do the installation by yourself. You must have sufficient knowledge of Oracle Data Integrator to make the correct decisions during the creation of the architectural setup.

The initial setup was straightforward.

It was straightforward.

The first time might look a bit complex but using the right documentation it should be easy to handle.

Straightforward set-up.

It is relatively complex for a first-time setup. There is a need to set up separately the RCU configuration of agents, and there's definitely a learning curve to this.