Monitoring Faults for an Outbound Adapter

31-2 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite 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.

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. Table 31–1 Cont. B2B Infrastructure SOA Binding SectionColumn Description Monitoring Oracle B2B 31-3

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

See Table 31–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.

31.2 Accessing Oracle B2B from the B2B Infrastructure Page

Use the B2B Console link under Related Links, as shown in Figure 31–1 , to log in to Oracle B2B. Figure 31–1 Accessing Oracle B2B from Oracle Enterprise Manager Fusion Middleware Control See Oracle Fusion Middleware Users Guide for Oracle B2B for information on using the Oracle B2B interface.

31.3 Viewing the Message Flow of an Oracle B2B Binding Component

To view the message flow of an Oracle B2B binding component in a SOA composite application instance: 1. Select a SOA composite application with an Oracle B2B binding component.