Suggested roadmap for using the Application Management Configuration Editor

Definitions of all applications, transactions, clients, and profiles are stored in a repository that is available to all users. (See About the configuration depot). A well-populated repository makes creating new profiles faster and more efficient. There are two ways to create items for your repository:

• (Suggested) Create applications, transactions, and clients independently. Items created in this way are not initially assigned to profiles, but go into the repository for later assignment. You can use the repository to assign one transaction to multiple profiles that are run by different monitoring agents. For this reason, you might find it more convenient to create applications, transactions, and clients before you create a profile.
• Create applications, transactions, and clients as you set up a profile. Items created this way apply to the profile with which you are currently working, but they also become part of the repository and can be assigned to other profiles later.

The following is a suggested order for using the Application Management Configuration Editor:

1. Define what you want to monitor:
   • Define applications that will be associated with one or more profiles (see Defining applications for profiles).
   • Define transactions for these applications which represent the real end-user transactions to be monitored. (see Defining transactions for profiles).
   • Define filters for the transactions to further refine what data to include or exclude from monitoring (see Using filters).
   • Define user and session tracking as needed to help you isolate performance and availability problems with specific users (see Monitoring unique users and sessions for Web Response Time).
   • Create and upload robotic scripts so you can monitor robotic transactions.
   • Determine if you want to run any CLI commands. If there are scripts associated with these commands, upload them. You also need to define CLI commands and scripts as transactions.
   • Define the clients to be monitored (see Creating clients).
2. Create profiles to describe how you want to monitor and associate applications, transactions, and clients (see Defining profiles).
3. Create managed system lists as needed and distribute profiles (see Creating and using managed system and distribution lists).

You can perform additional tasks as needed using the Application Management Configuration Editor to help manage your configuration:

• Define maintenance windows that identify when an application or a system is unavailable because of maintenance (see Scheduling maintenance windows).
• Define reporting properties that specify rules for naming and grouping data that is displayed in workspaces and views, to meet the needs of your business (see Defining reporting rules).
• Access profile configurations directly from the Application Management Configuration Editor central repository and use your preferred editor to manually modify these XML files as needed. This is useful when you are not signed in to the Tivoli Enterprise Portal and do not have access to the Application Management Configuration Editor (see About the configuration depot).
• You can define security settings that specify what applications, transactions, and profiles are available to users (see Setting up security for Response Time).