Download Docs   Site Map   Glossary  Search

Introducing WebLogic Platform

Introducing BEA WebLogic Platform

BEA WebLogic Platform represents the integration of the existing BEA WebLogic product suite into a unified, simplified, and extensible platform. WebLogic Platform merges all of the features of the existing BEA WebLogic products—application server, development, portal, and integration—into a highly integrated solution, combining the benefits of a common application infrastructure with an easy-to-use, robust framework.

The following figure shows the WebLogic Platform common application infrastructure.

Figure 1. BEA WebLogic Platform

WebLogic Platform Features

The following features comprise WebLogic Platform, as shown in Figure  1.

WebLogic Platform Benefits

Through its common application infrastructure, WebLogic Platform delivers the following benefits:

• Common models for packaging, download, installation, licensing, documentation, support, and release schedules
• Shared set of services and enterprise functionality
• Coexistence and interoperability across the platform
• Common application server run-time environment through the proven WebLogic Server
• Common OA&M and security frameworks
• Universal configuration wizard for generating application domains
• Seamless out-of-the-box experience, including access to the WebLogic Platform sample and QuickStart application for getting started using WebLogic Platform

Enterprise Challenges Confronted

The unified, simplified, and extensible architecture of WebLogic Platform confronts the business challenges facing your enterprise, as highlighted in the following table.

Summary

This section has introduced the main features and benefits of WebLogic Platform, and outlined the enterprise business challenges that it confronts.

The following sections explore WebLogic Platform features in more detail, and describe how the common application infrastructure enables you to build, integrate, and extend business processes across a collection of disparate systems.

Use the topics outlined in the following table to access the information most relevant to your business objectives.

Developing J2EE Applications

WebLogic Platform increases developer productivity by providing solutions that address the needs of its users. For example:

• Enterprise developers—WebLogic Server delivers a rich, flexible framework to promote the rapid development and deployment of J2EE applications, including enterprise-class Web services.
• Application developers—WebLogic Workshop empowers application developers, as well as J2EE experts, to rapidly develop, test, and deploy enterprise-class Web service applications.

The following sections describe the features of WebLogic Server that promote the rapid development of J2EE applications, including enterprise-class Web services. WebLogic Workshop is described in Developing Web Services with WebLogic Workshop.

Employing the Power and Flexibility of WebLogic Server

To promote the rapid development of your J2EE applications, you need a solid, reliable foundation. BEA WebLogic Server provides that foundation, serving as the backbone for WebLogic Platform.

WebLogic Server delivers the features that are essential for developing and deploying mission-critical J2EE applications. Furthermore, WebLogic Server is proven: it is used by more developers, independent software vendors (ISVs), application service providers (ASPs), and system integrators (SIs) than any other application server.

The following table highlights the features of WebLogic Server that promote the rapid development of J2EE applications.

For more information about WebLogic Server, see the WebLogic Server documentation on the BEA e-docs Web site at the following URL:

http://download.oracle.com/docs/cd/E13222_01/wls/docs70/index.html

The following sections explore the development of enterprise-class Web services in more detail.

Developing Enterprise-Class Web Services

Web services provide a standard means of communication between disparate applications within the enterprise and over the Internet. WebLogic Platform provides you with the tools and infrastructure you need to rapidly develop and deploy enterprise-class Web services that integrate distributed systems and provide you with the reliability, scalability, and availability you have come to expect from WebLogic.

What Are Web Services?

Web services make software application resources available to distributed clients over a network in a standardized way. Because Web services rely on standard methods of communication, applications that support these standards can take advantage of the resources that Web services expose, regardless of the internal implementation of the client application or Web service.

Web services are ideal for the enterprise because they are:

• Loosely coupled. Web services communicate using a public contract (Web Services Definition Language, or WSDL, file) that describes the XML messages to be exchanged, but leaves the underlying implementation details to each application. Loosely-coupled Web services enable communication between applications written in different languages and running on different operating systems.
• Coarse grained. Web services integrate at the business level, exchanging documents like POs and invoices rather than single data elements. Coarse-grained Web services allow greater flexibility when one part of the system changes.
• Asynchronous. Web services can communicate asynchronously, as well as synchronously, so that they operate the way your business does. Asynchronous Web services can perform operations that may require resources that are not immediately available, without blocking other requests or slowing down the system.

