WebSphere IBM Product Lifecycle Management Content Pack for IBM WebSphere Business Services Fabric version 6.2. Reference Architecture Guide

Transcription

1 WebSphere IBM Product Lifecycle Management Content Pack for IBM WebSphere Business Services Fabric version 6.2 Reference Architecture Guide

2 Note Before using this information and the product it supports, read the information in Notices at the end of this book. Permissions for the use of these publications are granted subject to the following terms and conditions. Personal Use: You may reproduce these publications for your personal, non-commercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative work of these publications, or any portion thereof, without the express consent of IBM. Commercial Use: You may reproduce, distribute and display these publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these publications, or reproduce, distribute or display these publications or any portion thereof outside your enterprise, without the express consent of IBM. Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the publications or any information, data, software or other intellectual property contained therein. IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the publications is detrimental to its interest or, as determined by IBM, the above instructions are not being properly followed. You may not download, export or re-export this information except in full compliance with all applicable laws and regulations, including all United States export laws and regulations. IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED AS-IS AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

3 Contents Preface v Chapter 1. Industry Content Pack overview WebSphere Business Services Fabric Industry Content Packs Available Industry Content Packs Chapter 2. Industry Content Pack Reference Architecture Framework of components in the Industry Content Packs Industry Capability and Process Maps Industry Business Service Templates Industry Service Interfaces Industry Business Glossary Industry Common Services Industry Business Object Model Knowledge assets Chapter 3. Product Lifecycle Management Content Pack Reference Architecture Assets packaged in the Product Lifecycle Management Content Pack Product Lifecycle Management Content Pack logical view Product Lifecycle Management Content Pack component model Product Lifecycle Management Content Pack deployment view Chapter 4. Industry Content Pack alignment with the IBM SOA Reference Architecture Chapter 5. Industry Content Pack alignment with the IBM SOA lifecycle methodology Model Assemble Deploy Notices and Trademarks Copyright IBM Corp iii

4 iv IBM Product Lifecycle Management Content Pack for IBM WebSphere Business Services Fabric version 6.2: Reference Architecture Guide

5 Preface About this guide This guide describes the reference architecture of the IBM Product Lifecycle Management Content Pack for the WebSphere Business Services Fabric. It provides a detailed explanation of its various components of the Product Lifecycle Management Content Pack, their inter-relationships, and the architectural framework that it is built on. This document does not cover: v Design/Architecture concepts of IBM WebSphere Process Server v Design/Architecture concepts of IBM WebSphere Integration Developer v Design/Architecture concepts of IBM WebSphere Business Services Fabric v Design/Architecture concepts of IBM Rational Software Architect For details on the architectural concepts of these platforms, see the relevant technical documentation. Audience The document intends to guide SOA architects at customer and partner organizations to understand the framework of components as part of the Product Lifecycle Management Content Pack. It is assumed that the reader is acquainted with the prerequisite software (IBM WebSphere Business Services Fabric bundle that includes the IBM WebSphere Integration Developer and the IBM WebSphere Process Server) and recommended software (the IBM Rational Software Architect) that serve as platform or tooling for the Industry Content Packs. Organization This document is organized as follows: v Chapter 1: Industry Content Packs Overview Provides overview of industry content packs, the various assets that help jump start deployment of the industry-specific Service Oriented Business Solutions, and the available industry content packs. v Chapter 2: Industry Content Packs Reference Architecture Provides the details about the framework of components, as part of the industry content packs, along with logical, component, and deployment views. v Chapter 3: Product Lifecycle Management Content Pack Reference Architecture Provides the detailed explanation on various components of the Product Lifecycle Management Content Pack aligned with the reference architecture. v Chapter 4: Industry Content Pack alignment with IBM SOA Reference Architecture Provides an explanation on the reference architecture of the Industry Content Pack aligned with the IBM SOA Reference Architecture. v Chapter 5: Industry Content Pack alignment with IBM SOA Lifecycle Methodology Copyright IBM Corp v

6 Provides an explanation on how the reference architecture of the Industry Content Pack aligned with the IBM SOA Lifecycle Methodology from a tooling perspective. Related documents In addition to this document, see the following documentation to install, work, and extend the Product Lifecycle Management Content Pack: v Product Lifecycle Management Content Pack version 6.2 Installation Guide v Product Lifecycle Management Content Pack version 6.2 Developers Guide v Product Lifecycle Management Content Pack version 6.2 How-To Guide See the following documentation to comprehend how to work with the IBM WebSphere Business Services Fabric: v IBM WebSphere Business Services Fabric version 6.2 documentation v IBM WebSphere Integration Developer version 6.2 documentation v IBM WebSphere Process Server version 6.2 documentation v IBM Rational Software Architect version 7.0 documentation vi IBM Product Lifecycle Management Content Pack for IBM WebSphere Business Services Fabric version 6.2: Reference Architecture Guide

7 Chapter 1. Industry Content Pack overview This section is an overview of the Industry Content Packs. WebSphere Business Services Fabric Across enterprises, there has been a strong momentum for deploying composite applications, while avoiding rip and replace of existing assets. Business Process Management (BPM) and Services Oriented Architecture (SOA) are the primary themes underlying most of these enterprise initiatives. However, there are pains associated with deployment of composite applications. Learn how WebSphere Industry Content Packs can jumpstart the delivery of service-oriented applications, and ensure consistency and reuse across their IT ecosystem. Current State of Enterprise IT Ecosystem Large and mid-size enterprises have invested billions and millions of dollars during the last decade to automate their business processes. These investments have focused on a variety of business applications, ranging from core transaction processing to CRM. With the advancements in telecommunication infrastructure, it has also been possible for an enterprise to connect with a diverse set of stakeholders in its ecosystems- be it customers, distributors, or suppliers. Enterprises have strived to use this new interconnected world to drive down operational costs, increase efficiencies, and provide faster response to various stakeholders. However, it has not been an easy task. In the quest to automate most parts of business processes, enterprises created a huge stockpile of information assets serving unique needs. These assets served extremely unique audiences lines of businesses, processes, services, roles, geographies, modes of access, and so on. This has led to the creation of what is called as an IT Hairball in the enterprise ecosystem. This IT Hairball has also lead to maintenance challenges that are typically rooted in automation that has been built in a myriad of many-to-many connections throughout the organization s backend systems. The proliferation of support requirements and many existing embedded systems produces rigid processes and thus, incremental changes are difficult. IBM 2007, 2008 IBM

