An application model defines the hardware and software used to support a business application. After an application is mapped (with hosts, internal elements, relationships, and end users), Portal uses the information to create dynamic dashboards for monitoring the end-to-end performance and status of the application.

When an application model is used to create an application map, the map visually shows performance and status using colors, defined by thresholds. The following figure shows an application model and the application dashboard summary created from the model.

 

Application dashboards are adaptive in that they show the best content available for the given model. For example, the dashboards for an application monitored with NetProfiler and NetSensor will be different than those monitored by AppInternals and AppResponse (9.x).

Creating an application model may seem like a daunting task, especially if your knowledge of the application is limited. However, if you breakdown the process into manageable steps, you may be surprised how easy it is. But don’t expect to create an application model in a single session. The iterative process involves trial and error. That is why the software is designed to save your updates as the model is refined and to not allow others to use the model for monitoring until you indicate that the model is complete. Additionally, the software allows you to enter notes to support your updates and findings.

This table lists the general workflow for creating an application model. Consider the workflow as a starting point and then customize the process to your specific requirements.

The ability to define thresholds for objects depends on the connected data sources. If one of the following data sources is connected, then you can define thresholds for those objects. (Also included are the metrics used to create the objects.) If one of the following data sources is not connected, then you cannot define thresholds for those objects. For example, if only AppResponse (9.x) and/or NetProfiler is connected, then you cannot define thresholds for hosts. But you can define thresholds for relationships.

.NET

Before creating an application model, conduct a little research. Ask the application developers and/or the IT staff about the application:

The Adding hosts dialog box appears for defining hosts (clients/servers) and relationships used by the application. For more information, see About application model back-ends.

To access an existing application model, perform the following procedure.

Content Creators: About Application Models

You can specify the data sources to use for an application model. That is, search results will include components from all data sources and relevant metrics from all data sources will be used for monitoring the application. By default, all data sources are included.

Defining the back-end of an application model includes these procedures:

Hosts are servers that are involved in the execution of an application. When adding hosts one hop away from specific hosts, the relationships, representing traffic between the hosts, are also added.

The following procedure describes how to add hosts and relationships to an application model.

The following procedure describes how to add hosts that neighbor the selected host(s). In other words, use this option to add hosts that are a single hop from selected host(s). This is an easy way to fill out an application model.

If a relationship between two hosts is not being observed by any of the current data sources, then you can manually add relationships between the hosts.

When defining the front-end of an application model, end users are a conceptual representation of how actual users access the application. End users connect to the application using one more relationships (response time).

The following procedure describes how to define end-user experience monitoring in an application model.

Refining the application model includes the following procedures:

Creating an application map can be an iterative process that involves both interviewing subject matter experts and some trial and error. Before an application map can be used for monitoring, all objects in the map (hosts, relationships, internal elements) must be verified and their statuses must be set to In Application Model. When an application map is published for monitoring, any objects in the map not set to In Application Model will not appear in the application map and will not be monitored as part of the application.

For example, the following figure shows an application map in the application editor and the same map in an application dashboard after the map has been published. The status of all objects in the map is set to In Application Model except for the engtfPortal01 host. Notice that the unconfirmed engtfPortal01 does not appear in the application dashboard after the map has been published.

Perform this task to set the status of objects:

Objects with the status Not Sure are not monitored as part of the application when the application map is published. For visual clarity, it is a good idea to delete the objects that are not part of the application. However, before deleting an object, it is good practice to adhere to the following guidelines:

To delete a Host from the application map, select the object and click Delete.

To delete a relationship from the application map, select the relationship. Then in the info dock, select the relationship and click Delete.

Because it is assumed that deleted objects are not part of the application map, objects that have been deleted are not included in search results unless the “Include previously deleted hosts and relationships in results” option is selected.

Additionally, if you change your mind and want to reinstate an object that was previously deleted, you can select the object from the View Notes dialog box (Model > View Notes…). Find the object from the list and click Add Back.

Use the merge feature when modeling Network Address Translation (NAT) hosts, where the IP address used within one network is translated to a different IP address in another network. In other words, when defining an application model, you can merge the front-end with the back-end. For example, you might see the following:

where 2.2.2.2 and 3.3.3.3 are different interfaces on the same physical host.

Use the group feature to represent logical hierarchy within the application model. When the application model is published and monitored, the status of a group will be based on the status of its members.

Groups can be collapsed or expanded using the View > Collapse Group and View > Expand Group options.

To remove a host from a group, select the grouped host. Then in the Groups inspector (shown below), select the host that you want to ungroup and click Remove.

You can specify the internal elements (databases, Java,.NET instances) to include when the application model is published and monitored. By default, all internal elements are included. That is, all internal elements will be monitored.

When the application model is complete, you can publish the model. When an application model is published, Portal generates an application dashboard that can be used to monitor the end-to-end performance and status of the application.

After publishing an application for monitoring, the application can be shared with users and/or groups so that others can monitor the application.

To view and monitor the application, select the application card from the Home screen.

Content Creators: About Application Models

Published application models can be unpublished. When an application model is unpublished, it will no longer be available for monitoring. To unpublish an application model, edit the model and click Unpublish.

Documenting your findings (such as how you learned about a specific host or your reasoning for excluding a relationship) is an important part of creating an application model. Your notes are a valuable resource for refining and maintaining application models.

This table lists the available places to enter your notes.

To review notes for the application and objects (hosts, relationships, end users, response times, internal elements), open the Notes dialog box. (Choose Model > View Notes.)

Use these features to find an object in the list:

After learning about an application, it’s time to create the model. Application models are defined using the application model editor. See Guidelines for modeling an application.

To access the application model editor, perform one of these procedures:

Use the Application Model Editor to define application models.

Application models are graphically defined with the objects listed in this table.

The inspector displays information and options specific to the selected object in the application model. If multiple types of objects are selected, the inspector displays the information on separate tabs. For a description of each inspector tab, see these sections:

To add an end user, choose Add > Add End Users.

To display internal elements for a host, select the host and choose View > Show Internal Elements.