As an administrator, you will sometimes need to monitor the recent instances and faults of the different components running in the SOA Infrastructure. The execution status and metrics for an instance in a particular engine can be monitored from the Fusion Middleware Control console by right-clicking on soa-infra and navigating to Service Engines | [Component] | Statistics.
Once you are there, you can observe high-level statistics for the selected component engine. The four component engines you can choose from are BPEL, Mediator, human workflow, and Business Rules. Each of their pages display statistics differently, depending on the engine. The following screenshot shows an example of the statistics for the Mediator Engine information.
Figure 6.20: Monitoring at the service engine level, in this case, the Mediator Engine
Here, you can see that the majority of processing is roughly divided between transformations and invocations. The BPEL Engine statistics page, on the other hand, lists the total number of active threads and the total number of active and pending requests.
This service engine statistics page is merely a snapshot but provides a quick insight into the overall performance of the engine and the types of request that burden it.
Oracle SOA Suite 12c has an out-of-the-box EDN that allows you to publish and subscribe to business events. The EDN framework creates the messaging plumbing out of the box so you will not have to create any backend queues in the infrastructure. The default EDN is configured on the database and this uses Oracle Advanced Queuing (AQ) behind the scenes. You can also have an EDN based on JMS that uses the JMS API. In the development and testing stages, access to the EDN logs will be of great help to identify and troubleshoot issues with your EDN implementation. You can change the EDN logging level by following the steps listed here:
- Log in to Oracle Manager Fusion Middleware Control.
- Right-click on soa-infra and then navigate to Logs | Log Configuration.
- Expand the logger nodes to oracle.integration.platform.blocks.event or enter
blocks.eventin the search box and press the Search button to filter the view. - Change the log level of oracle.integration.platform.blocks.event.saq to
TRACE:32. Configuring the logging at this level will ensure that the body of the event message is available in the EDN trace. - Check the Persist log level state across component restarts box and click on the Apply button. This will let the log level survive the managed server restarts.
In addition to configuring the EDN runtime Java loggers as discussed before, you can also enable the debug flag when using the default EDN implementation based on the database. The value of the ENABLED column in the EDN_LOG_ENABLED table in the dehydration store can be set to 1 to make the EDN logs available for review and configuration in a browser console at http://<soahost>:<soaport>/soa-infra/events/edn-db-log.
This page displays the event payload and status (Enqueing event, Enqueing Complete, Dequeing Complete, and so on.). The logging is disabled by default. However, it can be enabled by clicking on the ENABLE link on the page. You can also CLEAR the debug table or RELOAD logs from the same page.