8 Business Pressures: Launch new and innovative products Shorter change cycles Customized products for niche markets Partner Employees Customers 100s of applications 1000s of databases Multiple Lines of Business Suppliers Channels 10,000s of users Millions of manual touches 3rd Party Service Providers IT Constraints: Complex processes and systems Proprietary applications and interfaces IT budget priorities on maintenance, not new investments Figure 1. Current State of Enterprise IT Ecosystem Business climate has also undergone a dramatic change during the last decade. The business pressures are the same but the speed at which results are expected has rapidly increased- be it launch of new and innovative products, customized offerings for niche markets, or even shortening the change cycles. This means that the rate at which business processes need to change now is much higher thus pressurizing the operational side of the business to be highly agile and dynamic. IT has become the core component of business operations and therefore it is expected to meet these business challenges despite complex processes and systems. IT also faces proprietary applications issue thus making it difficult to interoperate across the ecosystem. Also, more than 50% of the budgets are devoted to maintenance costs thereby stifling innovation. It is in this context that enterprises have found composite business applications to be the enabler of both flexibility and responsiveness to use their IT investments better. To maximize business agility and rather than trying to implement broad processes using an individual application, business leaders today want to assemble flexible, modular, prebuilt components together to create a more dynamic of IT support. Composite Business Applications bring this vision into reality. IBM provides a strong technology platform to support assembly of Composite Business Applications that are designed to support a wide range of industry and technical standards. SOA and BPM are key principles and methodologies behind IBM technology platform for Composite Business Applications. SOA is a business-driven IT architectural approach that supports integrating the business as linked, repeatable business tasks, or services. BPM is a discipline combining software capabilities and business expertise to accelerate process improvement and facilitate business innovation. To gain additional benefit and value from SOA, enterprises are combining the principles of BPM with the flexibility provided by SOA to move their levels of innovation and operational excellence higher. The foundation components of Composite Business Applications are composed of modeling and simulation, business activity monitoring, rules and process execution, content-centric processing, and prebuilt industry accelerators. 2 IBM Product Lifecycle Management Content Pack for IBM WebSphere Business Services Fabric version 6.2: Reference Architecture Guide

9 Many of the organizations that have adopted SOA and BPM together are maximizing those investments by aligning their business intent and IT execution through the use of dynamic business services, which can be delivered across multiple constituents, channels, and service levels. Need for Industry Accelerators In a Composite Business Application project, operational capabilities are exposed and abstracted from many different IT assets into units of different functions called services. These assets can be reused across the enterprise, increasing the deployment speed of IT solutions and reducing IT maintenance costs. However, enterprises embarking on development of Composite Business Applications face the following issues: v Lack of a consistent framework to build SOA applications that can be easily extended to meet changing business needs. v In the absence of a framework, duplicate assets tend to evolve within an organization for multiple products, processes, channels, roles, and geographies. v Long analysis-and-design cycles spent in industry-specific tasks such as business decomposition and service specifications. v Higher development costs, risks, and time when new composite business applications are developed from scratch. v Leads to rip-and-replace of existing applications because of proprietary domain models and interfaces. v Never-ending custom integration and higher maintenance costs similar to monolithic or custom applications that use proprietary definitions. Industry accelerators that are pre-tested and pre-certified on SOA and BPM technology platforms are positioned to fill this gap. Industry accelerators provide a set of patterns, models, and code assets that help jumpstart the delivery of Composite Business Applications throughout their life cycle Model, Assemble, Deploy, and Manage. The industry accelerators are not end-applications that can be deployed off-the-shelf to solve a specific business problem. Rather, these are prebuilt assets that can be reused for multiple lines of businesses, geographies, processes, and services in a given industry vertical or its subset. The industry accelerators do not have their own unique definitions but the assets are derived from industry standards and use technical standards to ensure interoperability. The reason for having the industry accelerators pre-tested and pre-certified on BPM and SOA technology platforms is to enable consumable and ready-to-use assets in the required Composite Business Applications. To ensure consistency and reuse, enterprises are looking at use of industry standard, however, there are several steps and complex efforts needed to make the industry standards consumable. Industry accelerators solve this problem and make industry standards consumable on the top of SOA and BPM technology platforms. Chapter 1. Industry Content Pack overview 3

10 Composite Business Applications Industry Accelerators BPM and SOA Technology Platforms Figure 2. SOA and BPM technology platforms The Industry accelerators also bring in the required discipline for consistency across multiple projects with a common architecture and methodology. The industry accelerator architecture and methodology helps make it easy to make changes to these Composite Business Applications, if there is a business demand. This also ensures governance across the life cycle of Composite Business Applications. The common architecture and methodology also makes it possible for the assets within the industry accelerators to be configurable and extensible based on unique business process needs of enterprises. Some key characteristics required in these industry accelerators are as follows. Providing a governing architecture to interoperate methods, tools, and assets. This is based on BPM and SOA methodology For example, Model, Assemble, Deploy, Manage, and Govern. Providing prebuilt SOA assets that are primarily derived from subsets of industry standards and industry best practices. These should not define their own unique standards. Initiating delivery of composite business applications across an entire industry segment. These are not prebuilt applications that are ready to be deployed. Extending and configuring to support unique customer needs. Enterprises (and their business partners) should be able to add their own content or extend the content provided in these accelerators to suit unique business needs. Using the industry accelerator approach has the following benefits: v Designed for specific industry participants to facilitate more rapid composite business application development. v Optimized for industry standards and best practices, ensuring consistency and reuse for geographical locations, product lines, and processes. v Aligned with top-down decomposition of an industry domain thus providing visibility into reuse across the organizational ecosystem. v Help speed time-to-market using service decompositions that ensure consistency and reuse. v Help simplify interoperability by defining the common language to facilitate interoperability between disparate IT assets. 4 IBM Product Lifecycle Management Content Pack for IBM WebSphere Business Services Fabric version 6.2: Reference Architecture Guide

11 Industry Content Packs v Help speed time-to-market with prebuilt, frequently reused, and industry standards specific common transactional functions. v Enable standardized connectivity to disparate applications in the IT ecosystem with prebuilt services that are based on industry standards. v Expands the use within an enterprise, or enhances the security of publishing to a broader partner ecosystem. v Enables clients and partners to plug in their SOA assets into predefined service decompositions. The IBM BPM Suite contains key functions to control and manage business processes across their life cycle, and it emphasizes business user involvement and collaboration for multiple roles within the organization. IBM WebSphere Dynamic Process Edition is a key offering of the IBM BPM Suite and delivers dynamic BPM capabilities to assemble and manage composite business applications. WebSphere Dynamic Process Edition includes three products to help enterprises implement BPM: v IBM WebSphere Business Modeler to model and simulate v IBM WebSphere Business Services Fabric to rapidly deploy and change v IBM WebSphere Business Monitor to analyze and optimize The IBM WebSphere Business Services Fabric software provides an SOA platform that enables you to model, assemble, deploy, manage, and govern business services. It provides the design time tools, run time environment, and optional prebuilt industry SOA content to help you build more flexible and responsive business solutions on your BPM platform. Using the WebSphere Business Services Fabric platform, business level services can be combined into extended cross-enterprise business processes, and solutions that are dynamically personalized and delivered based on the business context of the service request. WebSphere Industry Content Packs are prebuilt accelerators for WebSphere Dynamic Process Edition and WebSphere Business Services fabric. The Industry Content Packs integrate seamlessly with WebSphere Dynamic Process Edition and provide a large variety of prebuilt, industry-specific assets to accelerate and enhance Composite Business Applications. Industry Content Packs are also extensible and open for configuration and customization, based on the organization s key business processes. Composite Business Applications based on WebSphere Dynamic Process Edition and Industry Content Packs can enable enterprises to support their business processes, develop new products and increase their competitive edge. See the following chart to understand the positioning and packaging of WebSphere Industry Content Packs. At the very top, you can see industry specific SOA solutions (called as composite business applications) built in several industry functions. The composite applications are available from IBM GBS and its business partners or can even be built by clients. The middle layer shows the industry content pack that provides reusable assets, which can be reused across these composite applications. These assets are based on industry best practices. The reference architecture of Industry Content Packs makes it easy to consume and extend these assets using the IBM SOA methodology and the WebSphere platforms. At the bottom, you see the WebSphere Dynamic Process Edition on which the content pack assets are pre-certified, tested, and supported. The content pack assets are also based on the IBM SOA methodology (Model-Assemble- Chapter 1. Industry Content Pack overview 5

12 Deploy-Manage) and ensure interoperability across the middleware. Enterprises can opt to buy the entire WebSphere Dynamic Process Edition or just the WebSphere Business Services Fabric bundle. On the modeling side, you will need Rational Software Architect to make use of some of the content pack assets. Industry Composite Business Applications Industry Content Pack Reusable, pre-built assets Governing architecture Industry standards based Extensible to client needs Model Assemble Deploy Manage Rational Software Architect Business Modeler Integration Developer Process Server Business Services Fabric WebSphere Dynamic Process Edition Business Monitor Figure 3. Positioning and packaging of WebSphere Industry Content Packs Industry Content Packs provide significant value in accelerating the delivery of industry-specific Composite Business Applications using prebuilt assets based on industry standards. A common architecture, interoperable tools, and use of industry standards ensure consistency and reuse for multiple business processes where the industry content packs get used. The Industry Content Packs also reduce some of the risks associated with complete governance in SOA projects. The Industry Content Packs are not a replacement for industry standards but rather they make it easy to consume the industry standards. Available Industry Content Packs Available Industry Content Packs include: IBM Insurance Property and Casualty Content Pack for WebSphere Business Services Fabric This pack focuses on the property and casualty lines of business for insurance enterprises. IBM Healthcare Payer Content Pack for WebSphere Business Services Fabric This pack focuses on the health insurance processes. IBM Banking Payments Content Pack for WebSphere Business Services Fabric This pack focuses on the payments capabilities of financial services enterprises. IBM Telecom Operations Content Pack for WebSphere Business Services Fabric This pack focuses on the service provisioning and service assurance processes for telecommunication service providers. 6 IBM Product Lifecycle Management Content Pack for IBM WebSphere Business Services Fabric version 6.2: Reference Architecture Guide

