Defining profiles
Define profiles that specify which transactions you want to monitor, when you want to monitor them, and the location on which you want to monitor them.
Before you begin
Depending
on the type of transaction for which you are creating the profile,
you might need to do one or more of the following tasks:
- For Rational Performance Tester, Rational Functional Tester, or Mercury LoadRunner robotic scripts, you must first record the scripts and upload them to the Application Management Console.
- For CLI commands, you must create a transaction. See Defining transactions for profiles. If the transaction calls a script, either upload it or know the complete path name to the computer on which it resides.
Consider completing the following optional task before
you begin defining profiles:
- Develop naming standards for your profiles that clearly identify
its scope and purpose. A standard for naming convention makes it easier
and more convenient to recognize different profiles according to any
of the following:
- Customer name
- Business application
- Scope of monitored transactions
- Type of monitoring agent
The following is a suggested format for naming profiles: <customer name>_<application name>_<type of monitoring>_<schedule_type>. For example, you might use this format for a Rational® Performance Tester robotic monitor for the IBM® Human Resources website. If you schedule it to run continuously, it might be named IBM_HR_RPTplayback_runforever.
You can create and manipulate profiles using either the Application Management Configuration Editor or the AMCECLI command-line tool.