29 Monitoring Oracle B2B

This chapter describes how to monitor Oracle B2B, including monitoring the Oracle B2B infrastructure, viewing Oracle B2B binding component message flow, viewing services and references, and accessing Oracle B2B reports from the Oracle B2B composite flow trace page.

This chapter includes the following topics:

29.1 Monitoring the Oracle B2B Infrastructure

To monitor the Oracle B2B infrastructure, metrics must be enabled (the default) on the B2B Server Properties page. to change the setting, click Related Links then select B2B Server Properties on the B2B Infrastructure (SOA Binding) page.

For more information on enabling metrics, see Configuring Oracle B2B Server Properties.

Table 29-1 describes the information displayed on the B2B Infrastructure (SOA Binding) page.

Table 29-1 B2B Infrastructure (SOA Binding)

Section/Column Description

Top 5 Recently Active Document Types

Shows the active document types with the maximum number of messages exchanged (inbound and outbound combined) during the current session of the server.

The document types listed in this section are from Oracle DMS metrics, triggered by runtime sensors. This data is not persisted. Therefore, if Oracle B2B is restarted, then new data based on Oracle B2B activity appears here.

Number of Messages Processed

Shows the number of document messages exchanged between the host and trading partners. Outbound indicates messages sent from the host to the trading partner and Inbound indicates messages sent from the trading partner to the host.

Average Message Processing Time (sec)

Shows the average document processing time, in seconds, for both outbound and inbound messages.

Average Message Size (kb)

Shows the average document size, in kilobytes, for both outbound and inbound messages.

Errors

Shows the document error count.

Top 5 Recently Active Trading Partners

Shows the active trading partners with the maximum number of messages exchanged (from and to combined) during the current session of the server.

The trading partners listed here are from Oracle DMS metrics, triggered by runtime sensors. This data is not persisted. Therefore, if Oracle B2B is restarted, then new data based on Oracle B2B activity appears here.

Number of Messages Processed

Shows the number of messages sent and received between the host and trading partners. From indicates messages sent from this partner to its trading partner. To indicates messages received by this partner from the trading partner.

Average Message Processing Time (sec)

Shows the average document processing time, in seconds, for exchanged messages.

Average Message Size (kb)

Shows the average document size, in kilobytes, for exchanged messages.

Errors

Shows the document error count.

Inbound Endpoints

Shows the status of the listening endpoints at the time the connection was attempted (not for a later point in time). For example, in an EDI transaction using Generic File transport, when Oracle B2B reads from a directory, that directory is the inbound endpoint.

Protocol

Shows the type of transport protocol used in the exchange, for example, File, AQ, and FTP, among others.

Endpoint

Shows the location from which messages are received. The endpoint can be a URL, folders, or path, among others.

Status

Shows the status (up or down) of the endpoint (protocol) the last time a connection was attempted.

Outbound Endpoints

Shows the status of the delivery endpoints at the time the delivery was attempted (not for a later point in time). For example, in an EDI transaction using Generic File transport, when Oracle B2B writes to a directory, that directory is the outbound endpoint.

Protocol

Shows the type of transport protocol used in the exchange, for example, File, AQ, and FTP, among others.

Endpoint

Shows the location to which messages are sent. The endpoint can be a URL, folders, or path, among others.

Status

Shows the status (up or down) of the endpoint (protocol) the last time a delivery was attempted.

To monitor the Oracle B2B infrastructure using Oracle Enterprise Manager Fusion Middleware Control:

  1. Expand the SOA node.

  2. Select the SOA Infrastructure, for example soa-infra (soa_server1).

  3. From the SOA Infrastructure menu, select Bindings > B2B.

    See Table 29-1 for a description of the information displayed.

Information displayed in Fusion Middleware Control is based on DMS metrics, including inbound and outbound endpoints. Therefore, changes to Oracle B2B runtime data are not necessarily or immediately reflected in Fusion Middleware Control.

For example, if you purge runtime data or make Oracle B2B configuration changes in the Oracle B2B interface, the changes do not affect DMS metrics. To view current runtime data, use the Oracle B2B interface. Fusion Middleware Control data shows Oracle B2B message traffic from the time that the Oracle B2B (SOA) server starts.

29.2 Accessing Oracle B2B from the B2B Infrastructure Page

To log in to Oracle B2B, click Related Links and select B2B Console.

Figure 29-1 Accessing Oracle B2B from Oracle Enterprise Manager Fusion Middleware Control

Description of Figure 29-1 follows
Description of "Figure 29-1 Accessing Oracle B2B from Oracle Enterprise Manager Fusion Middleware Control"

See Using Oracle B2B for information on using the Oracle B2B interface.

29.3 Viewing the Message Flow of an Oracle B2B Binding Component

Use these instructions to view the message flow of an Oracle B2B binding component in a business flow instance.

  1. Select a SOA composite application with an Oracle B2B binding component.

    A list of the recent instances is displayed in the Dashboard page.

  2. To see all instances of this SOA composite application, click the Instances tab.

    Note:

    You can see details of a specific message by searching on the instance ID on the Reports page of the Oracle B2B interface.

  3. Click a specific instance in the Instance ID list to see faults and the flow trace.

    The Flow Trace page displays the following details:

    • The Faults section shows the faults occurring and sensor information collected in the services, service components, and references that comprise the SOA composite application.

    • The Trace section shows the sequence of the message flow through the services, service components, and references that comprise the SOA composite application.

29.4 Viewing Services and References

When Oracle B2B is used as a service (inbound), it receives messages from trading partners and delivers them to SOA composite applications. When Oracle B2B is used as a reference (outbound), it sends messages from the SOA composite application to partners.

The Dashboard page for a composite application lists the services and references used in the composite.

Details of the Oracle B2B reference shown in Figure 29-2, B2B_Send_ebMS_PO, are displayed on the Reference home page.

Figure 29-2 The Oracle B2B Reference, B2B_Send_ebMS_PO

Description of Figure 29-2 follows
Description of "Figure 29-2 The Oracle B2B Reference, B2B_Send_ebMS_PO"

The Instances and Faults section shows the number of outgoing messages and the number of faults since the server was started. See Table 29-1 for a description of the Top 5 Recently Active Trading Partners section.

The Recent Faults section lists the faults, including details such as the error message, time of the fault, and the associated business flow instance ID. Faults can be on the incoming messages processed by a service binding component or on the outgoing messages processed by a reference binding component.

While all errors appear in the Oracle B2B console, only a subset of faults appears in Oracle Enterprise Manager Fusion Middleware Control. This subset includes all inbound messages containing an error after trading partner identification in Oracle B2B.

See Monitoring the SOA Infrastructure,and Monitoring Service and Reference Binding Components for more information.

29.5 Accessing Oracle B2B Reports from the Oracle B2B Composite Flow Trace Page

The Oracle B2B composite Flow Trace page displays Oracle B2B faults and traces. Click an instance to open the Oracle B2B console and view a report.