13 IBM Product Lifecycle Management Content Pack for WebSphere Business Services Fabric This pack focuses on the ecosystem of the manufacturers in automotive, aerospace and defense, and electronics verticals. This ecosystem includes suppliers, service providers, and other manufacturers. Chapter 1. Industry Content Pack overview 7

14 8 IBM Product Lifecycle Management Content Pack for IBM WebSphere Business Services Fabric version 6.2: Reference Architecture Guide

15 Chapter 2. Industry Content Pack Reference Architecture This section describes the Reference Architecture and the key asset types for Industry Content Packs. Framework of components in the Industry Content Packs An Industry Content Pack aims at accelerating delivery of the industry-specific service-oriented business solutions using the IBM WebSphere Business Services Fabric platform. The framework of components in the Industry Content Packs is a logical expansion of a Service Oriented Architecture (SOA), which promotes loose-coupling of assets for consistency and reuse across business processes. The inconsistency in the current IT systems of companies limits their ability to use industry and technical standards across the enterprise. The use of common industry and technical standards support common needs, and encourages consistency in the technical architecture of the standards. The framework is optimized for industry and technical standards to facilitate interoperability across the business. You can use extend and use this framework to meet your unique business needs. These components work in agreement to create a foundation in the Reference Architecture that helps you build your own specific business logic for competitive advantage. Using this Reference Architecture, you can create and customize your own components and model them based on your business demands. The Reference Architecture is based on the following key asset types of Industry Content Packs: v Industry Capability and Process Maps v Industry Business Service Templates v Industry Service Interfaces v Industry Business Glossary v Industry Common Services v Industry Business Object Model v Knowledge Assets As shown in following image, there are a variety of assets in the Industry Content Pack. It is important to realize that these are interoperable components that share common Reference Architecture. This ensures credible governance for the clients who are going down the path of developing SOA solutions. Also, these assets are not just focused on the IT side but rather on alignment between business and IT. Copyright IBM Corp

16 Industry Content Pack Industry Capability - Process Maps Industry Business Services Templates Industry Services Interfaces Industry Common Services Industry Business Object Model Industry Business Glossary Knowledge Assets Figure 4. Industry Content Pack Assets Hence, the very first assets are Capability and Process Maps: that are decomposition of industry domain into business capabilities and processes. Once you have decomposed your business into capabilities and processes, you need to define the business functions, called Business Service Templates, that can use existing IT applications to create new business processes. After you have identified the reusable building blocks of your business, you need Service Interfaces that can interoperate with the existing IT functionality. In a SOA scenario where you have several services, messages helping interoperate within and outside a company s four walls, you need a set of common transaction functions, also known as Common Services, that help you process transactions like bulking, de-bulking, validation, error identification, transformation, and that can be reused for multiple solutions. It is assumed that all the coded functionality can be used from existing IT assets. However, there might be a need to create new operational data stores or physical data models. For this, a conceptual domain model, called Business Object Model, is needed. SOA solutions require business metadata like definitions of roles, channels, conditions, policies, rules, events, and so on. All these definitions are typically inconsistent across various projects. The Business Glossary ensures reuse and consistency of insurance business terms using a common vocabulary that you can extend. You can also consume and extend content pack assets using Knowledge Assets. The following sections explain each asset type. The Reference Architecture for Industry Content Packs is shown in the following figure. 10 IBM Product Lifecycle Management Content Pack for IBM WebSphere Business Services Fabric version 6.2: Reference Architecture Guide

17 Installation Guide Developer's Guide Reference Architecture Guide How-To Guide Reference Implementation SCA Industry Common Services Industry Service Interfaces Business Service Templates UML Roles Policy Templates Industry Business Glossary Assertions Channels Industry Business Object Model Industry Capability & Process Maps Industry Standards Industry Best Practices IBM Industry Models Figure 5. Reference Architecture for Industry Content Packs The Reference Architecture for Industry Content Packs serves as a generic framework for building industry-specific content packs. Using this architecture, Industry Content Packs are developed with industry-specific standards. These standards form the basis for deriving various assets in the Industry Content Packs. The Industry Business Service Templates are based on industry standards and industry best practices. They can be used for development of a service-oriented business solution. The Business Service Templates contain the associated metadata such as channels, roles, assertions, and defined sample policies. The Industry Business Glossary and the Industry Business Object Model are derived from the industry standards such as ACORD, HL7, NGOSS SID, and ISO The Services Component Architecture (SCA) is a set of specifications that describes a model for building applications and systems using an SOA platform. From a service-oriented business solution perspective, SCA is now a standard programming model. The Industry Content Packs support the SCA programming model by packaging the Business Service Templates as SCA modules. The Industry Common Services and the Industry Service Interfaces are made available as SCA libraries that can be used as part of other SCA components such as Business Process Execution Language (BPEL). The SCA modules created as a part of each content pack provide integration with the WebSphere Business Services Fabric by using the IBM Business Services Dynamic Assembler within a Reference Implementation. Knowledge assets such as the Developer s Guide and the How-To Guide describe how to use and extend the Industry Content Pack assets. The following sections detail each asset types. Chapter 2. Industry Content Pack Reference Architecture 11

