IBM WebSphere Developer Technical Journal: Developing adaptive composite business services using WebSphere Business Services Fabric, Part 1

Introducing IBM's new platform for business service modeling, assembly, and deployment

This series of articles discusses the end-to-end process of creating composite business services with IBM® WebSphere® Business Services Fabric Version 6.0. Part 1 introduces the idea of composite business services, and how WebSphere Business Services Fabric supports the development of these services.

Libra Huang (librah@tw.ibm.com), IT Architect, IBM India Software Lab Services and Solutions

Author photoLibra Huang is an IT Architect with SOA Solution Center (SSC), IBM Software Group. His background is in J2EE and is now heavily involved with Composite Business Services (CBS) assets development for banking industry.



Hicks Lin (zhlin@tw.ibm.com), Software Engineer, IBM

Hicks LinHicks Lin is a developer from IBM China Software Development Lab in Taipei. He is currently developing Composite Business Service (CBS) applications for banking industry. He is interested in SOA, J2EE and other emerging server-side technologies.



Jimmy Tan (jimmytan@tw.ibm.com), Staff Software Engineer, IBM India Software Lab Services and Solutions

Author photoJimmy Tan is a senior developer from SOA Solution Center, IBM Software Group. He is developing Composite Business Service (CBS) for banking industry. He is interested in SOA, J2EE and software architecture.



Daniel Wu (danielwu@tw.ibm.com), Staff Software Engineer, IBM India Software Lab Services and Solutions

Daniel WuDaniel Wu is working at IBM Software Group as a software engineer in developing Composite Business Service (CBS) application for banking industry.



Frank Wong (zhwong@tw.ibm.com), Staff Software Engineer, IBM India Software Lab Services and Solutions

Author photoFrank Wong is a software engineer from IBM China Software Development Lab, Taipei. He is currently developing Composite Business Services (CBS) as the banking industry's solution accelerators.



04 April 2007

Also available in Chinese Russian Japanese

From the IBM WebSphere Developer Technical Journal.

Introduction

With Service-Oriented Architecture (SOA), a business can be visualized as a collection of loosely coupled reusable building blocks, called business services. A business service, which can be derived from freestanding components, derived from disparate legacy IT assets (such as legacy systems, packaged applications, custom applications, and so on), or provided by a third-party, provides a discrete business function (for example, check credit, open account, and so on) whose behavior can be adapted at run time based on the business context.

A composite business service (CBS) is a collection of business services that work together, along with a client’s existing applications, to provide a specific business solution. An enterprise can flexibly wire composite business services, user interfaces, and data services in innovative ways to create new composite business applications (aka service-oriented business applications, coined by Gartner, Inc.) to support business needs.

Figure 1 shows the conceptual layers of an SOA-based solution. At the bottom are existing enterprise and third party systems exposed as Web services: service interfaces defined using WSDL and messages encapsulated as SOAP documents. These IT services are then assembled into business services to automate or support a specific business function. A set of business services combined together represent a business solution: a CBS. At the top of the layer are the subscribers that consume the CBS, and who can be internal or external to the enterprise.

Figure 1. SOA layered architecture
Figure 1. SOA layered architecture

IBM envisions companies publishing standards-based service components and composite business services that customers and business partners can discover and use in their own business processes. Companies can build on each other’s services, creating new loosely coupled, process- and industry-centric business service ecosystems. The complexity, cost, and risk associated with traditional, large-scale enterprise software projects is hence significantly reduced.


What is WebSphere Business Services Fabric?

