Skip to main content

skip to main content

developerWorks  >  SOA and Web services | Sample IT projects | Architecture  >

On demand business process life cycle: Build reusable assets to transform an order processing system

Overview

developerWorks

On demand business process life cycle

Creating a flexible IT infrastructure -- one that allows for technical evolution, simple management of assets and processes, and leverages existing technology investments -- need not be just a utopian vision. Implementing an IBM® On Demand Operating Environment helps you build, integrate, and manage business processes that can evolve as your enterprise grows, enabling more efficient configuration, operation, and monitoring of the IT environment. With streamlined business processes, your business is agile and able to respond faster to problems, saving time and money.

To demonstrate this concept, the IBM On Demand development team performed a pilot project called Oneida-2. In this project, the team implemented a Service-Oriented Architecture (SOA) prototype to demonstrate the on demand transformation of a realistic subset of Customer Order Analysis and Tracking System (COATS), a core business process of the IBM Integrated Supply Chain (ISC) model. COATS implements the main business processes used by IBM worldwide to fulfill orders of complex hardware systems. The goal of Oneida-2 is to implement an on demand business transformation in an actual supply chain scenario.

In this series of articles -- using a scenario based on a real hardware order-processing system used by IBM – you will be presented with a methodology to implement an on demand environment to develop agile, on demand business processes. This scenario provides a common context and a set of use cases for the remaining articles in the series, which will cover patterns, modeling, workflow, rules, and monitoring. You will learn methods and techniques you can use to build reusable assets, all to support the rapid creation of on demand business processes.

Part 1: Create the foundation for your on demand business processes
October 2004
This series presents a methodology to develop agile, on demand business processes. This approach promotes the ability to rapidly define, create, and deploy flexible solutions to meet continually evolving customer demands through the integration of services, data, rules, roles, and metrics within business processes. The authors introduce a realistic order processing scenario based on a real hardware order processing system used by IBM. This scenario provides a common context and a set of use cases for the rest of the articles in this series, which will cover patterns, modeling, workflow, rules, and monitoring.

Part 2: Patterns for e-business recipe
November 2004
This paper shows you how to apply the Patterns for e-business, using a step-by-step recipe, to create effective run-time architecture for an Order to Manufacturing Processing System (OTMPS). The recipe includes the identification of Business, Integration, Composite, Application, and Run-time patterns. You also learn how to map the Run-time patterns to products. In addition, the authors introduce you to new, potential Composite, Application, and Run-time patterns: Business Process Composite pattern, Page Aggregation Application and Run-time pattern, and Managed Collaboration Run-time pattern.

Part 3: Business process modeling using WebSphere® Business Integration Modeler
December 2004
This paper introduces a method and techniques for graphically modeling a business process using WebSphere Business Integration Modeler V5 for the generation of artifacts to be used in the development environment. The authors present guidelines for conducting an iterative modeling method using an order processing system scenario which describes how to define a process model using control and data flows, sub processes, tasks, policies, roles and measurements. They then illustrate the step-by-step process modeling method with the identification and listing of tasks, sequencing of the tasks, creation of flow controls between tasks, introduction of data into the model, and the integration of services into the process model. The paper concludes with a description of the export options and the generated artifacts which are used as input to the development tools described later in this series.

Part 4: Integrate artifacts from Rational XDE and WebSphere Business Integration Modeler
January 2005
Learn how to integrate multiple artifacts for the development of an executable application for an on demand business process. The authors describe the high-level architecture for this scenario, which includes one process and three services. They use Rational XDE to create an object model for the objects used in the process. This object model, and the artifacts exported from IBM WebSphere Business Iintegration Modeler are imported into WebSphere Studio Application Developer Integration Edition.

Part 5: Workflow development, deployment, and testing
January 2005
Implement an executable application for an on demand business process with models from IBM(R) WebSphere(R) Business Integration Modeler and object models from IBM Rational(R) XDE. The authors show you how to use IBM WebSphere Studio Application Developer Integration Edition to create and test an executable workflow application and deploy it on IBM WebSphere Business Integration Server Foundation. They also describe service and data integration, run-time bindings, and deployment aspects of the application.

Part 6: Apply customization policies and rules
February 2005
Develop and manage rules to enforce the policies for on demand processes. As business owners introduce new requirements to respond to changing business conditions, on demand processes must adapt accordingly. Rapid customizations are achieved during execution through dynamic changes to the rules that enforce the business policies. Externalizing the rules allows analysts and other less-technical users to effectively modify the policies without changing the process logic.

Part 7: Monitor business processes and emit events using CEI
March 2005
Compare four different ways to emit events using the Common Event Infrastructure (CEI). The authors show you how to document the key performance indicators (KPIs) using IBM WebSphere Business Integration Modeler V5.1 and how to create the corresponding events in WebSphere Business Integration Server Foundation V5.1.1.

Part 8: Business process monitoring -- Create key performance indicators
March 2005
Learn how to receive the Common Base Events (CBE) using Event Access and Event Distribution services provided by Common Event Infrastructure (CEI) that comes with IBM WebSphere Business Integration Server Foundation V5.1.1. Learn, also, how to use an object model for event-to-KPI (Key Performance Indicators) mapping to create KPIs from events, as demonstrated in this article.

Part 9: Involve people
April 2005
Involve people in an on demand business process using staff activities in WebSphere Business Integration Server Foundation. Learn how a staff activity can be used to resolve unexpected problems during execution and how people are assigned to the activities by means of staff queries.

Part 10: Develop message adapters for CICS transaction servers
April 2005
This paper provides an architecture overview and step-by-step methods for developing the artifacts needed to invoke legacy CICS® business logic from a workflow process using the SOAP for CICS feature, which the CICS Transaction Server (TS) V2.3 provides. The authors shows you how to create message adapters in CICS TS for XML to COMMAREA conversion.