Database Reference
In-Depth Information
•
Every composite instance and component instance has metadata that in-
cludes the creation time, last updated time, and state of the instance.
Monitoring faulted instances
One of the more common activities an administrator performs is retrieving a
list of faulted or rejected instances and getting the necessary information to
troubleshoot them. This can be done through the following steps:
1.
Log in to Oracle Manager Fusion Middleware Control.
2.
Click on
soa-infra
.
3.
Click on the
Faults and Rejected Messages
tab.
4.
Click on the first instance ID. A pop-up window will appear, showing the de-
tails of the instance.
5.
Review the error.
6.
Repeat the steps for all faulted instance IDs.
In some cases, the fault shown on the console may not contain enough inform-
ation to effectively troubleshoot the error, and a review of the log files may be
necessary. Later in this chapter, we will discuss how to identify and view log file
information, as well as increasing the loggers to dump more information as ne-
cessary.
Searching composite sensors
Composite sensors are added to the composite at design time by the deve-
loper(s). They provide a method for implementing trackable fields on messages.
Instances that are displayed on the composite dashboard cannot be correlated
to a business indicator. More often than not in the real world, it is important to
know which instance corresponds to an important field in the message such as
a customer ID or an order number. Composite sensors can be used to capture
these business indicators at runtime and persisted in the database. These can
then be searched using these composite sensors, instead of the non-meaningful
instance ID via the Oracle Enterprise Manager Fusion Middleware Control con-
sole.