Web services are used to perform discrete business processes, such as accessing a product inventory, checking stock quotes, or exchanging user profile information.

For example, the following figure shows how a purchasing agent can access a company intranet site to check inventory and submit a request for quotes (RFQ)—using an asynchronous Web service—to various suppliers on low-inventory items.

Figure 2. Web Service Example

Each supplier receives an RFQ request and returns price and availability information. All communication takes place asynchronously, and information is posted to the intranet site as it is returned from suppliers. Based on the information returned, the purchasing agent reviews the quotes, selects a supplier, and submits a purchase order.

Web Service Standards

To expose their resources and ensure interoperability among applications that exist on heterogeneous hardware and software platforms, Web services adhere to the following communication standards:

• Describe their functionality through a Web Services Definition Language (WSDL) file, which may be published through a public registry.

A WSDL file describes how the Web service operates and how other software applications can interface with it. You can think of a WSDL file as the instruction manual for a Web service, explaining how a user can access the resources provided by the Web service. WSDLs are publicly accessible, providing enough detail to enable potential clients to operate the Web service.

WebLogic Server delivers:

• Built-in support for WSDL.
• Automatic generation of WSDL scripts when a Web service is deployed.
• An embedded Universal Description, Discovery, and Integration (UDDI) registry, providing a distributed, Web-based location registry for searching Web services.
• An API for searching and updating the UDDI or any third-party registry.
• Communicate with other applications via XML messages.

XML messages provide a common language that different applications can use to communicate over a network. To use a Web service, an application sends an XML message containing a request to perform an operation. The Web service responds by sending an XML message containing the results of that operation.

Typically, XML messages are formatted according to Simple Object Access Protocol (SOAP) syntax. SOAP specifies a standard format for applications to call other application methods and pass data. WebLogic Server delivers a high-performance SOAP implementation. Non-SOAP forms of XML messages are also possible, depending on the specific requirements of the Web service.

The XML message type and syntax requirements are defined in the WSDL file, making the Web service available to any client application capable of sending and receiving XML messages that meet those requirements.

• Receive requests and send responses using standard network protocols, such as HTTP (HyperText Transfer Protocol) and JMS (Java Message Service).

WebLogic Server supports the standard network protocols used during Web service communication.

Web Service Development Options

BEA supports two approaches to developing enterprise-class Web services:

• Use BEA WebLogic Workshop to develop, test, and deploy enterprise-class Web service applications. WebLogic Workshop is a graphical development framework that empowers application developers, as well as J2EE experts, to build powerful Web services quickly. The next section explores this approach in more detail.
• Use your favorite IDE or text editor to develop Web services, and leverage the Ant tasks provided by WebLogic Server that help you generate Web service components (such as data type serializers and deserializers, a client JAR file, and a Web service Home page) and to package all the pieces of a WebLogic Web service into a deployable EAR file. For more information, see Programming WebLogic Web Services in the WebLogic Server documentation on the BEA e-docs Web site at the following URL:

http://download.oracle.com/docs/cd/E13222_01/wls/docs70/webserv/index.html

Developing Web Services with WebLogic Workshop

BEA WebLogic Workshop is a graphical development environment that empowers application developers, as well as J2EE experts, to rapidly develop, test, and deploy enterprise-class Web service applications.

WebLogic Workshop enables developers to visually design robust Web services, without needing to understand the complexities of J2EE and object-oriented programming. Rather than learn complex APIs, developers can focus on the application logic, setting simple properties (expressed as Javadoc annotations) to access sophisticated functionality in the framework.

WebLogic Workshop provides all of the features commonly found in a development environment, including code editing, debugging, and project management. Tightly integrated build, deploy, and test phases are managed transparently to provide fast iterative development. Web services built using WebLogic Workshop are deployed automatically on WebLogic Server, streamlining deployment and providing consistency of service across the enterprise.

WebLogic Workshop consists of the following components:

• Visual development environment—WebLogic Workshop delivers an intuitive GUI-based integrated development environment (IDE) for developing Web services, supporting the development, test, and debug phases as a single, consistent process.
• Run-time framework—WebLogic Workshop delivers a run-time environment for deploying and managing Web services created with WebLogic Workshop.
• Format for Web service applications—Web services generated using WebLogic Workshop are stored as Java Web Services (JWS) files. A JWS file contains the Java code which determines how the Web service behaves, and consists of standard Java class definitions with annotations, expressed using Javadoc syntax, to define additional functionality. You can think of a JWS file as a Java class that communicates with the outside world through XML messages.

