Managing Applications › Manage a Multi-Tiered Application › How To Monitor a Multi-Tiered Application › Create a Multi-Tier Application

Create a Multi-Tier Application

To monitor a multi-tier application, create an application for each tier, and use a naming convention to help you more easily identify and report on some or all the tiers.

Use a naming convention that facilitates administration, reporting, and analysis so that a management console user can immediately recognize that a dependent relationship exists between each application tier. Typically, the performance of an application tagged as Tier 2 often depends on the performance of an application tagged as Tier 3. Review the Tier 3 application performance when you analyze Tier 2 application performance.

The following table shows an example of a multi-tiered application. If you define each tier of the applications this way, each application appears next to each other in the management console. This method shows the multiple pieces of the application architecture and reminds you that there is a dependent relationship among various elements of applications and processes:

Follow these steps:

1. Add the Tier 1 client networks to the Network List and be sure to specify a 24-bit (or higher) subnet mask.
2. Add all servers that participate in the application tier to the Server List and verify that the correct monitor feed is associated with the server.

   When you add a server, it is automatically added to the Network List as a host with a 32-bit mask, which indicates that the server acts as a client as is the case in N-Tier architectures. In the previous example, the HTTP server acts as a client to the Oracle database server.

3. Add the applications to the management console. Use the following naming convention for N-Tier applications:

   <ApplicationName>-<Protocol/Function>-(<TCPPort>)-<Tier#>

   where the variables are defined as follows:

   <ApplicationName>

   Is the name of the application.

   <Protocol/Function>

   Is the application daemon running on the server.

   <TCPPort>

   Is the daemon port number.

   <Tier#>

   The Tier number.

4. Repeat these steps to define each application tier.
5. Click the link to synchronize monitoring devices with the current client network, server subnet, and application definitions on the management console.

   Monitoring devices temporarily stop monitoring application performance during synchronization. To minimize interruptions to monitoring, complete all of your changes before synchronizing monitoring devices.

More information:

Managing Client Networks

Managing Servers

Manage User-Defined Applications