31 Monitoring Oracle B2B

This chapter describes how to monitor Oracle B2B using Oracle Enterprise Manager Fusion Middleware Control.

This chapter includes the following topics:

Section 31.1, "Monitoring the B2B Infrastructure"
Section 31.2, "Accessing Oracle B2B from the B2B Infrastructure Page"
Section 31.3, "Viewing the Message Flow of a B2B Binding Component"
Section 31.4, "Viewing Services and References"

31.1 Monitoring the B2B Infrastructure

To monitor the B2B infrastructure, shown in Figure 31-1, EM metrics must be enabled (the default) on the B2B Server Properties page.

Figure 31-1 B2B Infrastructure (SOA Binding)

Description of "Figure 31-1 B2B Infrastructure (SOA Binding)"

Use the B2B Server Properties link under Related Links to change the setting. See Section 30.1, "Configuring B2B Server Properties," for more information on enabling EM metrics.

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

Table 31-1 B2B Infrastructure (SOA Binding)

Area/Field	Description
Top 5 Recently Active Document Types	This section 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 run-time 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	This section 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 run-time 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	This section 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	Indicates the type of transport protocol used in the exchange, for example, File, AQ, and FTP, among others.
Endpoint	Indicates the location from which messages are received. The endpoint can be a URL, folders, or path, among others.
Status	Indicates the status (up or down) of the endpoint (protocol) the last time a connection was attempted.
Outbound Endpoints	This section show 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	Indicates the type of transport protocol used in the exchange, for example, File, AQ, and FTP, among others.
Endpoint	Indicates the location to which messages are sent. The endpoint can be a URL, folders, or path, among others.
Status	Indicates the status (up or down) of the endpoint (protocol) the last time a delivery was attempted.

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

Expand the SOA node.
Select the SOA infrastructure, for example, soa-infra (soa_server1).

Description of the illustration b2b_mon_binding1.gif
From the SOA Infrastructure menu, select Bindings and then B2B.

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

Information displayed in Oracle Enterprise Manager is based on DMS metrics, including inbound and outbound endpoints. Therefore, changes to Oracle B2B run-time data are not necessarily or immediately reflected in the Oracle Enterprise Manager console.

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

31.2 Accessing Oracle B2B from the B2B Infrastructure Page

Use the B2B Console link under Related Links, as shown in Figure 31-2, to log in to Oracle B2B.

Figure 31-2 Accessing Oracle B2B from Oracle Enterprise Manager Fusion Middleware Control

Description of "Figure 31-2 Accessing Oracle B2B from Oracle Enterprise Manager Fusion Middleware Control"

See Oracle Fusion Middleware User's Guide for Oracle B2B for information on using the Oracle B2B interface.

31.3 Viewing the Message Flow of a B2B Binding Component

To view the message flow of a B2B binding component in a SOA composite application instance:

Select a SOA composite application with a B2B binding component.

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

Description of the illustration b2b_mon2.gif
To see all instances of this composite application, click the Instances tab.

Description of the illustration b2b_composite2.gif

Note:
You can see details of a specific message by searching on the instance ID on the Reports tab of Oracle B2B.
Click a specific instance in the Instance ID list to see faults and the flow trace.

Description of the illustration b2b_trace1.gif

The Trace 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.

31.4 Viewing Services and References

The Dashboard tab for a composite application, shown in Figure 31-3, lists the services and references used in the composite.

Figure 31-3 Services and References

Description of "Figure 31-3 Services and References"

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

Details of the B2B reference shown in the figure, B2B_Send_ebMS_PO, are displayed on the Reference Home page, shown in Figure 31-4.

Figure 31-4 The B2B Reference, B2B_Send_ebMS_PO

Description of "Figure 31-4 The B2B Reference, B2B_Send_ebMS_PO"

The Instances and Faults area shows the number of outgoing messages and the number of faults since the server was started. See Table 31-1 for a description of the Top 5 Recently Active Trading Partners area. The Recent Faults area lists the faults, including details such as the error message, time of the fault, and the associated composite 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. See Chapter 34, "Monitoring Service and Reference Binding Components," for more information.