WebSphere Business Services Fabric is the platform to model, assemble, deploy, manage, and govern business services, and is packaged as follows:

  • IBM Business Services Tool Pack (hereafter called Tool Pack)

    The Tool Pack includes:

    • WebSphere Integration Developer, which enables you to assemble and integrate composite services.

    • Business Services Composition Studio (hereafter called Composition Studio) is a plug-in to WebSphere Integration Developer that lets you assemble business services, create business policies, and simulate dynamic assembly of business services.

  • IBM Business Services Foundation Pack (hereafter called Foundation Pack)

    The Foundation Pack is built on top of WebSphere Process Server (which is included) and provides the integrated run time and management-time environment for business services. The Foundation Pack is made up of five modules:

    • Business Services Repository is a standards-based business service model repository that captures information about business services, business policies, and service subscribers. This module supports discovery and federation of data from WebSphere Service Registry and Repository and Lightweight Directory Access Protocol (LDAP) systems.

    • Business Services Performance Manager is a Web-based console that provides visibility and monitoring of business services-based solutions. This module includes a set of reports that enables administrators to monitor the behavior and performance of their business services.

    • Business Services Subscriber Manager is a Web-based console that manages business service entitlements using an organizational enrollment and subscription model.

    • Business Services Dynamic Assembler is a highly scalable run time engine that selects the best service provider based on the operating context of a request.

    • Business Services Governance Manager is a Web-based console that provides lifecycle management of business services meta data. This module enables you to:

      • Control access and visibility to business service models and policies within the Business Services Repository.
      • Enforce consistency and coherency of business service model within the Business Services Repository.
      • Govern the changes to business service model in the Business Services Repository.
      • Migrate business service models between instances of the Business Services Repository.
  • Industry Content Packs (Optional)

    WebSphere Business Services Fabric provides optional Industry Content Packs that include industry-specific extensions and pre-built industry-common services to reduce your effort in creating industry-specific SOA solutions. Currently, two Industry Content Packs are available:

    • IBM Insurance Property and Casualty Pack

    • IBM Healthcare Payer Pack


Composite business services development lifecycle

How do the components above work together to support adaptive composite business services? Figure 2 shows the steps for creating composite business services using these components and related IBM products.

Figure 2. Composite business services development lifecycle
Figure 2. Composite business services development lifecycle

Let's walk through the steps:

  1. Use WebSphere Business Modeler to enumerate the roles, activities, high-level input/output, decision flow, and business measures that satisfy your requirements.

  2. Analyze the requirements and business process models to create a conceptual design for the solution, including service interface design in IBM Rational® Software Architect, and logical data model in IBM Rational Data Architect.

    If an applicable industry model is available, you should try to leverage it to facilitate the tasks described above. For example, IBM Information FrameWork provides a banking industry model which comprehends banking data and process definitions. Building with the available industry model eliminates the effort of rebuilding the cornerstone.

  3. Define WebSphere Business Services Fabric extensions (ontologies) based on the requirements, business process model, and industry model (if any). WebSphere Business Services Fabric extensions are then deployed into the Business Services Repository.

  4. Develop executable business processes, service components, and modules using the business integration, Java™ EE, and Web service tooling in WebSphere Integration Developer. Optionally, some of these components can be developed using IBM Rational Application Developer.

  5. Use Composition Studio to define the business service meta data and submit it to the Business Services Governance Manager for approval.

  6. Business service meta-data definitions will be reviewed by stakeholders in Business Services Governance Manager and published to the Business Services Repository.

  7. Define subscribers' entitlement to the created business services in Business Services Subscriber Manager. The entitlement information is stored in the Business Services Repository.

  8. Deploy the service components and executable processes into WebSphere Process Server.

  9. WebSphere Process Server executes the business processes with the optimal services instances selected by Business Services Dynamic Assembler, based on the business context and meta data in the Business Services Repository.

  10. The execution record is sent to the Business Services Performance Manager for capturing and future analysis.


Conclusion

Part 1 of this series provided some background and a brief overview of what IBM WebSphere Business Service Fabric is, what composite business services are, and what their development lifecycle looks like. In next installment, we will depict a business case, then perform the analysis to define the business services and associated service meta data Subsequent installments of this series will offer detailed steps to guide you through the creation of your first adaptive composite business service using the WebSphere Business Service Fabric platform.


More in this series

Resources

Comments

developerWorks: Sign in

Required fields are indicated with an asterisk (*).


Need an IBM ID?
Forgot your IBM ID?


Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.

 


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name



The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.

 


All information submitted is secure.

Dig deeper into Business process management on developerWorks


static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Business process management, WebSphere, SOA and web services, Architecture
ArticleID=206293
ArticleTitle=IBM WebSphere Developer Technical Journal: Developing adaptive composite business services using WebSphere Business Services Fabric, Part 1
publish-date=04042007