5 simple steps to follow in setting up monitors!
Posted: April 21st, 2008 | Author: TnT Admin | Filed under: Concepts | Tags: LoadRunner, Monitoring | No Comments »This is an expansion of the previous post Perform the steps logically; it’s an overview built will keep you on focus of the things to do during monitoring setup.
- Check the documentation, knowledge base article and support for the support level of the monitoring System Under Test (SUT); this will eliminate the possibility of unsupported monitors before moving on to the next step.
- Configure the native monitor; Always ensure this is working before moving on to the configuration on Controller. Saves you time working backwards from the Controller. This is described as “Monitoring Environment Setup” in the documentations.
- Ensure connectivity by pinging and telnet the ports (dependent on the setup and the SUT); Sometimes, it’s just ports not being opened, or machines not in the correct network that is causing the problem. Do ensure that connectivity is available between all machines before moving to the next item.
- Configure the Controller machine to communicate to the SUT; This can consist of user privileges on the Controller machine or installing clients that will be used for the communication (e.g. Oracle or Sybase clients).
- Lastly, configure the Controller through the GUI to connect to the native monitor; last item on the list, and should not give you too much problem if (1) to (4) is properly done.
If you follow through these simple steps, it should be easy to configure (minus the human factors involved). We will go into details of each individual native monitor setups in future posts as each of them is unique in it’s own setup.
Leave a Reply