18 Industry Capability and Process Maps Definition: The Industry Capability Map provides a logical view of the business competencies that an industry needs to process. The Industry Process Maps provides a logical view of the business processes used in an industry. Description: The Industry Capability and Process Maps provide the domain decomposition of the industry. The Capability Map defines the Capabilities and the Subcapabilities for the industry. Industry Capability Map: It defines the Capabilities and the Subcapabilities for the industry. These capabilities can be broken down to a granular level to identify the Subcapabilities. They can be decomposed to n-levels in the hierarchical representation. At the roots level in the hierarchy are the Capabilities that are represented in the Industry Capability Map. Industry Process Map: It defines a hierarchical representation of the business processes in an enterprise and can be decomposed to n-levels in the hierarchical representation. The Industry Capability Map is mapped to the Industry Process Map. There is a many-to-many relationship between capabilities and processes. Under a specific capability, there can be an n-level grouping of business processes. Various processes and subprocesses are required to support the identified capabilities. The Capability and Processes Maps can be extended to meet your unique business requirement. Source of Content: The Industry Capability and process definitions are based on Industry Standards such as etom, TAM, ISO 20022, and ACORD, HL7. Interoperability with other components These include the following components: Industry Business Service Templates: The Industry Capability and Process Maps is a reference for defining the Business Service Templates and their granularity. The Business Service Templates can be mapped to business processes. These business processes can be mapped to business capabilities. As part of the content pack definition, each business service is mapped to one or more process definition. Industry Service Interfaces: There is no direct dependency between the Industry Capability and Process Maps and the Industry Service Interfaces or vice versa. However, service interfaces mapped to Business Services can be used to fulfill a certain Business Capability or Process. Industry Business Glossary: There is no direct relationship between the Industry Capability and Process Maps and the Industry Business Glossary. Industry Common Services: There is no direct dependency between the Industry Capability and Process Maps and the Industry Common Services or vice versa. 12 IBM Product Lifecycle Management Content Pack for IBM WebSphere Business Services Fabric version 6.2: Reference Architecture Guide

19 However, the common services mapped to business services can be used to fulfill a certain business capability or process. Industry Business Object Model: There is no direct relationship between the Industry Capability and Process Maps and the Industry BOM. Value: The Industry Capability and Process Maps enables you to have a top-down visibility into the business by identifying the business capabilities and processes that are consistently reusable by mapping Capabilities, Processes, and Business Services. The Industry Capability and Process Maps demonstrate business to IT alignment. Tools: At design time, the Industry Capability and Processes Maps are represented as a Unified Modeling Language (UML) model. Rational Software Architect is the recommended tool. The IBM WebSphere Business Services Fabric Modeling Tool, a plug-in to the Rational Software Architect, is used to visualize and extend the Industry Capability and Process Maps. At run time, the Industry Capability and Process Maps are available as the Fabric Content Archive (FCA). Industry Business Service Templates This section describes the Industry Business Service Templates, a part of the Industry Content Pack, from a Reference Architecture perspective. Definition: The Industry Business Service Templates is a starting point for an industry specific service-oriented business solution. Description: The Industry Business Service Templates act as a building block for a business level, enabling it to be reused across multiple solutions and processes. They are based on business capabilities and business processes. An industry domain is divided into business functions represented by corresponding business services. These business service representations can be used as they are, or they can be extended to meet business requirements. Business Services adapt their behavior at run time, based on the associated business service metadata such as channels, roles, assertions, and policies. A Business Service Template consists of the following components: v Business service definitions v Relevant subscribers who can customize their services v Potential mode of access for the service v Assertions to represent its Business Capabilities v Sample policies that define its behavior v Mappings to the associated Web services Source of Content: The granularity of the Industry Business Service Templates is based on the business functions represented for a given industry domain in the context of an SOA solution. Typically, the business services decomposition is based on business capability maps, business process maps, and the domain knowledge of subject matter experts who understand the principles and methodologies of SOA. After the decomposition, these business services need to be defined with the associated metadata. Thus, there is no as-is use Chapter 2. Industry Content Pack Reference Architecture 13

20 of any source content (Capability and Process Maps) while defining Business Service Templates. The source content can be best used as a reference. Interoperability with other components: These include the following components: Industry Capability and Process Maps: The business service templates are mapped to corresponding processes in the Industry Process Maps. There is a many-to-many relationship between the Industry Business Service Templates and the Process Maps. A Business Service Template can be mapped to an infinite number of processes. Similarly, multiple Business Service Templates can be mapped to the same Process. Industry Service Interfaces: The Business Service Templates are mapped to the Industry Service Interfaces. This mapping is a many-to-many relationship. A Business Service Template can be mapped to an infinite number of Web services. Similarly, many Business Service Templates can use the same Web service. Industry Business Glossary: The Business Service Templates use the business terms defined in the Industry Business Glossary to define Roles, Channels, Assertions, and Policies. A specific business term can be used in multiple Business Service Templates. Industry Common Services: The Business Service Templates are mapped to the Industry Common Services. This mapping is a many-to-many relationship. Thus, a Business Service Template can be mapped to an infinite number of Common Services. Similarly, many Business Service Templates can use the same Industry Common Service. Industry Business Object Model: There is no direct relationship between Business Service Templates and Industry Business Object Model. The Industry BOM is used as a logical design to create an operational data store for implementing a customer-specific business service based on a Business Service Template. Value: This represents a business process by a set of business services. It enables shorter change cycles and improves reuse across the enterprise. The Business Service Templates are based on industry best practices and are supported by prevalent industry standards. Using these templates reduces the time and cost to implement business services, and enables simpler and more flexible business processes. It enables clients and partners to plug-in their SOA assets to the predefined Business Service Templates. Tools: At design time, the Business Service Templates are represented as SCA modules in the WebSphere Business Services Fabric Projects, and use the IBM Business Services Composition Studio and the WebSphere Integration Developer tooling. At run time, they are available as FCA files and use the WebSphere Business Services Fabric Foundation Pack. 14 IBM Product Lifecycle Management Content Pack for IBM WebSphere Business Services Fabric version 6.2: Reference Architecture Guide

21 Industry Service Interfaces Definition: The Industry Service Interfaces are prebuilt Web service interfaces that facilitate interoperability across diverse platforms for a given industry. Description: A key challenge faced by the enterprises today is of interoperability across diverse systems in their business. These include packaged applications, custom applications, existing systems, object-oriented applications, and third-party services. All of these disparate assets need to be able to operate with each other and this interoperability is facilitated by the Industry Service Interfaces. These interfaces are based on industry standards to ensure consistency and reuse. Source of Content: The Web service interfaces in the Industry Service Interfaces are based on industry standards. These industry standards provide the messaging schemas that can be used to define the Industry Service Interfaces. Cases where the industry standards only define the data types, a custom schema is created for defining the Industry Service Interfaces. Similar to the Industry Business Service Templates, the granularity of the Industry Service Interfaces is very important and is dependent on the way specific industry domain can be separated into a set of operations. Thus, this is based on business services and the types of interactions that take place across the IT departments in an industry. Typically, the Industry Service Interfaces are Web services that can perform a single task. Based on a client s unique business needs, multiple Industry Service Interfaces can be combined into a single composite service. Interoperability with other components: These include the following components: Industry Capability and Process Maps: There is no direct dependency between the Industry Service Interfaces and the Industry Capability and Process Maps. However, through the mapping to Business Service Templates, a reuse analysis of Service Interfaces can be done in context of the Capabilities and Processes. Industry Business Service Templates: The Industry Service Interfaces are mapped to the Business Service Templates. This mapping is based on a many-to-many relationship. Thus, many Industry Service Interfaces can be mapped to a single Business Service Template. Similarly, a single Industry Service Interface can be mapped to many Business Service Templates. Industry Business Glossary: The Industry Service Interfaces use the business terms defined in the Industry Business Glossary to define endpoint assertions. A specific business term can be used in defining assertions for endpoints with multiple Industry Service Interfaces. Industry Common Services: There is no direct dependency between the Industry Service Interfaces and Industry Common Services or vice versa. However, both of these can work together to run a business service. Industry Business Object Model: There is no direct dependency between the Industry Service Chapter 2. Industry Content Pack Reference Architecture 15

22 Industry Business Glossary Interfaces and Industry BOM. However, the Industry BOM is used as a logical data model to create an operational data store for implementing some of these Industry Service Interfaces. Value: A predefined Industry Service Interface enables interoperability across disparate IT assets using prevalent industry standards. This reduces time, cost, and improves consistency. Tools: At design time, the Industry Service Interfaces are represented as System Component Architecture (SCA) libraries and use the WebSphere Integration Developer. Definition: The Industry Business Glossary is taxonomy of the business terms for a given industry. It provides information about relationships with other industry-specific terms. Description: The WebSphere Business Services Fabric enables interoperability of diverse systems in an enterprise through business services metadata such as roles, channels, assertions, and policies. You must use industry standards to define the metadata for consistency and reuse of associated business services. The Industry Business Glossary contains common vocabulary that represents the taxonomy of business terms from various industry standards. Source of Content: The Industry Business Glossary is based on an industry standard that represents business objects or data types. The content for the Industry Business Glossary can be derived from any data standards, such as BOM models, messaging models, and industry dictionaries. An Industry Business Glossary can drive content from multiple industry standards. This enables you to choose one of the standards as an enterprise-wide information or canonical model for the business services. Interoperability with other components: These include the following components: Industry Capability and Process Maps: There is no direct dependency between the Industry Business Glossary and the Industry Capability and Process Maps. Industry Business Service Templates: The Industry Business Glossary provides the source content to define metadata for the Business Service Templates. This is a many-to-many relationship. An infinite number of terms in an Industry Business Glossary can be used as metadata for a Business Service Template. Similarly, a single term can be used as metadata for many Business Service Templates. Industry Service Interfaces: The terms included in the Industry Business Glossary can be used to define the endpoint assertions for the industry service interfaces. This also is many-to-many relationship. Multiple terms defined from the Industry Business Glossary can be used as metadata for an Industry Service Interface. Similarly, a single term from the glossary can be used as metadata for many Industry Service Interfaces. 16 IBM Product Lifecycle Management Content Pack for IBM WebSphere Business Services Fabric version 6.2: Reference Architecture Guide

23 Industry Common Services Industry Common Services: The terms included in the Industry Business Glossary can be used to define endpoint assertions for the Industry Common Services. This also is a many-to-many relationship. Multiple terms defined from the Industry Business Glossary can be used as metadata for an Industry Common Service. Industry Business Object Model: There is no direct relationship between the Industry Business Glossary and the Industry BOM. However, the industry BOM is derived from the Industry Business Glossary. You can choose to use the defined terms in the Industry Business Glossary that have been derived from the Industry BOM. This makes the semantic interoperability easier. Value: The Industry Business Glossary provides predefined and extensible business services metadata (based on industry standards) that serve as a framework to improve consistency and reuse of business services. Tools: At design time, the Industry Business Glossary is represented as a UML model using the Rational Software Architect, which is the recommended tool. The IBM WebSphere Business Services Fabric Modeling Tool is used to visualize and extend the Industry Business Glossary. At run time, the Industry Business Glossary is made available as a FCA file that can be imported into WebSphere Business Services Fabric. Definition: The Industry Common Services are industry-specific service implementations that enable transactional functions such as validation, error identification, and transformation. Description: An enterprise consists of diverse applications that contain common industry transactions such as validation, transformation, and so on. It can be used when various business services are instantiated. These transactions are relevant for communication between the customer and partners within the customer organization. There is a need to provide standards-based implementation of common message and document processing. The Industry Common Services must meet this requirement. Source of Content: The Web Service Interfaces in the Industry Common Services are based on industry standards. These industry standards provide the messaging schemas that are used to define the Industry Common Services. The industry standards define the data types. A custom-schema based on the industry best practices is created to define the Industry Common Services. The granularity of the Industry Common Services is based on the type of common message and document processing transactions performed across IT departments in an industry. Typically, the Industry Common Services are Web services that can perform a single task, based on a client s business needs, and they can be combined into a composite service. Interoperability with other components: These include the following components: Industry Capability and Process Maps: The Industry Common Services do not have direct dependency on Chapter 2. Industry Content Pack Reference Architecture 17

24 the Industry Capability and Process Maps. However, through the mapping of the Business Service Templates, a reuse analysis of common services can be done in context of the Capabilities and Processes. Industry Business Service Templates: The Industry Common Services are mapped to Business Service Templates. This mapping can be of many-to-many relationship. Multiple Industry Common Services can be mapped to a single Industry Business Service Template. Similarly, an Industry Common Service can be mapped to many Business Service Templates. Industry Service Interfaces: The Industry Common Services do not have a direct dependency on Industry Service Interfaces or vice versa. However, both can coexist to run a business service. Industry Business Glossary: The Industry Common Services use the business terms defined in Industry Business Glossary to define end point assertions. A specific business term can be used to define assertions for endpoints in multiple Industry Common Services. Industry Business Object Model: There is no direct relationship between the Industry Common Services and the Industry BOM. Value: The Industry Common Services provide prebuilt service implementations for industry-specific common functions that can be reused across multiple composite business applications. These can initiate the delivery of SOA applications. Tools: At design time, the Industry Common Services are represented as SCA libraries and use WebSphere Integration Developer as the development integrated development environment (IDE). At run time, the Industry Common Services are available as deployable EAR files in the WebSphere Process Server and as Fabric Content Archive (FCA) files in the WebSphere Business Service Fabric. Industry Business Object Model Definition: Industry BOM is a logical representation of business entities and attributes that set up a business domain or a subvertical within a domain. Description: The purpose of this model is to serve as an input to logical data model for a business domain. This model is derived from industry standards such as HL7, ACORD, NGOSS SID, and ISO model. The BOM contains business concepts, relationships, and enumerations that can be used into a tool such as Rational Data Architect (RDA) to construct a logical data model. The Industry Content Pack uses this source to define business terms within the Industry Business Glossary. Source of Content: The Industry BOM can be any industry standard that has a representation of business entities, attributes, and relationships as a BOM, data dictionary, and messaging model. 18 IBM Product Lifecycle Management Content Pack for IBM WebSphere Business Services Fabric version 6.2: Reference Architecture Guide

