Create the monitor model to monitor the business process

You use a wizard to auto-generate the monitor model from the process. You will then have two monitor models, the business measures model from the process in WebSphere^® Business Modeler (the high-level model) and the monitor model generated from the process in WebSphere Integration Developer (the low-level model). The high-level model contains the monitor elements that need to be implemented in the final monitor model. The low-level model contains the monitoring context instance creation, termination, and correlation information based on the events generated from WebSphere Process Server.

1. Generate the monitor model in WebSphere Integration Developer from the BPEL process by completing the following steps:
   1. In the Business Integration view, right-click ClipsAndTacksF1 and select Monitor Tools > Generate Monitor Model.
      
   2. For the Target monitor project, enter clips.
   3. Click New Project, then click Finish.
   4. For the Target monitor model name, enter clipsbpm and click Next.
      
   5. In the Generate Monitor Model dialog box, in the Choose what to monitor section, navigate the Event Source field to ClipsAndTacksF1 > ClipsAndTacksF1Module > Order Handling (Future 1) and select Order Handling (Future 1) as follows:
      
   6. On the Monitoring Templates tab, click Select All. The generated monitor model will contain monitoring elements that track all of the listed process characteristics. One of these characteristics is the Average Elapsed Duration, which will satisfy the requirement in the business measures model to track the average processing time.
      
   7. In Event Source, select ClipsAndTacksF1 > ClipsAndTacksF1Module > Order Handling (Future 1) > Order Handling (Future 1) > OrderHandlingFuture1_Flow:
      
   8. On the Emitted Events tab, click Select All. The generated monitor model will subscribe to these events. The events are for link traversals. These BPEL links represent the decision elements from WebSphere Business Modeler. The events indicate whether a link was skipped or if it was traversed because the condition was true or false. Note the event name OrderHandlingFuture1_FlowCONDTRUE. This will be used heavily in the monitor model.
      
   9. In the business measures model, it was specified to track the processing time for each task. To implement that, click the Monitoring template for elapsed duration for each activity. To do this, select Cancel Order and Send Notification. Then on the Monitoring Templates tab, select Average Elapsed Duration – Measure.
      
   10. Repeat step 1.h for the remaining three invoke activities and the two human tasks. Do not repeat step 1.h for the receive element, Order Handling (Future 1)Receive. Click Next.
2. Simplify the monitor model so that there is only one monitoring context. A monitoring context represents the entity or thing that is to be monitored. Additionally, simplify the monitor model by creating event groups to organize the events and provide structure in the monitor model:
   1. For each of the invoke activities and the human tasks, change the implementation to Event group by clicking in the Implementation column and selecting Event Group from the drop-down list.
      
   2. Click Next. You can preview the model here.
   3. Click Finish. When prompted, click yes to switch to the Business Monitoring perspective. When prompted, do not launch Getting Started. The monitor model opens in the monitor model editor.
   4. Check the Problems view. If you didn’t emit events that the monitor model requires, then the Problems view will show warnings to indicate that the events are missing. If you see these messages, update the monitor event settings in the module and then synchronize the model with the application (in the project tree, right-click the model and select Synchronize with Application).
      
3. Import the business measures model from WebSphere Business Modeler. Many errors will result from the following actions, but these will be fixed as you progress through the steps. To import the business measures model, complete the following steps:
   1. In the project tree, right-click the clips project and select Import > General > File System. Then click Next.
   2. Browse to the location that contains the business measures model (OrderHandling (Future1).mm) from WebSphere Business Modeler. Then select the two .svg files and the monitor model:
      
   3. Ensure that the Into folder is clips and then click Finish. There will be many errors in the Problems view because the metrics for the business measures model have not been implemented yet.
   You now have the auto-generated model (clipsbpm.mm) and the business measures model (Order Handling (Future 1).mm) in your clips project:
   
