Weblogic server 12c agosto 2012

Notas del editor

• #26: Main point: If anyone still has doubts, IDC,another independent and extremely reputed analyst firm has concluded that Oracle is #1 in app server market share. Script:Also that Oracle has strengthenedits lead in the market and that our growth is above the industry average. I think we can conclude with very high degree of confidence, based on analysis by these two extremely well reputed, independent analyst firms that not all app servers are created equal.
• #29: Left to right:Full 12c distro = 1 GB11g zip = 318mb12c zip distro = 168mbDeveloper Zip DistributionFull WebLogic Server 12.1.1.0 releaseSupported for development useLinux, Mac OS X, WindowsSize now down to 168MB-----Let’s talk about how WebLogic Server 12c enables lightweight development. Back in 11g our initial download offering for WebLogic Server 11g included all the technologies that might be used by developers, that might be used for production deployed. So we included the full WebLogic Server product offering, we included to JVM's, we included web server plug-ins that enable you integration with Web servers, we included some diagnostic tools which are used primarily for diagnosis in production environments. Feedback we received from you the developer community were that we’d smaller more lightweight distribution that we can use for installing WebLogic Server and our development environments So we delivered a zip file which contains only those components you are going to need for WebLogic Server developments so that would include the WebLogic Server runtime the WebLogic Server console WLST and other tools that you would typically use for doing development. In WebLogic Server 11g that zip distribution was approximately 300MB, so significantly smaller than the full distribution of provided for WebLogic 11g. In WebLogic 12c we may that even smaller, we’ve cut the size in half so we have now a zip distribution which is about 1/6 the size of the full WebLogic Server 11g distribution. So that makes it easier for you to download the product get started with your development activities and visit distribution supported on Windows machines on Linux and on Mac systems as well. Will, this a zip of the product installed right, so they don’t have to run an installer? That’s right, so you download, unzip and go. That’s great.  Some other capabilities that have been around for a number of years but that I like to call out are the options to start up WebLogic Server without the EJB JMS and JCA containers. So some of the feedback we've received from developers is a building very simple web applications that aren’t using EJB or JMS and they’d like the opportunity to start up the server where resources are not being consumed by EJB JMS containers and using this existing startup option, you can start up WebLogic server with just those containers which are required for web applications. Finally another technology that's been available in prior releases for WebLogic Server something we called FastSwap. FastSwap enables the ability to change a particular class within an application during the debugging process enables you to recompile that class and have the changed code activated within your running application without any change in session state without requiring a redeployment without requiring a reboot of the server The whole goal is to enable very fast iterative development see your changes effective immediately. All of these features are also supported and WebLogic Server 12c.
• #49: Main Point: Pre-Build Assembly Appliances for WebLoigc Server (note initially these are only available on WebLogic Server 11g (11.1.1.6) and these will include 11g versions of OTD, Coherence, WebLogic Server. Shortly after in 2012 there will be 12c versions available. Script: A major new part of the WebLogic and Fusion Middleware 12c release is Oracle Virtual Assembly Builder. What this does is change the packaging and deployment model of multi-tier applications on its head. As most applications not only multi-tier (e.g. Web, Middle tier and Database), they often span multiple platform infrastructures – Web/Portal front ends, feeding transactions into messaging infrastructure which then distribute transactions to backend applications and business processes. They are difficult to treat as a unit – from a management, packaging, deployment, upgrade and patching perspective. With Oracle Virtual Assembly Builder you can take a multi-tier application – e.g. Portal, Messaging, Business Process – and virtualize it into a series of virtual appliances and package these appliances into an assembly and then treat it as a unit. It is a higher level of abstraction for managing the lifecycle of large scale distributed applications. This is a major part of the 12c release. We will have pre-built appliances for WebLogic Server, Coherence, Oracle Traffic Director and more, ultimately to all Fusion Middleware 12c infrastructure. Clearly this takes virtualization to a new level of not only facilitating consolidation and utilization but also dramatically simplifying and reducing the cost in the application lifecycle.----Oracle virtual assembly builder I’ve alluded to conceptually what assembly builder does is it enables you introspect a physical multitier deployment consisting of Web servers, application servers and database servers and from those to create an assembly. An assembly consists of a set of appliances which represent each component of the multitier deployment and the assembly also contains metadata which describes the wiring among the appliances in the assembly. So the endpoints the connection points between the Web server tier and the app server tier and app server tier and the database tier. And what assembly builder enables you to do is to take these assemblies which are constructed of multiple appliances and redeploy those to virtual systems which may have different host names and ports or networking parameters etc.  As you change the networking parameters, URLs, host names, and ports, as you deployed to the virtual environment. Assembly builder will automatically ensure the integrity of the wiring among the appliances as they are deployed to the new environment. So for example you can ensure that a database URLs that are defined in the WebLogic Server data sources continue to connect successfully to new URLs which your virtual databases are now listening in on the virtual system. So it's basically a mechanism for simplifying deployment of standard reasonably complex applications to virtual environments whether those are on conventional systems and our plans to support these and engineered systems and ultimately this technology will also be used in the Oracle Public Cloud.
• #51: A key theme that you can see the WebLogic team taking is taking what frequently is rolled by hand in data centers, difficult to maintain and upgrade and converging into the application server space. We did this originally with the Data Grid by integrating Coherence. Now, we are doing the same with traffic management. Our customers have noted that frequently between applications and the ingress point to their applications they require more sophisticated traffic management, shaping and load balancing. This is particularly apparent to customers who introduce virtualization to their application layer and end up with a proliferation of virtual machines needing traffic management to correctly route, shape, cache and prioritize traffic.As a result, in WebLogic Server 12c we are introducing a new part of the architecture called Oracle Traffic Director. This is a layer 7 software load balancing component that not only does traffic routing, shaping and capacity management based on declarative rules within its configuration, it acts as a full reverse proxy to WebLogic Server (ala the old WebLogic Server Plug ins in early releases for Apache, IIS, OHS). Adding to that, Oracle Traffic Director has sophisticated declarative caching capabilities that can dramatically improve application performance. The bottom line is with this edge “application delivery controller” now part of the overall application server architecture, customers have a new simplified and application centric way to manage traffic into their applications and between their applications.One of the key areas of performance benefits customers will immediately see with Oracle Traffic Director is SSL termination. Clearly the dominant practice we see in our customers is SSL termination at the traffic routing layer and OTD fully supports this and has deep integration into the Advanced Encryption Set algorithms of the Intel chipset – this has been certified and integrated specifically on Exalogic augmenting the already dramatic performance enhancements WebLogic Server applications see on Exalogic.Bottom line: Oracle believes that having an application aware traffic director is a critical part of the next generation architecture in the cloud. ----------Another new product delivered and integrated with WebLogic Server 12c and associated with the WebLogic Server 12c is what we call Oracle traffic director. It is a software load-balancing technology in effect replacing much of the functionality offered by traditional Web servers but offers substantially higher performance unless CPU consumption then a Web server. So it's a very high-performance routing of requests to origin servers or servers in the backend which are providing, generating dynamic webpages are providing other application services to browser clients. It is very fast, it is highly configurable with a nice management interface and provides unique capabilities for shaping the way traffic is forwarded to backend server. So that traffic is optimally distributed across the servers in the backend environment. Oracle traffic director is supported on Exalogic Elastic Cloud systems and we believe offers unique performance advantages and extends some of the performance benefits of deploying WebLogic Server applications on the Exalogic systems.
• #52: In addition to both dramatically improving development and application deployment lifecycle, WebLogic Server 12c also stuck to its proverbial knitting and has provided some significant enhancements to the core runtime of WebLogic Server. A key area of focus has been the integration of Oracle RAC for an integrated WebLogic/RAC clustering model with Active GridLink for RAC and a number of changes to dramatically change how one can more easily manage WebLogic Server and the Coherence Data Grid in a multi-data center environment.In the RAC area, Active GridLink for RAC was introduced late in the 11g cycle and in 12c some additional features have been introduced. To enable the dramatic 3X OLTP performance improvement we have seen in our tests and customers, Active GridLink for RAC now has in addition to transaction affinity (pinning transactional activity to a single node of a RAC cluster) we have introduced Web session affinity which carries the affinity of stateful Web interaction through to the RAC node where that state is interacting. The end result is again a significant performance increase. This is on top of the existing runtime connection load balancing and fast connection failover – all enabled by WebLogic Server being able to interact with Oracle Database RAC *events* that publish workload, RAC up/down events. In competitor application servers there simply isn’t this integration – the same capabilities either don’t exist or are done by heavy weight polling mechanisms. Finally, we are seeing adoption with the customer base of the RAC One architecture and Active GridLink for RAC is fully certified and aware of the high availability architecture of RAC One.In the multiple data center area, there has been significant strides taken in WebLogic Server 12c. Two major capabilities have been added. First, WebLogic Server now enables customers to store their transaction logs in the database. This enables all live customer data – transactions, messaging and customer data to be in a database. If you are using Oracle Database, this means for DR you can use Active Data Guard as a full DR solution for you database and middle tier live data. This dramatically simplifies the architecture and reduces the time to recovery. We did not stop there. As there is also live data that our customers use in the Coherence Data Grid tier, we not only have push replication between data centers with Coherence, we enable database updates to be transparently propagated from the DB into the Data Grid using GoldenGate. It now truly is possible to set up a extremely reliable, simple and architecturally complete multi-data center solution that frankly no other application server approaches. ----------In the area of high availability and disaster recovery I mentioned earlier the active GridLink for RAC capability. That's the capability to easily connect WebLogic Server applications to Oracle RAC clusters and take maximum advantage of the Oracle RAC cluster technology. In affect the GridLink for RAC technology makes WebLogic Server data sources RAC aware. The WebLogic Server and data sources become aware of events that are occurring within the RAC cluster like when servers are being shut down or become unavailable or become busy and WebLogic Server connection pooling can take advantage of that information to stop making a connection request to servers that are being shut down, failover connections to surviving members of the RAC cluster, preferentially route new connection request to least busy servers in RAC clusters and other capabilities. This allows for higher performance availability, better manageability, configurability of your WebLogic Server environments.  And we delivered enhancements recently to this capability including a new feature called web session affinity which allows you to preferentially route database requests within the same web session to a single RAC node to obtain high-performance because it is likely all requests within the same web session context may be cached so if you route them to the same RAC node you will get higher performance. We also have delivered new features which simplify the configuration and deployment of WebLogic Server in multi-data center topologies. A particularly in cases where topologies are meant to support disaster recovery. What we've done is we've provided a feature called ?, which enables you to store transaction logs or records of WebLogic Server transaction which are used for recovering failed transactions, we store those in a database which allows you to store all of your dynamic application data including transaction state, including JMS messages, and the application data your writing to database, all within a database and use standard database replication technologies to replicate that data across data centers including to a disaster recovery site. In effect we make it very easy to configure disaster recovery solutions that offer unique capabilities.
• #53: In the area of management we've also delivered very significant enhancement to Oracle enterprise manage. Oracle enterprise manager is Oracle’s strategic technology for managing all of Oracle software and enterprise manager provides a management pack for managing WebLogic Server environments. And enterprise manager cloud control 12c has delivered enhancements to that which extend the benefits of using enterprise manager for managing WebLogic Server deployments, including cloud infrastructures. And these capabilities range from the ability to monitor very large-scale deployments of hundreds of servers and many WebLogic Server domains to doing deep drill-down performance analysis to managing configurations which are deployed across those domains and unique provisioning and now maintenance capabilities which greatly simplify the process of installing software on your server farms and maintaining that software all through a single pane of glass. So their unique capabilities for managing WebLogic Server infrastructures that can grow to a very significant scale.
• #54: Main point: we’ve made significant investment to deliver Extreme Performance with WebLogic on Exalogic.Script: Not only does Oracle WebLogic continue to lead on the industry standard benchmarks on conventional hardware, on Exalogic our engineered system, we have done specific architectural enhancements to WebLogic leveraging the high speed Infiniband network fabric that ties together the compute, storage, switch infrastructure of Exaloigc with performance results that go above and beyond what is achievable on conventional hardware. This is not just due to higher speed networking - though at 4X more bandwidth standard Ethernet and 10X better latency, it certainly helps. What changes the game is how WebLogic Server has been architected to take advantage of the additional bandwidth through something called parallel muxers and I/O enhancements (namely something called Scatter/Gather I/O) and also has been engineered to recognize the Exalogic hardware processors and local solid state storage to perform with results you see on this slide. Web applications can handle 10X requests/second, JMS applications can handle 5X messages/sec and SpecJ like complex applications see about 5X operations/second better than what is possible on conventional hardware. Bottom line: Not only is WebLogic on Exalogic superfast, again you need significantly less hardware to run the same workload which translates to significant savings.EL 1.0 multiple for Web: 3.4EL 1.0 multiple for JMS: 1.6EL 1.0 multiple for Enterprise Java: 2.2------------In the area of performance optimizations we delivered a performance optimizations and WebLogic Server 12c through capabilities like session affinity in the active GridLink for RAC technology. We delivered optimizations for running JMS on Exalogic hardware and other optimizations which extend WebLogic Server performance leadership and there is just some indicators here that suggest how much performance benefit you can actually realize by running on WebLogic Server and in particular running your WebLogic Server applications on the Exalogic engineered systems.
• #55: So what is all this mean for you we've got a number of new standards defined Java EE6 that enable that require less work for you building XML that require less code development. The APIs make it simpler to build your applications and make you more productive and in building applications and you can use modern techniques like contexts and dependency injection for accessing components throughout your application for example using a JSF to access managed beans and other resources in your applications. We tested this out building a sample application that was implemented both using Java EE5 standards and Java EE6 standards and in a sample application we found that using Java E6 you require 25% fewer classes in your at 50% less lines of code in about 80% less lines of XML. So this all means there's less code and XML to you to write and enables you to focus on building the business logic that your applications require.
• #56: Language enhancements:Strings in SwitchChanges to literalsMulti Catch, precise rethrowDiamond operatorTry with resources-----------------Getting back to standards WebLogic Server is and always has been standards-based another important development in the area standard support is Java SE many of you are aware I'm sure we announced Java SE7 this past summer. Java SE7 provides for new improvements to provide improved supports a new capabilities for building out applications optimizations within the Java language itself and WebLogic Server 12c supports both Java SE7 and Java SE6 so you as developers get the best of both worlds. For those of you who are very interested in taking advantage of the latest Java EE technologies you can use Java EE7 to build your WebLogic Server applications. I know NetBeans has picked up support for SE7 as well, they were very quickly to do that. I think Eclipse has picked up support for this as well. And I’m pretty sure that will be rolling into our enterprise pack shortly. Our goal is always to and make sure that developers have access to latest technologies as well as the option to use the more mature got Java EE6 technologies which we are also supporting so you get your choice of which JDK you want to use. We support, Java SE7 and SE6 both on the client and on the server Java SE7 provides new Internet internationalization support which we think are going to be important for those of you developing particularly abroad in Asia or in Europe.  There are also some significant enhancements maybe as developers are not going to be terribly interested in the that there's some important developments in SSL such as SSL TLS 1.2 that are supported directly in JSSE within the JDK which were taking advantage of and WebLogic Servers were trying to leverage some of the new capabilities that are being delivered at the JDK level.  So I’ve heard that TLS, the transport security layer is the successor to SSL, given some of the issues with it in the industry. That's right and for our customer's in financial services institutions or government agencies which have the most demanding security requirements we seeing lot of requirements to support the latest encryption technologies for the WebLogic Server applications. Now what about SE7 in particular, you mentioned some language changes? I think the probably the most notable one was something derived from project Coin, the term was coined to refer to a small change, or a number of features here and there which were delivered and they thought might be useful to various developers. It turns out that there's a diversity little developer enhancements which are actually in some total being considered fairly interesting and you now and in my experience in talking with developers there’s a fair amount of interest in getting their hands on Java EE7 to see what they can do and how we can make use of it.
• #80: Briefly in terms of the environment required to run WebLogic Server 12c, the minimum developer environment requirements are listed here. We provide a zip distribution for laying down WebLogic Server on development systems and these are the system requirements associated with that developer focused distribution. We also provide installation programs which can be used for both development and production purposes which support a range of operating systems including Windows LINUX, AIX, Exalogic systems and Solaris systems.