2. Business Architecture: Architecting SOA With A Business Focus
Mahesh Dodani
Dean, IBM School of Software Architecture

3. SOA Architect Summit Roadmap
What is the impact of SOA on current Enterprise Architectures?
Alignment of Business and IT Architectures
SOA Reference Models
SOA Governance
Information Technology Strategy
Business Strategy
Enterprise Architecture
How do you develop SOA with a business focus?
How do you reuse applications in the context of SOA?
Business Architecture
Processes
Information
People IT
Architecture
Applications
Information
Technology
Asset Discovery
Application Reuse
Business Components
SOA Design
Business Process Management
Transition Plan
EA Governance
How do you leverage information in an SOA?
Business Operating Environment and IT Infrastructure
Information as a Service
Master Data Management
IT Solutions
How does my infrastructure support SOA?
Service Management / QoS
Security

4. Agenda SOA Business Architecture Considerations
Business Strategy
SOA Design
Business Process Management
SOA Business Architecture Best Practices
IBM Capabilities to Support SOA Business Architecture
Summary

5. Enterprise Architecture Links Business and IT Reconciling Business Requirements and IT Capabilities
Business Perspective
IT Perspective
Business View
IT View
Business Analyst
IT Architect
Developer
Enterprise Architecture
Process/Operation Model
Architecture/ Execution Model
Business Process Model
Process Choreography
NOTES – Line up the concepts between Business and IT as part of notes …
Business Component
UML Class Model
Business Information
UML Data, XML, SQL Model
Business Services
Service Model, WS-BPEL

6. Business Strategy Drives IT Decisions IT’s Goal is to Flexibly Support Business Requirements
Business Intent
Meeting Strategic Goals?
Business Strategy & Design
Align
Strategic KPIs
Business Services
Business Understanding
Business Operations
Meeting Business Commitments?
Optimize
Operation Models
Business Performance Management
Operation Models
Solution Flexibility
Solution Composition
Response to Business Situations
Correct
Executable Solution
Executable Solution
Quality of Service
Detecting Business Situations
IT Implementation
Monitor

7. Service-Oriented Design Is An Evolutionary Approach
Increasing Levels of Abstraction *
Objects
Components
Services
Object-Oriented
Component-Based
Service-Oriented
SOA builds on well-established software architecture principles (such as information hiding, modularization and separation of concerns)
SOA adds additional aspects (including SOA interaction patterns, service registries, reuse considerations)
Service-oriented modeling needs techniques to support these aspects (service identification, specification, realization and implementation techniques)
The requirements for modeling and building a new architectural style, SOA, are different from more traditional process modeling and Object-Oriented Analysis and Design methods and require more specialized Service-Oriented Analysis and Design techniques.
Let’s discuss increasing levels of abstraction as we move from objects to components to services. Partial models of these increasing levels are depicted here.
Object-oriented applications are built on the structuring element of classes and objects. Later modeling techniques evolved to group objects into components and expose their interfaces. Thus, components emerge as the primary structuring unit of applications, where components represent run-time deployable unit of functionality.
A further decoupling of interfaces from implementation and binding through the service-provider and service-consumer paradigm led to emergence of SOA. In this paradigm, services are the primary structuring element for applications versus objects or components as before.
Just as OOAD is necessary to define object-oriented systems and component-based development is used to define component-based architectures, service-oriented modeling is necessary to build a service-oriented architecture.
Building a service-oriented architecture requires more than just a list of services. It requires conceptualization, identification, specification and realization of services that bridge business and IT together in the SOA paradigm. This requires modeling the attributes of each service and service relationships.
Today, methods exist for Object-Oriented Analysis and Design and Component-Based Development. There is no method in the public domain for service-oriented analysis, design and development. The objective of SOMA is to fill the current gap in OOAD and CBD to address services.
Just as OOAD is necessary to define object-oriented systems and component-based development is used to define component-based architectures, service-oriented modeling is necessary to define a service-oriented architecture

8. Service Oriented Analysis, Modeling, and Design
Top Down Approach – Business Requirements can be rendered as a Business Process Model
Articulate and model the business intent as a process
Process model becomes an input for service design
Meet-In-The-Middle Approach – Identification of business goals and sub-goals
Goals and sub-goals correlate to candidate services
Bottom Up Approach – Existing IT assets are discovered and evaluated as possible services
Identify existing components as candidate services
Assets can be transformed into service interfaces and implementations
Best approach is Meet-In-The-Middle
The Goal-Service Modeling technique helps discover business-aligned services and ensures that important services have not been missed during Process Decomposition or Existing Asset Analysis. By clearly articulating business goals, Goal-Service Modeling also provides an important mechanism for narrowing the focus of the other service identification techniques. It starts with business goals, breaks them into sub-goals, and then determines which services are needed to fulfill the sub-goals.
KPIs, metrics and associated events are identified that make it possible in the future to measure the performance of the identified services and assess them against sub-goals.
A good practical approach
Do the “to be” analysis unconstrained by current systems
Make any compromises necessary to integrate with existing IT components
Rational Developer products come with an integrated set of highly productive tools that make it easy to create and consume Web services.
Creation is simplified by tools that automate the definition, test and deployment of different Web services artifacts and developers can either build new Web services from scratch, or enable existing applications as Web services. And low level coding in WSDL, UDDI or XML is virtually eliminated through the use of the Web Services tools!
Consumption is simplified by tools like the built-in UDDI browser that automate the search for existing services, the exploration and test of the service’s functionality and the coding of the service invocation! And testing is a breeze thanks to the universal Web Service test client
The comprehensive Web services tools handle most of the hard work in developing or consuming web services. Very little coding is required to consume existing Web services or to enable existing assets and this leads to a shorter learning curve and high productivity for developers.
Now let’s take a look at Rational Developer’s support for building rich Java applications and full J2EE applications.

