Building rich Internet application monitoring workflows and processes (5)

Monitor process activities

In the first two steps (initialization process and workflow enabling) described above, the Process status is visually updated through the iprocesshandle and iinstancehandle API interfaces.

The Oracle BPEL console provides a web-based interface for deploying, managing, and debugging the BPEL process. It is a management tool designed to use JSP pages and servlets (call the API of the BPEL Process Manager. Therefore, you can easily use APIs to develop your own Ria console to provide a business-level process monitoring interface.

The console provides visual feedback for specific process instances, and even links to audit lead data associated with the given steps in the process. The main advantage of the RIA console is that it can perform actual analysis and plan analysis. The console displays all possible steps that a process may take during its execution; it also displays the actual paths used during the execution. You can click any flow node to search for the valid load of BPEL and display the load information in the dialog box.

With the ideal and actual flow path depicted visually and the ability to drill down at the effective load level, the end user can analyze the process and identify the fault point, without the involvement of IT personnel. Figure 4 depicts the actual and ideal process path analysis examples; the "actual" path is marked in green.

Figure 4 Actual and ideal process path analysis

Next, we will introduce how to display the process to achieve this analysis, and how to retrieve audit clue data and apply it in RIA.ProgramVisualizes it.

Display Process

The flex BPEL panel component calls the iprocesshandle interface to retrieve the XML Representation of the entire business model. The BPEL Panel uses the iinstancehandle interface to collect the XML Representation of the audit clue of the current instance. Then, the BPEL Panel compares and merges the two XML representations to create a user interface that can describe the entire model and the path used.

Flex is especially good at executing such operations through its native XML function. FLEX can use the flex Repeater control and the combination of ActionScript to easily combine two XML representations. During combination, they can convert XML into an array, and then use the inherent array processing function to simplify XML merging.

Because the process model XML contains all possible nodes, it actually serves as the basis of the BPEL panel. In each step of the process model, the process model ID and the audit clue model ID are compared. When the process matches the audit ID, the results of the node are copied from the Audit Model to the process model. It is as easy as determining which path to use and which nodes in the query model have the instance data associated with it.