> Tutorials > Tutorial 3. Validating a Loan Application

Tutorials

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Tutorial 3. Validating a Loan Application

AquaLogic Service Bus proxy services can be configured to validate messages passed between clients and business services. Validation actions can be configured at any stage in the message handling pipeline. However these actions are usually configured in the early stages to eliminate erroneous messages. XQuery conditional expressions can be used to perform explicit validation during message processing. You can configure message validation logic in the following ways:

This section includes the following topics:

 

Prerequisites

The following tutorials have to be completed before beginning this tutorial:

 

Tutorial Objectives

The objective of this tutorial is to provide steps to configure AquaLogic Service Bus resources to implement message validation and error handling, using the AquaLogic Service Bus Console. This tutorial includes the following:

Features Highlighted

This tutorial exposes you to the following features of AquaLogic Service Bus:

 

Definition of the Scenario

A primary mortgage company routes every loan application through an AquaLogic Service Bus proxy service that validates the message. If the application is:

The following figure summarizes the logical architecture to support this scenario. It illustrates how AquaLogic Service Bus is positioned in the enterprise system environment to mediate the messaging between the client and the business services.

Figure 5-1 Validating a Loan Application using AquaLogic Service Bus

Validating a Loan Application using AquaLogic Service Bus

Overview of the Run Time Process in AquaLogic Service Bus

In this scenario, you can configure AquaLogic Service Bus to validate an incoming message in the message flow against a schema definition in a WSDL resource. Every field is checked for valid content. All elements must be populated for the application to be valid. When the value of the loan duration field is not an integer, the validate action raises an error. The context variable, $fault, is populated with the error details. The error is trapped by a stage error handler which replaces the body context variable <Notes> field value with the text of the $fault <reason> element. A Report action then saves the error code and the message body, for later viewing and searching in the console. The Reply action returns the body context variable to the client.

In this scenario, the message routing is as follows:

Required Resources

Use the MortgageBroker project folder and the directory structure that you created in the previous tutorial to hold the project artifacts. The resources required for this scenario are described in the following table.

Table 5-1 Routing a Loan Application Tutorial Resources
Resource Name
Description
normalLoan
The WSDL resource
NormalLoan
The external business service used by AquaLogic Service Bus
LoanGateway3
The AquaLogic Service Bus proxy service

 

Steps in This Tutorial

In this tutorial, AquaLogic Service Bus is used to route a loan application within a mortgage company to a target Web Service. The loan application has to be completed correctly for the application to be processed. If there is an error in the application, AquaLogic Service Bus raises a validation exception, and returns an error message to the client.

You will create a proxy service, LoanGateway3, and configure it to route a message to the NormalLoan business service. You will configure the behavior of the proxy service, by performing the following tasks:

Complete the following steps to design and configure the proxy service and the associated resources in AquaLogic Service Bus to resolve this user case scenario:

Step 1: Prepare Your Environment

Ensure that AquaLogic Service Bus is running in the domain you created for the tutorial and that you have completed the steps described in Tutorial 1. Routing a Loan Application.

Step 2: Create a Session

For this tutorial, use the MortgageBroker project folder and the directory structure you created in Tutorial 1. Routing a Loan Application to hold the project artifacts.

  1. Click Create in the Change Center to create a new session.
  2. In the AquaLogic Service Bus Console navigation pane, select Project Explorer.

    3. The Project Explorer pane is opened in the navigation pane and a project page is displayed in the console.

  3. In Project Explorer expand the MortgageBroker project tree to expose the sub folders containing the project artifacts:
    • ProxyService
    • BusinessService
    • WSDL

Step 3: Create the Resources

In this step, you will create the proxy service, LoanGateway3. You will use the existing normalLoan WSDL resource to validate the content of the message. If the loan application is valid and meets the expected criteria it is routed to the existing NormalLoan business service. The normalLoan WSDL resource and the NormalLoan business service were created in “Create the normalLoan WSDL Resource” section in Tutorial 1. Routing a Loan Application.

Create a Proxy Service

In this step, you create a proxy service that is used to route the loan application to the appropriate business service. For creating this proxy service instance, follow the steps described in To Create the Proxy Service, and use the proxy service name and the endpoint URI specified in Table 5-2.

Table 5-2 LoanGateway3 Proxy Service Configuration Settings
Proxy Service Name
LoanGateway3
Service Type
Select normalLoan WSDL
Endpoint URI
/loan/gateway3