25 Interoperability with other components: These include the following components: Industry Capability and Process Maps: There is no direct dependency between the Industry BOM and the Industry Capability and Process Maps. Industry Business Service Templates: There is no direct dependency between the Industry BOM and the Business Service Templates. Entities defined as part of the BOM can be modeled as a Logical Data Model (LDM) to be used for creating an operational data store that can be used as a persistence mechanism to store and retrieve application data. Industry Common Services: There is no direct dependency between the Industry BOM and the Industry Common Services. Industry Service Interfaces: There is no direct dependency between the Industry BOM and the Industry Service Interfaces. Industry Business Glossary: There is no direct relationship between the Industry Business Glossary and the Industry BOM. However, the Industry BOM is one of the sources for the Industry Business Glossary. You can use these terms in the Industry Business Glossary that have been derived from the Industry BOM. This makes the semantic interoperability easier. Value: The Industry BOM provides a denormalized version of business entities, attributes along with their relationships. This enables to create an LDM that can be used to create a physical data model. Tools: At design time, the BOM is available as a UML model in the Rational Software Architect. The Industry BOM can be exported in an LDM format using the built-in UML transformation. This transformed LDM format can be imported into a data modeling tool such as the IBM Rational Data Architect. Knowledge assets Definition: Using the Knowledge Assets makes it easier for you to use and extend the assets packaged in the content pack to accelerate development of an industry-specific service-oriented business application. Description: Knowledge Assets includes the following assets: v Installation Guide: Provides the installation procedures for the Industry Content Pack. It covers the platform, software, and hardware prerequisites for installation. It describes both the manual and interactive installation processes for installing the Industry Content Pack. v Developer s Guide: Provides the technical details of various types of assets packaged in an Industry Content Pack. It describes the tools, architecture, and deployment details of these assets. v Reference Architecture Guide: Provides the Reference Architecture for an Industry Content Pack. It describes the framework of components for an Chapter 2. Industry Content Pack Reference Architecture 19

26 Industry Content Pack. It also explains the alignment of the reference architecture of an Industry Content Pack with the IBM SOA architecture and methodology. v How-To Guide: Explains how to use and extend an Industry content pack to meet your needs. It describes the application of Industry content pack assets that accelerate development of an SOA solution. v Reference Implementation: An Industry Content Pack is an accelerator for development of a service-oriented business application and not the application itself. It is important to take some of these assets to showcase a sample implementation. The Reference Implementation is based on a sample process specific to the Industry Content Pack and it uses some of the assets to demonstrate an end-to-end solution using WebSphere Business Services Fabric that enables service-oriented business applications. The assets used in the Reference Implementation are Industry Business Service Templates, Industry Common Services, Industry Service Interfaces, Roles, Channels, and Assertions from the Industry Business Glossary. The Reference Implementation is made available as an SCA module such as a BPEL process that can be imported into the WebSphere Integration Developer and run in the WebSphere Process Server. The Reference Implementation uses all the other components in the content pack except for the BOM. Using mock implementations for the Industry Service Interface, you can demonstrate, using a use-case how the Industry Content Pack integrates with the IBM Business Services Fabric Dynamic Assembler component available as part of the WebSphere Business Services Fabric Foundation Pack. Value: The knowledge assets provide guidance to help set the boundary for deployment of a service-oriented business application using the WebSphere Business Services Fabric and the Industry Content Packs. Tools: The Installation Guide, Developer s Guide, Reference Architecture, and How-To Guide are available as a PDF or HTML document. The Reference Implementation is available as a run time artifact and uses the WebSphere Process Server tool. 20 IBM Product Lifecycle Management Content Pack for IBM WebSphere Business Services Fabric version 6.2: Reference Architecture Guide

27 Chapter 3. Product Lifecycle Management Content Pack Reference Architecture Provided in the following topics are the details of the reference architecture and the key asset types of the Product Lifecycle Management Content Pack. Product Lifecycle Management is a strategic capability to integrate systems, processes, and data across the complete product lifecycle in a way that enables the use of information to better conceive ideas to meet the marketplace demands, to accurately transform these ideas into products that can be produced, to source and manufacture the products, and to continue with support and enablement of the products throughout their in service life. Product Lifecycle Management (PLM) Content Pack applies to automotive, electronics, aerospace and defense, and industrial verticals. It focuses on business areas such as product data management, engineering change management, bill of material, and supplier collaboration. It delivers assets aimed at an ecosystem of OEM, suppliers, service providers, and other manufacturers. The PLM Content Pack is a core offering from the IBM Product Development Integration Framework. The PLM Content Pack includes pre-built assets that are derived from the following industry standards: v American Productivity & Quality Center Process Classification Framework (APQC PCF) models v Object Management Group product lifecycle management (OMG PLM) Services 2.0 v Verband der Automobilindustrie e. V (VDA) 4965 v Open Applications Group Integration Specification (OAGIS) 9.1 Models The following figure explains the Reference Architecture for the Product Lifecycle Management Content Pack. Copyright IBM Corp

28 Installation Guide Developer's Guide Reference Architecture Guide How-To Guide Reference Implementation SCA Product Lifecycle Management Common Service OMG PLM Service 2.0, VDA 4965, OAGIS 9.2 OMG PLM Service Extensions Product Lifecycle Management Service Interface OMG PLM Service 2.0, VDA 4965, OAGIS 9.2 OMG PLM Service Extensions Business Service Templates UML Roles Best Practices Policy Templates Best Practices Product Lifecycle Management Business Glossary OMG PLM Service 2.0, VDA 4965, OAGIS 9.2 OMG PLM Service Extensions Assertions OAGIS, OMG PLM Service VDA, OMG PLM Extensions Channels Best Practices Product Lifecycle Management Business Object Model OMG PLM Service 2.0, VDA 4965, OAGIS 9.2 Product Lifecycle Management Capability and Process Maps Auto/A&D CBM Map, APQC Process Classification Framework Product Lifecycle Management Standards OMG PLM Service 2.0, VDA 4965, OAGIS 9.2, APQC Process Classification Framework IBM Industry Models AUTO/A&D CBM Map Product Lifecycle Management Best Practices Figure 6. Reference Architecture for Product Lifecycle Management Content Pack Assets packaged in the Product Lifecycle Management Content Pack Provided here are the details about each asset in the Product Lifecycle Management Content Pack. Product Lifecycle Management Capability and Process Maps The Capability in Product Lifecycle Management Content Pack is based on AUTO/A&D CBM Map and the Process Maps are based on the APQC process classification framework. Product Lifecycle Management Business Service Templates The definition and granularity of the Product Lifecycle Management Business Service Templates is dependant on the following factors: v The Product Lifecycle Management Capability and Process Maps v The application ecosystem based on industry applying Product Lifecycle Management v The applicable SOA principles and methodologies for granularity of services Product Lifecycle Management Service Interfaces The Service Interfaces in Product Lifecycle Management Content Pack are based on the PLM Services, VDA, OAGIS standard, and the best practice extensions around PLM Services. 22 IBM Product Lifecycle Management Content Pack for IBM WebSphere Business Services Fabric version 6.2: Reference Architecture Guide

