WebLogic Suite Reviews

The most valuable features are that it's easily deployable and easily scalable. It'll shrink and can grow as much as you want. Those are the benefits, but when compared to other products, such open-source Tomcat, we've considered moving from WebLogic to Tomcat because WebLogic is very expensive.

It's scalable for the company and easily deployable. The GUI and integration with SSO is more beneficial than other available options.

It's definitely a complex solution. It throws at least a million lines of errors just for one password. You can get a small issue that could potentially generate about a thousand of lines with warnings, and those warnings might mean nothing. It will just pop up warnings, so you'd have alerts for nothing. It's not that easy from the admin perspective if you're not really familiar with what you're getting into. It's not 100% GUI, so that you need to know lots and lots of configuration files.

We've had no issues with deployment. In fact, it deploys very easily.

WebLogic is not a light product. Java uses the whole memory of the server so it's a memory hog.

We've had no issues with scaling it for our needs.

The initial setup was easy and pretty straightforward.

We did the implementation ourselves with our in-house team.

It's quite expensive.

If it were like Tomcat, configuring .xml files would take care of some things, but there's not a particular main .xml file available with WebLogic. In fact, there are so many important .xml files that are needed for WebLogic.

It's highly expensive and there are other much, much better products out for the cost of peanuts.

We mainly use this program for forms and reports, as well as application provisioning for Java and so on.

This solution has greatly improved security wise over the last couple of years. The user experience is much better now than it was in the previous version, version 12. And the new inference manager is also much better.

All the areas of this program needs to improve. The integration with other providers and the user management could be better, and the upgrades are pretty complicated. So I would like to see that being improved in the next version.

The program is stable and we haven't had any issues so far.

The program is scalable. You can create domains so we're fine with it. We currently have around 50 internal users and we have customers that which are big, state companies or government companies that use our solutions extensively. 

The first line of support in India is quite bad, but as we go further into the problems, we are referred to some really good technical guys, and they are really great. But it's not immediately opened as a priority one issue of support, so that's pretty bad.

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.

My advice to others would be: don't complicate things. Keep it simple. On a scale from one to 10, I rate this solution a seven. I think the support could be much better. So perhaps the developers can work on that. Also, the WebLogic management console could be more intuitive or more up to date, because it's still the old console from version 10. Bring us up to enterprise manager or cloud control, which has been in design and very intuitive.

The most valuable feature is the update deployment feature. Update deployment is when you already have an application deployed and you want to handle a new deployment. The feature ensures you don't need to add or remove anything. Rather, you just need to update and the feature will handle everything else, like adding the new features that have been released on the new deployment. It's very simple.

I had issues when I installed the SSL. With WebLogic, it's a very lengthy process.

The solution isn't 100% stable, but it's pretty good. I'd rate it 3.5 out of five in terms of stability.

Scalability on the solution is great. It's very very easy to scale.

I've never had to reach out to technical support.

The initial setup is very simple. 

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

The licensing for the solution is pretty expensive. It may be the most expensive solution, if you were to compare it to the competition.

I'd suggest those considering implementing the solution to move to the cloud. It's very simple and easy.

I'd rate the solution eight out of ten.

It performs well.

It is connected with our systems, and our systems run on Oracle. It is beneficial because it integrates with our internal systems. This resolves half of our problems for our internal system integration, data retrieval, and subscription to specific events.

A valuable feature is its integration with Oracle Database. We have another system running Oracle Database which can be easily updated from the database and pushed to the middleware. Also, it easily connects to other Oracle products and services.

We need to have more adapters and connectors, especially healthcare system adapters. This solution doesn't have connectors to other external applications. We connect with other vendors' and other companies' systems, therefore we have been asking Oracle for specific interfaces because we have been unable to integrate with these systems using any adapters.

It is stable.

Scaling is costly. 

Technical support is very costly.

We tried to connect our healthcare systems with Oracle, and it needs a lot of support. We would needs to hire a consultant, and the consultant would cost us $4,000 a day. Therefore, it's very costly to integrate with the other systems, which is why we are looking for other alternatives.

I was not involved in the initial setup.

In general, it is a costly solution.

Microsoft.

I rate this solution as a seven out of 10, because it is not fully satisfying our needs. It is good in specific areas, but it's not satisfying all of our requirements. It is not a one stop shop.

Most important criteria when selecting a vendor:

• It is affordable.
• Easy to use.
• Ready documentation, training, and examples.
  

It's a very scalable, extensible, middleware component. It's especially useful for big data applications if you're using APIs or have geo-spatial data or complex data sets.

It's also a very affordable and efficient.

I would like to see Oracle offer the WebLogic Suite in other areas, like SaaS or PaaS. From what I've seen at Oracle World, they're already moving in that direction, so it gives you a broader portfolio or different ways to leverage their technology.

We haven't had any issues with deployment.