9. Choreography (business rules and processes)
Top Down SOA Approach IT
WSDL
Business
Analyst IT
Business Requirements
Services (reusable functional components)
Story Board
And/or
Process Model
WSDL
Business
Analyst
Service
Specification IT
Business Use Cases
Business
Analyst
Business
Analyst
Note: Include Example in Speaker Notes – one for JK Enterprises – e.g. process model for Account Administration for example
From Clive Gee
Services identified using this technique are likely to be meaningful to the business and help to link business and IT But, be careful
This approach does not take into account non-functional requirements such as security and quality-of-service.
It’s important to treat services identified in this way as ‘candidates’. You must perform further analysis before confirming such a service
Strengths
Good approach for “green field” creation of new IT solutions
Excellent approach for defining new business processes
Weaknesses
The existing applications simply may not be capable of working the way that you would like them to
Encourages “build it yourself” – since vendors might not have the same approach as you
Requires a lot of analysis before any code can be created
New Application
Choreography (business rules and processes)
Business
Analyst IT

10. Bottom Up SOA Approach WSDL Legacy application Service Specification
Interface
Specification IT
Legacy
application
WSDL IT IT
Service
Specification
Business Requirements
Services (reusable functional components) IT
New Application
Business use Cases
Note: Include Example in Speaker Notes – one for JK Enterprises – e.g. exposing CICS transaction for example
This is not simply about exposing the existing interface to a system as a web service
You need to consider the design characteristics of the service (refer to the Service Design Principles lecture for more detail on good service design)
The interface to the existing system may not follow good service design principles, e.g.
operations may not be grouped into cohesive interfaces
many operation calls may be needed where an SOA approach would use a single operation with a composite message type
technology-specific object references may be passed in and out
From Clive Gee
Strengths
Good approach for integration of a new commercial off-the-shelf (COTS) package with existing systems
Good for wrappering existing applications to make them more flexible
Weaknesses
Doesn’t change the function
May be impossible to re-engineer some processes that are built-in to current software
Business
Analyst
Story Board
And/or
Process Model
Choreography (business rules and processes)
Business
Analyst
Business
Analyst IT

