Deployment was easy. Sometimes, the API response is a problem if your payload is heavy.

We have a very huge project, almost 400 services. For developing support and services, it will take time.

We are using cloud and on-prem both. The deployment took around 15 minutes only. The deployment process involves submitting our code, and the admin team takes the latest version of the Endpoint. They then execute some scripts to deploy it.

With respect to implementation, this is a very heavy product. It isn't something that is implemented in isolation. Rather, you have to have applications such as a database and an application server, in addition to the Oracle Service Bus itself.

The basic installation will take a day to complete. After that, you need the resources to run that type of software.

The deployment itself is very easy because you just have to install a service on the application server. 

The initial setup for Oracle Service Bus was easy.

The initial setup for Oracle Service Bus wasn't complex. You can easily install it. There wasn't any challenge with installing the solution.

The implementation strategy my company used was to install Oracle Service Bus via scripts, similar to a DevOps deployment.

Its implementation depends on your skills. The more experience you have, the better designs or architecture you will have. The product might be the same, but the quality will vary based on how you implement it.

The initial setup is complex.

The initial setup is not straightforward. It's very complex. 

The initial setup is very straightforward and simple. It's not overly complex or difficult to implement.

In our systems, we install it for our local development. It's easy for us. It takes minutes to install it. The deployment process is quick.

We have five or six technical people that can handle deployment and maintenance tasks.

The initial setup is relatively simple and straightforward. It's not difficult for a layman to implement, especially the cluster environment. Deployment in an enterprise-level environment requires some experience because there are some complexities. If you're implementing without having modeled the threading effectively, the service performance is reduced. It's not a product limitation, but more about how you implement it. 

The initial setup process depends on project to project, however, typically, everything is paid for. Probably if you want to sell something, everything which is currently being sold in Oracle is specific to the cloud. If they want to move their on-prem to cloud, or they have services, free services, lift and shift services, and of course open-source. You name it and within a month maybe, or three months, depending on the type of job but other than that, everything is costed. Basically, everything, whatever resources you have to buy from Oracle is available and can be taken care of.

Any maintenance requirements are related to whatever package the client decides on. 

The setup was simple and deployment was managed on my own. It took only a few minutes.

Implementation took a few weeks, no more. It was relatively simple I believe but I'm not an expert on deployment and installation.

Initial setup involves a learning curve; it’s not as straightforward as Oracle BPEL. For example, defining custom variables, assigning and replacing different activities is a bit intriguing compared to BPEL.

Initial setup is pretty straightforward for an Oracle product. Again, we know what to expect with it and it works well.

The initial setup is a little bit complex. One of the ways it is complex is that there are a lot of features and the customer may not want all of them. Once you figure out which ones the customer doesn't want, they have to be disabled.

I carried out the deployment and it took a maximum of two hours. We have five users and one specialist who deals with maintenance. 

It may not be for others but I feel that the initial setup is straightforward. It is not complex. 

Once I put in a request and it is approved by a manager, it takes ten to fifteen minutes to deploy.

We deploy both on-premises and Cloud. It's a private company cloud, not public.

It's my understanding that the solution isn't straightforward. It's actually quite complex.

The setup and onboarding process is hard, and it's made more difficult by a murky licensing process that needs to be clarified.

It needs some knowledge of different artifacts and you also need to have some knowledge of Web servers, the application server, something about the database; at least some knowledge. It is not very difficult and not easy. I would put it somewhere between easy and medium complexity.

The initial setup is not complex. It takes less than one minute to deploy.

The initial setup is straightforward.

It took me an hour and a half to install.

We have a team of five including one manager, and four engineers to maintain this solution.