creating an soa with ibm websphere
TRANSCRIPT
© 2007 IBM Corporation
SOA From a Business Centric Perspective
Vladimir ErgovicSoftware IT ArchitectIBM CEMAAS South East [email protected]
Agenda
• IBM’s view of SOA– the business alignment and enterprise wide trend
• SOA entry points – governance and how it impacts many aspects of an organization
• Methodologies and products– CBM, SOMA, RUP, GS Method, RUP4SOA
• Business services– WebSphere Business Services Fabric
• Summary– current and future industry trends
• SOA is one of IBM’s long term strategies to enable innovation that matters
– Continuing to deliver SOA centric offerings
• IBM’s view of SOA is business centric
• How to get started is crucial– People, process and information – Reuse & connectivity is critical
• Entry points are accelerated by SOA Foundation products and business insight
– new and enhanced products– new service offerings– 90,000 GBS skills trained– Best practice customer examples– Enhancements to SOA Standards Roadmap– Many more…
• SOA Governance is a key to success
SOA impacts Business and IT… But that doesn’t mean everything is SOA. This presentation is about how IBM enables customers to take an SOA approach to solving problems across business domains.
Key Takeaways
Enable Business Flexibility
Easy to enhance reconfigure and maintain
Able to be deployed in incremental steps
Increase the speed of the decision making
Improve collaboration
Reduce administrative time
Deploy end-to-end business process
The business alignment and enterprise wide trend projects snapshot
Web Services Interoperability across
Heterogeneous Environments
Service ComponentsSimplified Composition and
Implementation of Services and Data
Business ProcessesBusiness Process Modeling &
Management
Enterprise Governance
Aligning business strategy
ESB Mediation of servicesSecurity Federation for Telco Partner Integration
Enterprise SOA Transformation including setup of SOA Governance Organization (large insurance company)
Enterprise Wide SOA Portfolio Management for automotive industry
Container Shipping Company transformation
Airport Ramp Control Trucks Customer Order process Electronic Industry Contracts management Telco “Meet me Service”
Service Registry & RepositoryComponents for Car DealersService Portfolio for Heavy Industry
Business
Technology2003
2007
Enable human and process interaction with consistent levels of service
Achieve greater efficiency and effectiveness with business model innovation
Recent studies of over 1900 customers showed SOA starting points of people, process, information or a combination of all three
IBM's View of SOA: Business Centric Built on SOA Lifecycle
Deliver trusted information in business context to enable innovation
Entry Points Based on Real Customers’ Engagement
Pattern Example Customer Value Business Challenge
Information Rapid project payback from reuse – second interface was delivered within 10 weeks, at 2.5% of the cost of the first interface
Competition and regulatory pressures forced to improve their understanding of and relationships with customers
Process Harley Davidson Financial Services
Financial Programs that map to Marketing Promotions can be done faster and cheaper
Poor integration between channels and desire to optimize E2E processing
People Web Services based Infrastructure reduce nearly 50% application deployment and 30% operations cost
Post merger standardization of application development & deployment infrastructure
ReuseSavings of 4M pounds to date, 1M pounds a quarter
Reduce cost of business with multiple channelsMake data in existing systems available to sales portal
Connectivity: Standardize application integration estimate saving $720,000 annually and 25% less application development time
Applications in silos, can’t communicate with each otherRouting of requests through multiple data centers
33
11
22
55
44
11
ValueImprove business operations and reduce risk with trusted information services delivered in-line and in-context
Start withDiscover and understand information sources, relationships & business context– Choose reusable high value data for first servicesNext stepsExpand number and scope of services across internal and external processes
Information Centric Approach – Greater Value through SOADelivering Information as a Service to People & Processes
Information as a Service
Data Content
Processes PeopleApplications
Why SOA?Trusted information packaged as services are embedded inline within processes or delivered to people
22
Web order?
Check order
Shipment status
On time?
Order is delayed
Publish order to back-end
Approve order as is?
Get EDI orders from ERP
Web order?Web
order?Check order
Shipment status
On time?On
time?Order is delayed
Publish order to back-end
Approve order as is?
Approve order as is?
Get EDI orders from ERP
Get EDI orders from ERP
ValueInnovative business models deployed quickly with flexible and optimized processes. Measure performance to drive improvement.
Start withA single process – Model an underperforming process. Optimize and deploy as enhanced process.
Next stepsFlexibly link multiple processes across the enterprise & to suppliers / partners. Monitor the process to measure & track performance.
Process Centric Approach - Greater Value through SOABusiness Process Management for Continuous Innovation
Why SOA?Modeled processes, converted into services, are re-used, connected and re-deployed more flexibly and quickly with SOA
33
ValueImprove people productivity by aggregating views that deliver information and interaction in the context of a business process
People Centric Approach - Greater Value through SOAIntuitive & Adaptive User Experience
Why SOA?Composite applications created, deployed, and updated faster with SOA portlets
Start withBuild a view of a key business process by integrating information in front of people to improve decision making
Next stepsManage performance more tightly with alert-driven dashboards tied to processes
44
*Software Strategies “Enterprise Integration Challenge” 2005
Value Deliver services through new business channels
for a secure, consistent user experience Service-based connections with trading partners Potential savings of 2X-4X over custom-built
integration or FTP*
Start with Messaging backbone leveraging messaging and web
services protocols as the foundation for SOA connectivity
Enable mediated exchange between services, by leveraging an ESB
SOA appliances for ESB functions in a hardware form factor
Connectivity - Greater Value through SOAUnderlying Connectivity to Support Business-centric SOA
* Software Productivity Research (SPR)
Creating & Reusing Services - Greater Value through SOACreate Flexible, Service-based Business Applications
ValueFlexibility and elimination of duplication for reduced cycle times Expanded access to core applications Consultant studies have found it 5X less expensive to re-use existing applications than to write new applications*
Start withWhat services are needed to run your business?Identify high-value existing IT assets and service-enable them for reuse
Fill in gaps by creating new services for today's business needs and future reuse
Registry/repository to facilitate centralized access and control of reusable services
55
Funding
Service Domains
Categorization of Services
Roles and responsibilities
Ser
vice
s O
wne
rshi
p an
d
Dom
ains
Service Oriented Development Lifecycle
Operational Life-cycle
Managem
ent
Service management
SLA
Capacity and Performance
Security
Monitoring
Identification and Maturity of Services
Service Assembly and Deployment
Change Management
Governance
Governance is critical to success with SOA• For business services and composite apps/services to become reused, they must be “trusted”• Trust is enabled by effective governance for compliance to Service Level Agreements, and
nonfunctional requirements (e.g. security, reliability, performance, etc.)
Creating effective SOA governance is challengingExamples of key questions to address:
• What common business services are needed?
• What potential applications (service consumers) will reuse these service(s)?
• Which policies are common, which are unique?
• Can the differences be isolated to maximize consistency?
• What services already exist and are candidates for reuse?
• Who decides which existing LOB service has the best customer data for the new shared process to be used by all LOBs?
• Who owns the shared service(s)?
• Who should fund it?
• Who is responsible for upgrades?
• How to motivate each LOB to reuse the service (rather than their own unique version because they feel they have unique needs)?
• Who decides who can use the service and how often?
• How to organize the shared services/assets so they can be effectively reused at a later date?
• Who is allowed to change a service reused by others?
• Who is using a service and what will be impacted by changes to that service?
• Who needs to approve any changes?
• Who will be responsible for funding upgrades to meet a specific user's requirements?
Key aspects to control:• Service registration • Service versioning • Service ownership • Service funding • Service monitoring • Service auditing • Service diagnostics • Service identification • Service modeling • Service publishing • Service discovery • Service development • Service consumption • Service provisioning • Service access• Service and composite app
deployment• Service security
Service Lifecycle Management Flow
• Service Creation leads into a focused development lifecycle• Service Deploy and Availability focus on change and release mgmt• Service Operational Management focuses on system management
Service Lifecycle ModelService Lifecycle Model
Service Reuse / UseService Reuse / UseExisting?
Service Creation(Development Lifecycle)
Service Inception (Organization Needs)
No
Yes
Yes, but...
Service Deploy
Service Deploy Service
Availability
Service Availability
Service Variation Request Service
Versioning
Service Versioning
Service Operational Summary
Service Operational Summary
Service Retirement
As SOA practices mature, a the “Service Lifecycle” view has emerged
Service lifecycle management is a component of an overall SOA Governance Strategy, and provides control and rigor appropriate to the nature of services
Two types of methodology are needed, with different delivery options
The Rational Unified Process (RUP) for SOA, and other RUP methodologies
• Very comprehensive methodology for managing the lifecycle of services, both from bottom-up and top-down perspectives
• Separate tasks and deliverables provided as in plug-ins
• Rational Method Composer hosts the plug-ins, and facilitates tailoring the collection of methodology elements to the specific needs of the enterprise
1. Methodology for the Identification, Design, Creation, Deployment, and Management of services
2. Methodology for the creation of a governance strategy and approach for SOA
Customer Delivery Services Delivery
IBM’s CBM, SOMA, and other GS Method methodologies
• GBS and GTS use proprietary intellectual capital and tools, which can be very specific to industry requirements
The RUP plug-in for SOA Governance• Accessed and customized via the Rational Method
Composer• Guides the design and implementation of an end-to-
end Governance approach through a series of tasks and deliverables
• Leveraged by Rational Portfolio Manager (RPM) to create project templates that are in alignment with the established governance policies and procedures (ensures that all projects are in conformance)
Governance aspects of IBM’s SOMA methodology
• GBS and GTS use proprietary intellectual capital and tools
IBM’s SOA Methodology
Organizations
Business Modeling
Requirements
Analysis and Design
Implementation
Test
Deployment
Configuration & Change Mgmt.
Project Management
Environment
Operations
RUP
GS Method
RUP4SOA
CBM
SOMA
domain areasCBM – Component Business ModelingSOMA – Service Oriented Modeling and ArchitectureRUP for SOA – Rational Unified Process for SOA
IBM Confidential
To-BeBusiness
Process Model
Component Business Modeling
• CBM is a business consultancy method used by IBM Global Business Services• CBM is a technique to decompose an Enterprise into its constituent building blocks
(business components)• A component is a logical grouping of people, technology, and resources that
delivers specific business value, and can operate independently• The output of a CBM engagement can be the input to an SOA engagement
SOMA
Heat Map
ComponentBusiness
Model
RUPfor BM/SOA
CBM
CBM
Enterprise Architecture“the city plan”
Solution Architecture• functional aspects• operational aspects
“the infrastructure and Single building design”
BusinessStrategy
InformationTechnology
Strategy
BusinessOpportunity
TechnologyAvailability
- Processes- Information- People- Locations
- Applications- Data- Technology
Planning
Design andDelivery
En
terp
rise
wid
e fo
cus
Pro
jec
t fo
cus
Strategy
IT Solutions
Transition Plan
Enterprise Architecture embraces both Business and IT Architectures, providing the “city plan” for “building projects”
Domain Architectures“regions of the city plan”
SOA ReferenceArchitecture
Business Operating Environmentand IT Infrastructure
Enterprise Architecture
BusinessMap
InfrastructureMap
BusinessArchitecture
ApplicationMap
Strategic Capabilities Network (SCN)
V VV
C
C
C
CC
C
CC
RR
R
R
R
R
R
R
R
R
R
R
R
R
RR
R
EA Engagement: During enterprise architecture activities, we focus on refining the needed capabilities and identifying the resources (capability enablers) the client needs to meet its strategic objectives.
The SCN is created and developed in Strategy engagements and Enterprise Architecture engagements. In each of these, the focus is slightly different.
Strategy Engagement: During strategy activities the focus is on understanding the client’s existing capabilities, evaluating their strengths and weaknesses and identifying new capabilities required.
How does an SOA engagement use CBM work products?
• CBM can identify where to focus attention in an SOA engagement – e.g. areas of key strategic value (heat map)
• CBM gives a loosely coupled architecture – an SOA should not bind the business components in a way that compromises the business architecture.
• If CBM has identified business services, these can be analyzed to identify the software services needed to support them
• If CBM has identified business processes then these act as requirements on the functionality that must be offered by a service-oriented solution
CBM
SOMA
• Service-Oriented Modeling and Architecture
• It is a method with roles and activities that produces artifacts (workproducts) relating to the identification, specification and realization of services, components and flows (processes)
SOMA
RealizationDecisions
Specification of Services, Components, and Flows
Identification of Candidate Services and Flows
Domain Decomposition
SubsystemAnalysis
ServiceSpecification
message & event
specification
component flowspecification
service flowspecification
Realization Decisions
Goal-ServiceModeling
Existing AssetAnalysis
Component Specification
informationspecification
service allocation
to components
componentlayering
technical feasibility exploration
More about SOMA
• SOMA is aimed at enabling target business processes through the identification, specification and realization of business-aligned services that form the SOA foundation.
• It introduces new and innovative techniques where gaps exist in existing techniques, in order to specifically address SOA needs. SOMA enables creation of composable services.
• It creates continuity between the business intent and IT implementation by extending business characteristics (e.g. goals and key performance indicators) into the IT analysis and architectural decisions.
• Analysis and modeling performed during SOMA does not impose any product, but establishes a context for making technology and product specific decisions in later phases of the lifecycle.
• Its goal is to provide guidance in the modeling (analysis and design) of SOA.
SOMA
SOMA Activities SOMA
Domain Decomposition
SubsystemAnalysis
ServiceSpecification
message & event
specification
component flowspecification
service flowspecification
Realization Decisions
Goal-ServiceModeling
Existing AssetAnalysis
Component Specification
informationspecification
service allocation
to components
componentlayering
technical feasibility exploration
RealizationDecisions
Specification of Services, Components, and Flows
Identification of Candidate Services and Flows
• SOMA activities are grouped into three major steps: Identification, Specification, and Realization
• At the heart of SOMA is the identification and specification of flows, services, and components
• SOMA activities are performed iteratively. Each step is carried out by applying one or more complementary techniques.
Service Identification
• A combination of three strategies is used
– Goal-Service Modeling
– Domain Decomposition (Top down Analysis)– Existing Asset Analysis (Bottom-up Analysis)
SOMA
Top-down Analysis
Bottom-up Analysis
Align Serviceswith Business Goals
Domain Decomposition
Existing AssetAnalysis
Goal-ServiceModeling
Service Specificationnext step:
Service Specification SOMA
Service Realization
• Service Specification– Elaborates the Service Model. For example: service dependencies, composition, non-
functional requirements, service message specifications, design decisions, etc.– Includes Service Litmus Test that “gate” service exposure decisions
• Subsystem Analysis– Partitioning into service components that will be responsible for service realization
• Component Specification– Detailed component modeling, flow, information architecture, and messages
Subsystem Analysis
Subsystem Analysis
Component SpecificationComponent Specificationinformation
specificationinformation
specification
component flow specification
component flow specification
Service Specification
Service Specification
service flow specificationservice flow specification
message & event
specification
message & event
specification
next step:
Service Realization
• Review the Service Model to determine how each Service is realized
– Decide how Services are Realized:buy, build, integrate, transform, subscribe, outsource
– Document the Service Realization Decisions
SOMA
Service Implementation
Realization DecisionsRealization Decisions
component layering
component layering
technical feasibility
exploration
technical feasibility
exploration
service allocation to components
service allocation to components
next step:
SOMA delivery
• SOMA is intended to be used by IBMers (especially IGS) working on client engagements
• Can be left with customers provided contracts and licenses are in place
SOMA
IBM Confidential
Rational Unified Process
It’s a set of software development best practices collected over twenty years of client engagements
It’s an IBM Product
• RUP is iterative– executable releases at each
iteration (risk reduction)• RUP is Use Case based
– business or system use cases– use cases are used to define
scope, plan, test and documentation
• RUP is Architecture driven• RUP is modular
– plug-ins for SOA, Systems Engineering, etc.
RUP always needs to be tailored to the specific project
RUP
RUP for SOA
• It’s a RUP plug-in, available in Rational Method Composer 7.0
• Focuses on the Analysis and Design of Services
• Activities in all the RUP disciplines have been updated with Service-Oriented content
• Shares many concepts, activities and artifacts with SOMA
• Top-Down, Business Process Driven • Top-Down, Use Case Driven • Data Driven • Rule Driven • Bottom-Up, Exposing Existing Assets
RUP for SOA
Refine the Architecture
Design Services
RUP for SOA – Some key elements RUP for SOA
Rational Method Composer• RMC is an Eclipse-based tool for creating and
customising development processes• RMC includes RUP and several RUP plug-ins
including RUP for SOA• Processes are deployed (“published”) as HTML and
Java applet web sites
RUP for SOA Governance Plug-in (IBM SOA Governance and Management Method)
IBM’s foundation SOA technology provides support for governance
WebSphere Business Modeler
•Define and document the governed processes
•Roles, Decision Rights, Process
WebSphere Integration Developer
•Enable the governed process as executable business process
•Lifecycle state machine
WebSphere Process Server
•Execution runtime for governance workflow
•Manages the SOA Lifecycle through enforced workflow
WebSphere Portal
•UI Interface for decision rights
•Authentication and Authorization for workflow and checkpoints
WebSphere Monitor
•Monitor results and KPIs of the governed process
WebSphere Registry and Repository
•Definitive source of state for services as they progress through governed workflow
Development Sub-Process
•Rational Tools, enforcing a defined development process as defined during the governance process
•ClearCase, ClearQuest, Requisite Pro, RAM, BuildForge
•Development workflow managed by Process Server
IT Service Mgmt Sub-Process
•Tivoli Management products, enforcing defined ITSM processes as defined during the governance process
•CCMDB, TPM, ITCAM
•Systems Management workflow managed by Process Server
Composition Studio
• A visual modeling environment where domain-experienced software architects can easily create and manage industry specific service meta-data models and policies.
Subscriber Manager
• Controls and automates entitlement of Business Services for subscribers.
• Enables creation, control, and management of service packages to subscribers across the ecosystem.
Governance Manager
• Provides powerful visual zooming and panning models of hierarchies and service dependencies so that technical and business users can monitor business SLAs & performance.
Business Services Repository
• A standards-based, enterprise SOA metadata repository to manage ontologies, service descriptions and policies.
• Enables developers to publish, reuse, & manage services.
Dynamic Assembler
• A highly scalable, semantic services broker that enables dynamic service assembly and provides service behavior personalization based on content, context, and contract.
Performance Manager
• Provides visibility and monitoring of service oriented processes and applications. It includes multi-perspective views and enables drill-down analysis of events and exceptions.
WebSphere Business Services Fabric
WBSF leverages and extends WSRR
.wsdl .xsd
Bpel Metadata
Classifications
CBS Metamodels
Industry Ontologies
Subscription Policies
Business Policies
WSRR
BSR
Web Service Details
Discovery WSRR API
Web Service Technical Artifacts
Business Service Metadata
Business Services Repository (BSR)
• Focus on business service metadata, policies, and subscribers
• Foundation for "housekeeping of business services" throughout their lifecycle
• Spans design-time to run-time and manage-time usage scenarios
• Federation framework for scalable/extensible SOA that supports other authoritative data sources; WSRR, LDAP, and others
Websphere Service Registry & Repository • Focus on Web service technical artifacts • System of record repository to physically store assets
such as WSDL, XSD, BPELs, etc• Metadata classifications to enable easy search and
storage
WBSF and WSRR provide differentiated and comprehensive registry/repository capabilities through the runtime use and management of both business and technical metadata
The Need: A simple and reusable process
The Reality: Different variations are needed in the process
Channels
A
B
C
D
E
Option 1: Write many different processes (low reuse)
Channels
A
B
C
D
E
Option 2: Write processes with complex decision paths (difficult process creation and management)
Channels
A
B
C
D
E
Option 2: Write processes with complex decision paths (difficult process creation and management)
Channels
A
B
C
D
E
P
The Best Option: Dynamic Assembly
Repository for Policies, Rules, etc.
A
B
C
D
E
Pre-Built Industry-Specific SOA Assets
• Categories of SOA assets that speed time-to-market and instill industry standards and best practices
Categories of Pre-Built Industry SOA Content
Business ProcessesExecutable processes and workflowsVisio/WBI modeler-based, BPEL compliant
Business ServicesData, process, visibility, optimization services Pre-built semantic mediation services
Business Rule Assets Configurable business rule templates By line of business, product and state
Industry Message SetsACORD and IAA-based (insurance example)Configurable, XML-based schemas
Ontology and Data ModelsPre-built SOA meta modelsOWL-based configurable ACORD and IAA models
Policies and AssertionsMulti-tier PRISM policies WS-Policy based models
3rd Party and BPO Service InterfacesInsurance interfaces to key services MVR, CLUE, Credit, Locations, and others
Legacy Adaptors300+ adaptors to legacy and ERP systems Sourced within Business Services Catalog
Benefits of the Business Services Fabric Storage of business services, subscribers and policies to enable assembly of composite business
services
• Central repository for business service meta-data, domain ontologies, policies, and subscribers
• OWL/RDF-based, meta-model, which allows for capturing semantics and easy extensibility
• Ontology-driven semantic mediation and interoperability
• Ability to federate meta-data from other repositories such as LDAP systems and WebSphere Service Registry and Repository
• Conflict detection during collaborative development
• Powerful search, dependency, and impact analysis
• Source and syndicate ISV and third-party IT assets into the catalog
• Role-based, context and namespace level security that leverages existing access control systems
• Support for entire meta-data life cycle including comprehensive versioning, change tracking, and collaborative governance of service meta-data
Benefits of the Business Services Fabric (cont.)Comprehensive business service governance
• Governs and manages the set of services, policies, and processes that drive reuse of business services, define and enforce policies, control proliferation of services, provide composite business service visibility, and manage the life cycle of business services
• Leverages components of WebSphere Business Services Fabric to govern life-cycle changes, particularly for design-time promotion of services to run-time and for recording service performance and changes
• Governs all aspects of business services: performance, reliability, interoperability, security, and management
• Manages life-cycle changes to business services
• Controls meta-data promotion between environments
• Validates meta-models to ensure accuracy and correctness before publishing
• Ensures meta-data integrity while modeling composite business services in a multi-authoring environment
• Defines policies for meta-data visibility in collaborative development environments
• Notifies users when changes are made
• Offers change management process for service versioning, validation, and performance management
• Includes open APIs for integration with change management systems, such as IBM Rational ClearCase®
Benefits of the Business Services Fabric (cont.)Meta-data-driven assembly of composite business services
• Enables publishing and managing service models, policies, and service portfolios
• Designed to work with WebSphere Integration Developer and tools such as IBM Rational® Software Architect, providing architects, developers, and system integrators with a common meta-data life-cycle management fabric for connecting services, exchanging meta-data, and aligning context across different applications and domains
• Achieves rapid and secure assembly of disparate IT assets into composite business services
• Supports both top-down business domain decomposition and bottom-up analysis of underlying IT systems
• Creates and enforces design-time, runtime, and change-time policies
• Composes unique multi-channel services that power multiple access modes such as Web, business-to-business (B2B), IVR and fax
• Delivers model and manage meta-information about business services including WSDL-, WS-Policy- and BPEL-defined declarations, and actual behavior of services
• Includes model policies as a basis for dynamic discovery, matching, and binding of services based on content, context, and contract
• Simulates service behavior based on different usage scenarios
• Manages run-time meta-information for matching service requestors and service providers using policies
• Applies policies at various levels; for example, business ecosystem, application, business service, or service end point
• Assembles policies in a unified, flexible and extensible grammar to express the capabilities, requirements, and characteristics of entities within an SOA
Benefits of the Business Services Fabric (cont.)Dynamic business service personalization and delivery • A highly optimized semantic mediation engine enabling meta-data-driven service discovery,
matching, and interoperability during both design-time and run-time. • Leverages business service policies to replace hard-coded service bindings in enterprise
service bus, Business Process Execution Language (BPEL), and B2B connections with dynamic end-point selection based on content, context and contract of the service request
• Dynamic service behavior adaptation that is based on business context, content, and contract
• Policy-based customization across multiple domains, business processes, and service end points
• Policy enforcement that is based on performance, reliability, interoperability, security, and manageability of business services
• Dynamic business service and process customization without affecting larger subscriber base
• Elimination/reduction of hard-coded binding changes with policy-based process customization
• Reduced integration complexity through ontology-based classification and data transformation rules
• Multi-protocol support for HTTP and JMS, and can be extended to other protocols • Multi-message support, for example, ACORD, HIPAA, HL7 • Out of the box support for SOAP, Java™ Messaging Service (JMS) topics, Remote Method
Invocation, and MQ
Benefits of the Business Services Fabric (cont.)Real-time business service visibility and control • Business visibility and monitoring of composite business services and service
oriented processes for business analysts and IT administrators • Multi-perspective views and drill-down analysis of events and exceptions with
respect to business context in a loosely coupled, service-oriented business ecosystem
• Subscriber- and role-based drill-down performance visibility against business goals and service level agreements
• Business service support for billing and metering of composite business services at business service level
• Central performance monitoring console customizable by business need • Domain, subscriber, and service-based performance and Service Level
Agreement (SLA) reporting • Business content monitoring and alert notification • Context specific error handling across multiple messages and protocols • Configurable audit trails on service invocations for security, SLA, and compliance
monitoring • Real-time monitoring of aggregate or individual level traffic including faults,
throughput response, and availability
Summary• IBM’s view of SOA is business centric
• Governance is critical to success with SOA
• Various methods, future improvement
• Alignment between Enterprise Architecture and SOA
• Business Services are in focus for the next generations of SOA project
Questions ?
Backup
Design Tools
WBSF Design-Time Perspective
Business Services Definition Tooling:
Composeable Business Service-based
3. Governance Manager
• Publish Business Service adds, changes and deactivations
4. Subscriber Manager• Add, Change, Deactivate Business Service subscribers
5. Performance Manager• View existing performance metrics
WebSphere Process Server
WebSphere Service Registry & Repository
Business Service Repository is loosely coupled with WSRR to consume service metadata and policies
2. Business Services Repository
Ontologies
• Business Policy Data
• Subscription Data
6. Semantic MediationPlug-in (Dynamic Assembler)
Usage Extensions
WebSphere Business Modeler
WebSphere Integration Developer
Process &/or Flow Models
1. Composition Studio
•Access to the Business Services Repository
•Create Business Service assembly definition
Eclip
se
BPEL Editor, WSDLs, and Deployment
WebSphere Process Server is required to run the web-based tooling
Local Test Instance Fabric
WebSphere Process Server
WBSF Run-Time Perspective
2. Business Services Repository
6. Semantic MediationPlug-in (Dynamic Assembler)
Business Service Repository is loosely coupled with WSRR to collect service metadata and policies
Industry Fabric Runtime:WebSphere Process Server includes WAS, BPEL Engine and WESB• Loosely Coupled using JMS
Exposed Business Services
WebSphere Service Registry & Repository
Web Service or JMS
Connections
Common or Core Services
Composeable Business Services
• Fabric Common Services
• Common Industry Services
• Usage data with Performance Manager
• LDAP Services
Ontologies
• Business Policy Data
• Subscription Data
Performance & Usage Data
Run-time Tools
Management Tools
WBSF Manage-Time Perspective
Business Services Definition Tooling:
Composeable Business Service-based
3. Governance Manager
• Publish Business Service change lists• Manage Business Service Lifecycle approval/rejections• Track and Audit Change history
5. Performance Manager• View existing performance and utilization metrics• View Billing and Metering information
WebSphere Process Server
WebSphere Service Registry & Repository
Business Service Repository is loosely coupled with WSRR to consume service metadata and policies
2. Business Services Repository
Ontologies
• Business Policy Data
• Subscription Data
6. Semantic MediationPlug-in (Dynamic Assembler)
Performance & Usage Data
WebSphere Service Registry & Repository
User Interface
1. Composition Studio
• Access to the Business Services Repository
• View Business Service assembly definitions
Eclip
se
Loosely connected through the Eclipse IDE using plug-ins
WebSphere Process Server is required to run the web-based tooling