The WebLogic Workshop visual development and run-time environments are described in the following sections. For more information about WebLogic Workshop, see the WebLogic Workshop documentation on the BEA e-docs Web site at the following URL:

http://download.oracle.com/docs/cd/E13226_01/workshop/docs70/index.html

Developing Web Services Using WebLogic Workshop

The WebLogic Workshop IDE, shown in the following figure, provides a powerful development environment for building Web services.

Figure 3. Developing Web Services—WebLogic Workshop IDE

The main area of the WebLogic Workshop IDE displays the Web service that is currently being defined, and the surrounding panes display information that is related to the current Web service.

As shown in the previous figure, WebLogic Workshop provides access to the following three views of your JWS file:

• Design View—visually design Web services
• Source View—view and edit Web service source code
• Test View—test and debug Web services

WebLogic Workshop supports two-way editing, ensuring that updates that are made in the Design View are automatically reflected in the Source View, and vice versa. For example, when you add the requestReport method in the Design View, the corresponding source code is generated automatically, and can be viewed from the Source View, as shown in the following figure.

Figure 4. WebLogic Workshop Two-Way Editing

The following sections describe the design, source, and test views in more detail.

Visually Designing Web Services

The Design View, shown in the following figure, enables you to visually design Web services and their interactions with client applications and data resources, such as databases and other Web services.

Figure 5. Visually Designing Web Services—Design View

While designing a Web service, you can define:

• Web service interfaces, including methods to expose the functionality of the Web service, and callbacks to return results to clients asynchronously.
• Controls to:

• Access advanced J2EE functionality, including EJBs, databases, JMS queues.
• Execute an operation at specific time intervals.
• Access other Web services.
• Properties (expressed as Javadoc annotations) to access sophisticated functionality in the framework. See the Properties Pane in Figure  3. Properties include:

• Conversations to maintain the state of your Web service over a long-running sequence of asynchronous calls. The icons shown in Figure  5 indicate the start and finish points of a conversation.
• Message buffers to store requests and responses on a nonvolatile queue to ensure that they are processed.
• Protocols supported by the interface.
• XML maps to control how data is converted between XML messages and Java objects. The Map and Interface Editor makes it easy to define parameter and return XML maps, and build the interface to your application.

Editing Web Service Source Code

The Source View, shown in the following figure, enables you to edit Web service source code directly to customize generated code and implement the application logic.

Figure 6. Editing Web Service Source Code—Source View

The Source View supports productivity features such as auto-complete, parameter hints, and as-you-type error highlighting. When you compile a file with syntax errors, the Error pane displays error messages at the bottom of the Source View. Syntax errors are also marked by red underlines in your code. Double-clicking on a particular message moves the cursor next to the offending code.

Testing and Debugging Web Services

The Test View, shown in the following figure, enables you to test Web services. The Test View consists of a dynamically generated HTML page that enables you to call service methods with specific parameter values.

Figure 7. Testing and Debugging Web Services—Test View

The Message Log on the left-hand side of the window displays messages that are sent to and received from the Web service during testing. You can click on a log entry to display the request and response details of the message.

While testing, you can use WebLogic Workshop integrated debugger to debug your Web service. The debugger allows you to set breakpoints, step through your code line-by-line, view local variables, set watches on variables, and view the call stack and exception information.

Deploying and Managing Web Services Using WebLogic Workshop

WebLogic Workshop run-time environment provides the framework to easily deploy and manage Web services created with WebLogic Workshop.

WebLogic Workshop run-time environment reads a JWS file and automatically performs the following tasks:

• Compiles and deploys Web services, generating the required EJBs, messages queues, and other J2EE resources to deploy the application, and creating the deployment descriptors for each EJB.
• Instantiates controls used by the Web service.
• Generates WSDL files for describing the Web service.
• Generates Java client code for invoking the Web service.
• Generates an EAR file containing any collection of Web services for standard deployment to a production server.

The following section explores how to build enterprise portals, which can interact with Web services to integrate distributed systems.

Building Enterprise Portals

BEA WebLogic Portal delivers a unified framework for building enterprise portals that:

• Enables you to build, launch, and maintain portals that are interactive, adaptable to the needs of the audience, and customizable based on visitor preferences.
• Facilitates the creation, customization, and administration of multiple portals.
• Simplifies, personalizes, and reduces the cost of self-service access to information, applications, and business processes.
• Increases IT productivity through simplified portal development, deployment, and management by leveraging a common infrastructure and enabling component reuse.
• Runs in the common application run-time environment, provided by WebLogic Server.

The following sections define what a portal is, and explore the WebLogic Portal features and design tools.

For more information about WebLogic Portal, see the WebLogic Portal documentation on the BEA e-docs Web site at the following URL:

http://download.oracle.com/docs/cd/E13218_01/wlp/docs70/index.html

What Is a Portal?

A portal provides a single point of access to enterprise data and applications, presenting a unified and personalized view of that information to employees, customers, and business partners.

There are three main types of portals:

• Business-to-business (B2B) for exchanging information between business partners.
• Business-to-consumer (B2C) for tailoring content, applications, and services to different types of consumers.
• Business-to-employee (B2E) for enhancing member or employee intranet Web sites.

The following figure provides an example of a Business-to-Consumer portal.

Figure 8. Portal Example

As shown in the previous figure, a portal manages and organizes content through the use of portlets. A portlet is a standard user interface that displays content or applications within a section of a portal page. Multiple portlets can appear within a portal, and they can display personalized content, and commerce and campaign services, and integrate with back-end systems. These concepts are explored in more detail in the following section.

WebLogic Portal Features

The following table describes the main features of WebLogic Portal.

WebLogic Portal Tools

WebLogic Portal provides the following tools for accomplishing fundamental design and management tasks:

• Portal Management Tool, which is part of the BEA WebLogic Portal Administration Tools

Note: For more information about the WebLogic Portal Administration Tools, see Managing Additional WebLogic Portal Features.

• E-Business Control Center, which is a standalone graphical tool

These tools are described in the following sections.

Portal Management Tool

The Portal Management tool is part of the browser-based WebLogic Portal Administration tools, runs on the application server, and is used to accomplish the following tasks:

• Creating and managing the default portal content
• Managing the customization of content for specific group members through the use of group portals

For example, you can define the default skin appearance of a portal for all of the members of a group portal using the Select Skins page that is accessible from the Portal Management tool, as shown in the following figure.

Figure 9. Defining Default Portal Skins—Portal Management Tool

The following figure shows how a Web site visitor can select skins for a sample portal. (Visitor-specific settings do not impact the default portal settings.)

Figure 10. Selecting Skins Using Sample Portal Visitor Tools

E-Business Control Center

E-Business Control Center is a standalone graphical tool that simplifies the tasks required to create and maintain site infrastructure, business logic, and presentation resources for enterprise portals and sites built using WebLogic Portal. The E-Business Control Center enables you to define the design, functionality, and visitor attributes of portals and portlets with limited coding knowledge of Java, Java Server Pages (JSPs) or HTML.

The E-Business Control Center provides a number of useful editors and wizards for accomplishing fundamental portal design tasks, including the Webflow and Pipeline Editor, Portal wizard, and Portlet wizard.

Webflow and Pipeline Editor

The Webflow and Pipeline Editor, shown in the following figure, enables you to specify navigation between pages and simplifies inter-portlet communication.

Figure 11. Defining Webflow and Pipelines—E-Business Control Center

Webflows and Pipelines are flexible mechanisms designed to help you separate and manage the presentation and business logic that comprise your applications, without the need for advanced programming skills.

Portal and Portlet Wizards

The Portal wizard, shown in the following figure, enables you to easily create a new portal based on an existing template.

Figure 12. Creating a Portal—Portal Wizard

Similarly, the Portlet wizard, shown in the following figure, enables you to easily create a new portlet and specify its components.

Figure 13. Creating a Portlet—Portlet Wizard

The Portal and Portlet wizards collect the required information and automatically generate a new portal and/or portlet, respectively, based on the information specified.

Integrating the Enterprise

Today's global enterprise requires an integration solution that enables applications to exchange business-critical information in real-time. Integration initiatives may be intra-enterprise, linking your back-office systems, or inter-enterprise, linking internal data and processes with customers and other corporate enterprises.