4. Merge these two monitor models together. There are several options. You could use the menu options Combine Monitor Models or Compare With > Each Other. Because the names of the monitoring contexts, KPI contexts, and cubes are different in the two models, using the merge tools will result in a monitor model that is a union of the two monitoring contexts, two KPI contexts, and two cubes. The merge options work better if both models start from a common base so that these containers have the same name. In our example, it is easier to copy the monitor elements functions from one model to the other.
   1. Open the editor for both monitor models, clipsbpm.mm and Order Handling (Future 1).mm, by double-clicking each of them in the project tree.
   2. Start Copying elements from the Order Handling (Future1) to clipsbpm. Click the Monitor Details Model tab for Order Handling (Future1). Select the six percentage metrics (Acceptable Credit Risk? No Percentage, Acceptable Credit Risk? Yes Percentage, Account in Good Standing? No Percentage, Account in Good Standing? Yes Percentage, Approve Without Review? No Percentage, and Approve Without Review? Yes Percentage), right-click, and select Copy.
      Note: There are several additional metrics in the details model for Order Handling. These are for processing time, but you will not need them because they were created automatically in clipsbpm when you selected the duration monitoring templates in the generation wizard.

      
   3. Click the Monitor Details Model tab in clipsbpm, and then right-click Order Handling (Future 1) and paste the metrics that you copied.
   4. Save your work. You will have errors for the pasted metrics.
   5. Click the KPI Model tab for Order Handling (Future1). Select all of the elements: the two KPIs and the two triggers. Right-click and select Copy.
      

   6. Click the KPI Model tab in clipsbpm, and then right-click Template KPI Context and paste the elements that you copied.
   7. Save your work.
   8. Click the Dimensional Model tab for Order Handling (Future1). Select all of the elements, except for the seven measures with names that end with _Processing_Time (these measures are already in the clipsbpm model). Right-click and select Copy.
      

   9. Click the Dimensional Model tab in clipsbpm and then right-click Order Handling (Future 1) Cube and paste the copied elements.
   10. Save your work.
5. For the seven processing time measures that you did not copy, you will need to copy the tracking keys from Order Handling (Future1) to clipsbpm. WebSphere Business Modeler needs the tracking keys when you export WebSphere Business Monitor data back to WebSphere Business Modeler.
   1. In the dimensional model of Order Handling (Future1), click the measure Average Cancel Order and Send Notification Processing Time. You will see the tracking key in the editor as in the following screen capture.
      

   2. Select the text for the tracking key and then copy it to the corresponding measure of the dimensional model in clipsbpm: Cancel Order and Send Notification Average Elapsed Duration.
   3. Repeat step 5.b for the following six processing time measures.
      • From Average Check Customer Account Status Processing Time to Check Customer Account Status Average Elapsed Duration
      • From Average Check Order Handling for Automatic Approval Processing Time to Check Order Handling for Automatic Approval Average Elapsed Duration
      • From Average Order Handling (Future 1) Processing Time to Order Handling (Future 1) Average Elapsed Duration
      • From Average Review Order Processing Time to Review Order Average Elapsed Duration
      • From Average Ship Order to Customer Processing Time to Ship Order to Customer Average Elapsed Duration
      • From Average Update Order Database Processing Time to Update Order Database Average Elapsed Duration
      Note: For Order Handling in clipsbpm there is a working duration measure and an elapsed duration measure, so update the tracking key for the elapsed duration only.
6. The diagram view is based on SVG images and shape sets. To create shape sets in the SVG diagrams, complete the following steps:
   1. Click the Visual Model tab in clipsbpm. For Selected Context equal Order Handling (Future 1), click Browse for SVG File. Navigate to clips and select Order_Handling__x0028_ Future_1_x0029__MDM_Order_Handling__x0028_ Future_1_x0029__MC.svg and click OK. When prompted, choose to create shape sets.
   2. Change the Selected Context to Template KPI Context and then click Browse to select an SVG file for this context. Navigate to clips and select Order_Handling__x0028_ Future_1_x0029__KM_Order_Handling__x0028_ Future_1_x0029__KC.svg; click OK. When prompted, choose to create shape sets.
   3. Save your work.
   4. Close the Order Handling monitor model because you have copied everything you needed from this model to clipsbpm.
   5. To remove the numerous errors that are associated with this model in the Problems view, right-click OrderHandling (Future1) in the project tree and select Delete.