Tuesday Sep 01, 2015

Active GridLink URLs

Active GridLink (AGL) is the data source type that provides connectivity between WebLogic Server and an Oracle Database service, which may include one or more Oracle RAC clusters or DataGuard sites.  As the supported topologies grow to include additional features like Global Database Services (GDS) and new features are added to the Oracle networking and database support, the complexity of the URL to access this has also gotten more complex. There are lots of examples in the documentation.  This is a short article that summarizes patterns for defining the URL string for use with AGL.

It should be obvious but let me start by saying AGL only works with the Oracle Thin Driver.

AGL data sources only support long format JDBC URLs. The supported long format pattern is basically the following (there are lots of additional properties, some of which are described below).


If not using SCAN, then the ADDRESS_LIST would have one or more ADDRESS attributes with HOST/PORT pairs. It's recommended to use SCAN if possible and it's recommended to use VIP addresses to avoid TCP/IP hangs.

Easy Connect (short) format URLs are not supported for AGL data sources. The following is an example of a Easy Connect URL pattern that is not supported for use with AGL data sources:


General recommendations for the URL are as follows.

- Use a single DESCRIPTION.  Avoid a DESCRIPTION_LIST to avoid connection delays.

- Use one ADDRESS_LIST per RAC cluster or DataGuard database.

- Put RETRY_COUNT, RETRY_DELAY, CONNECT_TIMEOUT at the DESCRIPTION level so that all ADDRESS_LIST entries use the same value. 

- RETRY_DELAY specifies the delay, in seconds, between the connection retries.  It is new in the release.

- RETRY_COUNT is used to specify the number of times an ADDRESS list is traversed before the connection attempt is terminated. The default value is 0.  When using SCAN listeners with FAILOVER = on, setting the RETRY_COUNT parameter to 2 means the three SCAN IP addresses are traversed three times each, such that there are nine connect attempts (3 * 3).

- CONNECT_TIMEOUT is used to specify the overall time used to complete the Oracle Net connect.  Set CONNECT_TIMEOUT=90 or higher to prevent logon storms.   Through the JDBC driver, CONNECT_TIMEOUT is also used for the TCP/IP connection timeout for each address in the URL.  This second usage is preferred to be shorter and eventually a separate TRANSPORT_CONNECT_TIMEOUT will be introduced.  Do not set the oracle.net.CONNECT_TIMEOUT driver property on the datasource because it is overridden by the URL property.

- The service name should be a configured application service, not a PDB or administration service.

- Specify LOAD_BALANCE=on per address list to balance the SCAN addresses.

Using Orachk to Clean Up Concrete Classes for Application Continuity

As I described in the blog Part 2 - 12c Database and WLS - Application continuity, Application Continuity (AC) is a great feature for avoiding errors to the user with minimal changes to the application and configuration. Getting rid of any references to Oracle concrete classes is the first step.

Oracle has a utility program that you can download from MOS to validate various hardware, operating system, and software attributes associated with the Oracle database and more (it’s growing). The program name is orachk. The latest version is and starting in this version, there are some checks available for applications running with AC.

There is enough documentation about getting started with orachk so I’ll just say to download and unzip the file. The AC checking is part of a larger framework that will have additional analysis in future versions. This article focuses on the analysis for Oracle concrete classes in the application code.

AC is unable to replay transactions that use oracle.sql deprecated concrete classes of the form ARRAY, BFILE, BLOB, CLOB, NCLOB, OPAQUE, REF, or STRUCT as a variable type, a cast, the return type of a method, or calling a constructor. See New Jdbc Interfaces for Oracle types (Doc ID 1364193.1) for further information about concrete classes. They must be modified for AC to work with the application. See Using API Extensions for Oracle JDBC Types for many examples of using the newer Oracle JDBC types in place of the older Oracle concrete types.

There are three values that control the AC checking (called acchk in orachk) for Oracle concrete classes. They can be set either on the command line or via shell environment variable (or mixed). They are the following.

Command Line Argument

Shell Environment Variable


–asmhome jarfilename  


This must point to a version of asm-all-5.0.3.jar that you download from http://asm.ow2.org/.

-javahome JDK8dirname


This must point to the JAVA_HOME directory for a JDK8 installation.

-appjar dirname


To analyze the application code for references to Oracle concrete classes like oracle.sql.BLOB, this must point to the parent directory name for the code. The program will analyze .class files, and recursively .jar files and directories. If you have J2EE .ear or .war files, you must recursively explode these into a directory structure with .class files exposed.