BEA WebLogic Integration, shown in the following figure, delivers a complete solution for developing, deploying, and integrating applications and business processes from within and across the enterprise.

Figure 14. BEA WebLogic Integration Framework

As shown in the previous figure, WebLogic Integration supports the following key services.

WebLogic Integration runs in the common application run-time environment, provided by WebLogic Server.

The following sections describe WebLogic Integration services in more detail.

For more information about WebLogic Integration, see the WebLogic Integration documentation on the BEA e-docs Web site at the following URL:

http://download.oracle.com/docs/cd/E13214_01/wli/docs70/index.html

Integrating Applications

Application integration enables you to integrate information systems and new applications across the enterprise, including enterprise resource planning (ERP), supply chain management (SCM), human resource (HR), and customer relationship management (CRM), as well as custom and legacy applications.

Using adapters, businesses can share data and business processes between connected applications without having to modify their original applications or data structures. You can develop and host J2EE Connector Architecture (CA)-compliant service and event adapters using the Adapter Developer Toolkit (ADK). A service adapter invokes a specific function in the enterprise information system to which it is connected. An event adapter propagates information from the enterprise information system to the integration environment.

Application views provide an abstract view of an adapter, exposing existing enterprise applications as business services that accept XML data as input and return XML data as output. Application views enable integration specialists to access enterprise data without worrying about the technical implementation.

The Application View Console, shown in the following figure, is a graphical user interface (GUI) that offers an easy way to access, organize, and edit all the application views in your enterprise.

Figure 15. Managing Application Views—Application View Console

Using the Application View Console, you can define and manage application views for event and service adapters. By storing your application views in folders, you can organize them according to your own navigation scheme, regardless of the adapters to which the individual application views belong.

To extend the application integration functionality, you can integrate application views with BPM business processes using the BPM plug-in framework.

Managing Business Processes

Business process management (BPM) enables you to streamline the management of enterprise business processes. A business process consolidates company-wide tasks, actions, decisions, and events, and can span applications, systems, and people.

Using WebLogic Integration Studio, you can design and monitor business processes, as shown in the following figure.

Figure 16. Defining and Monitoring Business Processes—Studio

The Studio provides a graphical interface in which familiar flowchart elements are available for business process workflow modeling to graphically represent a business process. The Studio supports workflow design, workflow monitoring, and data administration functions.

During execution, you can interact with business processes as an end user using WebLogic Integration Worklist, as shown in the following figure.

Figure 17. Interacting with Business Processes—Worklist

Using the Worklist, you can manage the current organization, start business processes, and manage tasks.

To extend the BPM functionality, you can develop custom client applications and/or plug-ins using the BPM API. WebLogic Integration delivers predefined plug-ins for connecting with application integration, business-to-business (B2B) integration, and data integration functionality.

Integrating B2B Collaborations

B2B integration enables you to collaborate with business trading partners and manage B2B interactions.

Using the WebLogic Integration B2B Console, you can configure and manage these collaborations and B2B interactions, as shown in the following figure.

Figure 18. Configuring and Managing B2B Integration—B2B Console

Using the B2B Console, you can configure and manage:

• Conversations. Within the context of B2B, a conversation consists of a series of business messages exchanged between trading partners.
• Trading partners and their respective delivery channel configurations. Delivery channels define how a trading partner sends and receives messages. In a peer-to-peer configuration, trading partners communicate directly with each other through their delivery channels. In a hub-and-spoke configuration, trading partners communicate with each other through an intermediary, or routing-proxy, delivery channel. The delivery channel also defines the business protocol (ebXML Message Service or RosettaNet) to be used in the conversation, the transport protocol, and security parameters.
• Collaboration agreements to map trading partners to the roles specified in conversation definitions.

To extend the B2B integration functionality, you can:

• Develop custom management and messaging applications, and enable message logging using the B2B integration API.
• Enable specialized processing of business messages using the logic plug-ins.
• Use Power.Enterprise!, an electronic data interchange (EDI)-capable system, to enable the integration of WebLogic Integration with EDI environments.
• Integrate trading partner conversations with BPM business processes using the BPM plug-in framework.

Translating and Transforming Data

Data integration enables you to integrate data from diverse enterprise applications using XML as the standard format.

Using the data integration functionality, you can:

• Translate binary data to XML, and vice versa.
• Transform data to XML grammars, such as ebXML or RosettaNet.

To translate data, you must define a binary-to-XML map, specifically a metadata description of the record layout in the binary data, and store the information as a Message Format Language (MFL) file.

To facilitate this process, you can use Format Builder, as shown in the following figure.

Figure 19. Defining Data Translations—Format Builder

You can use Format Builder to:

• Create format descriptions derived from structural and detailed analyses of your data, and store them as MFL.
• Test format descriptions before applying them to your actual data.

To transform data, you develop XSL style sheets that describe how one XML grammar is mapped to another. You can create the XSL style sheet manually, using the design-time GUI provided by Contivo Analyst, or use the auto-mapping functionality in Contivo Analyst and Contivo eService.

The following figure shows the Contivo Analyst Mapping Editor.

Figure 20. Defining Data Transformations—Contivo Analyst Mapping Editor

To extend the data integration functionality, you can integrate with BPM business processes as follows:

• Integrate data translation functionality with business processes using the BPM plug-in framework.
• Integrate data transformation functionality with business processes using the XSL Transform workflow action in WebLogic Integration Studio.

Managing the Enterprise

As noted previously, WebLogic Platform features execute within the application server run-time environment provided by WebLogic Server, and make use of a set of interrelated, sophisticated systems resources.

Examples of system resources include:

• Clusters—distributing the workload of your application across multiple WebLogic Server instances. Clusters support replication, load balancing, and failover services to ensure scalability and high availability of your e-commerce systems.
• Security—providing a comprehensive, flexible security architecture, enabling you to control and track access to system resources. Supported security features include access control, cryptography-based privacy, user authentication, user- and group-level Access Control Lists (ACLs), Realms, Secure Sockets Layer (SSL), and Digital Certificates.
• Transactions—ensuring data integrity by guaranteeing that database transactions are performed accurately, in accordance with strict guidelines. Supported features include distributed transactions, updating multiple resource managers in a coordinated manner, and two-phase commits, guaranteeing that transactions are committed by all participating databases.

WebLogic Platform delivers a set of integrated management tools for managing application server resources across the enterprise.

The primary tool for accomplishing the core management tasks is the WebLogic Server Administration Console Web-based interface. WebLogic Server also provides a command-line interface for developing sophisticated system management scripts, or for use with non-GUI-based systems. Additional, value-add tools are provided for configuring domains, and managing specific features of WebLogic Portal and WebLogic Integration.

WebLogic Platform management tools are described in more detail in the following sections.

Managing Application Server Resources

To manage application server resources, use the WebLogic Server Administration Console, shown in the following figure.

Figure 21. Managing Application Server Resources—Administration Console

The Administration Console is a Web-based interface to the WebLogic Administration Service, an implementation of Sun's Java Management Extension (JMX) standard that provides facilities for managing server resources.

You can perform the following set of core management tasks using the Administration Console:

• Start, stop, monitor, and configure system resources.
• Monitor and evaluate system performance.
• Balance load on servers or connection pools.
• Detect and correct problems.
• Deploy Web applications, EJBs, or other resources.

A command-line interface is also provided for developing sophisticated system management scripts, or for use with non-GUI-based systems.

Configuring Domains

The BEA Configuration Wizard enables you to create custom domains. A domain is the basic administrative unit for WebLogic Server, and consists of an interrelated set of WebLogic Server resources that are managed as a unit. A domain includes one or more WebLogic Server instances, and may also include WebLogic Server clusters.

For more information about the Configuration Wizard, see Using the Configuration Wizard on the BEA e-docs Web site at the following URL:

http://download.oracle.com/docs/cd/E13196_01/platform/docs70/confgwiz/index.html

Managing Additional Features

In addition to the WebLogic Server Administration Console, you can use the tools described in this section to manage additional features of WebLogic Portal and WebLogic Integration.

Managing Additional WebLogic Portal Features

To manage specific features of WebLogic Portal, use the WebLogic Portal Administration Tools, shown in the following figure.

Figure 22. Managing WebLogic Portal Features—Administration Tools

The following table describes each WebLogic Portal Administration Tool, highlighting the additional features that can be managed.

WebLogic Portal supports the delegated administration of users, portal presentation, and entitlements management using the Delegate Administration tool shown in the following figure.

Figure 23. Delegating Administration Tasks—Delegate Administration Tool

