bea white paper a bea enterprise architecture guide bea white paper – a bea enterprise...

Download BEA White Paper A BEA Enterprise Architecture Guide BEA White Paper – A BEA Enterprise Architecture

Post on 01-May-2020

0 views

Category:

Documents

0 download

Embed Size (px)

TRANSCRIPT

  • BEA White Paper

    A BEA Enterprise Architecture Guide Creating SOA from a Monolithic Portal Environment

  • Copyright

    Copyright © 1995 - 2006 BEA Systems, Inc. All Rights Reserved.

    Restricted Rights Legend This software is protected by copyright, and may be protected by patent laws. No copying or other use of this soft-

    ware is permitted unless you have entered into a license agreement with BEA authorizing such use. This document is

    protected by copyright and may not be copied photocopied, reproduced, translated, or reduced to any electronic

    medium or machine readable form, in whole or in part, without prior consent, in writing, from BEA Systems, Inc.

    Information in this document is subject to change without notice and does not represent a commitment on the part of

    BEA Systems. THE DOCUMENTATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND INCLUDING

    WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

    FURTHER, BEA SYSTEMS DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING

    THE USE, OR THE RESULTS OF THE USE, OF THE DOCUMENT IN TERMS OF CORRECTNESS, ACCURACY,

    RELIABILITY, OR OTHERWISE.

    Trademarks and Service Marks Copyright © 1995-2006 BEA Systems, Inc. All Rights Reserved. BEA, BEA JRockit, BEA WebLogic Portal, BEA

    WebLogic Server, BEA WebLogic Workshop, Built on BEA, Jolt, JoltBeans, SteelThread, Top End, Tuxedo, and

    WebLogic are registered trademarks of BEA Systems, Inc. BEA AquaLogic, BEA AquaLogic Data Services Platform,

    BEA AquaLogic Enterprise Security, BEA AquaLogic Service Bus, BEA AquaLogic Service Registry, BEA Builder, BEA

    Campaign Manager for WebLogic, BEA eLink, BEA Liquid Data for WebLogic, BEA Manager, BEA MessageQ, BEA

    WebLogic Commerce Server, BEA WebLogic Communications Platform, BEA WebLogic Enterprise, BEA WebLogic

    Enterprise Platform, BEA WebLogic Enterprise Security, BEA WebLogic Express, BEA WebLogic Integration, BEA

    WebLogic Java Adapter for Mainframe, BEA WebLogic JDriver, BEA WebLogic Log Central, BEA WebLogic Network

    Gatekeeper, BEA WebLogic Personalization Server, BEA WebLogic Personal Messaging API, BEA WebLogic

    Platform, BEA WebLogic Portlets for Groupware Integration, BEA WebLogic Server Process Edition, BEA WebLogic

    SIP Server, BEA WebLogic WorkGroup Edition, Dev2Dev, Liquid Computing, and Think Liquid are trademarks of BEA

    Systems, Inc. BEA Mission Critical Support, BEA Mission Critical Support Continuum, and BEA SOA Self Assessment

    are service marks of BEA Systems, Inc. All other names and marks are property of their respective owners.

    CWP1478E1106-1A

  • BEA White Paper – A BEA Enterprise Architecture Guide

    Contents

    Executive Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

    Achieving the strategic goals of SOA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

    Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

    Step 1: decoupling of data logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

    Step 2: controlling service proliferation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

    Step 3: loosely coupling consumers from producers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

    Step 4: decoupling presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

    Step 5: consuming other services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

    Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

    About BEA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

    Join the BEA community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

  • BEA White Paper – A BEA Enterprise Architecture Guide

    Executive summary SOA is an IT strategy that organizes the discrete functions contained in enterprise applications into interopera-

    ble, standards-based services that can be combined and reused quickly to meet business needs. IT and line-

    of-business managers and administrators often want to realize the benefits of SOA. Doing so can be simple, if

    a few maxims are kept in mind:

    • Plan strategically but implement tactically. While long-term goals are important, a “big bang” approach to strategic goals can be problematic. The success of an SOA implementation depends on the ability to implement transitional architectures over weeks and months yet preserving goals which may take a period of years to achieve completely. With SOA, IT can remain agile, staying close to business requirements over the course of successive changes and enhancements.

    • Treat the service infrastructure as a toolbox. The service infrastructure is the first of the critical capabilities that determine the success of an SOA. Over time, the service infrastructure should provide the ability to add new “tools” to an environment that complement existing tools and provide new capabilities without necessitating rework or affecting other tools already in use. This allows an architecture to mature over time and is a key factor in maintaining an organization’s business agility and fiscal constraints.

    This paper documents one path to an SOA given a particular starting point, the monolithic portal.

    1

  • BEA White Paper – A BEA Enterprise Architecture Guide

    2

    Achieving the strategic goals of SOA

    Getting started To start down a strategic path, one must first understand the current environment. This paper assumes as a

    starting point an existing monolithic portal environment.

    As shown in figure 1, a monolithic portal environment, which exists in many IT environments, can be defined as

    a portal that encapsulates presentation, business, data, and security logic into the same container. The chal-

    lenge of a Monolithic portal environment is that it is tightly coupled to its data feeds. Because a company’s

    investment in portals can be substantial, IT personnel are faced with the question, “How can we leverage the

    current environment and at the same time achieve an SOA?”

    Figure 1

    Monolithic portal environment.

    Presentation Business Data

    Data WarehouseERP.NetMainframedB

  • BEA White Paper – A BEA Enterprise Architecture Guide

    Step 1: decoupling of data logic Decoupling of the architecture’s data logic is the first step in transitioning from a monolithic portal to a SOA-

    based environment. As shown in figure 2, creating a data services layer and abstracting its data logic from the

    current portal infrastructure can be leveraged for the future. Creating a data service layer makes it possible to

    create and expose common views of key information and to utilize data as a service.

    The data service layer must have the following capabilities:

    • The ability to interact with, and consume data from, heterogeneous data sources and environments as the data moving into and out of an enterprise will be from many sources.

    • The ability to provide data virtualization. Otherwise, heterogeneous data, schematics, or ownership issues can make physically merging data difficult or even impossible.

    • The ability to perform dynamic data transformation since data from disparate sources and environments rarely are homogeneous in format or accessibility.

    • The ability to handle security through data redaction and participation of data security in the larger enterprise’s SOA security implementation.

    • The ability to handle complex data read and write requirements in a heterogeneous environment.

    • The ability to do all the above with minimal or no hand-coding, so the service infrastructure can deliver on require- ments in weeks rather than months and remove programmer expertise or availability as potential bottlenecks.

    3

    F igure 2

    The Data Service layer enables abstaction and de-coupling of the Presentation Business Data layer from the physical data feeds.

    Data Services Layer

    Data WarehouseERP.NetMainframedB

    Presentation Business Data

  • BEA White Paper – A BEA Enterprise Architecture Guide

    Step 2: controlling service proliferation As successive sets of data services are built and deployed, the service infrastructure must be able to control

    service proliferation, service creation, service consumption, and service reuse. If it cannot, there is the risk of

    creating numerous services that are never consumed or reused; even worse is a declining ability to satisfactori-

    ly monitor and manage the environment in the event that the most popular services are unplanned successes

    without adequate infrastructure to support demand.

    Controlling service proliferation d

Recommended

View more >