Figure 5-2 LoanGateway3 Proxy Service

LoanGateway3 Proxy Service

While configuring the proxy service, accept the default settings for the HTTP transport configuration, message level security configuration, and default SOAP Body Type operation selection algorithm. When the Create a Proxy Service - Summary page is displayed, you must review the summary of configuration settings prior to registering the proxy service.

When you complete this step, the MortgageBroker/ProxyService folder must contain the following proxy services you created in this tutorial and the previous tutorials:

Step 4: Configure the LoanGateway3 Proxy Service

The proxy service is implemented in AquaLogic Service Bus as a message flow. AquaLogic Service Bus message flows define the implementation of proxy services using request and response pipelines. Message flows can include zero or more of the following pipeline pairs:

Each pipeline can include one or more stages, which in turn include actions.

To configure the behavior of the LoanGateway3 proxy service, you must complete the following tasks:

Create a Pipeline Pair

  1. In the AquaLogic Service Bus Console navigation pane, select Project Explorer.

    2. The Project Explorer pane is opened in the navigation pane.

    Note: You must be in a session to edit resources. If you have not already done so, begin a session (click Create in the Change Center) so that you can configure the proxy service and edit the message flow.
  2. In the Actions column associated with the LoanGateway3 proxy service, click the Edit Message Flow LoanGateway3 Proxy Service icon.

    3. The Edit Message Flow page for the proxy service LoanGateway3 is displayed.

  3. Click the LoanGateway3 node, then select Add Pipeline Pair.
    4. Figure 5-3 Add Pipeline Pair Node


    Add Pipeline Pair Node

The PipelinePairNode1 is created and placed in the message flow. Request and response pipelines are displayed for this node as shown in the following figure.

Figure 5-4 Add Pipeline Pair

Add Pipeline Pair

Configure the Request Actions for the LoanGateway3 Proxy Service

You must now configure the Request actions for the proxy service.

  1. Click the Request Add Pipeline Pair icon, then select Add Stage.
  2. Click Stage1, then select Edit Name and Description.
  3. Enter validate loan application and click Save.

    4. The page is displayed as shown in the following figure.

    Figure 5-5 Add Stage to Request Pipeline


    Add Stage to Request Pipeline

Configure an Action to Perform Message Validation
  1. To edit the stage, click validate loan application, then select EditArrow symbolStage. The Edit Stage Configuration page is displayed.
  2. Select Add an Action, then select Message ProcessingArrow symbolValidate from the drop-down list. The Validate action is added to the stage.
    3. Figure 5-6 Add Validate Action


    Add Validate Action

  3. In the Validate statement, click the XPath link to edit the XPath expression. The XPath Expression Editor page is displayed.
    4. Figure 5-7 XPath Expression Editor


    XPath Expression Editor

  4. Click Variable Structures. The Variable Structures pane is displayed.
  5. In the Variables Structure pane, from the Select Structure drop-down list, select body.

    6. A structural representation of the body element is displayed in the Variables Structure pane.

    1. Click + beside the processLoanApp element to expand the element.

      2. The processLoanApp element is within the $body - processLoanApp (request) element.

    2. Click + to expand the loanRequest element.

      3. A graphical representation of the structure of the loan request document is displayed.

      Figure 5-8 Variable Structures Pane


      Variable Structures Pane

    3. Select the Node Variable Structures Pane icon associated with the loanRequest element, drag and drop it in the XQuery Expression text box. The XQuery expression is written in the text box.

      4. ./exam:processLoanApp/loanRequest

      Figure 5-9 XQuery Expression Editor


      XQuery Expression Editor

      Note: The drag and drop functionality works only in Internet Explorer (IE) browsers. If you are using a browser other than IE, select the loanRequest element in the Variable Structures pane. The expression is displayed in the Property Inspector palette. Place the cursor in the XQuery expression text box and click Copy Property. The expression is copied to the text box. You can also copy the expression in the palette and paste it into the XQuery Expression text box.
  6. Click Validate to validate the XQuery.

    7. It is good practice to do this before you submit the expression. The expression is validated for syntax. If there are errors in the expression, they are displayed directly above the Validate button. In this case, the expression is valid.

  7. Click Save.

    8. The Edit Stage Configuration page displays <XPath> which is replaced by the XQuery expression.

  8. In the Variable text field, enter body.
  9. Click Resource and select WSDL from the list. The Select a WSDL page is displayed.

    10. You must validate the message against the resource as the proxy service is based on the WSDL resource that you originally created.

    Figure 5-10 WSDL Resource Selection


    WSDL Resource Selection

  10. In the Select a WSDL page, select the normalLoan WSDL resource.

    11. The Select WSDL Definitions pane is populated with the content categories of the WSDL.

    1. In the Select WSDL Definitions pane, from the Types category, select the WSDL type for this WSDL as loanStruct.
      2. Figure 5-11 WSDL Definitions Pane


      WSDL Definitions Pane

    2. Click Submit to complete the selection.
  11. Select the Raise Error on validation failure option. The Validate action must be displayed as shown in the following figure.
  12. Click Save to save the configuration.
    13. Figure 5-12 Configured Message Validate Action


    Configured Message Validate Action

Note: Message validation must be done as early as possible in a message flow. This prevents unnecessary processing of invalid message content. By raising an exception, further message processing is stopped and an error response is immediately returned to the client.
Note: Messages can be validated at the route node or using a separate Validate action (as in this case). When you create a Validation stage, message processing is more modular since the configured validate actions logically break down the message flow. If multiple validations are performed on a message, the validate action is logically expanded.
Add a Stage Error Handler

The following tasks are performed to configure the Stage Error Handler:

  1. Configure error code checking using an If...Then action and Else actions (Add an If...Then action to the Stage Error Handler).
  2. Add a Replace action within the If portion of the If...Then... action of the stage. This action replaces the Notes element value with the fault context variable reason text. The fault description is returned to the client (Add a Replace Action to the Stage Error Handler).
  3. Add a Report action within the If portion of the If...Then... action of the stage (Add a Report Action to Report the Error).
  4. Add a Replace action within the Then... section of the stage (same as step 2).
  5. Add a Log action within the Then... action of the stage (Add a Log Action Within the Else Action).
  6. Add a Reply with Failure for both conditions of the stage (Add a Reply Action to Reply with a Failure Code).
Add Stage Error Handler Element
  1. Click validate loan application, then select Add Stage Error Handler. The Edit Error Handler page is displayed.
  2. Click Error Handler, then select Add Stage. The stage1 node is displayed.
    3. Figure 5-13 Add Stage Error Handler


    Add Stage Error Handler

  3. Click stage1 and select Edit Name and Description as shown in the following figure.
    4. Figure 5-14 Edit Stage Error Handler


    Edit Stage Error Handler

  4. Change the stage name to Reply, then click Save.
    5. Figure 5-15 Edit Name and Description of Stage


    Edit Name and Description of Stage

    The Edit Stage Configuration page is displayed as shown in the following figure.

    Figure 5-16 Edit Error Handler Page


    Edit Error Handler Page

  5. To edit the stage, click Reply, then select Edit Stage.
Add an If...Then action to the Stage Error Handler
  1. Select Add an Action, then select Flow ControlArrow symbolIf...Then to add an If...Then action to the Reply stage.
    2. Figure 5-17 Add Flow Control Action


    Add Flow Control Action

    The If...Then action is added to the Reply stage.

  2. Click the If...Then action <Condition> link to specify the expression that needs to be validated. The Xquery Condition Editor page is displayed.
    1. Select the Builder pane.
    2. In the Comparison Expression pane within the Expression Builder pane, enter $fault/ctx:errorCode in the Operand textbox.
    3. Select the = Operator from the drop-down list.
    4. Enter "BEA-382505" (including double quotes) in the Value pane.
    5. Select the radio button for the And conjunction.

      6. The Expression Builder Pane is displayed as follows:

      Figure 5-18 Expression Builder Pane


      Expression Builder Pane

    6. Click Add to add expression to the Expressions textbox.

      7. The following expression is displayed in the Expressions textbox:

      Figure 5-19 Expressions Textbox


      Expressions Textbox

  3. Click Save to save the expression and return to the Edit Stage Configuration page.
Add a Replace Action to the Stage Error Handler
  1. Select Add an Action within the Then... portion of the If...Then action to add a Replace statement.
    2. Note: When adding multiple Actions on a page, click the Action preceding the placement of the new action and select the Action to be added from there. Actions are added in sequence.
  2. Select Message ProcessingArrow symbolReplace.
    3. Figure 5-20 Add a Replace Action


    Add a Replace Action

    The Replace statement must be displayed as shown in the following figure.

    Figure 5-21 Replace Statement


    Replace Statement

  3. In the Replace statement, click the <XPath> link to edit the XPath expression. The XPath Expression Editor page is displayed.
  4. In the Variable Structures pane, select body from the Select Structure drop-down list.

    5. A structural representation of the body element is displayed in the Variable Structures pane.

    1. Click + beside the processLoanApp element to expand the element.

      2. The processLoanApp element is within the $body - processLoanApp (request) element.

    2. Click + to expand the loanRequest element.
    3. Select the Node Replace Statement icon associated with the Notes element of $body, drag and drop it on the XPath Expression text box. The following XPath expression is written in the text box.

      4. ./exam:processLoanApp/loanRequest/java:Notes

      Figure 5-22 Replace Statement XPath Expression


      Replace Statement XPath Expression

  5. Click Validate to validate the expression, then click Save.
  6. In the Variable text field, enter body.
  7. Click the <Expression> link to display the XQuery Expression Editor page.
  8. In the XQuery Text pane, enter:
    $fault/ctx:reason/text()
    9. Figure 5-23 Replace Statement XQuery Expression


    Replace Statement XQuery Expression

  9. Click Validate, then Save.
  10. Select the Replace node contents option. You need not replace the entire node.

    11. The Replace action is displayed as shown in the following figure.

    Figure 5-24 Add Error Handler Using Replace Action


    Add Error Handler Using Replace Action

Add a Report Action to Report the Error

Next, you must add a Report action and configure it to report the body context variable as detailed context, and set a key name of errorCode and the key value to the actual error code found in the fault context variable.

  1. Click the Replace Add Error Handler Using Replace Action icon and select Add an ActionArrow symbolReportingArrow symbolReport. The Report action is added to the page.
    2. Figure 5-25 Adding a Report Action


    Adding a Report Action

    The Stage Error Handler is displayed as shown in the following figure.

    Figure 5-26 Stage Error Handler with Report Action


    Stage Error Handler with Report Action

  2. In the Report statement, click the <Expression> link. The XQuery Expression Editor page is displayed.
  3. Accept the default selection of XQuery Text in the page.
  4. In the Variables Structures pane, select body - processLoanApp from the Select Structure drop-down list.
    1. Select the Stage Error Handler with Report Action icon associated with the $body element and drag and drop it on the XQuery Expression text box.

      2. The $body XQuery expression is written in the text box.

      Note: The drag and drop functionality works only in Internet Explorer (IE) browsers. If you are using a browser other than IE, select the body element in the Variable Structures pane. The expression is displayed in the Property Inspector palette. Place the cursor in the XQuery expression text box and click Copy Property. The expression is copied to the text box. You can also copy the expression in the palette and paste it into the XQuery Expression text box.
    2. Click Validate, then Save.

      3. The Edit Stage Configuration page is displayed.

  5. In the key-value pair table, select the Add a key link.
    1. Enter a name for the key. In this case, enter errorCode.
      2. Figure 5-27 Report Action Expression Key


      Report Action Expression Key

    2. In the key value field, click <XPath> link. The XPath Expression Editor is displayed.
  6. In the Variable Structures pane, select fault from the Select Structure drop-down list.
    7. Figure 5-28 Fault Variable Structure


    Fault Variable Structure

    1. Select the Node Fault Variable Structure icon associated with the errorCode and drag and drop it in the XPath Expression text box.

      2. The ./ctx:errorCode expression is written in the text box.

      Figure 5-29 Report Action ErrorCode Expression


      Report Action ErrorCode Expression

      Note: The drag and drop functionality works only in Internet Explorer (IE) browsers. If you are using a browser other than IE, select the errorCode element in the Variable Structures pane. The expression is displayed in the Property Inspector palette. Place the cursor in the XPath expression text box and click Copy Property. The expression is copied to the text box. You can also copy the expression in the palette and paste it into the XPath Expression text box.

      This step enables you to index the reporting data by error code. The keys are a convenient way to identify a message. You can use the error code to search for reporting entries in the reporting module.

  7. Click Validate to validate the XQuery, then click Save.
  8. In the Variable text field, enter fault.

The Report action must be displayed as shown in the following figure.

Figure 5-30 Configured Report Action

Configured Report Action

The Edit Stage Configuration page is displayed as shown in the following figure.

Figure 5-31 Request Actions for LoanGateway3 Proxy Service

Request Actions for LoanGateway3 Proxy Service

Add an Else Action to the Stage Error Handler
  1. Click the If...Then Request Actions for LoanGateway3 Proxy Service icon.
  2. Select Add else Condition to add an Else action to the Stage Error Handler.
