Using the AquaLogic Service Bus Console
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
This section includes the following topics:
Before you can use the Reporting module, you must first create a proxy service in the Project Explorer module, then use the Resource Browser module to add a Report action to the message flow of that proxy service.
To learn more about Reporting, see Reporting in the BEA AquaLogic Service Bus User Guide.
The following table lists the pages you can access from the Reporting module. The tasks and help topics associated with each are provided:
The Summary of Messages page enables you to view a list of reporting messages. The page displays up to 100 messages.
Note: Before you can use the Reporting module, you must first create a proxy service in the Project Explorer module, then use the Project Explorer or Resource Browser modules to add a Report action to the message flow of that proxy service.
A link to the View Message Details page. To learn more, see Viewing Message Details. Report indexes are key value pairs that you use to extract key identifiers from a message context variable. Keys are a convenient way to filter messages. You use the Report action to add key value pairs. To learn more, see Adding an Action. |
|
The date and time that the message was added in the database. |
|
The inbound service associated with the message. The service is a link to the View Proxy Service Details page. To learn more, see Viewing and Changing Proxy Services. |
|
The error code associated with this message, if there is one. You specify error codes when you configure the Raise Error action. To learn more, see Error Messages and Handling and Adding Error Handling for the Proxy Service. |
Note: The service name, error code, and report index fields can use wildcard searches.
Note: You can click Close Filter at any time to remove the filter fields from the display.
Note: To locate a message, you can also do the following:
Reporting in the BEA AquaLogic Service Bus User Guide.
The View Message Details page enables you to view details of a specific message.
The View Message Details page displays the following General Configuration information:
The page displays the following Inbound Service information:
The inbound proxy service associated with this message. This is a link to the View Proxy Service Details page. To learn more, see Viewing and Changing Proxy Services. |
|
The page displays the following Outbound Service information:
The outbound business service associated with this message. This is a link to the View Business Service Details page. To learn more, see Viewing and Changing Business Services. |
|
The page displays the following Report Index information:
Report indexes are key value pairs that you use to extract key identifiers from a message context variable. Keys are a convenient way to filter messages. You use the Report action to add key value pairs. To learn more, see Adding an Action. |
The page displays the following Fault information:
The error code associated with the message, if there is one. You specify error codes when you configure the Raise Error action. To learn more, see Error Messages and Handling and Adding Error Handling for the Proxy Service. |
|
The fault details associated with the error code. These details, if present, are typically a stack trace of where a particular fault occurred, and may be truncated due to a size limitation in the database. The limit is 2048 characters. |
The page displays the following Report Body information:
This link opens another browser that displays the details of the report body. You use an Expression in the Report action to capture the report body text. To learn more, see the procedure for the Report action in Adding an Action. |
Reporting in the BEA AquaLogic Service Bus User Guide.
The Purge Messages page enables you to purge selected messages from the reporting datastore.
Message purging occurs in the background so the Summary of Messages page is not locked up while the purge occurs. Therefore, you can do a purge that takes a while to finish; the length of time depends on how many messages need to be purged. However, if you filter reporting messages, the purging process is slowed down; the Summary of Messages page may display incorrect data as some of the data hasn't been purged yet.
Note: The Purge Messages feature may be useful during design and test phases of your project. However, in a production environment, BEA recommends that the management of the data in your datbase (including purging) is handled by the Database Administrator using database management tools.
To learn more about purging, see Reporting in the BEA AquaLogic Service Bus User Guide.
![]() ![]() |
![]() |
![]() |