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® Robot, 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, you should either upload it or know the complete path name to the computer on which it resides.

The following are optional tasks that you should consider doing 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 customer name, business application, scope of monitored transactions, and type of monitoring agent. The following is a suggested format for naming profiles: <customer name>_<application name>_<type of monitoring>_<schedule_type>. For example, using this format for an RPT robotic monitor for the IBM® Human Resources Web site that you schedule to run continuously might be named it IBM_HR_RPTplayback_runforever.