This chapter includes the following topics:
An invocation to a service from a composite may result in an error. This error is captured as a fault in the service. You can view the details of the instances and faults of the inbound adapter in the Instances and Faults section of the Dashboard page.
To monitor instances and faults for an inbound adapter:
Navigate to the SOA composite application by using either of the following options:
From the SOA Infrastructure Menu... | From the SOA Folder in the Navigator... |
---|---|
|
|
Monitor the instances and faults for an inbound adapter:
The Dashboard page is, by default, selected once you select the composite under soa-infra.
Select the Flow instance tab. Under that the Instances with Faults Section is displayed. You can view the instances and faults within the Instances and Faults section.
The details of the fault is displayed in a line chart in the Instances and Faults section, which you can search within to find recent faults. This line chart shows the total number of outgoing messages since the start of the server, and the total number of faults since the start of the server.
For more information about monitoring adapters, see Understanding Technology Adapters.
You can view the details of the recent faults and rejected messages of the inbound adapter under the Flow Instances tab of the Dashboard page.
To monitor the recent rejected messages for an inbound adapter:
Navigate to the SOA composite application by using either of the following options:
From the SOA Infrastructure Menu... | From the SOA Folder in the Navigator... |
---|---|
|
|
Monitor the recent faults and rejected messages for an inbound adapter:
Click Dashboard.
The Dashboard page is displayed.
View the recent faults and rejected messages listed in Instances and Faults section within the Flow Instances tab.
A list of recently rejected faults and messages with details such as error message, fault time, and the business flow instance ID is displayed.
For more information about monitoring adapters, see Understanding Technology Adapters.
You can view the details of the faults and rejected messages of an inbound adapter in the Flow Instances page.
To monitor the rejected messages for an inbound adapter:
Navigate to the SOA composite application by using either of the following options:
From the SOA Infrastructure Menu... | From the SOA Folder in the Navigator... |
---|---|
|
|
To monitor the faults and rejected messages for an inbound adapter:
View the recent faults and rejected messages listed in Instances and Faults section within the Flow Instances tab.
A list of faults and rejected messages with details such as error message, fault time, and business flow instance ID is displayed.
For more information about monitoring adapters, see Understanding Technology Adapters.
Use the Search feature to search for faults and rejected messages for an inbound adapter.
To search for faults and rejected messages for an inbound adapter:
Navigate to the SOA composite application by using either of the following options:
From the SOA Infrastructure Menu... | From the SOA Folder in the Navigator... |
---|---|
|
|
Select the Flow instance tab to obtain the Instances with Faults section.
Enter any or all of the following search options:
Instances within a Time Range
Enter any part of the error message text.
Time
Enter the ID of the fault.
Composite
Select Initiating or Participating from the toggle.
State
Select Active, which can be one of All Active, Recovery, Running, Suspended, or Inactive, which can be one of All Inactive, Completed, Failed or Aborted
Fault
Select a type from the list of faults available. These include: All Faults, Recovery Required, Nonrecoverable, Recovered, System Auto Retries
You can also choose to search for only Recent Instances, Instances with Faults, Recoverable Instances.
Click Search to start the search operation.
The fault or rejected message matching the criteria you specified is displayed.
Click Reset to reset the search criteria.
For more information about configuring adapters, see Understanding Technology Adapters.
You can directly delete rejected messages from the database by specifying a search criteria.
To delete rejected messages for an inbound adapter:
Navigate to the SOA composite application by using either of the following options:
From the SOA Infrastructure Menu... | From the SOA Folder in the Navigator... |
---|---|
|
|
Select the Flow instance tab to obtain the Instances with Faults section.
Click the Delete Selected Flow Instances icon
The Delete Selected Flow Instances dialog is displayed.
Click Delete.
To delete a fault, you must delete the associated business flow instance from the Instances page.
For more information about configuring adapters, see Understanding Technology Adapters.
You can view the details of the properties of an inbound adapter in the Properties page.
To monitor the properties for an inbound adapter:
Navigate to the SOA composite application by using either of the following options:
From the SOA Infrastructure Menu... | From the SOA Folder in the Navigator... |
---|---|
|
|
Monitor the properties for an inbound adapter:
Click Properties.
The Properties page is displayed for that adapter.
A list of properties with details such as name and value is displayed.
Note:
For any adapter that has an inbound asynchronous request-reply scenario (the Get Message operation preceding the Send Reply operation), only details about the activation specification are displayed; details about the interaction specification are not displayed.
For more information about monitoring adapters, see Understanding Technology Adapters.
An invocation to a reference from a composite may result in an error. This error is captured as a fault in the reference. The details of the instances and faults of the outbound adapter can be viewed in the Instances and Faults section of the Dashboard page.
To monitor instances and faults for an outbound adapter:
Navigate to the SOA composite application by using either of the following options:
From the SOA Infrastructure Menu... | From the SOA Folder in the Navigator... |
---|---|
|
|
Monitor the instances and faults for an outbound adapter:
Click Dashboard.
The Dashboard page is displayed.
View the instances and faults listed in the Instances and Faults section, after clicking on the Flow Instances tab.
The details of the fault is displayed in a line chart in the Instances and Faults section. This line chart shows the total number of outgoing messages since the start of the server, and the total number of faults since the start of the server.
Select Table View to see an expanded table view listing to see total number of messages since server start or total number of faults since server start, which you can sort by ascending, or descending order, or you can sort by more advanced criteria by choosing advanced.
For more information about monitoring adapters, see Understanding Technology Adapters.
The details of the instances and faults of the outbound adapter can be viewed in the Faults page.
To monitor faults for an outbound adapter:
Navigate to the SOA composite application by using either of the following options:
From the SOA Infrastructure Menu... | From the SOA Folder in the Navigator... |
---|---|
|
|
To monitor the faults for an outbound adapter:
Select the Flow instance tab to obtain the Instances with Faults section.
Select Table View to see a listing of faults, total number of incoming messages since server start and total number of faults., and to sort the displayed data according to your preference.
For more information about monitoring adapters, see Understanding Technology Adapters.
Use the Search feature to search for faults for an outbound adapter.
To search for faults for an outbound adapter:
Navigate to the SOA composite application by using either of the following options:
From the SOA Infrastructure Menu... | From the SOA Folder in the Navigator... |
---|---|
|
|
Select the Flow instance tab to obtain the Instances with Faults section.
Click the Search icon at the right to execute any saved Searches.
In the Search Options section, enter any or all of the following search criteria:
Select the Reset icon to reset the search criteria.
Select the Disk icon to save the custom search.
Select the Bookmark icon to generate a bookmarkable link.
Select the Funnel icon on the right to customize (that is, add or remove) filters.
On the Add/Remove Filters link t you can set Filters by you can add or remove Filters by Time, Composite, Resequencer, Flow Instance, State, Fault, or User.
Using Search Options, you can set Recent Instances, Instances with Faults, Recoverable Instances, All Saved Searches.
You can either select Customize Time Period, or Last number of hours, minutes, days or weeks.
Choose Participating or a Composite.
Choose State, which can be All Active, Recovery, Suspended, Running.
Chose Fault, which can be any one of All Faults, Recovery Required, Nonrecoverable, Recovered, System Auto Retries.
Click Search to start the search operation.
The fault matching the criteria you specified is displayed.
For more information about configuring adapters, see Understanding Technology Adapters.
The details of the properties of the outbound adapter can be viewed on the Properties page.
To monitor properties for an outbound adapter:
Navigate to the SOA composite application by using either of the following options:
From the SOA Infrastructure Menu... | From the SOA Folder in the Navigator... |
---|---|
|
|
Monitor the properties for an outbound adapter:
Click the Properties tab.
The Properties page is displayed.
Click View.
A list of properties with details such as name and value is displayed.
Note:
Where an adapter has an outbound asynchronous request-reply scenario (the Send Message operation preceding the Get Response operation), only details about the interaction specification are displayed, and details about the activation specification are not displayed.
For more information about monitoring adapters, see Understanding Technology Adapters.
Oracle Fusion Middleware components generate log files containing messages that record all types of events, including startup and shutdown information, errors, warning messages, access information on HTTP requests, and additional information. There is only one logger for all Oracle JCA Adapters, and the logger is called oracle.soa.adapter
.
To monitor the File adapter logs:
For information about configuring logs, see Configuring Log Files. For information about diagnostics related to logs, see Diagnosing Problems with SOA Composite Applications.
Oracle Adapter Configuration reports provide information on how you have configured Adapters.They provide diagnostics information in addition to Snapshot reports and Monitoring reports. Without this the support, customer has to go through multiple consoles and logs for diagnosis. There are many more Adapter properties than those reported on in the diagnostic reports; however, the reports provide information from the most relevant properties.
The configuration report provides information on the service endpoints; each of these reports correlate and provide you with information that would otherwise require you to do a large amount of moving between different reports to find information related to Adapter configuration.
Adapter Configuration reports capture:
Connection Factory properties
Service Definition Properties (Activation Properties and other specs related to a service endpoint).
Service Tuning Properties - Service endpoint properties used to tune the service to alter performance items such as throughput and throttling.
Reference Definition Properties (Interaction Properties and other types of specs involved in Reference endpoint).
Reference Tuning Properties - Reference endpoint properties used to tune the service to alter performance factor such as throughput and throttling.
The Reports do not provide information on Adapter-specific properties that are not part of Connection Factory properties. For example, the reports do not provide information on LDAP RootDSE properties.
You can enable the following Adapter reports to display in Oracle Enterprise Manager Fusion Middleware Control:
You can enable reports by checking the box at the top of the Monitoring Reports page. Another way to enable reports to add corresponding property on the Properties tab.
Within a Monitoring report, showing real-time monitoring statistics, the activation spec provides configuration-related information, including:
EIS connection configurations, displayed as connection factory properties.
Resources that are being accessed. These include Managed Connections and the Most Recent Timestamp for such connections.
Additional tuning information, such as Currently Free Connections and Maximum Pool Size for Connections.
Figure 26-1 shows the appearance of the Monitoring report in the context of the Diagnosability and Snapshot reports. This report shows a information related to a service endpoint.
Figure 26-1 Monitoring Report Showing Statistics for a Service Endpoint
See Figure 26-1 for a description of the elements in the Monitoring Report.
Table 26-1 Adapter Monitoring Report Elements
Element | Description |
---|---|
Server Name |
The name of the server where the endpoint is deployed. |
EIS Connection Status |
Indicates if the EIS is connected to the Endpoint. You can click status icon to obtain stack trace if status is Not connected. |
Managed Connections |
Connection pool statistics for the managed connections for this Adapter to Enterprise Information System (EIS) systems. |
Currently Free |
The pool size of this Connector connection pool. |
Average Number Used |
The running average usage of created connections that are active in the Connector Pool since the pool was last shrunk. |
Currently Free |
The current total free connections. |
Maximum Pool Size |
The maximum capacity configured for this Connector connection pool. |
Most Recent Time Stamp |
The most recent time stamp for last message publication and last service activation. |
Last Message Publication |
Last message published to the fabric for a service endpoint; last message published to the EIS for a reference endpoint. |
Last Service Activation |
Last time the service endpoint was activated. Only for a service endpoint. |
Last Reference Interaction |
Last time the reference endpoint was activated. Only for a reference endpoint. |
The Configuration report within the Diagnosability Report from the Oracle Enterprise Manager Fusion Middleware Control dashboard shows a summary of connection factory, binding and activation properties for a specific service endpoint.
Figure 26-2 shows an Adapter Configuration Report for a Service Endpoint, showing Deployment Configuration Type, and information about EIS Connectivity and Service Properties, including definition properties and Tuning Properties, in this case properties that are specific to a File Adapter.
Figure 26-2 Adapter Configuration Reports
See Table 26-2 for a description of the elements in the Adapter Configuration Report.
Note that you need to select Related Links (at the top right of the page) to initiate the process of configuring a connection factory within the WebLogic Server Console.
Table 26-2 Adapter Configuration Reports Elements
Element | Description |
---|---|
Deployment Configuration Type |
Indicates if the endpoint is part of an active-active or active-passive configuration. This is only displayed for a service endpoint. |
EIS Connectivity |
Provides information about connection factory properties related to this endpoint and its connection to the Enterprise Information System. |
Service Properties |
Lists Definition Properties, used to define services specific to this endpoint, and Tuning Properties, used to tune services specific to this endpoint. For Reference Endpoints, there are Reference Properties which include Definition Properties and Tuning Properties. See the User's Guide to Technology Adapters appendix for the complete list and definitions of the properties. |
The Snapshot Reports section of the Service or Reference Adapter Reports Page provides connection downtime and message statistics over a specified period.
Snapshot reports aggregate historical data over a selected period of time.
The default for snapshot data persistence is 15 minutes, which is the period of time collection over which the captured data persists when Write to database is checked. You can configure the snapshot interval from the snapshotInterval
property in the Properties tab. Because the default value of some properties on the Properties tab is not shown explicitly, you might need to add snapshotInterval
property from the properties page and then modify it as you require. You can select Write to Database on a Report Screen to have the data persisted.
Similarly, you can add or modify enableSnapshots
(enables Write to Database) and select the Enables Reports
checkbox (enables Reports).
Note that you must understand each Snapshot report in the context of the functioning of the specific adapter; for example, for the Database Adapter, the payload size that is reported and displayed is the size of XML produced by the Adapter, never the size of XML consumed by the Adapter.
Where an adapter has no output, the size is reported as 0.
For the same service endpoint, you can correlate information from the Snapshot report and the Monitoring Report.
Figure 26-3 shows an example Snapshot Report, with the Message Statistics tab selected. The Report shows:
Data will be retrieved over the last 24 hours
The name of the server for which information is being collected
Average Message Size, in bytes
Maximum Message Size, in bytes
Minimum Message Size, in bytes
Total Message Size, in bytes
Number of Messages
Data Location, specifying Persisted or In-Memory, as indicated by an icon and tooltip
Write to Database-enables data persistence. By default, the data is not persisted. Note that when enabled, persistence is enabled concurrently for both EIS Connection statistics and Message statistics at once. Once you enable persistence, the value for writes to the database is displayed (for example, "every 15 minutes".)
Figure 26-3 Snapshot Report, with Message Statistics Tab Selected
Figure 26-4 shows an example Snapshot Report, with EIS Connection Downtime, or the down shown. The Report shows:
Server Name
The Start EIS Downtime-when the connection downtime began
The End EIS Downtime-when the connection downtime ended
Error Summary-A summary of the errors that might be related to the downtime.
Total EIS Connection Downtime.
Data Location, specifying Persisted or In-Memory, as indicated by an icon and tooltip
Show XML button, which when clicked on provides XML data for the information that is displayed.
Figure 26-4 Snapshot Report with EIS Connection Downtime Tab Selected
The snapshot persistence period can provide historical data over the period the data is persisted; this period is different than the global refresh period for the Oracle Enterprise Manager Fusion Middleware Control.
You must also distinguish the Snapshot Interval (default is 15 minutes) versus the Retrieve Data period, which is defaulted to one day.
Persisted and In-memory data is shown per query criteria (that is, EIS connection downtime falls within the time range used for searching or message publication time is within the time range used for searching).
The persistence setting provides a way to guard saved data from crashes and downtime. However, there is a performance cost to retaining saved data.
A Data Location column in the reports contains either or both of two icons which signify the place of origin of the data in the reports in the appropriate row: either from persistent data or from in-memory data.
Also note that data is not persisted in the following circumstances.
For non-persisted (in-memory) data, when the following occur:
Write to database is unchecked
The adapter's composite application is shutdown or retired
Composite is un-deployed
The Adapter endpoint is de-activated (for service endpoints)
The SOA server is bounced
Auto purge occurred
For persisted data, data is not persisted when the following occur:
Auto purge occurred
You can search and retrieve past data. Therefore, the Retrieve Data search control is always available for data that persists. The search feature is specific to Enterprise Information System (EIS) Connection statistics and is distinct from Message statistics.
Table 26-3 provides information about the different elements found in the Snapshot Adapter Reports and their meaning.
Table 26-3 Snapshot Adapter Report Elements
Element | Description |
---|---|
EIS Connection Downtime |
(Only shown for the service downtime.) |
Select a Time Range |
The time range filter delimits the statistics displayed in the snapshot reports to a specified number of minutes, hours, days, or weeks. |
Show XML |
Shows the EIS connection downtime in an XML format. |
Server Name |
The name of the server connected to this Adapter for which messages are being displayed. |
End EIS Connection Downtime |
Time at which the EIS connection is restored. |
Start EIS Downtime |
The time at which the EIS connection is lost. |
Error Summary |
Select Error Summary to provide stack trace. |
Message statistics |
|
Server Name |
The name of the server where this endpoint is displayed. |
Average Message Size |
Average message size processed for the filtered snapshot interval. |
Maximum Message Size |
Maximum message size processed for the filtered snapshot interval. |
Minimum Message Size |
Minimum message size processed for the filtered snapshot interval. |
Total Message Size (Bytes) |
Sum total of all the messages processed for the filtered snapshot interval. |
Number of Messages |
Number of messages processed for the filtered snapshot interval. |
Data Location |
Specifies Persisted or In-Memory, as indicated by an icon and tooltip. |
Write to Database |
Select this checkbox to enable persistence. The value (for example, every 15 minutes) shows how often that write to the database happens, when enabled. By default the check box is not selected. Persistence is enabled for both EIS Connection starts and Message statistics at the same time. The screen indicates the following: “Select to persist the data. Persisted data remains available in case of downtimes or crashes, or if you disable the reports; but it impacts performance. Persistence operations involve a snapshot scheduler and repetitive I/O (disk read and write) operations. Persistent operations are different from in-memory operations because I/O operations from memory are faster than Database operations. |
The following tables show, for each Adapter type, the configuration report category, the available property name, and a description of each property. Although adapter configuration properties can be set at service/reference Mbean and Adapter binding Mbean, the Adapter configuration report shows only properties from the Adapter binding Mbean.
Table 26-4 MSMQ Adapter Connection Factory Properties
|
Table 26-5 MSMQ Adapter Service Definition Properties
|
Table 26-6 MSMQ Adapter Service Tuning Properties
|
Table 26-7 MSMQ Adapter Reference Definition Properties
|
Table 26-8 MSMQ Adapter Reference Tuning Properties
|
Table 26-9 File Adapter Connection Factory Properties
|
Table 26-10 File Adapter Service Definition Properties
|
Table 26-11 File Adapter Service Tuning Properties
|
Table 26-12 File Adapter Reference Definition Properties
|
Table 26-13 File Adapter Reference Tuning Properties
|
Table 26-14 FTP Adapter Specific Connection Factory Properties (Properties in addition to those for file adapter)
|
Table 26-15 FTP Adapter Specific Service Definition Properties (Properties in addition to those for file adapter)
|
Table 26-16 FTP Adapter Specific Service Tuning Properties (Properties in addition to those for file adapter)
|
Table 26-17 Socket Adapter Connection Factory Properties
|
Table 26-18 Socket Adapter Service Definition Properties
|
Table 26-19 Socket Adapter Service Tuning Properties
|
Table 26-20 Socket Adapter Reference Definition Properties
|
Table 26-21 UMS Adapter Connection Factory Properties
|
Table 26-22 UMS AdapterService Definition Properties
|
Table 26-23 UMS Adapter Service Tuning Properties
|
Table 26-24 UMS Adapter Reference Definition Properties
|
Table 26-25 UMS Adapter Outgoing Message Properties
|
Table 26-26 LDAP Adapter Connection Factory Properties
|
Table 26-27 LDAP Adapter Service Definition Properties
|
Table 26-28 LDAP Adapter Service Tuning Properties
|
Table 26-29 LDAP Adapter Reference Definition Properties
|
Table 26-30 LDAP Adapter Reference Tuning Properties
|
Table 26-31 DB Adapter Service Definition Properties
|
Table 26-32 DB Adapter Service Tuning Properties
|
Table 26-33 DB Adapter Reference Definition Properties
|
Table 26-34 JMS Adapter Connection Factory Properties
|
Table 26-35 JMS Adapter Service Definition Properties
|
Table 26-36 JMS Adapter Service Tuning Properties
|
Table 26-37 JMS Adapter Reference Definition Properties
|
Table 26-38 JMS Adapter Reference Tuning Properties
|
Table 26-39 AQ Adapter Connection Factory Properties
|
Table 26-40 AQ Adapter Service Definition Properties
|
Table 26-41 AQ Adapter Service Tuning Properties
|
Table 26-42 AQ Adapter Reference Definition Properties
|
Table 26-43 Coherence Adapter Connection Factory Properties
|
Table 26-44 Coherence Adapter Reference Definition Properties
|
Table 26-45 Coherence Adapter Reference Tuning Properties
|
Table 26-46 MSMQ Adapter Connection Factory Properties
|
Table 26-47 MSMQ Adapter Service Definition Properties
|
Table 26-48 MSMQ Adapter Service Tuning Properties
|
Table 26-49 MSMQ Adapter Another Poll-Cycle
|
Table 26-50 MSMQ Adapter Reference Definition Properties
|
Table 26-51 SAP Adapter Connection Factory Properties
|
Table 26-52 SAP Adapter Service Definition Properties
|
Table 26-53 SAP Adapter Reference Definition Properties
|
Table 26-54 Oracle E-Business Suite Adapter Connection Factory Properties
|
Table 26-55 Oracle E-Business Suite Adapter Service Definition Properties
|
Table 26-56 Oracle E-Business Suite Adapter Service Tuning Properties
|
Table 26-57 Oracle E-Business Suite Adapter Reference Definition Properties
|
You can schedule activation and deactivation of the SOA composite JCA Adapter Services from Oracle Enterprise Manager Fusion Middleware Control. Using Oracle Enterprise Scheduler schedule metadata you provide, you can:
Schedule a request for composite JCA Adapter service activation.
Schedule a request for composite JCA Adapter service deactivation.
Oracle Enterprise Manager Fusion Middleware Control also displays the current state of an Adapter endpoint (composite service), which can be either active or inactive.
You can also edit existing metadata to alter your schedule, and you can remove schedules for Adapters.
Note:
Because the Oracle Enterprise Scheduler installation is optional, this feature is not be available if the Oracle Enterprise Scheduler is not installed.
Follow these steps to schedule activation and deactivation of the SOA composite JCA Adapter Services:
To create the schedule metadata, you fill in a form by selecting Define Schedules. The form populates the metadata.
You next use the metadata you have created to schedule the deactivation and activation of an Adapter.
You can edit existing metadata you have created using the Oracle Enterprise Scheduler/Oracle Enterprise Manager Fusion Middleware Control page. To do so: