To set up Oracle BPM, you just have to follow instructions. The vendor provides the zip files.

Setting up Oracle BPM on-premises isn't that difficult because you just need to follow the steps.

On a scale of one to five, I'm rating the initial setup for Oracle BPM a three.

The initial setup was somewhat challenging but we had a support from Oracle team.

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

The initial setup was straightforward, and it took us one day to deploy. It can be deployed with an integrator. I rate the setup a six out of ten.

I rate the solution’s initial setup a four out of ten since it’s quite difficult. The solution took a day to deploy.

I would rate the setup as four out of five.

For our implementation strategy, we did some load testing. We expected that the system could handle many concurrent requests and that it would be stable without any issues. Then, we increased to 20,000 requests. There weren't any errors, memory issues, or failures on the network side. The security, utilization, and everything else that we monitored was fine.

I was not involved in the initial setup. It was done six or seven year ago. This was before I joined the company.

The person implementing the solution needs technical skills. Camunda is much easier to implement than Oracle. It doesn't need a developer. A configurator or an administrator can implement Camunda.

Initial setup requires the knowledge of someone familiar with Oracle SOA Suite and WebLogic.

This solution is easy to install. We have a dedicated team for installation and configuring these applications. We never face any issues, and if there are any version conflicts or anything, we can reach out to Oracle's support. Our complete team is comprised of 60 people, but our Oracle BPM team is 10-15 guys. They are a combination of developers and infrastructure support guys. 

If you have an enterprise system then one person is required to maintain it, full-time. Oracle database is not easy to maintain, and in an enterprise application, you need to have a DBA. Normally, if you have one person for Weblogic and one person for the database, it’s enough.

The length of time required for deployment depends on the number of different instances. For example, if you want to have forty BPM and forty processes then the deployment will take a long time.

At the moment we have a deployment of forty instances, and it takes about twenty minutes to run. Most of the time, we need to restart the server because of some kind of error, such as a memory problem. This is absolutely not good in a production environment. The product is not yet mature enough in this regard.

The initial setup is not very easy, as with most of Oracle's products. Some aspects of the setup were not very clear and it took a lot of time to solve challenges. Setting up the system took one week  but we had to come back and change settings many times.

How complex the initial setup is depends on the requirements.

If you need a highly available, clustered solution (Multiple Nodes), then it's more complex than only creating a single node instance.

If you do it for the first time, it seems to be very complex, but there's documentation available (Enterprise Deployment Guide), which describes the needed setup steps on a very detailed level.

The learning curve is steep, but it is a complex technology.

The initial setup is straightforward.

Setup process improved immensely with the 12c version, and it’s very well documented. No issues.