What is most valuable?
Ease of scalability through both assymetric and symmetric clustering; ease of integration with existing and potential future Oracle product technologies; leverages many industry-standard technologies for application support (JSON, REST, SOA, JavaBeans, J2EE; continues to evolve towards a fully-integrated solution designed to front-end enterprise applications whether related to transactional websites, dynamic content management solutions, or acting as an intermediary service provider between other web/URI data sources.
How has it helped my organization?
Provides a uniform technology platform between multiple application installations, whether Enterprise Resource Planning or Customer Relationship Management (ERP/CRM) based systems, Imaging ingestion and integration, or document content management. Administration techniques are consistent with only minor UI changes between versions, providing relatively seamless upgrade integration for future deployments and upgrade of the web platform.
What needs improvement?
Cloning and replication (detailed below) could be much more flexible and standardized. WebLogic out-of-the-box installations are only templated and automated for Oracle-packaged applications. For independent installations, answering the myriad WebLogic setup parameters can be quite confusing as to what are the correct parameters, other than the defaults (some of which are not provided.)
While many seasoned DBAs like to attribute how Oracle's 3-click Weblogic "Typical Install" type is easy-peasy, what doesn't meet the road requirements is that 90% of current WLS installs are to support purchased Oracle applications (OBIEE, EBS, SOA Suite, Identity and Access Management, etc.) and not the historic period of when companies bought BEA as an enterprise alternative to Apache.
The OUI templates that come with the packaged applications tend to whizz you through the 27+ pages of the "Custom Install" without guidance as to why you're picking certain options, nor why you should or should not select different options. With most WLS build settings, you can't go back and reconfigure an existing setup once deployed. For example, even though it's the same WLS engine used, I cannot change an EBS configured WLS to run as a SOA Suite shared install. I have to do it again as a separate installation.
Costs customers money and time. Works, yes, but less than efficient.
For how long have I used the solution?
Installations first went live in 1998 with version 9.x (originally packaged as BEA WebLogic through IBM) supporting Maximo (Enterprise Asset Mgt) and Cognos (BI) and have continued post-Oracle acquisition to support eBusiness Suite R12.2 and Oracle Enterprise Manager 13c.
What was my experience with deployment of the solution?
Generally the only major concerns involve legacy Operating System desupport which has occurred over the years. Platform migrations have been planned ahead of each lifecycle change in order to mitigate application availability issues. Since the binaries between OS's are not compatible, we do have to exercise some level of re-implementation each time a platform (hardware or software) change forces such migration.
What do I think about the stability of the solution?
Weblogic tends to be extremely stable once appropriate memory and CPU requirements have been determined for a particular application under production load conditions. When given insufficient resources, like any web application platform, we have had our share of out-of-memory errors or exhausting a Java virtual machine's capacity.
What do I think about the scalability of the solution?
Being extremely scalable is one of WebLogic's best features. If you anticipate dramatic upward changes in capacity, one of Oracle's Universal License Agreements might be the best approach as it decouples the CPU-based license costs from the costs to scale. In our case, we often use the same WebLogic servers for multiple applications to reduce overall licensing and maintenance costs. As long as the application is compatible with a particular version, they can co-reside (multi-tenant) on the same WebLogic cluster, keeping in mind that the additional CPU and memory resources need to be accommodated.
How is customer service and technical support?
Service with Oracle tends to be directly related to your amount of new product purchasing. This can be a disadvantage to mature and stable installations that don't tend to expand much (i.e. don't expect weekly follow-up calls.) A significant improvement will be experienced by customers who adopt one of Oracle's emerging technology products (such as Cloud-based WebLogic Services) wherein the success of your implementation often becomes the next customer reference for Oracle. That doesn't last forever, but it's nice to experience during the often rocky start-up stages of new technologies. Technical Support
My Oracle Support takes a little getting used to for new customers used to more narrowly focused technology vendors. The vast number of different products Oracle supports has created a bit of a maze of how to get connected to the technology group best capable of answering a particular question, or dealing with an issue. For example, what starts as a "My application isn't available" issue might stem from access management, database, middleware technology, the application group, or because some 3rd party plugin failed causing a cascade failure. Oracle does attempt to support all of its products with alacrity, but it helps a lot for you as the customer, to know how it all fits together. Your perception could range from 4 to 9/10 depending on your experience level with the products.
Which solutions did we use previously?
We use a half-dozen different appliication server technologies - which one is used depends more on application compatibility than choosing one specific one-size fits all solution. These include Microsoft IIS, LAMP (Linux-Apache-MySQL-PHP), InfoSphere, and many smaller vendors.
How was the initial setup?
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.
What about the implementation team?
This depends on whether we have experience configuring the new application being hosted, or not. WebLogic by itself, is simply an application hosting architecture. But most applicaiton deployments are not as simple as visiting an online store and clicking an Install button. WebLogic is not what I would recommend for quickly standing up a proof-of-concept beta application. But when architecting a solution for hundreds, thousands or millions of users, it's perfectly suited.
What was our ROI?
For our installations, we've recovered our initial procurement costs within the first five years of operation, simply by re-using existing excess capacity to host additional applications. Once configured for production load, there is very minimal day-to-day administration required, and integration with Oracle Enterprise Manager monitoring allows full transparency to all processes and targets within the WebLogic technology stack.
What's my experience with pricing, setup cost, and licensing?
As an application platform, you will need to carefully forecast your overall user and process load, and service-level agreements (SLA) in order to purchase an appropriate CPU count licensing, and host licensing for clustering, if needed. If your growth and capacity requirements aren't easily determined, you may want to consider Oracle's hosted Cloud options which have more of a capacity on-demand pricing model (especially the Public Cloud version.)
Which other solutions did I evaluate?
As mentioned, we purchase based upon application-focus, and not for custom development. As a result, choice of application hosting technology is driven according to compatibility and certification, rather than technical featuresets.
What other advice do I have?
Cloning and replication of WebLogic instances isn't exactly a rote science. Because the stacks become secured against the hosting environments, encapsulating and re-cconfiguring a working installation into a new set of hosts (with differing names and IP addresses) involves several procedures to re-secure, re-encrypt and reinstate the software to hardware trust certificates. While this process is relatively encapsulated for WebLogic in eBusiness Suite, sometimes it's faster to simply re-install WebLogic on the new hosts, than attempting to re-configure from a backup from a different host set. This is differentiated from the process of scale-up or scaled-down of a cluster, which is a well-defined process by comparison (and automated as an Oracle Enterprise Manager provisioning process.) Once deployed, most change management involves the deployment of application services between instances, and not replication of the WebLogic environment itself.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Nov 29 2016