Add a Replace Action Within the Else Action
  1. Select Add an Action to add a Replace statement, then select Message ProcessingArrow symbolReplace.
  2. Execute step 3 to step 10 in the Add a Replace Action to the Stage Error Handler section.

    3. The Edit Stage Configuration page is displayed as shown in the following figure.

    Figure 5-32 Edit Stage Configuration Page - Else Replace Action


    Edit Stage Configuration Page - Else Replace Action

Add a Log Action Within the Else Action
  1. Click the Replace Edit Stage Configuration Page - Else Replace Action icon within the Else Action.
  2. Select Add an Action to add a Replace statement, then select ReportingArrow symbolLog.
    3. Figure 5-33 Reporting Log Action


    Reporting Log Action

    The Reply Error Handler Else action is displayed as shown in the following figure.

    Figure 5-34 Reporting Log Action
  3. Click the <Expression> link to display the XQuery Expression Editor page. Enter $fault/ctx:reason/text() in the XQuery Text page.
  4. Click Save to save the expression and return to the Edit Stage Configuration page.
  5. Enter Other than validation error, in the With Annotation text box.
  6. Select Error from the At Severity Level drop-down list.

The completed Else condition must be displayed as shown in the following figure.

Figure 5-35 LoanGateway3 Proxy Service Request Else Actions

LoanGateway3 Proxy Service Request Else Actions

Add a Reply Action to Reply with a Failure Code
  1. Click the Report LoanGateway3 Proxy Service Request Else Actions icon under the If...Then action.
  2. Select Add an ActionArrow symbolthen select Flow ControlArrow symbolReply. The Reply action is added to the page.
  3. Select the With Failure option. The Report Reply Action is displayed as shown in the following figure.
    4. Figure 5-36 Report Reply Action with Failure Code


    Report Reply Action with Failure Code

  4. Click Save to save the stage configuration and return to the Edit Error Handler page.
  5. Click Save to save the error handler configuration.

Step 5: Add a Default Routing Case

You must now add a Route Node to the Pipeline pair and configure it to enable default routing to the NormalLoan business service.

Configure the Route Node
  1. Click PipelinePairNode1, then select Add Route.
    2. Figure 5-37 Pipeline Route Node


    Pipeline Route Node

    The Edit Message Flow page is displayed as shown in the following figure.

    Figure 5-38 Edit Message Flow Page - Pipeline Route Node


    Edit Message Flow Page - Pipeline Route Node

  2. Click RouteNode1, then select Edit Route. The Edit Stage Configuration page is displayed.
  3. Click Add an Action, then select CommunicationArrow symbolRouting.
    4. Figure 5-39 RouteNode1 Communication Routing Action


    RouteNode1 Communication Routing Action

    The Route to action is displayed in the Edit Stage Configuration page as shown in the following figure.

    Figure 5-40 Route to Statement


    Route to Statement

  4. In the Route statement, click the <Service> link to define the service to which you want to route messages. The Select Service page is displayed as shown in the following figure.
    5. Figure 5-41 Route to Statement Service


    Route to Statement Service

    1. Select the NormalLoan business service.
    2. Click Submit and return to the Edit Stage Configuration page.
  5. In the Operation drop-down list, select processLoanApp. Click Save

    6. This is the operation on the NormalLoan business service that is invoked at run time. You have now defined the case for routing the loan application to the NormalLoan business service. The Edit Message Flow page is displayed as shown in the following figure.

    Figure 5-42 LoanGateway3 Proxy Service Message Flow


    LoanGateway3 Proxy Service Message Flow

  6. Click Save to save the configuration and return to the MortgageBroker/ProxyService page.
  7. Click Activate, then Submit.

    8. You can view the map of the message flow of the proxy service as shown in the following figure.

    Figure 5-43 Map of Message Flow for LoanGateway3 Proxy Service


    Map of Message Flow for LoanGateway3 Proxy Service

Step 6: Test the Loan Application Routing Configuration

Now that you have configured AquaLogic Service Bus to work with the client and the target business services, you must test the configuration. To test the routing configuration, you must change the value of the Loan duration (in years) field in the build.xml file. Then you must test the routing logic by verifying whether the proxy service behavior changes for different loan values. If the loan value entered is a non integer, a fault must be triggered and an error message displayed in the Notes field of the message. If the loan value entered is an integer, the message must be routed to the NormalLoan business service. The message returned in the command window indicates whether a validation exception occurred or the message was routed to the appropriate business service.

