Introduction to Oracle Weblogic Server 11G Release 1 (10.3.1)

Oracle® Fusion Middleware Introduction to Oracle WebLogic Server 11g Release 1 (10.3.1) E13752-01 May 2009 This document provides an overview of Oracle WebLogic Server features and describes how you can use them to create enterprise-ready solutions. 1 Introduction to Oracle WebLogic Server The following sections provide a brief overview of Oracle WebLogic Server features and describe how you can use them to create enterprise-ready solutions: Note: Oracle Fusion Middleware 11g contains Oracle WebLogic Server 11g. The version number of Oracle WebLogic Server is 10.3.1. ■■■■■■■■■■■■■Section 1.1, "The WebLogic Server Solution" Section 1.2, "Programming Models" Section 1.3, "High Availability" Section 1.4, "System Administration" Section 1.5, "Diagnostic Framework" Section 1.6, "Security" Section 1.7, "Oracle JRockit JVM" Section 1.8, "Client Options" Section 1.9, "Upgrade" Section 1.10, "Integration with Oracle WebLogic Suite" Section 1.11, "Integration with Other Systems" Section 1.12, "Integration with Web Servers" Section 1.13, "WebLogic Server API Examples and Sample Application" 1.1 The WebLogic Server Solution Oracle WebLogic Server is a scalable, enterprise-ready Java Platform, Enterprise Edition (Java EE) application server. The WebLogic Server infrastructure supports the deployment of many types of distributed applications and is an ideal foundation for building applications based on Service Oriented Architectures (SOA). SOA is a design methodology aimed at maximizing the reuse of application services. See <a href="/goto?url=http://www.oracle.com/technology/tech/soa/index.html" target="_blank">http://www.oracle.com/technology/tech/soa/index.html</a>. 1The WebLogic Server complete implementation of The Sun Microsystems Java EE 5.0 specification provides a standard set of APIs for creating distributed Java applications that can access a wide variety of services, such as databases, messaging services, and connections to external enterprise systems. End-user clients access these applications using Web browser clients or Java clients. It also supports the Spring Framework, a programming model for Java applications which provides an alternative to aspects of the Java EE model. See Section 1.2, "Programming Models." In addition to the Java EE implementation, WebLogic Server enables enterprises to deploy mission-critical applications in a robust, secure, highly available, and scalable environment. These features allow enterprises to configure clusters of WebLogic Server instances to distribute load, and provide extra capacity in case of hardware or other failures. New diagnostic tools allow system administrators to monitor and tune the performance of deployed applications and the WebLogic Server environment itself. You can also configure WebLogic Server to monitor and tune application throughput automatically without human intervention. Extensive security features protect access to services, keep enterprise data secure, and prevent malicious attacks. 1.2 Programming Models WebLogic Server provides complete support for the Java EE 5.0 specification at <a href="/goto?url=http://java.sun.com/javaee/5/docs/api/" target="_blank">http://java.sun.com/javaee/5/docs/api/</a>. For more information, see the following WebLogic Server programming guides: ■Web Applications provide the basic Java EE mechanism for deployment of dynamic Web pages based on the Java EE standards of Servlets and Java ServerPages (JSP). Web applications are also used to serve static Web content such as HTML pages and image files. ■Web Services provide a shared set of functions that are available to other systems on a network and can be used as a component of distributed Web-based applications. ■■XML capabilities include data exchange, and a means to store content independent of its presentation, and more. Java Messaging Service (JMS) enables applications to communicate with one another through the exchange of messages. A message is a request, report, and/or event that contains information needed to coordinate communication between different applications. ■■Java Database Connectivity (JDBC) provides pooled access to DBMS resources. Resource Adapters provide connectivity to legacy and other external enterprise systems. ■■■Enterprise JavaBeans (EJB) provide Java objects to encapsulate data and business logic. Remote Method Invocation (RMI) is the Java standard for distributed object computing, allowing applications to invoke methods on a remote objects locally. Security APIs allow you to integrate authentication and authorization into your Java EE applications. You can also use the Security Provider APIs to create your own custom security providers. ■WebLogic Tuxedo Connectivity (WTC) provides interoperability between WebLogic Server applications and Tuxedo services. WTC allows WebLogic Server clients to invoke Tuxedo services and Tuxedo clients to invoke EJBs in response to a service request. 2■■Overview of WebLogic Server Application Development describes developer tools and best practices for coding WebLogic Server applications. For additional programming topics, see the Developing Applications on Oracle WebLogic Server topic page. In addition, WebLogic Server supports applications developed using the Spring Framework, an open source application framework for the Java platform. Oracle Fusion Middleware Spring Support in Oracle WebLogic Server provides an overview of Spring and the WebLogic Server support for developing and deploying Spring applications. It also gives examples of how to write Spring applications for WebLogic Server. See also SpringSource at <a href="/goto?url=http://www.springsource.org/" target="_blank">http://www.springsource.org/</a>. 1.3 High Availability The following WebLogic Server features and tools support the deployment of highly-available and scalable applications: ■WebLogic Server clusters provide scalability and reliability for your applications by distributing the work load among multiple instances of WebLogic Server. Incoming requests can be routed to a WebLogic Server instance in the cluster based on the volume of work being processed. In case of hardware or other failures, session state is available to other cluster nodes that can resume the work of the failed node. In addition, you can implement clusters so that services may be hosted on a single machine with options to migrate the service to another node in the event of failure. In addition to replicating HTTP session state across servers within a cluster, WebLogic Server can also replicate HTTP session state across multiple clusters, thereby expanding availability and fault tolerance in multiple geographic regions, power grids, and Internet service providers. ■Work Managers prioritize work based on rules you define and by monitoring actual run time performance statistics. This information is then used to optimize the performance of your application. Work Mangers may be applied globally to a WebLogic Server domain or to a specific application or component. ■■■Overload protection gives WebLogic Server the ability to detect, avoid, and recover from overload conditions. Network channels facilitate the effective use of network resources by segregating network traffic into channels based on the type of traffic. WebLogic Server persistent store is a built-in, high-performance storage solution for WebLogic Server subsystems and services that require persistence. For example, it can store persistent JMS messages or temporarily store messages sent using the Store-and-Forward feature. The persistent store supports persistence to a file-based store or to a JDBC-enabled database. ■Store-and-forward services enables WebLogic Server to deliver messages reliably between applications that are distributed across WebLogic Server instances. If the message destination is not available at the moment the messages are sent, either because of network problems or system failures, then the messages are saved on a local server instance, and are forwarded to the remote destination once it becomes available. ■Enterprise-ready deployment tools facilitate deployment and migration of applications from the development phase to a production environment. 3■Production redeployment enables enterprises to deploy a new version of their application without interrupting work in progress on the older version. 1.4 System Administration System administration of a WebLogic Server environment includes tasks such as creating WebLogic Server domains; deploying applications; migrating domains from development environments to production environments; monitoring and configuring the performance of the WebLogic Server domain; and diagnosing and troubleshooting problems. WebLogic Server provides many tools for system administrators to help with these tasks, including a browser-based Administration Console, the WebLogic Scripting Tool (WLST), a scripting language for automation of WebLogic system administration tasks based on Jython, SNMP, the Configuration Wizard, and command-line utilities. See Section 2.1, "Choosing the Appropriate Technology for Your Administrative Tasks" and Section 2.2, "Summary of System Administration Tools and APIs." Because WebLogic Server's management system is based on Java EE and other standards, it integrates well with tools used to manage other enterprise software and hardware components. In addition, WebLogic Server implements the Java EE Java Management Extension (JMX) specification, which allows programmatic access to the WebLogic Server management system. Using this API you can create your own administration utilities or automate frequent tasks using Java classes. 1.5 Diagnostic Framework The WebLogic Diagnostic Framework is a monitoring and diagnostic service that lets you create, collect, analyze, archive, and access diagnostic data generated by a running server and its deployed applications. This data provides insight into the run-time performance of WebLogic Server instances and deployed applications and lets you isolate and diagnose faults and performance bottlenecks. 1.6 Security The WebLogic Server security architecture provides a comprehensive, flexible security infrastructure designed to address the security challenges of making applications available on the Web. WebLogic security can be used standalone to secure WebLogic Server applications or as part of an enterprise-wide, security management system that represents a best-in-breed security management solution. See Overview of the WebLogic Security Service. 1.7 Oracle JRockit JVM The Oracle JRockit JVM is a high performance JVM optimized for Intel architectures and developed to ensure reliability, scalability, manageability, and flexibility for Java applications. Oracle JRockit JVM optimizes performance of your Java applications on either the Windows or Linux operating system platforms with either 32-bit or 64-bit architectures. Oracle JRockit JVM is included with your WebLogic Server installation. See Oracle JRockit JVM. 1.8 Client Options In addition to support for browser-based Web application clients, WebLogic Server also supports a variety of client types for creating rich GUI applications or simple 4command-line utilities. These client types include: RMI-IIOP, T3, J2SE clients, Java EE thin clients, CORBA/IDL clients, and C++ clients that communicate with BEA Tuxedo. See Programming Stand-Alone Clients. 1.9 Upgrade Tools and documentation are provided to help you migrate applications implemented on earlier versions of WebLogic Server to the current WebLogic Server environment. See Upgrading WebLogic Application Environments. 1.10 Integration with Oracle WebLogic Suite WebLogic Server provides the core application server run time within the integrated Oracle WebLogic Suite Java infrastructure. WebLogic Suite contains the following server-side components: ■■■■Oracle WebLogic Server Oracle JRockit Oracle Coherence Oracle TopLink This integrated infrastructure enhances application performance, improves application availability, and enables predictable and reliable application scalability with high quality of service. WebLogic Suite includes highly productive development tools based on Oracle JDeveloper and Oracle Enterprise pack for Eclipse, and a fully integrated management for large-scale administration and operations with Oracle Enterprise Manager. Taken together, the development, run time and management capabilities of WebLogic Suite provide the foundation for implementing mission-critical enterprise applications. 1.11 Integration with Other Systems WebLogic Server provides a variety of tools to integrate your applications with disparate systems. These tools include Web Services, Resource Adapters, the JMS .NET client, Messaging Bridge, and RMI. 1.12 Integration with Web Servers Plug-ins are provided with your WebLogic Server installation that allow WebLogic Server to operate with Web servers from Apache, Microsoft, and Sun Microsystems. Typically, these Web servers serve static HTML content while requests for dynamic Web content such as JSPs are directed to the WebLogic Server environment. See Using Web Server Plug-Ins with WebLogic Server. 1.13 WebLogic Server API Examples and Sample Application Code examples demonstrating Java EE APIs and other WebLogic Server features are provided with your WebLogic Server installation. To work with these examples, select the custom installation option when installing WebLogic Server, and select to install the Server Examples. To access the code examples, start the WebLogic Server Examples domain using the WebLogic Examples Server entry in the Windows Start menu, or launch the startWebLogicEx.cmdor startWebLogicEx.shscript from WL_ HOME/samples/domains/wl_server, where WL_HOME is the directory where you 5installed WebLogic Server. As they become available, you can also download additional examples. Along with the code examples, two versions of a complete sample application, called Avitek Medical Records (or MedRec), are installed when you install the examples, as described above. The original MedRec (which was included in previous versions of WebLogic Server) is a WebLogic Server sample application suite that concisely demonstrates all aspects of the Java EE platform. MedRec is designed as an educational tool for all levels of Java EE developers. It showcases the use of each Java EE component, and illustrates best practice design patterns for component interaction and client development. MedRec also illustrates best practices for developing applications on WebLogic Server. The Spring version of MedRec, called MedRec-Spring is MedRec recast using the Spring Framework. If you are developing Spring applications on WebLogic Server, you should review the MedRec- Spring sample application. In order to illustrate how Spring can take advantage of the enterprise features of WebLogic Server, MedRec was rearchitected to replace core Java EE components with their Spring counterparts. The functionality in the original version of MedRec is reimplemented using Spring in Spring-MedRec. Refer to the Spring MedRec sample for details. To launch MedRec, select Start Medical Records Server from the Windows Start menu or run startWebLogicEx.cmdor startWebLogicEx.shscript from WL_ HOME/samples/domains/medrec, where WL_HOME is the directory where you installed WebLogic Server. To launch MedRec-Spring, select Start Medical Records Server (Spring Version) from the Windows Start menu or run the startWebLogicEx.cmdor startWebLogicEx.shscript from WL_ HOME/samples/domains/medrec-spring, where WL_HOME is the directory where you installed WebLogic Server. 2 Overview of WebLogic Server System Administration System administration of WebLogic Server includes a wide range of tasks: creating WebLogic Server domains; deploying applications; migrating domains from development environments to production environments; monitoring and managing the performance of the run-time system; and diagnosing and troubleshooting problems. (A WebLogic Server domain is a collection of WebLogic Server services designed for a specific purpose. For example, you might create one domain to provide an employee portal and another domain to provide business services to your customers.) Because the WebLogic Server management system is based on Java EE and other standards, it integrates with systems that are frequently used to manage other software and hardware components. In addition, WebLogic Server includes several of its own standards-based, extensible utilities. Alternatively, you can use APIs to create custom management utilities. The following sections provide an overview of system administration for the WebLogic Server component of your development or production environments: ■Section 2.1, "Choosing the Appropriate Technology for Your Administrative Tasks" Section 2.2, "Summary of System Administration Tools and APIs" ■For information about installing WebLogic Server, see the Oracle WebLogic Server Installation Guide. 6For information about using Fusion Middleware administration tools, such as the Oracle Enterprise Manager Fusion Middleware Control, Oracle Fusion Middleware command-line tools, and the Fusion Middleware Control MBean Browser, see "Overview of Oracle Fusion Middleware Administration Tools" in Oracle Fusion Middleware Administrator's Guide. 2.1 Choosing the Appropriate Technology for Your Administrative Tasks Table 1 describes common system administration tasks and associated technologies. Table 1 Choosing the Appropriate Management Technology <ul style="display: flex;"><li style="flex:1">To do this... </li><li style="flex:1">Use this technology... </li></ul><ul style="display: flex;"><li style="flex:1">Create domains </li><li style="flex:1">The Configuration Wizard guides you through the process of creating or </li></ul>extending a domain for your target environment. See Creating WebLogic Domains Using the Configuration Wizard. To automate the creation of domains, use the WebLogic Scripting Tool, which is a command-line scripting interface based on Jython. See "Creating Domains Using WLST Offline" in Oracle Fusion Middleware Oracle WebLogic Scripting T o ol. Or create domain configuration XML files that conform to the WebLogic Server schema. See "Domain Configuration Files" in Understanding Domain Configuration. Migrate domains from development environments to production Domain Template Builder's packcommand archives a snapshot of a domain into a JAR file. The unpackcommand expands the archive and creates the necessary start scripts and certain security and configuration files. See Oracle WebLogic Server Creating T e mplates and Domains Using the Pack and Unpack Commands. environments Track changes in a domain's configuration In environments that you allow configuration changes to active domains, WebLogic Server automatically maintains a versioned archive of configuration files. See "Configuration File Archiving" in Oracle Fusion Middleware Understanding Domain Configuration for Oracle WebLogic Server. To receive real-time notifications that a domain's configuration has been modified, enable the configuration auditing feature. See "Configuring the WebLogic Auditing Provider" in Oracle Fusion Middleware Securing Oracle WebLogic Server. For tightly controlled production environments, configure the run-time domain to be read-only (see "Restricting Configuration Changes" in Oracle Fusion Middleware Understanding Domain Configuration for Oracle WebLogic Server). You can change the read-only setting if you need to roll in changes that have been tested and approved in a staging environment, or you can modify and test your staging environment, and then use a Web server to re-route requests from your production environment to the staging environment. <ul style="display: flex;"><li style="flex:1">Configure </li><li style="flex:1">Web server plug-ins. See "Understanding Using Web Server Plug-Ins </li></ul>connections to Web With WebLogic Server" in Oracle Fusion Middleware Using Web Server servers Plug-Ins with Oracle WebLogic Server. 7Table 1 (Cont.) Choosing the Appropriate Management Technology <ul style="display: flex;"><li style="flex:1">To do this... </li><li style="flex:1">Use this technology... </li></ul><ul style="display: flex;"><li style="flex:1">Configure </li><li style="flex:1">Within individual applications, you can define your own data sources or </li></ul>database connections using JDBC, or connect to external systems using resource adapters. When you deploy such an application, WebLogic Server creates the data sources and connections for you. See: connections to databases or other systems ■"Configuring WebLogic JDBC Resources" in Oracle Fusion Middleware Configuring and Managing JDBC for Oracle WebLogic Server ■"Understanding Resource Adapters" in Oracle Fusion Middleware Programming Resource Adapters for Oracle WebLogic Server If you have not defined your own data sources or connections within an application, you can use the Administration Console or the WebLogic Scripting Tool to create the resources. See Oracle Fusion Middleware Oracle WebLogic Server Administration Console Help or "Using the WebLogic Scripting Tool" in Oracle Fusion Middleware Oracle WebLogic Scripting T o ol.

Introduction to Oracle Weblogic Server 11G Release 1 (10.3.1)

Details

Download

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

Support