11. Developing Business Process and Consumer Layers
Services
atomic and composite
Operational Systems
Service Components
Consumers
Business Process
Composition; choreography;
business state machines
Service Provider
Service Consumer
(Enterprise Service Bus)
Integration Infrastructure
Monitoring Infrastructure Services)
QoS Layer (Security, Management &
Information Architecture (meta-data) &
Business Intelligence
Governance (managing the service portfolio)
Channel
B2B
Packaged
Application
Custom OO
Atomic Service
Composite Service
Registry
In spite of earlier efforts, soa good app services must be based on a model

12. Enabling Business Process Management Through SOA
Business process design
Alignment of designed functionality with business requirements and performance objectives
Quality of the design (complete, correct, and consistent with best practice process design principles, standards and guidelines)
Integration across processes based on common business items or services
Business process implementation
Alignment of operational organization with the process
Alignment of application services with process functionality
Integration with other applications and data via ESB
Use of application services components that support dynamic reuse and reconfiguration
Business process execution
Monitoring of real-time process performance and trends against performance targets
Response to execution problems with effective interventions to restore performance

13. Developing the User Interaction Layer Portlet-based User Interface Components Provide Access to Services
JService
CustomerInfo
Export
MyValue
JService
MyValue
Execute business functions through process and service layers
Personalize interactions based on user identity and role
Support workflow within portal execution space
Import
StockQuote
MyValueModule
JService
CustomerInfo
Export
MyValue
JService
MyValue
Import
StockQuote
MyValueModule

14. Agenda SOA Business Architecture Considerations
SOA Business Architecture Best Practices
Business Component Analysis
Service-Oriented Modeling and Architecture (SOMA)
Business Process Management
IBM Capabilities to Support SOA Business Architecture
Summary

15. Business Component Analysis
The enterprise is mapped out as a set of categorized business components
Heat map highlights components for analysis based on criteria such as gaps and efficiency
Enables approaches to understanding how the business can be improved
Business
Administration
New Business Development
Relationship Management
Servicing & Sales
Product Fulfillment
Financial Control and Accounting
Directing
Business Planning
Sector Planning
Account Planning
Sales Planning
Fulfillment Planning
Portfolio Planning
Controlling
Business Unit Tracking
Sector Management
Relationship Management
Sales Management
Fulfillment Monitoring
Compliance
Product Management
Credit Assessment
Reconciliation
Staff Appraisals
FROM:
Columns are Business Competencies, defined as large business areas with characteristic skills and capabilities (e.g., product development, supply chain).
An Accountability Level characterizes the scope and intent of activity and decision-making at three levels:
Directing is about strategy, overall direction and policy.
Controlling is about monitoring, managing exceptions and tactical decision making
Executing is about doing the work
NOTE – Explain this … part of JK Enterprises – discuss the hot areas – how do you do a heat map… Look at PPI notes for more information (on Sales Day)
Executing
Account
Administration
Product Directory
Credit Administration
Sales
Product Fulfillment
Customer Accounts
Product Administration
Marketing Campaigns
Customer
Service
Document Management
Purchasing
General
Ledger
Collections
Branch/Store Operations

16. Business Components Define The Key Business Functions
Component Name
Account Administration
Resources: Account Data, CRM
People: Call Center, Customers
Technology: CICS Customer Account, SAP
SLA/KPIs: Time to Open Account
Description
Functional aspects of administration including account opening, account management, account closure
A business component is “a grouping of the people, technology, & resources delivering specific business value”
Components have well-defined interfaces, allowing them to interact smoothly with each other and to be 'snapped' in and out at will, like building blocks”
The Interfaces of the Business Components Enable Identification of Candidate Business Services
FROM:
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
Components allow for understanding interdependencies between parts of the business
The output of this process becomes the input for SOA design
Account Administration

17. SOMA (Service Oriented Modeling and Architecture) Identification, Specification, Realization and Implementation of Services, Components and Flows
SOMA is IBM's end to end SOA Solution development method
SOMA is an integral part of the Rational Unified Process
UML Profile for Software Services
RUP SOMA
SOMA has the following phases:
Service Identification
Service Specification
Service Realization
Identification
of Candidate Services and Flows
Specification
of Services, Components, and Flows
Realization
Decisions
SPEAKER NOTES – RUP/SOMA is key – identify in the notes as open source – part of overall movement – IBM Thought Leadership again – also indicate this is a METHODOLOGY versus a concept
The main three activities are service identification and specification, component identification and specification of its internal attributes, rules, methods, events, flow, messages and information model. The latter will collectively help realize services.
Service realization is the binding of a component and the services it provides to actual instances of implementation: this service will be realized through this newly developed EJB that we will expose as a web service; this other service’s operations will be realized through the wrappering of a set of the following CICS transactions after we have componentized the legacy system to be able to expose these CICS transactions and have separated out the COBOL copybooks.

18. Service Allocation to Components
SOMA (Service Oriented Modeling and Architecture) Identification, Specification, Realization and Implementation of Services, Components and Flows
SOMA is IBM's end to end SOA Solution development method
SOMA is an integral part of the Rational Unified Process
UML Profile for Software Services
RUP SOMA
SOMA has the following phases:
Service Identification
Service Specification
Service Realization
Domain
Decomposition
Goal-Service
Modeling
Existing Asset
Analysis
Subsystem
Analysis
Service
Specification
Message & Event
Component Flow
Service Flow
Component
Information
SPEAKER NOTES – RUP/SOMA is key – identify in the notes as open source – part of overall movement – IBM Thought Leadership again – also indicate this is a METHODOLOGY versus a concept
The main three activities are service identification and specification, component identification and specification of its internal attributes, rules, methods, events, flow, messages and information model. The latter will collectively help realize services.
Service realization is the binding of a component and the services it provides to actual instances of implementation: this service will be realized through this newly developed EJB that we will expose as a web service; this other service’s operations will be realized through the wrappering of a set of the following CICS transactions after we have componentized the legacy system to be able to expose these CICS transactions and have separated out the COBOL copybooks.
Realization
Decisions
Service Allocation to Components
Component
Layering
Technical
Feasibility
Exploration

19. Service Exposure Decisions Within Service Specification
Business Alignment:
Is the service business relevant?
Is funding available for service development and management?
Is the service sharable?
Composability
Is the service consistent with NFRs at the composite level?
Is service stateless?
Is the service self-contained? (Are there dependencies?)
Is the service technology neutral?
Externalized Service Description
Is there an externalized service description e.g. WSDL?
Can the service be discovered and bound via the service description?
Does the description contain meta-data about itself?
Redundancy Elimination
Can the service be applied to all processes where its function is required?
Candidate Services
Business Alignment
Composability
Externalized Service Description
Redundancy Elimination
Service Litmus Test
Services
(exposed)

20. Designing the SOA Service Model
<< Input from: Business Componentization/Analysis >>
Pre-modeling activities
Channel
B2B
Identification
of Candidate Services and Flows
Consumers
Service Consumer
Business Process
Composition; choreography;
business state machines
Services
atomic and composite
Specification
of Services, Components, and Flows
(Enterprise Service Bus)
Integration Infrastructure
Monitoring Infrastructure Services)
QoS Layer (Security, Management &
Information Architecture (meta-data) &
Business Intelligence
Governance (managing the service portfolio)
Service Components
Realization
Decisions
Service Provider
SOMA activities are grouped into three major steps: Identification, Specification and Realization decisions. At the heart of SOMA are identification and specification of services, service components and flows.
As many other architectural activities, SOMA activities are carried out iteratively.
The modules 2, 3, and 4 will provide detail for one of SOMA steps each.
Operational Systems
Packaged
Application
Custom
Application OO
Application
<< Output to: SOA Implementation >>

21. Business Process Management Within The SOA Lifecycle
Process Execution
Integrated deployment of business processes
Modeling and Simulation
Capture and optimize business models
Business Monitoring
Real-time visibility for coordinated action
Process Orchestration
Standards-based development environment
Main Point: BPM with SOA includes Software and Expertise. For Software, there are a core set of “table stakes” capabilities that customers should look for in a complete BPM solution. IBM goes on to differentiate our BPM software by incorporating the latest in Service Oriented Architecture (SOA) as a core part of our product design.
Using eight key BPM capabilities, or entry points, business leaders and process owners can directly control and manage the execution of business processes to improve business results and facilitate business innovation. These key capabilities are described below followed by a scenario using IBM’s “BPM with SOA” suite of products to demonstrate how these capabilities can be tied together to improve a business process.
Business Modeling and Simulation
The ability to deliver to business professionals a means to visualize their processes and accompanying decision points is the foundation of process management. A multilevel modeling environment supporting business and IT collaboration for process designs and business rules is required. Modeling the process flows immediately identifies bottlenecks, disconnects and inefficiencies. Process owners can quickly see areas for improvement, automation and opportunities for error cycle reduction. Process models can also be used as a universal communication tool for the business to document and describe the work for systems integrators, developers, trading partners, regulators and business process outsourcers.
Policies and Rules
Rules engines and associated management procedures govern business processes. As businesses strive to become more agile it becomes increasingly important for them to have the ability to change rules in real time. Rule changes are often aimed at the action portion of a process, an application or a system. However, rules can also be applied to watch for exceptions or significant variances in business or technical events or to indicate a need to tune a business model for expected or unexpected conditions. Rules engines can be “inference-based” -- identifying possible paths to a common outcome based on data/facts. Rules engines can also use “case-based” reasoning-- watching the decisions made by humans and suggesting rule extensions.
Collaborative Development
As part of process design and assembly clients need to utilize standards-based iDEs, ideally these are Eclipse based using Eclipse tooling and use J2EE and service oriented architecture standards. The ability to check out, develop, configure and test BPEL-based process models allows the development community to ultimately support process deployment effectively.
Process Execution/Automation (Workflow and Choreography)
Human tasks are an important element of a business process. Executing human-based process steps in conjunction with system-automated steps and information flows is required for most end-to-end business process management cases. Human workflow automation – the management of work items as they move from one person to another over a period of time -- and Human-to-system workflow automation – managing roles and tasks for routing, review and approval, are example capabilities. Human-intensive processes offer some of the most significant opportunities for error reduction and cost savings.
Content Management
In all business processes, information is either created or consumed as work progresses. Content is the primary object to be manipulated in a business process. Therefore participants in a process need the ability to create new content as well as the ability to access and leverage existing content. Having the right information at your fingertips at the right time is critical to process success.
Collaboration
Sharing the responsibility for completing business events and evolving processes to compete more effectively anywhere, at any time, is a strong and unstoppable trend. To facilitate teamwork, throughput and team creativity for changing rule processes and rules no matter what the geographic location of the participants, there is a need for collaboration features combined with ubiquitous computing. Making group collaborative interactions highly integrated within a broader business process can deliver significant productivity gains. Take, for example, negotiating a contract with a customer as part of a sales process: collecting critical information about the customer to better understand its position of strength; contacting colleagues across the organization to gain insights regarding where there is leeway and where to draw a line; and, if it’s an international negotiation, there are protocols that must be followed and tax laws and currency conversions that must be understood, all of which reside in rule repositories. The ability to seamlessly assemble all this information becomes an advantage in today’s competitive marketplace. This is an area of emerging use and need, and the inclusion of these features shows real vision for BPMS players.
Business Activity Monitoring
The ability to monitor process performance and detect events that may influence performance is a key ingredient for gaining control of business processes. Workers, managers, and executives alike want their own view of the progress of business events and business transactions while watching the effectiveness of their business model. Analyzing process efficiency and efficacy and aligning process improvement with enterprise goals and objectives involves using software agents (BAM technology) to listen for critical business events, correlating the event data and updating key performance indicators (KPIs). When these are combined with KPI-designed dashboards, operational managers can visually monitor and thus better manage the progress of individual work items in real time. This approach enables managers to intercept work where appropriate and alter the work item or the process flow to improve the desired result.
Analysis and Optimization
The ability to continuously evaluate process execution and results, applying analytical insight, trending, and predictive, action-based suggestions, to optimize the in-process model.

22. Developing Business Process Models
Enable business users to graphically model processes
Support documentation and training for the organization and external parties
Support simulation and analysis to substantiate process design decisions
Generate code artifacts to support IT implementation of processes
Graphically Model Processes
Define: Goal, Scope, Perspective, Audience, Level-of-detail, Content
Introduce naming conventions for all process objects (costs, time, resources, decision points, actions, etc)
Agree on a maximum number of process levels (3-4) and number of activities per process diagram (15-20)
Simulate and Analyze
Simulate execution with statistical analysis tools
Run "what if" scenarios to predict outcomes
Identify bottlenecks and workload imbalances
Isolate projects that will generate the greatest returns
Hand off to Implementation
Export business and data models for use in IT deployment
Direct export of models to IT such as WS-BPEL or XPDL for execution, XSD for data definitions, WSDL for services interfacing, UML for IT architect refinement
Main Point: WebSphere Business Modeler provides a Top-down approach to BPM Design.
Enhanced SOA lifecycle artifact management and re-use
Simplifies maintainability by enabling the reuse of existing artifacts
Artifacts from already deployed processes can be brought in to define subsequent design iterations of the business process
Ability to import and maintain fidelity of WSDLs and XSDs
Customers can associate existing service and data definitions to the business process and maintain those when they export to the WID tooling to jumpstart the implementation of a process built by a business user.
Improved business analysis report outputs
Export of reports in standard XML format
This allows customers to take all of our simulation and profile analysis reports in XML so that they can be consumed and used outside of the business modeler , this also helps customers who have multiple processes bring reports together to create consolidated reports
Allows report to be utilized by and incorporated into additional environment
The XML format can be used to bring reports into different environments, such as web publishing and additional reporting tools so that they
New and updated analysis reporting
Allows business analysts greater flexibility through higher level of aggregation of analysis data
Reports can be aggregated up to as many levels as need to allow users to see aggregated cost and time analysis reports for complex processes
Addition of key durations (process working and resource durations) to the analysis reports
Additional report customization capabilities
Ability to have global attributes for custom reports (names, logos, etc)
Ability to define header and footer masters for reports
Ability to format the data in the report to be able sort reports
Increased Business Analyst productivity
Enhanced simulation validation
The simulation validation now allows for improved validations of the required simulation inputs and reports on how to fix those errors to perform a simulation
Reduction of time to run simulations
With improved validations and some new implicit validation criteria the time to it takes from first creating a model with attributes to simulation is reduced allowing users to start doing simulations earlier in the creation cycle of a model
Improved interoperability between modeling and monitoring
Linkage of any business process model to Key Performance Indicators
Ability to associate KPIs and business metric to any business process or task regardless of where it is deployed and links to the new monitor toolkit as well as being able to bring in feedback from the WebSphere Business Monitor back into the business modeler for use as part of simulation and analysis in the Modeler
Architectural Benefit:
Support top-down approach to service and process design
Coordination of process development across business stakeholders as well as interaction with IT organization to articulate process design
Creation of artifacts to support process development and implementation

23. Building Process Solutions
Business Process Choreography orchestrates services as deployable processes
Integrate information and user interaction into process development and deployment
Mediations to transform/route service requests and responses
Enable inter and intra-enterprise (B2B) service integration
Business Process Choreography orchestrates services to form deployable processes:
Process model based on WS-BPEL
Choreography includes automated and human based services, business rules, service invocations and control of flow aspects
Processes support transactions and compensation
Modeling : BPEL Editor (Flow based) and Business State Machine Editor (Event based)
Architectural Benefit:
Simplified, standards-based business process development
Support for industry process and data models
Invoke mediations for routing/transforming requests between services

24. Monitoring Business Process Solutions
Assemble dashboards on process behavior for different views/user perspectives
Generate business event triggers and notifications via , pager, SMS messages based on process events
Generate preprogrammed responses based on process behavior
Analyze process metrics over time to identify process trends
Assemble dashboards from different views
Views include Monitor, Report, Dimensional, KPI, Scorecard, Gauge, Alert, and Organizational
Combine standard and custom portlets to meet various business needs
Enable business event triggers and notifications via , pager, SMS messages
Intervene based on business events and trends as they emerge by redirecting workload or changing process flows based on real needs
Generate preprogrammed responses
Automatic corrective action based on pre-defined business triggers leveraging BPEL process and Web Service
Analyze business metrics over time to identify trends
Discover previously hidden patterns using dimensional analysis
Use analytics and business intelligence technologies
Populate a business performance warehouse
Main Point: The ability to manage BPM is a key area and it involves more than just monitoring a process.
Create visible UI components like monitors, KPI, SLAs and other artifacts relevant to business to increase business visibility and use them effectively to manage your enterprise from internal and external changes that can take place. These visual elements increase the visibility and reduce the latency in decision making to improve the efficiency and productivity of the organization.
Business Activity Monitoring capability
Increased scope of activities and applications that can be monitored
Customers can now create complete business processes and deploy to multiple environments and are not just limited to the WebSphere Process Server
Ability to monitor additional environments
Increases the scope of activities and applications that can be monitored by the business analyst by providing the ability to monitor additional environments that generate common base events. These environments include IBM products and non-IBM products that have CBE (Common Base Event) emitters
Availability of a custom event emitter toolkit
Customers, ISV’s, SI’s can start to create custom event emitters using this new toolkit to enable events in the CBE format to be generated by there applications and then consumed by the business monitor
Monitoring Extensibility
Improved business insight and flexibility
Customers can now monitor end to end processes as well as allow them to react to business situations that can occur at any point regardless of which IBM or non IBM technology the process is deployed
Ability to define monitoring models that have input from various sources including WebSphere Business Monitor, WebSphere Integration Developer and custom sources
The Monitor Model Perspective allows users to import the following
Business Measure definitions from the WebSphere Business Modeler
BPEL Process Definitions from WID
Custom event definitions from their custom event emitters
Improved administration and testing environment
Unit test environment
This allows users to test monitoring models prior to deployment to ensure they are syntactically correct
Guided administration
Administration guides users through previously manual steps
Command Line Interfaces
To allow for automation for common development and deployment tasks in order to avoid human errors
Improved performance and scalability with support for WAS ND
Allows for monitoring in a highly scalable and highly available environment.
Updated dashboards and dashboard frameworks
Enhanced KPI management dashboard
Both historical and real time Key Performance Indicators are managed through the performance warehouse and can be used to perform dimensional analysis right in the dashboards in real time
Custom dashboards
Availability of an SDK to allow users to build custom dashboards directly against the performance warehouse
Architectural Benefit:
Monitoring links to KPIs and Metrics defined by business analysts
Integrates processes as part of an event-driven infrastructure
Analyze trends in the business to enable ongoing optimization of solutions

25. Composite Business Services Business Services Provide the “Building Blocks”
Composite Business Services definition:
A collection of integrated and related business services that provide a specific business solution and support business processes built on SOA
Business Services definition:
A business function whose execution can be adapted at runtime based on business policy and user context
Designed at business level to represent a discrete business function (e.g. check credit, open account)
Can provide flexible, adaptable behavior based on business policy and user context
Provisioned through multiple communication channels
Simplify text, do a build
=============
NOTE: encapsulates Composite and Atomic Services
Designed at business level to represent a discrete business function (e.g. check credit, open account)
Can provide flexible, adaptable behavior based on business policy and user context
Derived from disparate IT resources (e.g. legacy systems, custom applications, ISV systems, third party services)
Built using Web service and industry standards (e.g. WS-I, SWIFT, eTOM, MISMO, ACORD, HIPAA, HL7)
Provisioned through multiple communication channels (e.g. Web, B2B, IVR)
Can be combined to create loosely coupled applications and processes

26. Composite Business Services
Applications
Composite
Business
Services
User Experience/ Business Process
Middleware

27. Agenda SOA Business Architecture Considerations
SOA Business Architecture Best Practices
IBM Capabilities to Support SOA Business Architecture
Summary

28. IBM Products to Support SOA Business Architecture
Rational Unified Process for SOMA
Rational Method Composer
Rational Software Architect
WebSphere Business Modeler
WebSphere Integration Developer
WebSphere Business Services Fabric
WebSphere Business Monitor
WebSphere
Portal Server
WebSphere
Process Server
WebSphere Process Server
WebSphere Portal
Interaction Services
Information Services
Partner Services
Business App Services
Access Services
Development Services
Management Services
Infrastructure Services
Enables collaboration between people, processes & information
Manages diverse data and content in a unified manner
Connect with trading partners
Build on a robust, scaleable, and secure services environment
Facilitate interactions with existing information and application assets
Integrated environment for design and creation of solution assets
Manage and secure services, applications & resources
Optimizes throughput, availability and utilization
Apps &
Info Assets
Process Services
Business Services
Supports enterprise business process and goals through businesses functional service
Enterprise Service Bus
Orchestrate and automate business processes
**Main point: The SOA reference architecture is a vendor-neutral way of looking at and planning the set of services that go into building an SOA.
The SOA reference architecture is a way of looking at the set of services that go into building an SOA. This architecture is not unique to IBM; these are things that you need to consider when approaching SOA regardless of what products and services are used. These capabilities can be implemented on a build-as-you-go basis allowing capabilities and project level solutions to be easily added as new requirements are addressed over time. You can see that these services organized along the same lifecycle we’ve discussed. On the left in is Development Services which is model and assemble, in the middle are the elements of the deployment run-time environment you use and on the right is management. The backbone of the reference architecture is the enterprise service bus which facilitates communication between services. The reference architecture is a great tool for laying out roadmaps for pursuing SOA. Regardless of what kind of project you’re undertaking, it makes sense to lay it out on a reference architecture to see how the various services you’re designing are going to interact with each other
Additional detail:
The SOA Reference Architecture outlines the key capabilities that are required for comprehensive, enterprise wide SOA solutions. These capabilities can be implemented on a build-as-you-go basis allowing capabilities and project level solutions to be easily added as new requirements are addressed over time.
Tools are an essential component of any comprehensive integration architecture. The SOA Architecture includes both Development Services which are used to implement custom artifacts that leverage the infrastructure capabilities, and Business Innovation & Optimization Services which are used to monitor and manage the runtime implementations at both the IT and business process levels.
At the core of the SOA Reference Architecture is the Enterprise Service Bus. This delivers all of the inter-connectivity capabilities required to leverage the services implemented across the entire architecture. Transport services, event services, and mediation services are all provided through the ESB.
The SOA Reference Architecture also contains a set of services that are oriented toward the integration of people, processes, and information:
Interaction Services provide the capabilities required to deliver IT functions and data to end users, meeting the end-user's specific usage preferences.
Process Services provide the control services required to manage the flow and interactions of multiple services in ways that implement business processes.
Information Services provide the capabilities required to federate, replicate, and transform data sources that may be implemented in a variety of ways.
Many of the services in an SOA are provided through existing applications; others are provided in newly implemented components; and others are provided through external connections to third party systems.
Existing enterprise applications and enterprise data are accessible from the ESB through a set of Access Services that provide the bridging capabilities between legacy applications, pre-packaged applications, enterprise data stores and the ESB.
The SOA Reference Architecture also contains a set of Partner Services that provide the document, protocol, and partner management capabilities required for business processes that involve inter-actions with outside partners and suppliers.
Business Application Services provide runtime services required for new application components to be included in the integrated system.
Underlying all these capabilities of the SOA Reference Architecture is a set of Infrastructure Services which are used to optimize throughput, availability and performance.
IT Services Management Services include capabilities that relate to scale and performance, for example edge services, clustering services, and virtualization capabilities allow efficient use of computing resources based on load patterns.
The SOA Reference Architecture is a complete and comprehensive architecture that covers all the integration needs of an enterprise. Its services are well integrated and are delivered in a modular way, allowing SOA implementations to start at a small project level. As each additional project is addressed, new functions can be easily added, incrementally enhancing the scope of integration across the enterprise.
Background:
The IBM SOA Foundation delivers the capabilities you need to adopt SOA through a comprehensive architecture. These capabilities can be implemented on a build-as-you-go basis, and yet, because of the architecture and its service orientation, capabilities and project level solutions can be easily added as new requirements are addressed over time.
The SOA Reference Architecture shows the key capabilities that are required for comprehensive, enterprise wide SOA solutions.
Development Services are an essential component of any comprehensive integration architecture. The SOA Architecture includes development tools, used to implement custom artifacts that leverage the infrastructure capabilities, and business performance management tools, used to monitor and manage the runtime implementations at both the IT and business process levels. Development tools allow people to efficiently complete specific tasks and create specific output based on their skills, their expertise, and their role within the enterprise. Business Analysts who analyze business process requirements need modeling tools that allow business processes to be charted and simulated. Software Architects need tool perspectives that allow them to model data, functional flows, system interactions, etc. Integration Specialists require capabilities that allow them to configure specific inter-connections in the integration solution. Programmers need tools that allow them to develop new business logic with little concern for the underlying platform. Yet, while it is important for each person to have a specific set of tool functions based on their role in the enterprise, the tooling environment must provide a framework that promotes joint development, asset management and deep collaboration among all these people. A common repository and functions common across all the developer perspectives (e.g. version control functions, project management functions, etc) are provided in the SOA Reference Architecture through a unified development platform.
The Business Innovation & Optimization Services incorporate monitoring capabilities that aggregate operational and process metrics in order to efficiently manage systems and processes. Managing these systems requires a set of capabilities that span the needs of IT operations professionals and business analysts who manage the business operations of the enterprise. These capabilities are delivered through a set of comprehensive services that collect and present both IT and process-level data, allowing business dashboards, administrative dashboards, and other IT level displays to be used to manage system resources and business processes. Through these displays and services, it is possible for LOB and IT personnel to collaborate to determine, for example, what business process paths may not be performing at maximum efficiency, the impact of system problems on specific processes, or the relationship of system performance to business process performance. This collaboration allows IT personnel and assets to be tied more directly to the business success of the enterprise than they traditionally have been.
One key feature of the SOA Reference Architecture is the linkage between the Development and the Business Innovation & Optimization Services. The ability to deliver runtime data and statistics into the development environment allows analyses to be completed that drive iterative process re-engineering through a continuous business process improvement cycle.
At the core of the SOA Reference Architecture is the Enterprise Service Bus. This architectural construct delivers all the inter-connectivity capabilities required to leverage and use services implemented across the entire architecture. Transport services, event services, and mediation services are all provided through the ESB. Transport services provide the fundamental connection layer; event services allow the system to respond to specific stimuli that are part of a business process; and mediation services allow loose-coupling between interacting services in the system. The ESB is a key factor in enabling the service orientation of the SOA Reference Architecture to be leveraged in implementing service oriented solutions and can be implemented today to meet the quality of service requirements of any integration solution.
The SOA Reference Architecture also contains a set of services that are oriented toward the integration of people, processes, and information. These services control the flow of interactions and data among people and automated application services in ways appropriate to the realization of a business process:
- Interaction Services provide the capabilities required to deliver IT functions and data to end users, meeting the end-user's specific usage preferences.
- Process Services provide the control services required to manage the flow and interactions of multiple services in ways that implement business processes.
- Information Services provide the capabilities required to federate, replicate, and transform data sources that may be implemented in a variety of ways.
Automated application services, implementations of business logic in automated systems, are a critical part of any integration architecture or solution. Many of these services are provided through existing applications; others are provided in newly implemented components; and others are provided through external connections to third party systems. Existing enterprise applications and enterprise data are accessible from the ESB through a set of access services. These Access Services provide the bridging capabilities between legacy applications, pre-packaged applications, enterprise data stores (including relational, hierarchical and nontraditional, unstructured sources such as XML and Text), etc and the ESB. Using a consistent approach, these access services expose the data and functions of the existing enterprise applications, allowing them to be fully re-used and incorporated into functional flows that represent business processes. Existing enterprise applications and data leverage the Business Application and Data Services of their operating environments such as CICS, IMS, DB2, etc. As these applications and data implementations evolve to become more flexible participants in business processes, enhanced capabilities of their underlying operating environments, for example support of emerging standards, can be fully utilized.
The SOA Reference Architecture also contains a set of Business Application Services that provide runtime services required for new application components to be included in the integrated system. These application components provide new business logic required to adapt existing business processes to meet changing competitive and customer demands of the enterprise. Design and implementation of new business logic components for integration enables them to be fully re-useable, allowing them to participate in new and updated business processes over time. The Business Application Services include functions important to the traditional programmer for building maintainable, flexible, and re-useable business logic components.
In many enterprise scenarios, business processes involve inter-actions with outside partners and suppliers. Integrating the systems of the partners and suppliers with those of the enterprise improves efficiency of the overall value chain. Partner Services provide the document, protocol, and partner management services required for efficient implementation of business-to-business processes and inter-actions.
Underlying all these capabilities of the SOA Reference Architecture is a set of Infrastructure Services which provide security, directory, IT system management, and virtualization functions. The security and directory services include functions involving authentication and authorizations required for implementing, for example, single sign-on capabilities across a distributed and heterogeneous system.
IT Services Management Services include functions that relate to scale and performance, for example edge services and clustering services, and the virtualization capabilities allow efficient use of computing resources based on load patterns, etc. The ability to leverage grids and grid computing are also included in infrastructural services.
While many of the Infrastructure and IT Service Management services perform functions tied directly to hardware or system implementations, others provide functions that interact directly with integration services provided in other elements of the architecture through the ESB. These interactions typically involve services related to security, directory, and I/T operational systems management.
The SOA Reference Architecture is a complete and comprehensive architecture that covers all the integration needs of an enterprise. Its services are well integrated and are delivered in a modular way, allowing SOA implementations to start at a small project level. As each additional project is addressed, new functions can be easily added, incrementally enhancing the scope of integration across the enterprise. In addition to supporting SOA strategies and solutions, the architecture itself is designed using principles of service orientation and function isolation.

29. IBM SOA Service Offerings Focused on SOA Business Architecture
SOA Strategy
How do I get started in SOA?
SOA Diagnostic
I’ve started with SOA, how am I doing? What can I do better?
SOA Implementation Planning
There is a specific Business Area I want to improve using SOA – how should I approach it?
Business Process Management (BPM) Enabled by SOA
How can I leverage SOA to implement and improve business processes that meet my performance objectives, make better use of IT resources and give me a competitive edge?
SOA Design, Development and Integration Services
I’ve done the preliminary planning work, now I’m ready to develop and sustain SOA solutions
SOA Management
I’ve implemented SOA-based solutions, how can I manage them effectively to ensure ongoing benefit realization?
SOA Strategy
Helps the C-level executives lay out a business blueprint, complete with an SOA strategy, architecture and governance roadmap to guide the transformation of the organization and its systems to a service-oriented model using component-based business models
SOA Diagnostic
Helps an organization assess its current state in service orientation, integration and business process management to evaluate how it’s doing and make recommendations for corrective action, if warranted
SOA Implementation Planning
Helps a line of business develop a robust implementation plan that includes a high-level solution architecture review and the definition of scope in terms of process, service and governance to successfully realize a SOA solution
Business Process Management (BPM) Enabled by SOA
Helps businesses plan, design, model, simulate, measure and optimize core processes across the organization to achieve maximum operational effectiveness in a SOA environment
SOA Design, Development, and Integration Services
Helps an organization design, build and integrate the targeted SOA application and infrastructure
SOA Management Services
Helps an organization establish the management framework and supporting infrastructure to sustain the SOA environment, helping to ensure ongoing value and benefits realization

30. The Service Offering Lifecycle Spanning the Full SOA Continuum
End-to-End Lifecycle
Ongoing Maintenance and Optimization
Process and System Change
Strategy and Planning
BPM Enabled by SOA Services
SOA Diagnostic
SOA Management Services
Typical client entry points
Typical client entry point
SOA Strategy
SOA Design, Development and Integration Services
SOA Implementation Planning

31. Summary Designing SOA with a Business Focus requires:
Linking Business and IT – normally through an Enterprise Architecture
Applying discipline and rigor to SOA Design
Business Process Management to design and implement business relevant services
Best practices for designing SOA based on a business focus implies:
Decomposing the Enterprise into Business Components to design business-relevant service architectures
Use of SOMA to ensure an optimized service design for the enterprise
Application of tools and techniques to support business process modeling, assembly and deployment, and business process monitoring
Development and refinement of SOA Governance to enable a service lifecycle development approach and ensure business/IT linkage for SOA

32. Thank You Gracias Danke Obrigado Merci Multumesc Grazie Thai Hindi
Traditional Chinese
Russian
Spanish
Obrigado
Thank You
Portuguese
Arabic
Danke
Grazie
Merci
Italian
German
French
Multumesc
Simplified Chinese
Romanian
Korean
Japanese