Delegated administration enables you to create an administration hierarchy to delegate and distribute workload, or provide backup administrative support. For example, you may want to delegate portal presentation management to members of a Design group.

Managing Additional WebLogic Integration Features

To manage WebLogic Integration features, use the tools described in the following table.

Building a WebLogic Platform Solution

The following sections provide examples that demonstrate how to use WebLogic Platform to build an enterprise business solution. The examples show how WebLogic Platform enables a fictitious digital camera equipment supply company, Avitek Digital Imaging, to meet its business objectives.

Avitek Digital Imaging, a subsidiary of Avitek Corporation, is a leading manufacturer of audio, video communications, and information technology products for the consumer and professional markets. Avitek Corporation is a large, global enterprise, and its employees are geographically dispersed. To stock product inventory, employees must elicit quotes from multiple suppliers.

Avitek Digital Imaging's key objectives are to:

• Increase company revenue by establishing an online, personalized sales channel.
• Increase employee productivity and reduce costs by automating the product purchasing process.
• Increase HR productivity by facilitating employee access to public and personal HR information.

The WebLogic Platform solution consists of:

• B2C Internet Web site enabling customers to browse the Avitek Digital Imaging product catalog, select an item, and submit an order, and, for industry professionals, receive personalized content.
• B2B purchasing portal enabling Avitek Digital Imaging purchasing agents to interact with suppliers and replenish its product inventories.
• B2E intranet Web site enabling Avitek Digital Imaging employees to access all public and personal HR material online.

With the exception of the last solution, the B2E intranet Web site, the solutions described are based on the WebLogic Platform sample application, as described in Tour of the BEA WebLogic Platform Sample Application.

Before diving into the detailed example descriptions, it is important to understand the WebLogic Platform feature interoperation that enables the business objectives demonstrated. The following section describes WebLogic Platform feature interoperation.

WebLogic Platform Feature Interoperation

WebLogic Platform provides a standards-based, build-to-integrate approach that enables companies to develop and deploy applications, rapidly integrate with existing systems, automate business processes, and connect with business partners.

To support its build-to-integrate approach and enable WebLogic Platform feature interoperation, specific integration entry points are available to facilitate process-level communication and data flow between front-end Web applications and heterogeneous back-end systems. An integration entry point defines a place at which interoperation can take place.

The following figure shows WebLogic Platform integration entry points.

Figure 24. WebLogic Platform Integration Entry Points

As shown in the previous figure, integration entry points include:

• Web services—integrate disparate systems.
• WebLogic Integration features, including:

• Application integration—call a J2EE Connector Architecture (CA) adapter directly to integrate with back-end systems. Typically, this is used for synchronous communication.
• BPM—communicate synchronously through calls to the API or asynchronously via JMS. Extend BPM functionality using the BPM plug-in framework.
• B2B integration—communicate through a message API or the BPM plug-in collaboration functionality. Use JSP tag library to build thin-client interfaces that can communicate with a hosted B2B integration enabler.
• WebLogic Portal features, including:

• Portlets—discover and interact with Web services or call WebLogic Integration APIs.
• Unified user profiles (UUP)—maintain a single view of the user across multiple data sources including user profiles, existing user databases, and legacy applications.
• Webflow/Pipeline components—manage flow of business logic and site presentation. Enable process-level communication and data flow between Web applications and enterprise information system, including WebLogic Integration features.

The following sections provide examples of how to build enterprise business solutions using WebLogic Platform, while demonstrating the interoperation scenarios described in this section.

Building an Online Sales Portal

One of Avitek's main business objectives is to increase company revenue and maintain a competitive edge by establishing an online, personalized sales portal. Using WebLogic Platform, Avitek builds a B2C portal allowing customers to browse the Avitek Digital Imaging product catalog, select an item, and submit an order, and, for industry professionals, receive personalized content.

The following summarizes the WebLogic Platform features that Avitek employed when building the online sales portal:

• WebLogic Portal powers the front-end B2C Web application.
• Application integration communicates with back-end enterprise systems to check product availability.
• BPM streamlines the order fulfillment process.
• Web services supply product evaluation and payment authorization functionality.

The following table describes the online sales portal user interactions and the corresponding WebLogic Platform features at work behind the scenes.

Building a Product Inventory Portal

