ibm. com/developerWorks developerWorks⑧ disjointed global processes in Business Modeler. It is therefore necessary to 1. Define the "glue" that holds them together in a containing business process 2. Define a modeling pattern that enables an end-to-end view of this process These two steps are outlined in the following sections Business rules serve as the" glue The most flexible way to govern the dynamic composition of processes and services is through the use of business rules. In a typical implementation, business rules are used to inspect the data that flows through a particular node or point in the process flow(known as a point of variability) and to make a decision that determines the next path in the flow. In our example a simple rule could be "if the outcome of the validation is an error code of 999 then the corresponding amendment to the order must be authorised by the supervisor". The phrase "must be authorised by the supervisor simply means that the process that implements this capability(Amen Order With Authorization, in the example)is dynamically invoked. WebSphere Business Services Fabric(hereafter referred to as Business Services Fabric)is ideally suited for defining, managing and executing such rules. In Business Modeler, you can designate a service interface to be a Dynamic Assembler(Figure 4)to indicate that it is a Business Services Fabric point of variability Then, you can define rules and policies for the component within Business Services Fabric. Refer to Resources for details on points of variability igure 4 Point of variability identified as a Business services Fabric Dynamic Assembler B%%andeExcepton x 田) Technical Specification +bUsness items V Component Attributes - specfication f Abstract Process Order E2EM Defne the comoonent nformation thatrepresents the target roemer t Amend Order Amend Order wath Authorizes onent splay na te Cance Order to processorder t processorder_CoePM t Update Orde withT e Update order LA Casters 以 Quenes 么 会 ExceoborHender nterface s② Excestortande Define the implementation informaton hand eExceoton Model business processes for flexibility and re-use: A component-oriented approach o Copyright IBM Corporation 2009. All rights reserved Page 5 of 11disjointed global processes in Business Modeler. It is therefore necessary to: 1. Define the “glue” that holds them together in a containing business process 2. Define a modeling pattern that enables an end-to-end view of this process These two steps are outlined in the following sections. Business rules serve as the “glue” The most flexible way to govern the dynamic composition of processes and services is through the use of business rules. In a typical implementation, business rules are used to inspect the data that flows through a particular node or point in the process flow (known as a point of variability) and to make a decision that determines the next path in the flow. In our example, a simple rule could be “if the outcome of the validation is an error code of ‘999’ then the corresponding amendment to the order must be authorised by the supervisor”. The phrase “must be authorised by the supervisor” simply means that the process that implements this capability (Amend Order With Authorization, in the example) is dynamically invoked. WebSphere Business Services Fabric (hereafter referred to as Business Services Fabric) is ideally suited for defining, managing and executing such rules. In Business Modeler, you can designate a service interface to be a Dynamic Assembler (Figure 4) to indicate that it is a Business Services Fabric point of variability. Then, you can define rules and policies for the component within Business Services Fabric. Refer to Resources for details on points of variability. Figure 4. Point of variability identified as a Business Services Fabric Dynamic Assembler ibm.com/developerWorks developerWorks® Model business processes for flexibility and re-use: A component-oriented approach © Copyright IBM Corporation 2009. All rights reserved. Page 5 of 11