29 A A A A Product Lifecycle Management Business Glossary The Business Glossary in Product Lifecycle Management Content Pack is derived using VDA, PLM Service, OAGIS, and Product Lifecycle Management best practices. v Roles: These are based on Product Lifecycle Management best practices. v Assertions: These are derived from VDA, PLM Service, OAGIS and Product Lifecycle Management best practices. v Channels: These are based on Product Lifecycle Management best practices. Product Lifecycle Management Common Services The Common Services in Product Lifecycle Management Content Pack are based on VDA, PLM Service, OAGIS, and Product Lifecycle Management best practices. Common services also contain reusable components that are commonly used across the manufacturing industry. Product Lifecycle Management Business Object Model The Business Object Model in Product Lifecycle Management Content Pack is derived using VDA, PLM Service, OAGIS and Product Lifecycle Management best practices. This model provides an information or data reference model and a common information or data vocabulary from a business and systems perspective. This model uses UML to formally express needs of a particular view. It provides consistent data and concept that can be reused across multiple information structures including messages. It represents a rich set of concepts that can be shared throughout the PDM Systems. Product Lifecycle Management Content Pack logical view Provided here is the logical view of the Product Lifecycle Management Content Pack. The following figure provides a logical view of the Reference Architecture for Product Lifecycle Management Content Pack. The earlier topics addressed the various dependencies between each of the components. These components are visualized using the association notation. Reference Business Service Templates Product Lifecycle Management Content Pack How-To Guide Product Lifecycle Management Content Pack Install Guide 1 1 Knowledge Assets Product Lifecycle Management Content Pack Developer Guide 1..* 1..* 1..* 1..* Product Lifecycle Management Content Pack Reference Architecture Guide «Metadata» Business Service Business Policy Business Role Access Channels Policy Assertion Product Lifecycle Management Common Services Product Lifecycle Management Service Interfaces Product Lifecycle Management - Reference Impl. * Product Lifecycle Management Business Glossary «derive» «derive» 1..* «derive» «derive» Product Lifecycle Management Capability Model * * Product Lifecycle Management Business Processes «derive» «derive» OAGIS BOM OAGIS 9.2 «derive» «derive» «derive» PLM Service BOM «derive» PLM Service 2.0 «derive» «derive» VDA BOM «derive» VDA 4965 Auto/A&D CBM Map APQC Process Classification Framework PLM Service Extensions BOM «derive» PLM Service Extensions You may need to zoom in for reading contents Figure 7. Product Lifecycle Management Content Pack - Logical View Chapter 3. Product Lifecycle Management Content Pack Reference Architecture 23

30 Product Lifecycle Management Content Pack component model Provided here is the Component Model for the Product Lifecycle Management Content Pack. The following figure details the component model for the Product Lifecycle Management Content Pack. The components in this view have been categorized into two separate stacks that are made available as part of the Product Lifecycle Management Content Pack. v The top level stack contains the run time components and their dependencies. v The bottom stack contains the design time components. «EAR» Specify and Decide on Engineering Change mock services OSGi Bundle «FCA» Product Lifecycle Management Reference Model «imports» «FCA» Product Lifecycle Management Reference Implementation «EAR» Specify and Decide on Engineering Change - Reference Implementation «imports» «imports» «FCA» Product Lifecycle Management Fabric Model «imports» «EAR» «component» «component» Create Component Common Service «imports» «FCA» ISO-Codes «imports» «FCA» Product Lifecycle Management Business Glossary «imports» «ProjectInterchange» Product Lifecycle Management Capability & Process Maps «ProjectInterchange» Specify and Decide on Engineering Change - Reference Implementation Module «ProjectInterchange» Product Lifecycle Management Business Glossary «references» «references» «ProjectInterchange» Product Lifecycle Management Common Services «ProjectInterchange» Product Lifecycle Management Service Interfaces «ProjectInterchange» VDA «ProjectInterchange» OAGIS-BOM «references» «references» «ProjectInterchange» OMG PLM Service Extensions «ProjectInterchange» OMG PLM Service «ProjectInterchange» Product Lifecycle Management Business Service Templates You may need to zoom in for reading contents Figure 8. Product Lifecycle Management Content Pack - Component Model Product Lifecycle Management Business Glossary The UML model representation of the Product Lifecycle Management Business Glossary is packaged as a Project Interchange file, which can be imported into Rational Software Architect. Architects and developers can use these UML models to create and extend industry core concepts. Product Lifecycle Management Common Services The Product Lifecycle Management Common Services includes the standards-based Web service implementation. The interfaces and data types for these Common Services are made available as SCA libraries during design time. These SCA libraries are then packaged as EAR files that can be deployed in WebSphere Process Server at run time. Product Lifecycle Management Service Interfaces Product Lifecycle Management Service Interfaces in Product Lifecycle Management Content Pack are standards-based Web service interfaces designed using WebSphere Integration Developer. These Industry Service 24 IBM Product Lifecycle Management Content Pack for IBM WebSphere Business Services Fabric version 6.2: Reference Architecture Guide

31 Interfaces are WS-I compliant and they confirm to the latest WSDL and XSD specifications. There is no run time component associated with this asset. These service interfaces are packaged as SCA libraries, which are used as dependent projects for the SCA modules. These SCA modules are then made available as a part of the Product Lifecycle Management Business Service Templates. Product Lifecycle Management Reference Model Product Lifecycle Management Reference Model includes Business Service Templates and map to Process Maps, application suites, applications, roles, assertions, and service interfaces. For distributed OS, this is installed as an OSGi bundle and for Z/OS it is packaged as FCAs that can be imported into WebSphere Business Services Fabric. The following table shows the various design time and run time components along with the recommended tools for various asset types: Table 1. Product Lifecycle Management Content Pack Component Model Asset Product Lifecycle Management Capabilities and Process Maps Product Lifecycle Management Business Service Templates Product Lifecycle Management Service Interfaces Product Lifecycle Management Business Glossary Product Lifecycle Management Common Services Product Lifecycle Management Business Object Model Reference Implementation Design Time Run Time Tools UML Models SCA Libraries and Modules, WebSphere Business Services Fabric Projects SCA Libraries UML Models SCA Libraries UML Models SCA Modules FCA/OSGi Bundle FCA/OSGi Bundle v Rational Software Architect - Design time v WebSphere Business Service Fabric - Run time v WebSphere Integration Developer Design time v WebSphere Business Service Fabric Run time None v WebSphere Integration Developer Design time FCA/OSGi Bundle v Rational Software Architect Design time (Recommended tool) v WebSphere Business Service Fabric Run time EAR v WebSphere Integration Developer Design time v WebSphere Process Server Run time None v Rational Software Architect RSA Design time (Recommended tool) EAR v WebSphere Integration Developer Design time v WebSphere Process Server Run time Chapter 3. Product Lifecycle Management Content Pack Reference Architecture 25