Avitek's second business objective is to increase employee productivity and reduce costs by automating the product purchasing process. Using WebLogic Platform, Avitek builds a B2B product inventory portal that allows its purchasing agents to interact with suppliers and replenish its product inventories.

The following summarizes the WebLogic Platform features that Avitek employed in the product inventory portal:

• WebLogic Portal powers the front-end B2B Web application.
• B2B integration provides the functionality to enable purchase agent and suppliers to collaborate using standards-based conversations.
• BPM coordinates tasks among multiple systems.

The following table describes the product inventory portal user interactions and the corresponding WebLogic Platform features at work, behind the scenes.

Building an Employee HR Portal

Avitek's final business objective is to increase HR productivity by facilitating employee access to public and personal HR information. Using WebLogic Platform, Avitek builds a B2E intranet Web site that allows its employees to access all public and personal HR material online.

The following summarizes the WebLogic Platform features that Avitek employed in the employee HR portal:

• WebLogic Portal powers the front-end B2E Web application.
• Application integration communicates with back-end HR and benefits systems.
• BPM streamlines the benefit enrollment process.

The following table describes the employee HR portal user interactions and the corresponding WebLogic Platform features at work, behind the scenes.

Extending the Platform

As noted previously, WebLogic Platform delivers an extensible architecture, supporting a robust, scalable framework and enabling you to leverage current and future assets.

WebLogic Platform delivers extensibility through its support of:

• Standards-based J2EE technologies and services.
• Web services, which provide a standard way to integrate distributed systems.
• Other WebLogic Server EIS integration options, described in Table  4, including J2EE Connector Architecture (CA), WebLogic/Tuxedo Connector (WTC), and WebLogic jCOM.
• Application integration, as described in Integrating Applications.
• Java Management Extensions (JMX) for integrating with third-party management and monitoring tools, that also provides a Service Provider Interface (SPI) for managing security.
• Third-party Java IDEs, such as JBuilder and WebGain.
• MQ Series as a transactional resource manager.

BEA is committed to the development community, working closely with its customers, and offering assistance via the following resources:

• BEA eSupport (http://support.bea.com/welcome.jsp): Industry-leading support from BEA Customer Support, providing you with the technical expertise to effectively deliver proactive, responsive services for your critical e-business initiatives.
• BEA dev2dev Online (http://dev2dev.bea.com): Technical resources for designing and deploying applications using WebLogic Platform.
• BEA Newsgroups (http://forums.bea.com): Forum to exchange ideas, share best practices and lessons learned and discuss and obtain technical support from your peers.
• BEA Portal Solutions Catalog (http://dev2dev.bea.com/products/wlportal/psc/index.jsp): Online resource center for businesses to design and develop enterprise portal solutions. The BEA Portal Solution Center simplifies portal design and development by providing secure, self-service access to a catalog of portlets, software integrations, and pre-designed portal solutions from BEA and leading systems integrators and software vendors.

BEA offers individual licensing programs to independent software vendors (ISVs), third-party developers, or partners that want to build their own products on top of BEA core technologies. BEA is committed to investing in strategic partnerships to provide complete e-business solutions, and works closely with each partner to deliver complete e-business solutions.

Benefits of a partnership with BEA include:

• Build on a proven, reliable foundation—WebLogic Server is the de facto standard application server, and is used by more developers, independent software vendors (ISVs), application service providers (ASPs), and system integrators (SIs) than any other application server.
• Increase productivity—achieve rapid development of e-commerce applications that use the J2EE standards for application services.
• Reduce cost structure—leverage existing assets and reduce number of products to learn, integrate, support, and maintain.
• Grow your business—achieve scalability and high-availability through open standards and clustering, supporting aggressive growth rates in a customer base.

For more information about BEA partner programs, see:

• BEA Partners at the following URL:

http://www.bea.com/framework.jsp?CNT=index.htm&FP=/content/partners

• WebLogic Server Partner's Guide on the BEA e-docs Web site at the following URL:

http://download.oracle.com/docs/cd/E13222_01/wls/docs70/isv/index.html

Conclusion

This document has explored how WebLogic Platform, through its unified, simplified, and extensible architecture, contributes to an increase in developer productivity, resulting in faster time-to-market and a reduced cost structure.

To access more information about WebLogic Platform, refer to the information sources provided in the following table.