Oracle WebLogic Server Reviews

WebLogic is a mature Java application server and when compared to competitors, it excels in speed, scalability and stability. Important features out-of-the-box are the JMS server, database tuning options, full script ability, and Java EE 6.0 support.

It's improved our organization in lots of ways. For example, using the WLST scripting allowed us to build a continuous integration environment. We’ve also managed to increase throughput and reliability by replacing an older JMS server with the internal WebLogic JMS engine.

Although WebLogic is fully supported with different Linux distributions and most installations run on Linux machines, on a clean installation there are no startup or service scripts, requiring time investment and perhaps external help for a robust set up.

I've used it for over ten years. WebLogic server was developed by BEA systems as an early adopter of the J2EE specification and was later bought by Oracle.

We have had no issues with the deployment.

There have been no issues with its stability.

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

Oracle support is expensive, but they're good and available 24/7. Support for any version is for years and any given version of WebLogic is already extremely stable. Bug fixes, security updates, and bundle patches come often.

For a 120 requests/second web shop I was consulted in, WebLogic was chosen because of the seamless service – production redeployments allowed for user sessions ending and the new application taking over without any end-user errors. Rolling upgrades and automatic server migration on failure were also important arguments that other offerings could not match.

As mentioned, some Linux scripting is needed to set up a system that will survive reboots. However, after the first graphic or command-line setup, it’s easy to roll out additional domains: you have many options for different levels of expertise such as domain extension, templating, having the installer saving the installation script and so forth.

I set up implementations for our customers. If implementing a mission critical system, you should consider getting external expertise for advice on monitoring and failover configuration and such.

WebLogic uses a per-physical core pricing model. The basic “WebLogic Server” license does not support clustering and is useless in most enterprise situations. The often-bought “WebLogic Suite” license is very expensive if you do not plan on using the included Coherence cache. Take special care when using virtualization: Oracle licensing will insist on counting the number of physical cores on the hypervisor and will not care for configured partitioning of CPU’s!

When compared to Tomcat and JBoss, WebLogic performed better with the same applications and also allowed for easier scaling and system administration.

WebLogic is an amazing product, reflected by its pricing model. I would always advise on setting up a clustered environment, even if this is not a user requisite, as this allows for more flexibility. Also, consider using Apache with the WebLogic plugin as a web tier and SSL terminator instead of a commercial offering.

We're using the web server very tightly and operating the Java E7 specifications. The most important point for the prime web server is to operate Java E7. WebLogic is historically the default standard of financial systems and our systems interlock with them. I think that WebLogic is best application server, the E7 system.

The web server is just a Java E7 application server. But a special point is the operational functions, especially for the mission controls, and enterprise managers, and some easier management functions.

We are satisfied with the current functionality, but I am concerned about the future of Java E8 and 9. Also the server, the EJB and the RMI, OOP and maybe a T3 protocol in the WebLogic server and the next Java E specifications. The financial systems are increasingly in our company now using RMI over OOP protocols, so we need more support for the future efforts with OOP.

It's basically stable, but sometimes runs out of memory.

We're now using a binary WebLogic server without coherence so the in-memory replication we are operating, sometimes fail. So we are now continuous rebooting, once a week.

We're pleased with the support.

I believe WebLogic is the most important application server.

We are a software solution provider and I am a Java software developer. When I deploy my work, I use an application server like Oracle WebLogic. 

We have not deployed this product for our own use, but rather for a client. It is being used as a SOAP solution for a backend service for a BASE24-eps ACI product. 

The most valuable feature is the performance.

It has good integration with security features, including OWASP.

We have had some problems with cluster solutions when working with a WebLogic domain. It may be because the error codes and error information is poor.

In the future, I would like to see better support for the REST interface.

I have been working with Oracle WebLogic for about three years.

We're having trouble with the stability of this solution.

In our country, we have had trouble with scalability because the DPS is lower.

Our client is a large company, but the market as a whole is small.

The Oracle team is not a good provider when it comes to supporting. They do not have good knowledge of the technical aspects, so Google is better.

The documentation is really good. The community is also good, although the documentation is better.

The initial setup is straightforward. It is not complex.

The deployment takes approximately two weeks at the client's site, on-premises. The total time it takes for implementation is perhaps three months.

In our country, this is an expensive product.

My client is moving from Oracle to a Red Hat solution. The main driver is that it is open-source.

I would rate this solution a six out of ten.