It's very stable. It can handle a lot of database storage and repositories. It's really the backbone of a lot of our systems that we use for our federal customers. It's very smooth and not buggy, and now that more people are learning how to troubleshoot and work with the product, it's becoming exponentially easier to find quality to support it during the WebLogic application process.

Obviously, it works best with Exadata servers, so that's what it really helped us with. We were running WebLogic on servers that weren't optimized for that software. I think we may have had it on IBM Blade and the servers we were using weren't necessarily optimized for the WebLogic tool. Once we kicked in the Exadata server, it increased the time to process.

The level of technical support is very good. The SMEs that are coming to help us have been excellent. It's very easy to get a hold of them and we talk weekly with our account reps to make sure things are going well. They are very approachable and always easy to get hold of, as well as being very knowledgeable.

We just like Oracle products.

I like that fact that it is the most scalable and the best-of-breed application server for hosting any kind of an application. One of the best things about WebLogic Suite is that the enterprise customers we work with have a broad spectrum of Oracle products that they use, from BPM to E-Business Suite to whatever. One thing common to all of these solutions is the fact that they're all on WebLogic server.

It's multi-tenant, is highly available, and I believe it's the best-in-class application server for Java. Most of Oracle's products are in Java, so they are all supported on WebLogic Server. That is one of the biggest aspects. It's very reliable, it's enterprise-grade, so we get great support from Oracle as well.

Technically, there's absolutely nothing that you cannot get from a WebLogic Server in terms of availability and scalability. It is very easy to maintain, and if you look at other JMX process based servers, they don't give you a great console. But WebLogic Server gives you a console for administration, creating resources, managing those resources, troubleshooting, diagnostics, and everything else all in one place.

In an enterprise, a solution is not delivered by a single system but a lot of them. You would often find that to achieve a particular business function, you're using ABS, you're using Server Suite, you're likely using several other solutions. So WebLogic Server provides one common platform for deploying all of these applications, and you don't have to invest in five different application servers for five different applications that you're using. It helps consolidate your systems, especially your middleware servers.

Multi-tenancy is needed. It is starting to come in the latest releases, but it is a very basic multi-tenant feature at the moment. I would like a more enterprise-grade multi-tenancy feature coming into WebLogic. Many organizations use WebLogic for all of their applications, but what we also have to think about is that each application wants to share the platform, and they want some sort of isolation from other tenants or other business units in an organization. How WebLogic addresses that challenge is by having multiple tenants that share the same infrastructure without disturbing each other.

I've been using WebLogic since v5.0 to v12.2, where it is right now.

We've had no issues with deployment.

Stability is not necessarily dependent upon WebLogic, but it depends upon the type of application that you deploy. It's a common platform where you can put pretty much everything. Most often than not, what we see is a combination of WebLogic and the application that you deploy on top of it which causes stability issues, not just in isolation.

For example, you know that you have Java and that Java has memory leaks. But it's not just Java that's causing memory leaks, it's the application and Java in combination that can cause this problem. The same thing with WebLogic, so it's not just WebLogic alone. It is almost always your application as well as WebLogic Server together that causes a problem. But as a platform, it is very stable.

We can scale it to thousands of users without a problem. We've had no issues at all with scalability.

The initial setup is very easy and very straightforward.

Our team works on it every day but; I don't do the technical work. I'm an operations manager and I  manage the team.

It runs smoothly and everything works fine. 

It integrates well with other solutions.

Sometimes there are issues when we work on a VM because people use it to put all of their reports on it at the same time. Then I have to restart and rebuild the machine. That is more of an issue with the users though. 

I have around 10 years of experience working with this solution.

We have between 40 to 60 users who use this solution.

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

I would rate it a seven out of ten. 

The client is happy and there are some issues sometimes with the scalability but it's probably because of the users. Otherwise, we don't have any other problems. Sometimes there are issues with the reports. 

One of the most valuable features of WebLogic is that deployment is an easy process. The code can be deployed on multiple instances without rework.

With a huge number of servers for our application, manual deployment would be an extremely tedious, error prone and time- (hence money-) consuming process. WebLogic has assisted us in this aspect.

The initial setup and administration does require expertise. While bigger organizations can afford to have dedicated horizontal teams, I assume smaller organizations may not be able to afford this. The default setup should include more features such as more scripts and more users with different privileges, which could resolve this issue.

I have used this solution for over four and a half years.

I did not encounter any issues with stability.

I did not encounter any issues with scalability either.

WebLogic was our first choice.

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

Licensing is expensive but it is worth the cost. If you are going to utilize all its features, then you should go for it. If you do not have enough budget, you could choose for other freeware options and use automation and orchestration tools instead. This will surely have an impact on stability in the initial phases of implementation.

Although, I was not working while choosing it, WebLogic has been the first choice for organization. However, now after many years we are evaluating to look for other freeware options.

You need to consider the licensing and upgrade costs. In addition, it will help to have a dedicated administration team.