The solution is easy to set up.

The initial setup for WebLogic Suite on the cloud is just "Click, click, click", and that's it. It's very easy. Though the on-premise edition of the solution needs some installation and configuration, it still isn't so tough or complex. It has become easier nowadays, particularly in the last two versions of WebLogic Suite, where the setup has been quite easy and straightforward. Enabling the features of the solution isn't that difficult as well. It's easy. On the cloud, setting up WebLogic Suite is pretty easy.

I'm running the tool from Oracle Private Cloud Appliance. Since I have some training, I can easily deploy the solution.

One major pre-installation question that catches you unaware is the question of a "standalone" versus "single node cluster" installation style selection. Single-node clusters can be scaled up and out. Standalone installations are single-node only, and would have to be re-installed to enable clustering. This is an old throwback to the original licensing model, and tends to be a source of odd frustration if you choose the wrong one inadvertently. Most of the modern upgrade releases are now out-of-place upgrades (meaning they install to new installation file system bases, and not overlaying an existing install). This change was designed to maximize uptime, but does mean you'll need the extra storage available to have the side-by-side software reside during the upgrade process.

The installation was easy, it took approximately one week.

One major pre-installation question that catches you unaware is the question of a "standalone" versus "single node cluster" installation style selection. Single-node clusters can be scaled up and out. Standalone installations are single-node only, and would have to be re-installed to enable clustering. This is an old throwback to the original licensing model, and tends to be a source of odd frustration of you choose the wrong one inadvertently. Most of the modern upgrade releases are now out-of-place upgrades (meaning they install to new installation filesystem bases, and not overlaying an existing install). This change was designed to maximize uptime, but does mean you'll need the extra storage available to have the side-by-side software reside during the upgrade process.

I wouldn't say that the initial setup is very simple, but at the same time, it is not. It needs an external person to do it, so I will say moderately complex, rather than very complex, and it needs an expert.

I would estimate the time for deployment between one and three days.

The initial setup is complex. We did a migration from WebSphere to WebLogic.

The reason it's complex is it was already running, but it was a very different animal than WebSphere. There were code changes required, which fell to the developers on the development side. On the operational side, things like fine-tuning little things like the data sources work a bit differently, but once you figure one out, then the rest all falls into place.

At the moment the deployment model we use is on-premises, and nothing has been migrated to the cloud. It's a project for the future.

The deployment was approximately just over one year to get it migrated fully to where we were stable enough to turn off the WebSphere.

It was a little bit better than I had expected it to be. We all felt it would be an eighteen-month to a two-year project, and it did come in a little bit less than that. But of course, the business expects it in three to six months. We did try but realized that it was not going to happen unless everything just magically works the first time.

I'm on the operations side, I'm not on the development side. We look after the infrastructure and the upgrading.

The developers are a large team. On the operations team, we have approximately ten people. One person can do a feature release, which is what we call a deployment, in an evening. This is done three times a week.

The initial setup was easy and pretty straightforward.

The initial setup of WebLogic is very easy. You only need about 10 minutes to start the application. Compared to other Oracle products, it's very straightforward and easy to configure. 

The actual WebLogic we're running runs on Oracle Linux, and when we put that on, we found the documentation to get the High Availability running quite complicated as well. Also I would say when Oracle releases these new versions of their products, you find that the support you get isn't probably what it should be. It takes a long while for support to ramp up and to get the knowledge of the new products, so I think a good thing would be for these products to come out unreleased to businesses. Then the support people should be brought right up to speed and be ready for any questions because by the time you get to an engineer who maybe knows the product or knows the situation you're in, it takes an awful lot of escalation time.

The initial setup was not handled by myself. We have a separate team that handles the actual installation of WebLogic. However, I didn't see challenges in the implementation and the team didn't raise any issues that I know of.

We did not require vendor support. Setup was done by my team and me.

The initial setup is very easy and very straightforward.

The initial setup is very simple. 

If you have everything ready from the OS side, it requires one to two hours to deploy.

The initial setup was relatively straightforward. Basically, it’s a couple check boxes, a few nexts and then a couple configuration items and connection strings. An amateur computer user could go through it and use it straight away.

It's straightforward and easy to install and set up. There is plenty of documentation and online experience to follow and learn from.

The initial setup was straightforward.

The initial setup was complex at first, but we soon got the hang of it and then it wasn't too bad. To deploy it by hand takes a couple of hours, but provisioning with a custom script takes around 10 minutes. It depends on the environment it will be run in.

I was not involved in the initial setup.

The setup was complex but there weren't any issues.

We only had to deploy this solution once. Since that time, we have switched it off and on every two or three months for maintenance.

The initial setup doesn't take much time although it really depends on the quality of the infrastructure. 

We didn't set up the solution ourselves. Rather, we hired our vendor to handle all of the implementation details for us.