This test works with software classes compiled for Oracle JDBC 11 or 12.

When you run the AC checking, the additional checking about database server, etc. is turned off. It would be common to run the concrete class checking on the mid-tier to analyze software that accesses the Oracle driver.

I chose some old QA test classes that I knew had some bad usage of concrete classes and ran the test on a small subset for illustration purposes. The command line was the following.

$ ./orachk -asmhome /tmp/asm-all-5.0.3.jar -javahome /tmp/jdk1.8.0_40 -appjar /tmp/appdir

This is a screen shot of the report details. There is additional information reported about the machine, OS, database, timings, etc.

From this test run, I can see that my one test class has five references to STRUCT that need to be changed to java.sql.Struct or oracle.jdbc.OracleStruct.

Note that WLS programmers have been using the weblogic.jdbc.vendor.oracle.* interfaces for over a decade to allow for wrapping Oracle concrete classes and this AC analysis doesn’t pick that up (there are five weblogic.jdbc.vendor.oracle.* interfaces that correspond to concrete classes). These should be removed as well. For example, trying to run with this ORACLE extension API and the WLS wrapper

import weblogic.jdbc.vendor.oracle.OracleThinBlob;

OracleThinBlob blob = (OracleThinBlob)rs.getBlob(2);
java.io.OutputStream os = blob.getBinaryOutputStream();

on a Blob column using the normal driver works but using the replay driver yields

java.lang.ClassCastException: weblogic.jdbc.wrapper.Blob_oracle_jdbc_proxy_oracle
$1OracleBlob$$$Proxy cannot be cast to weblogic.jdbc.vendor.oracle.OracleThinBlob

It must be changed to use the standard JDBC API

java.sql.Blob blob = rs.getBlob(2);
java.io.OutputStream os = blob.setBinaryStream(1);

So it’s time to remove references to the deprecated Oracle and WebLogic classes and preferably migrate to the standard JDBC API’s or at least the new Oracle interfaces. This will clean up the code and get it ready to take advantage of Application Continuity in the Oracle database.

Thursday Jul 17, 2014

Exciting New JTA 12.1.3 Feature “XA Transaction without Transaction Logs”

One of the most exciting new features in WebLogic Server 12.1.3 is a JTA new feature
“XA Transaction without Transaction Logs.” This feature does not only provide performance optimization when applications use XA transactions, but also has great advantages for Disaster Recovery scenarios.

XA transactions provide a standards-based mechanism to preserve data integrity for mission-critical applications. Traditionally XA transaction recovery requires the transaction manager to persist transaction records to stable storage (TLog) after all of the transactions resources have been prepared, and purging them after all of the transactions resources have been completed. However, recording pending transactions for recovery purposes requires additional I/O which affects performance. In cases of disaster recovery transaction logs need to be replicated to make sure that global transactions can be recovered.

XA Transaction without Transaction Logs,” uses a determiner resource which can be either a DataSource or a WebLogic JMS resource to determine the recover outcome of pending transactions. When using a determiner resource, WebLogic Server will no longer write and purge transaction checkpoints to TLogs. XA Transaction without Transaction Logs,” takes advantage of the two-phase-commit protocol, as well as prepare and commit ordering of resources participating in the global transaction to determine if pending transactions need to be recovered with a commit or a rollback.

The advantages of this feature are:

· Up to three times performance throughput improvement

· Prepare and Commit ordering

· I/O latency removed by not writing to TLOG (default file store)

· Resource and/or batch blocking removed (JDBC Tlog)

· Memory consumption reduced

· Capacity requirements reduced

· TLOG replication made easy

In WebLogic Server 12.1.3 “XA Transaction without Transaction Logs,” is restricted to transactions that involve a single Transaction Manager (WebLogic Server). The mixture of transactions that enlist determiner resources and span single Transaction Managers, with those who do not enlist a determiner resource and/or span multiple Transaction Managers is supported. In the future, WebLogic will support not logging transactions that involve multiple Transaction Managers.

Check out the YouTube recordings that go into detail how this feature works "JTA 12.1.3 New Feature and Optimization". There is even a demo that shows you how it is configured, how it works, and how you can debug your transactions to verify if the determiner is working "XA Transaction without Transaction Logs" and Demo.

Refer to the WebLogic Server 12.1.3 documentation JTA documentation "XA Transaction without Transaction Logs" for further details on how to configure and use the feature.

