I would rate my experience with the initial setup an eight out of ten, where one is difficult, and ten is easy. 

For someone like me who's been working with Oracle solutions, it's one of the easiest deployments.

I rate the ease of setup a seven out of ten. There were some difficulties. It is not easy for a person doing it for the first time with guidance and an installation document. The process is complex for domain configurations, DB setup, and adding additional features compatible with the product. There are different domains involved. The person installing the product should know which one is better suited for them. It is very complicated. This process should be made easy. The solution is mostly deployed on-premise, but the trend has started toward the cloud. Recently we migrated to OCI. We use Oracle Cloud predominantly.

The initial setup was straightforward; it wasn't too complicated. I would rate my experience with the initial setup as a nine, where one is difficult, and ten is easy.

It took around two days to deploy. The process involved following a set of documentation and guidelines provided by Oracle. We followed the documentation to set up the solution. Some of the steps included ensuring the availability of prerequisite applications like the database and JDK. Once those prerequisites were met, we proceeded with the setup process.

The initial setup was cumbersome. It took almost a week to set up. It required support from Oracle Labs and a lot of training and assistance.

The initial setup was quite complex. We were interested in an HA DR setup with scale out, including multiple web, app, and DB servers having no single point of failure. Hence, we went with an enterprise deployment which is quite a bit more complex than the standard install.

The initial setup is straightforward and easy. I think in a week it can be implemented if we have the entire infrastructure.

The initial setup for Oracle SOA Suite is seven out of ten.

It was not really complex and not really straightforward. It was somewhere in between the two.

We are currently using the DevOps model, so it is deployed through DevOps. Deployment is not taking much time because we are not doing it manually. It is an automated deployment.

Usually regarding Oracle products, deployment takes time because it requires manual effort to go around and deploy the code correctly.

The initial setup of the solution is easy because I have experience with it.

It's complex for 11g, but in getting started with the new 12c platform, we have seen far greater development although production environment are still a fairly sophisticated task.

The initial implementation has improved a lot with the latest version. It used to be a more complex activity in the past, while with the latest version the installation is smooth and more straightforward.

The initial setup was complex. It was more of a brownfield. The deployment took one year.

The initial setup is straightforward. I rate it an eight out of ten.

Initial setup was full of learning.

The installation was very straightforward. We have encountered issues in the production environment for missing several configuration where we spent more time in streamlining all the environments.

The initial set up was easy, as there are lot of resource available online.

The initial setup is not very complex.

Our scenario is different. We do not have write access in our production environment, so we have to depend on Oracle Managed Services. Because they have to make the changes, it gets a little bit delayed. If we had the write permissions then it wouldn't be an issue.

Initial setup was pretty straightforward, but we had one of the Platinum Partners come in and actually install it. They knew how to do it and there was pretty minimal involvement from us.

SOA Suite setup was fine as it installs per their instructions. Our biggest issue we had was with our API integration from agile to EBS. It took us several months to get that up and running correctly, with a lot of escalated Oracle support around that. It was a tough nut to crack but we eventually got there.

I wasn't directly involved in the setup. Nonetheless, I would say it's as straightforward as it can be considering our environment.

It is very easy to set up a development environment by using Quick Installer.

The effort and complexity remain same for traditional setup of production or test build as we used to have in it's previous version 11g.

The complexity increases with implementation of high availability environment in expected line.

If you know it, it's straight forward. If you don't know it, it's rather complex and can be very tricky. If you haven't invested time, you will make mistakes. Then it is not very simple to get back and start again.

The complexity of setup depends on the set up. For developers and/or development environments, setup is very simple. With SOA Quickstart, it only takes a few minutes to have SOA Suite and full IDE up and running. For production environments, it takes a bit longer. However, there are several ways including products that will automate full installation out-of-the-box.

This is a complex environment so unless an experienced administrator is involved, having an environment that is clustered and load balanced requires quite a bit of time. There are third-party tools to automate this configuration, but there is nothing currently out of the box to ease difficulty the installation issues customers run into.

Initial setup is straightforward and there is plenty of documentation available on the Oracle website to help you with it.

The installation can be straightforward if you follow the right guidance from Oracle. The infrastructure needs to be properly done.

The full implementation took use approximately one year, but it was because we have a  disaster recovery(DR) site also. We had to install it on both sides. We installed it on the DR site, used it, then copied it onto the DC site, the goal was for it to be faster.

The initial setup is neither straightforward nor complex. It always depends on the specific situation, like the available IT system landscape, the already existing applications, and the needs of a project.

The platform as such can be installed following best practices provided by the vendor, such as the Enterprise Deployment Guide. Oracle partners also provide tools that support you in infrastructure setup and maintenance.

The initial setup has been improved with this version 12.1. Development environments are autonomous and faster to use and to deploy.

However, the Oracle solution is based on a JEE architecture which teams must mastered. Otherwise the length of growing competence is long.

Initial environment setup can be complex (this is different for the SOA Suite Cloud Service where provisioning is largely automated). There are many steps to perform and choices to make. Also, the installation is layered. You require a supported OS, the application server needs to be installed on top, the database needs to be prepared, and the SOA Suite must be installed in the application server. There are other components like load balancers, HTTP servers, etc. which might need to be configured. High Availability is supported on all layers and multi-tenancy on almost all layers, but you need to think about how you are going to implement this.

I think for a developer instance, it's straightforward. You can just follow the wizard and click Next, Next, Next. For production, it's quite complex. For every other element in your IT, because it's an integration product, so naturally it has complexity because you need network connectivity, you need to know what type of storage, you need high availability, and you need to tune it.

I think that one of the things that can ease that is automation of the installation. We use scripts for that, so we don't forget anything. Of course, the other option is the SOA Suite in the cloud. Oracle took away part of the complexity by offering the wizards in the cloud.

Installation is not a product strength as mentioned above. Depending on the components that you install and the scope of your project, things can get a bit complicated.

SOA Suite is a bit challenging. SOA Suite has a lot of products inside it but they're all bundled together. You have the option of bundling them all together when you're installing and then adding additional components once you've installed. That process is straightforward, but it is very complicated. It is straightforward for demos, but when it comes to enterprise-grade deployment, it is very complicated.

The initial setup was complex without proper documentation.

The Initial setup of the product is straightforward as long as you do your pre-planning and follow the prerequisites. Also, occasionally you encounter an issue that requires that a ticket be created with support or independent research must be done to resolve the issue (i.e. search the web or read blogs for missing steps.)

For trying out a developer edition, the installation was easy unlike previous versions. The automatic upgrade from 11g to 12c was not painful.

It was medium. The initial setup is not very complex, but you need specific skills to do it right.

Initial setup in the previous version was quite complex. It has improved a lot in the 12c version. Still, you need to configure quite a few things before you get it right. Some of the things are not easy to configure. Also, there are number of places where configuration is required and that makes it a bit tricky.

The initial setup was done by our third-party implementer. The main solution we used it for was obviously for EDI. Going forward, it may change.

Setup of the development environment has become a lot easier, as has the production environment. For the production environment, I would recommend someone who has done this before.

Setup is straightforward, particularly for development environments. For production and separate domains, you need to know what you are doing. However, the provided documentation is adequate.

The initial setup is pretty good, actually, and it's very well documented.

The initial setup was not very straightforward and is a bit complex. During initial setup, many things need to be taken care of -- DB installation, dehydration store version, number of CPUs, RAM size, heap size, Java versions and their conflicts, and many other configurations. We have to follow each step carefully, and it's not the same for all servers.

Initial setup was really complex.

Until version 10, the initial setup was cumbersome. Over the years and subsequent upgrades, with 11g setup became easier and, now, setting up with 12c is a walk in the park.

Quick Install is quick and easy. It takes less time to install and there is no complexity while navigating through the setup screens.

There are two kinds of setups possible. The "Quick Start" and the "Regular" one. The first is targeted at individuals trying to get a glance at the product without too much time invested on installation and configuration. It comes with a development environment ready to use (including an integrated application server and a database) and is installed in a few minutes. The "Regular" setup is intended for production use (or other environments) and takes longer due to custom configurations that might be needed, but is well documented.

The initial setup is complex. There are many things involved and if you don't know it very well, you can damage the installation.

SOA Suite setup and deployment is very user friendly and easy to implement.

The setup was not really straightforward. I think it was medium complex.