WSO2 Business Process Server v3.1.0 Documentation

##### Overview

- Home
- Release Note
- WS-BPEL Compliance
- License

##### Downloads

- Releases

##### Installation Guide

- Installing WSO2 BPS

##### Quick Start Guide

- Modeling the process
- Deploying the process
- Testing the process

##### User Guide

- Deploying BPEL Processes
- Deploying Human Tasks
- Managing BPEL processes
- Managing BPEL process instances
- QoS for BPEL processes
- Securing BPEL processes
- Invoking secured partner services
- Versioning
- Management API

##### Human Task Guide

- Human Tasks Quick Start Guide
- Deploying HumanTasks
- Managing Tasks
- Developing a Human Task Artifact
- Human Task Management and Configuration
- Human Task Concepts

##### Administrator Guide

- External data sources Configuration
- Registry Configuration
- Events
- Unified Endpoints
- BPEL Extensions
- Transaction Factory Configuration
- Message Exchange Interceptors
- OpenJPA specific properties
- JMS Transport Configuration
- Process Instance Cleanup Tasks
- Process Hydration and Dehydration
- Enabling Peer-to-Peer(P2P) Communication
- Setting up a BPS Cluster

##### Best Practices

- Process Deployment Best Practices

##### Concepts

- Process Versioning
- Process instance events
- Partner links

##### WS-BPEL Extensions

- Activity Failure and Recovery
- Extension Activities and Extensible Assign Operations
- XPath Extensions
- Iterable ForEach
- Flexible Assigns
- BPEL4People Extension

##### Samples

- HelloWorld
- If-Else
- ForEach
- While
- Repeat Until
- Flow and Links
- Pick
- Synchronous and Asynchronous Service Invocations
- Fault Handling
- Split
- XslTransform
- Compensation Handler
- Event Handler

##### Resources

- FAQ
- External Articles
- Library
- Source Code

##### Community

- Forum
- Mailing Lists

##### Project Information

- Issue Tracking

# View Flows

The View Flows feature provides graphical and textual views of the globally engaged handlers of the system at any point of time.

The modules use the handlers to engage in different message flows at defined phases . There are four different message flows defined in the system (explained in the following section). You can observe the handlers invoked in each phase of each flow in real time.

For example, the Apache/Rampart module (the security module of the system) defines the handlers in the security phase of each flow, which handles the security aspects of the messages that are transferred through these flows. So if the Rampart module is engaged, you will see the Apache/Rampart handlers in the message flows in real time.

## User Interface

1. In the navigator, under Monitor, click Flows. The Message Flows page appears.
2. You can switch between the graphical view and the textual view by clicking Text View or Graphical View as applicable. The textual view provides the name and the fully qualified classes of all handlers within each and every phase.

There are four different flows defined in the system.

In Flow : A correct message coming into the system.

Out Flow : A correct message going out of the system.

In Fault Flow : A faulty message coming into the system.

Out Fault Flow : A faulty message going out of the system.

In each flow, a message passes through a set of phases to reach the service. These phases vary according to the currently engaged modules within the system. The interface displays the current phases in each and every flow as shown in the following figure.

In the graphical view of the message flows, click the links to get a view of the engaged handlers in each phase.

For example, the figure below shows the handlers engaged in the Addressing phase at system start up.