Thursday Jun 26, 2014

Oracle WebLogic Server 12.1.3 is Released

We're proud to announce that Oracle WebLogic Server 12.1.3 has been released as part of the Cloud Application Foundation and Oracle Fusion Middleware 12.1.3 release as described at the Cloud Application Foundation Blog. Oracle WebLogic Server is the industry's leading application server, providing unparalleled choice for deploying applications in public clouds, on-premise private clouds, engineered systems such as Oracle Exalogic Elastic Cloud, Oracle SPARC SuperClusters, and Oracle Database Appliance systems, and conventional systems.

Oracle WebLogic Server 12.1.3 is a new version release of Oracle WebLogic Server 12c.   It builds on the features provided in WebLogic Server 12.1.2 to improve developer productivity, performance and high availability, and manageability.   It enables you to develop and deliver innovative applications, to meet the application service level requirements for your business, and to manage your application infrastructure efficiently to achieve low total cost of ownership.

For developers we have placed specific focus on enabling development of server applications that support rich client applications running in HTML5 browsers or mobile devices. Such applications typically rely on REST based Web Services, use JSON as the data format for message payloads, and often require dynamic updates between clients and servers. In Oracle WebLogic Server 12.1.3, we have implemented support for selected Java EE 7 APIs including JAX-RS 2.0, Java API for JSON Processing, Java API for WebSocket, and JPA 2.1, to enable and support development of such applications.  We have also delivered related value-added capabilities like support for Server-Sent Events and unique WebSocket emulation capability.

High availability and performance improvements include improvements to Oracle Database 12c integration support - we have bundled the latest version of the Oracle Database 12c driver for ready access to database integration features, and have certified Oracle Database 12c AQ JMS as a Foreign JMS Server within Oracle WebLogic Server.    Innovations to the Oracle WebLogic Server transaction processing subsystem enable elimination of transaction logs in many cases, increasing performance and simplifying distaster recover configuration.   Optimizations for Oracle Exalogic systems include JMS performance improvements, and Cooperative Memory Management to adapt server memory usage based on memory consumption on Oracle Exalogic systems.

Manageability enhancements include improvements to dynamic clusters introduced in Oracle WebLogic Server 12.1.2.   In Oracle WebLogic Server 12.1.3 we support use of whole server migration to provide improved availability for dynamic clusters environments using JMS.    We have expanded our support for REST-based management, adding lifecycle management, application deployment, and datasource configuration support via REST.   We have also made similar improvements to support for Oracle WebLogic Server management in Oracle Fusion Middleware Control.

Finally, Oracle WebLogic Server 12.1.3 is the foundation of the Oracle Fusion Middleware 12.1.3 release, which adds Oracle SOA Suite 12c and other Oracle Fusion Middleware products to the family of products that is supported with Oracle WebLogic Server 12c.  This will make it easy for Oracle WebLogic Server 12.1.3 customers to adopt the latest releases of these products, and will also enable Oracle Fusion Middleware users to take advantage of the latest features in WebLogic Server 12.1.3.  To learn more:

...and look for more information from us in the coming days and weeks.  Thanks!

Monday Jun 16, 2014

Detailed Analysis of a Stuck Weblogic Execute Thread Running JDBC Code

The following thread was extracted from a thread dump taken on a JVM instance running WebLogic Server.

In this post I will deconstruct this thread and describe the data it contains and the potential issues it may illuminate.

[STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)' id=73 idx=0x128 nid=13410 prio=1 alive, in native, daemon 

 java.net.SocketInputStream.socketRead0(Native Method)


oracle.net.ns.Packet.receive(Unknown Source)

oracle.net.ns.DataPacket.receive(Unknown Source)

oracle.net.ns.NetInputStream.getNextPacket(Unknown Source)

oracle.net.ns.NetInputStream.read(Unknown Source)










com.foo.abc.util.ConnectionPool.createConnection(Unknown Source)

This thread is considered Stuck by WebLogic because it's been running for over the time defined in MaxStuckThreadTime (600 seconds by default). Weblogic Server waits for this time to be reached before marking a thread as stuck if the thread is still working after this time.  If you deem that 600 seconds is too long before a running thread is considered stuck then you can change the value of the this parameter using the WebLogic Console (as shown below), or use setMaxStuckThreadTime from the ServerFailureTriggerMBean interface.