This section describes the steps to test the proxy service for the above cases and includes the following test case scenarios:

Note: Run the tests in this section multiple times (at least five times) to generate data to enable you to explore the reporting and monitoring features described in Step 7: Using Reporting and Monitoring.
Caution: To run this test correctly, ensure that WebLogic Server is started in the BEA AquaLogic Service Bus 2.6 (ServiceBusTutorial) domain.
To Test Validation Exception
  1. Open a command window. If you have not run the setEnv.cmd to set up your environment, you must do so now.
  2. Change to the following directory:
    3. BEA_HOME\weblogic92\samples\servicebus\examples\src\
  3. In this directory, run the following command at the command prompt: 
    4. setEnv.cmd
    Note: If you are testing the configuration on a UNIX system, run the setEnv.sh script at the command prompt.
  4. Change to the following directory:
    5. BEA_HOME\weblogic92\samples\servicebus\examples\src\examples\webservices\jws_basic\normal
  5. Open build.xml. Scroll to the end of the build.xml file to the string:
    6. <arg line="http://$...
    1. Replace the string found at this location with:
      2. <arg line="http://${wls.hostname}:${wls.port}/loan/gateway3 steve 555 2500 20.5 4.9 notes" />

      This specifies a loan duration value of 20.5 (a non-integer value) and changes the URI to that of the proxy service running in the tutorial domain.

      The input parameters specified on the arg line are described in Table 5-3.

      Table 5-3 Input Parameters
      Input Parameter
      Description
      steve
      a single string representing the client name
      555
      the client ID
      2500
      the requested loan amount
      20.5
      the duration of the loan
      4.9
      the requested interest rate
      notes
      a string that can contain miscellaneous notes

    2. Save changes to the build.xml file.
  6. To test the routing logic of the proxy service, at the command prompt, enter:
    7. ant run

    The following response message from the Web Service is displayed at the command line. 

    [java] Loan Application Response: ALSB Validate action failed validation
    [java] Rate: 4.9
    BUILD SUCCESSFUL

    This response message indicates that a validation exception occurred because the loan duration specified was not an integer.

To Test Routing to NormalLoan Business Service
  1. Navigate to the following directory:
    2. BEA_HOME\weblogic92\samples\servicebus\examples\src\examples\webservices\jws_basic\normal
  2. Follow the procedure in the To Test Validation Exception section, to edit the build.xml file. In this case, to test the NormalLoan business service, you must enter a loan duration value of 20 in the build.xml file (see Table 5-3).
    1. Replace the <arg line="http://$... string with:
      2. <arg line="http://${wls.hostname}:${wls.port}/loan/gateway3 steve 555 2500 20 4.9 notes" />
    2. Save changes to the build.xml file.
  3. To test the routing logic of the proxy service, on the command prompt, enter:
    4. ant run

    The following response message from the Web Service must be displayed at the command prompt: 

    [java] Loan Application Response: APPROVED BY THE <i><b>NORMAL</b></i> LOAN APPLICATION PROCESSING SERVICE
    [java] Rate: 4.9
    BUILD SUCCESSFUL

    The response message indicates that the NormalLoan business service processed the loan request because the loan duration value was an integer.

Step 7: Using Reporting and Monitoring

Now that you have tested the proxy service, you can explore the reporting and monitoring features of the AquaLogic Service Bus Console.

Note: You must have run the tests in Step 6: Test the Loan Application Routing Configuration multiple times (at least five times) to generate data to enable you to explore the reporting and monitoring features.

Reporting

AquaLogic Service Bus includes a JMS Reporting Provider for message reporting. The Reporting module in the AquaLogic Service Bus Console displays the information captured from this reporting provider. You can create your own reporting provider using the Reporting Service Provider Interface (SPI) if you do not wish to use the out-of-the-box reporting provider.

The dashboard of AquaLogic Service Bus Console contains reporting features that are presented in a drill-down format. When you explore the links presented, the information is made available to you.

For more information, see:

Monitoring

AquaLogic Service Bus can monitor and collect run time information for both systems operations and business auditing purposes. AquaLogic Service Bus aggregates run time statistics that you can view on a customizable Dashboard. The Dashboard allows you to monitor the health of the system and alerts you to problems in your messaging services. With this information, you can quickly and easily isolate and diagnose problems as they occur.

For more information, see:


  Back to Top       Previous  Next