Composite applications allow you to group a set of targets according to tier, so that you can distinguish between issues occurring in different tiers.
Note:
A composite application can be defined to represent multiple tiers (for example, WebLogic servers, SOA Suite and Coherence servers), or it could be defined to represent a web application (WebLogic servers and database). This allows different Enterprise Manager users to create different definitions to represent their unique perspective of the environment, for example application administrators might define a different composite application compared to DBAs.
Defining a composite application is described in the Composite Applications chapter of this guide.
Using the environment in Figure 18-1 as an example, the composite application might be defined as:
Add all WebLogic servers from Service 2 to a composite application in Enterprise Manager. (The managed server becomes a key member of the composite application).
Add a service target to the composite application.
Define a SLA rule that determines when the composite application is considered to be down.