An error including BEA-000337 will be logged in the server log file when the thread changes its status to stuck but the server won't take further action on this thread.  However, you might want to investigate why this thread is taking such a long time to process the work assigned to it.

Lets now look at the thread itself.  From its header, you can spot the thread identifier (2 in this example) and the queue where it originated.  The term Self-tuning indicates that the associated thread pool consistently checks the overall throughput to determine if the thread count should change.

id (or tid) is the thread identifier, a unique process-wide number that identifies this thread within the JVM process.  This id is unique but can be reused by another thread once this thread is terminated. 

nid is the OS-level native thread identifier.  It can be used effectively to correlate with high CPU usage threads identified at the OS level (e.g. with Linux watch command).  See Unexpected High CPU Usage with WebLogic Server (WLS) Support Pattern (Doc ID 779349.1) for detailed steps.

idx is the thread index in the threads array.

prio refers to the thread priority, a number inherited from the thread that created it.  You can learn more about thread priorities at Class Thread but basically threads with higher priority are executed in preference to threads with lower priority.

alive refers to the fact that this thread has not ended yet and is still active.  

in native means that the thread uses the operating system's native ability to manage multi-threaded processes.  

daemon indicates that this thread can't prevent the JVM from exiting.

The thread header is accompanied with a full java stack which lists each method and class invoked since the first assignement to the thread up to its most recent action. This thread consists of obtaining a connection to an Oracle database using a Type 4 JDBC driver and then issuing a call but getting no response from the back end database server.  The database failed to respond, and the thread has probably been in the same waiting mode (unchanged and not progressing java stack) for a long time since it's now considered stuck; the most recent invocation being java.net.SocketInputStream.socketRead0.

At this point the back end database needs to be checked to understand why it's not responding to the java thread request.  A starting point could be to query v$session to find potential blocking sessions at the database level.

Blocking sessions occur when one session holds an exclusive lock on an object and doesn't release it.

Needless to say, the communication with the database needs to be confirmed as healthy with none to very limited latency.  Firewall issues should be ruled out as well.  Firewalls could time out idle sockets used by JDBC connections to the database and lead to not closing the socket the JDBC driver is using.

Friday Aug 30, 2013

Introducing Elastic JMS

In WebLogic 12.1.2, we enhanced the way that you can configure JMS servers, stores, and subdeployments so that the JMS subsystem can automatically scale with the Managed Servers in a cluster. We call this Elastic JMS. My friend Maciej Gruszka calls it Magic JMS!

 Here are some details:

JMS Servers: In releases before WebLogic Server 12.1.2, each JMS Server was individually configured and targeted at a single Managed Server. It didn’t matter whether or not that Managed Server was part of a cluster. Starting in WebLogic Server 12.1.2, you can target a JMS Server at a cluster. Under the covers, WebLogic spins up a JMS Server on each managed server in the cluster. If you add or remove servers from the cluster, JMS Servers are added or removed automatically.

WebLogic Persistent Stores: Like JMS Servers, in releases before WebLogic Server 12.1.2, each WebLogic Persistent Store (file store or JDBC store) was individually configured and targeted to a single Managed Server, clustered or not. In WebLogic Server 12.1.2, you can target a WebLogic Persistent Store at a cluster. Under the covers, WebLogic creates a store instance on each Managed Server in the cluster. Each instance of a file store uses the same path to either a shared file system or to a local file. Each instance of a JDBC store uses the same JDBC data source, but gets its own underlying tables.

Subdeployments: A subdeployment defines the list of JMS Servers that will host a queue or topic. In releases before WebLogic Server 12.1.2, when you defined a subdeployment for a distributed queue or topic, you listed each JMS Server in the cluster. When you scaled up the cluster by adding a Managed Server and a corresponding JMS Server, you also needed to update the subdeployment with the new JMS Server. Starting in WebLogic Server 12.1.2, subdeployments are much simpler. You can list a single JMS Server that is targeted at the cluster. When you scale up the cluster, the distributed queue is automatically extended to the new JMS Server instance without any changes to the subdeployment.

Pulling it all together: By using cluster targeted JMS Servers and Persistent Stores, you get some nice benefits:

  • Simplified configuration – Even initial JMS configuration is much simpler than it was in the past: no need for individually configured JMS Servers and related items.
  • Elastic scalability – As you scale the cluster, the JMS services automatically scale with it. 
  • Support for Dynamic Clusters – Because Dynamic Clusters require homogenous targeting of services, the new configuration options make it possible to run JMS on Dynamic Clusters. 

  • Check out the documentation at http://docs.oracle.com/middleware/1212/wls/JMSAD/dynamic_messaging.htm or see my video at for more details.

    Tuesday Jul 30, 2013

    Now available installers for Oracle Enterprise Pack for Eclipse 12c and SmartUpgrade 12c

    Now available for download  new installers for  Oracle Enterprise Pack for Eclipse 12c and WebLogicServer SmartUpgrade 12c from the Oracle Technology Network for free development and evaluation purposes.  Licensed customers should download the software from the Oracle Software Delivery Cloud site, which offers different licensing terms.

    Oracle Enterprise Pack for Eclipse (OEPE) 12.1.2 provides exciting new features for enhancing ease of integration with Oracle Coherence 12.1.2 and Oracle WebLogic Server 12.1.2.

    To find what is new in Oracle Oracle Enterprise Pack for Eclipse (OEPE) 12.1.2 read What is New in OEPE 12c, for installation documentation read Oracle Enterprise Pack for Eclipse Installation Guide.

    WebLogic Server SmartUpgrade tool  ensures a highly reliable upgrade process of applications from OC4J  to WebLogic Server 12c.

    Find SmartUpgrade documentation here: Oracle WebLogic Server SmartUpgrade Documentation.

    Don’t forget to register for the WebLogic Server 12.1.2 Online Launch Event on July 31st.

    Friday Apr 19, 2013

    Improved Developer Experience and Productivity: The Power of Maven and WebLogic Server

    Are you using Maven to automate your builds? If so, Oracle WebLogic has some greatly improved, out-of-the box features that make Maven work even harder for you, improving your experience while increasing productivity.

    Here are some of the features that enable you to use Maven with the Oracle stack to speed time to market, reduce costs and more effectively manage your application lifecycle:

    • Java EE 6 Full Profile Certified
      WebLogic Server is Java EE 6 full-profile certified so you can make use of the latest programming model to build your applications.
    • Standard Java IDE Support
      WebLogic Server supports various IDEs and offers advanced Maven integration.
    • Developer Zip Distribution
      In order to set up your development environment more quickly, WebLogic Server supports developer Zip distribution.
    • Support for many operating systems
      WebLogic Server supports many operating systems including Windows, MacOSX, and Linux.
    • Open Source
      WebLogic Server offers support for popular third-party frameworks.
    • Classloading
      Oracle’s Classloading Analysis Tool (CAT) is bundled with WebLogic Server to address classloading issues for your applications that use different Java classes i.e. Enterprise Beans, servlets and JavaServer Pages, utility classes and third-party packages. CAT simplifies filtering classloader configuration and helps you analyze classloading issues.
    • Free Developer License
      Oracle offers a free single developer desktop licensed version of WebLogic Server. Link to free download.

    Learn More:
    Watch the DevCast archive on demand: The Power of Maven: Smarter DevOps through Automation and Integration

    You will learn about:

    • WebLogic Server for Developers
    • Apache Maven
    • Working with WebLogic Server from Maven
    • Advanced uses of Maven with WebLogic Server
    • Java IDEs and Maven

    Stay Connected

    Cloud Application Platform (CAP):

    Monday Apr 15, 2013

    Oracle is #1 in the Application Server Market Segment for 2012

    Oracle takes the top spot for market share in the Application Server Market Segment for 2012 according to the March 2013 Gartner “Market Share: All Software Markets, Worldwide 2012” report.*

    Supporting Resources

    (*) Source: Gartner, Inc. “Market Share, All Software Markets, Worldwide, 2012," March 29, 2013, By Colleen Graham, Joanne Correia, David Coyle, Christine Arcaris, Fabrizio Biscotti, Matthew Cheung, Ruggero Contu, Federico de Silva Leon, Yanna Dharmasthira, Tom Eid, Chad Eschinger, Bianca Granetto, Hai Hong Swinehart, Hideaki Horiuchi, Koji Motoyoshi, Yurika Nagashima, Chris Pang, Asheesh Raina, Dan Sommer, Bhavish Sood, Michael Warrilow, Laurie Wurster and Jie Zhang”

    Stay Connected

    Cloud Application Foundation (CAF):

    Thursday Mar 28, 2013

    Hotelbeds Enhances its IT Infrastructure with Oracle WebLogic Server and Oracle Coherence

    Hotelbeds is an accommodation wholesaler that services over 50,000 hotels across 183 countries. When the organization realized their current IT infrastructure environment had become too complex and costly to manage and its middle-tier database cache could no longer scale to serve the company's busiest seasons, they underwent a rigorous evaluation process to find a solution that would better meet their business needs.

    Hotelbeds analyzed the total cost of ownership (TCO) of Oracle WebLogic Server versus open source application servers in the market today, and decided to migrate their entire applications ecosystem to Oracle WebLogic Server.

    By consolidating onto Oracle WebLogic Server, Hotelbeds was able to reduce operating costs and eliminate the risk of running their business critical applications on unsupported platforms.

    Additionally, Hotelbeds opted to replace its existing open source caching systems MemCached and EHCache with Oracle Coherence to increase performance, scalability and ease-of-use. Upon consolidating on WebLogic and Coherence they have reduced maintenance costs by more than 165%.

    Hotelbeds also uses a range of other Oracle technologies to support its infrastructure, including Oracle Database, Oracle Exadata Database Machine, Oracle GoldenGate, Oracle WebCenter Content, Oracle JDeveloper and Oracle JRockit Java Virtual Machine.

    Check out the video, Hotelbeds Moves from Open Source: Consolidates on WebLogic, to hear Juan Di Dos, Director of IT for Hotelbeds, talk about the benefits of aggregating all their applications on a single platform.

    Was the overview information provided in this blog useful?
    What WebLogic topics would you like to hear more about?

    Stay connected

    Follow WebLogic on:
    WebLogic Blog

    Cloud Application Foundation (CAF) on:

    Follow Coherence on:





    Coherence Blog

    Follow Tuxedo on:



    Tuxedo Blog

    Monday Mar 25, 2013

    What to Expect from Maven on Oracle WebLogic

    Many of today's WebLogic shops are already using Maven. To make sure users can take advantage of all of Maven's capabilities, Oracle is constantly iterating on Maven support in WebLogic Server.

    Please Join us this Thursday, March 28, at 10 am PT/1 pm PT, to see how Oracle WebLogic and Maven can further your development processes (all while keeping your Ops budget guys happy with the time savings).

    Join us for this Webcast and hear about our out-of-the-box support, features, and tips for enhancing your development projects. Discover how:

    • Maven integration improves your time to market by applying cross-cutting logic to well-defined project object models
    • Maven technology advances are easier to use and more accessible with Oracle support
    • You can decrease application lifecycle management costs through build automation and Oracle WebLogic integration

    Register for the webcast: What to Expect from Maven on Oracle WebLogic
    Thursday, March 28, 10am PDT/1pm EDT
    With: Pyounguk Cho, Principal Product LineManager, Oracle WebLogic

    Thursday Mar 14, 2013

    Are you using the application server that best serves your changing business needs? Maybe it’s time to consider an upgrade?

    If you’re running mission-critical applications, consolidating your data center or thinking about creating a private cloud infrastructure, and you are not currently using WebLogic Server 12c, you may want consider an upgrade.                 

    Oracle WebLogic Server 12c is the #1 Application Server across conventional systems, engineered systems and cloud environments. It provides significant enhancements to help customers and partners lower their total cost of ownership and derive more value from their current application infrastructure, while accelerating the development cycle and reducing time-to-market for their applications.

    As the centerpiece of Oracle’s Cloud Application Foundation, and a core part of the Oracle Fusion Middleware product family, Oracle WebLogic Server continues to deliver innovative new capabilities for building, deploying and running Java Platform, Enterprise Edition (Java EE) applications Some of the new product features and enhancements include:

    ·        Oracle WebLogic Server 12c is now certified for the full Java EE 6 platform specification, which enables higher developer productivity with standards-based, modern APIs, including Servlet 3.0, JAX-RS 1.1, Java Server Faces 2.1, EJB 3.1, Context and Dependency Injection for Java, and many others.

    ·        Oracle WebLogic Server developers can now leverage Java Platform Standard Edition (Java SE) 7 features to create cleaner, more maintainable code.

    ·        Leveraging graphical tooling and open, PaaS Web Service APIs, Oracle Virtual Assembly Builder enables simplified configuration and packaging of multi-tier enterprise applications on environments virtualized with Oracle VM.

    ·        Improved integration between Oracle WebLogic Server and Oracle Real Application Clusters (RAC), which can auto detect and correct database node failures to help drive higher performance and simplify management.

    ·        Oracle WebLogic Server is optimized to run as a high performance, mission critical, elastic cloud infrastructure on Oracle Exalogic Elastic Cloud, the world‘s first and only engineered system for cloud computing. Oracle Exalogic Elastic Cloud is tested and tuned by Oracle to provide the best foundation for Java applications, Oracle applications and other enterprise applications with blazing performance.

    ·        Oracle WebLogic Server is also a key component of the new Oracle Java Cloud Service, an enterprise platform for developing, deploying and managing business-critical Java EE applications, which supports development and deployment from multiple Java-based integrated development environments (IDEs), including Oracle JDeveloper, NetBeans IDE and Eclipse.

    These are just a few of the many reasons you may want to consider upgrading now. To learn more, plan to attend the webcast --It Pays to Upgrade to Oracle WebLogic Server –March 27 at 10 am PT, 1pm ET. Presenters Roger Freixa Vidal, Sr. Principal Product Manager, Oracle WebLogic, and Michael Ferrante, Principal Product Manager, Oracle Application Development Tools will explain how you can gain new functionality and unparalleled performance by upgrading. They’ll also explain just how easy that is to do.  

    Was the overview information provided in this blog useful?
    What WebLogic topics would you like to hear more about?

    Stay connected

    Follow WebLogic on:
     WebLogic Blog

    Cloud Application Foundation (CAF) on:

    Follow Coherence on:
     Coherence Blog

    Follow Tuxedo on:
     Tuxedo Blog

    Wednesday Mar 06, 2013

    WebLogic Server- Integrated and Optimized with Best of Breed Oracle Offerings to Turbo Charge your Applications

    Oracle WebLogic Server, a foundational technology in Oracle’s Cloud Application Foundation portfolio and a key enabling technology for Oracle’s Exalogic hardware/software engineered systems solution, is designed to help you seamlessly move into the public or private cloud with an open, standards-based architecture. WebLogic is further enhanced with technologies such as Java SE, Oracle Coherence and Oracle’sActive GridLink for RAC.

    Runtime predictability and lower latency with Java SE and JRockit Real Time
    Oracle Java SE Suite, the Java Runtime for Oracle WebLogic Suite, provides access to the  leading JVMs- HotSpot and Oracle JRockit—offering you the choice of the right tool for your performance needs and profile. Within Java SE Suite, Oracle JRockit Real Time uses deterministic garbage collection to reduce pause times to a consistent, predictable level.
    Learn more.

    Scale linearly while improving performance and reliability with Oracle Coherence
    Oracle Coherence, the industry leading in-memory data grid, pools and shares memory across multiple systems. Coherence adds in a layer of in-memory capability between your back end resources and the database allowing you to move data that your applications are accessing into memory close to the applications, improving performance and reliability.

    Coherence is installable as part of WebLogic Server, and is managed and configured using WebLogic Server administration tools. Users can configure, start and stop, and monitor Coherence clusters from the WebLogic Server console, or from the WebLogic Scripting Tool (WLST).

    WebLogic Server and Coherence runtime integration includes Coherence Web for WebLogic Server session state management, programming model integration with annotations, and WebLogic JNDI integration with Coherence caches. Learn more.

    Active GridLink for RAC Enhanced Performance and Availability
    Oracle WebLogic Server and Oracle RAC are designed to work together to provide an environment for highly performant, available and scalable applications.

    Oracle WebLogic Server Active GridLink for RAC provides the best available support for RAC features in Oracle Database, minimizing database access time while allowing transparent access to pooling management functions that maximizes both connection performance and availability.

    The combination of Oracle WebLogic Server Data Source and Connection Pooling solutions and Oracle RAC provides a high-end mission-critical environment offering performance, high scalability and availability features. Load-balancing and Affinity capabilities offer significant performance improvement for online transaction processing scenarios, as well as improving throughput and total response time. Failover solution gives end-to-end rapid failure detection supporting graceful shutdown for planned and unplanned Oracle RAC node outages. Learn more.

    Was the overview information provided in this blog useful?
    What WebLogic topics would you like to hear more about?

    Stay connected

    Follow WebLogic on:
    WebLogic Blog

    Follow Cloud Application Foundation (CAF) on:

    Follow Coherence on:
     Coherence Blog

    Follow Tuxedo on:
    Tuxedo Blog


    The official blog for Oracle WebLogic Server fans and followers!

    Stay Connected


    « September 2015