View Message Flows
- Former user (Deleted)
- Former user (Deleted)
Message Flows provide graphical or textual views of the globally-engaged handlers in the system at a given time. This functionality is provided by the following feature:
Name : WSO2 Carbon - Message Flows Feature
Identifier : org.wso2.carbon.message.flows.feature.group
If the above feature is not included in your product by default, you install it using the instructions given in section, Feature Management.
Modules use handlers to engage in different message flows at defined phases. You can observe the handlers invoked in each phase of each flow in real time. For example, the Apache/Rampart module defines handlers in the security phase of each flow, which handles the security aspects of the messages that are transferred through these flows. Therefore, if the Rampart module is engaged, you can see the Apache/Rampart handlers in the message flows in real time.
Follow the instructions below to access the Message Flows.
1.Log on to the product's management console and select "Monitor -> Message Flows".
2. The Message Flows page with the graphical view of the message flows appears. 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 diagram below.
3. 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.
4. You can see the text view of message flows. Click on the "Show Text View" link.
5. The page with the text view of message flows appears. The textual view provides the name and the fully qualified classes of all handlers within each and every phase.