32 E Product Lifecycle Management Content Pack deployment view The following figure outlines an approach for deploying the Product Lifecycle Management Content Pack run time and design time components. For this approach, the Product Lifecycle Management Content Pack and the WebSphere Business Services Fabric must be associated with the same WebSphere Process Server profile. Websphere Process Server Websphere Integration Developer Rational Software Architect WBSF Profile «buildcomponent» WBS Fabric Tool Pack «UMLModel» Product Lifecycle Management - BOM «buildcomponent» Specify and Decide on Engineering Change.ear «FabricProject» Product Lifecycle Management Reference Model «buildcomponent» WBS Fabric Tool Pack «buildcomponent» Com «buildcomponent» Common Services 2.ear «buildcomponent» Mock Services.ear «FabricProject» Product Lifecycle Management Reference Implementation «UMLModel» Product Lifecycle Management Business Glossary «buildcomponent» WBS Fabric Foundation Pack «Library» Product Lifecycle Management Common Services «UMLModelt» Product Lifecycle Management Capability Model «UMLModel» ISO Codes «OSGiBundle» Product Lifecycle Management Core Ontology «Module» Specify and Decide on Engineering Change «Library» Product Lifecycle Management Services Interfaces «UMLModel» Product Lifecycle Management Process Model «Module» Product Lifecycle Management Business Service Templates «UMLModel» Product Lifecycle Management Fabric Model Figure 9. Product Lifecycle Management Content Pack - Deployment View You may need to zoom in for reading contents The following artifacts are deployed during run time and design time. During design time, the Business Service Templates are imported and visualized using the WebSphere Integration Developer. The SCA modules and libraries are made available as project interchange files that are imported into the business integration perspective of WebSphere Integration Developer. During run time, the executable part of the content pack, Common Services and Reference Implementation, are deployed as EAR files in the WebSphere Process Server. Fabric Content Archives are imported into WebSphere Business Services Fabric at run time. Product Lifecycle Management Business Glossary and Industry BOM can be imported, visualized, and extended using IBM Business Services Fabric Modeling Tool within Rational Software Architect. 26 IBM Product Lifecycle Management Content Pack for IBM WebSphere Business Services Fabric version 6.2: Reference Architecture Guide

33 Chapter 4. Industry Content Pack alignment with the IBM SOA Reference Architecture This section describes the industry content pack alignment with the IBM SOA Reference Architecture. The Industry Content Packs are accelerators for the development of industry-specific service-oriented business solutions. The content pack Reference Architecture is based on the SOA. SOA provides a roadmap and guidelines for the architectural design, and implementation decisions. Additionally, it provides patterns and insights for integrating these aspects to enable end-to-end, SOA-based business solutions that cover enterprise modeling, business process modeling, service modeling, and integration and management of business applications. The SOA Lifecycle is fundamentally an important foundation for service-oriented business solutions. It begins with modeling business processes, and then working toward deployable artifacts. These artifacts are managed in a way that they can provide feedback for continuous improvement. Copyright IBM Corp

34 Capability and Process Maps Consumers Channel B2B IVR Business Service Templates Business Process Composition; choreography; business state machines Service Consumer Industry Service Interfaces Services atomic and composite Industry Common Services Service Components Service Provider Operational Systems Packaged Application Custom Application OO Application Integration (Enterprise Service Bus) QoS Layer (Security, Management & Monitoring Infrastructure Services) Data Architecture (meta-data) & Business Intelligence Governance Industry Business Glossary Industry Business Object Model Knowledge Assets You may need to zoom in for reading contents Figure 10. Industry Content Pack alignment with the IBM SOA Reference Architecture The IBM SOA Reference Architecture is represented in the following layers: Business Process Layer: The Business Process Layer contains the Business Service Templates. The business process layer is a process representation of composition methods, which serve as building blocks for aggregating loosely coupled services, such as a sequencing process that is aligned with business goals and definition for concepts available in the Capability and Process Maps. Services layer (atomic and components): The Services layer aligns the Industry Service Interfaces. Service Components layer: The Service Components layer contains the Industry Common Services. This provides the implementation for realization or operation on a service. Data Architecture layer: The data architecture layer contains the Industry Business Glossary and the Industry BOM. 28 IBM Product Lifecycle Management Content Pack for IBM WebSphere Business Services Fabric version 6.2: Reference Architecture Guide

35 Chapter 5. Industry Content Pack alignment with the IBM SOA lifecycle methodology Model WebSphere Rational Rational FMT Rational Industry Business Object Model In UML WebSphere Business Modeler Rational Software Architect Fabric Modeling Rational Data Architect Industry Standards in UML WebSphere Rational Rational Reference Implementation as SCA Module Assemble WebSphere Integration Developer Rational Application Developer WebSphere Service Registry & Repository Rational Data Architect Industry Service Interfaces as SCA Libraries Catalog Industry Business Glossary In UML Industry common services As SCA Libraries COMPOSITION STUDIO GOVERNANCE MANAGER BUSINESS SERIVCES REPOSITORY Industry Capability and Process Maps In UML Business Service template As SCA Module Deploy WebSphere Tivoli Industry Business Glossary as Fabric Content Archive Industry Common Service WebSphere Process Server DYNAMIC ASSEMBLER SUBSCRIPTION MANAGER Tivoli Identity Manager Business Service Templates as FCA Industry Reference Implementation Manage WebSphere Tivoli Tivoli Tivoli Tivoli Reference Implementation as FCA WebSphere Business Monitor PERFORMANCE MANAGER Tivoli Service Management Rational Rational Requisite Pro Governance & Processes Rational Rational Portfolio Manager Figure 11. Industry Content Pack alignment with the SOA Lifecycle Methodology Tools View Model Model: During the model stage, you can extend the Industry Business Glossary, the Industry Capability and Process Maps, and the Industry BOM. To extend Industry Business Glossary: v Identify new terms in the industry model and mark them as glossary terms. v Add new terms using extensions to industry standards. v Add new enumerations to the existing terms. v Add new enumeration values to existing enumerations. v Create new assertions, channels, and role types using extensions to the Industry Business Glossary. IBM 2007, 2008 IBM

36 To extend the BOM: v Add new attributes to the existing classes as an extension. v Add a new class with attributes as an extension. To extend Industry Capability and Process Maps: v Add new capabilities or subcapabilities to an existing capability. v Add new processes or subprocesses to an existing process. v Add new mappings to the existing maps, such as process mapped to new capabilities and so forth. Assemble Assemble: The Business Service Templates consist of the business services metadata. During the assemble stage, the relevant SCA modules and libraries are instantiated using the WebSphere Integration Developer-Business Services and Business Integration perspectives. Deploy Deploy: During the deploy stage, run time artifacts are packaged and deployed into the WebSphere Process Server and the WebSphere Business Services Fabric. You can create run time environments in the WebSphere Business Services Fabric. You can also configure and create new users and roles. These users are then subscribed to the Business Services. 30 IBM Product Lifecycle Management Content Pack for IBM WebSphere Business Services Fabric version 6.2: Reference Architecture Guide

37 Notices and Trademarks Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this documentation in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user s responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this documentation. The furnishing of this documentation does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo , Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web Copyright IBM Corp

38 sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: Lab Director IBM Corporation Burnet Road, Austin, TX U.S.A Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. All statements regarding IBM s future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, 32 IBM Product Lifecycle Management Content Pack for IBM WebSphere Business Services Fabric version 6.2: Reference Architecture Guide

39 modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows: (C) (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. (C) Copyright IBM Corp. 2006, 2007, All rights reserved. If you are viewing this information softcopy, the photographs and color illustrations may not appear. Trademarks and service marks The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States or other countries, or both: IBM IBM (logo) AIX ClearCase ClearQuest DB2 DB2 Universal Database Rational Tivoli Tivoli (logo) Tivoli Enterprise Tivoli Enterprise Console WebSphere z/os Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel Inside (logos), and Pentium are trademarks or registered trademarks of Intel Corporation in the United States, other countries, or both. Solaris, Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Notices and Trademarks 33

40 UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. 34 IBM Product Lifecycle Management Content Pack for IBM WebSphere Business Services Fabric version 6.2: Reference Architecture Guide

41

42 Printed in USA