Service Response Monitor › Functional Characteristics › Control File Processing

Control File Processing

When you add tests to the configuration file, consider the following procedure.

To add tests to the configuration file

1. Stop SystemEDGE agent to edit the svcrsp.cf file.
2. Add tests with status active or notInService to the svcrsp.cf file.
3. Store the file and start SystemEDGE.

At this stage SystemEDGE and SRM perform the following steps:

1. SRM parses the svcrsp.cf file and initializes itself.
2. If any critical error is encountered (like invalid java path), the configuration fails and SystemEDGE disables the AIM.
3. If any test configuration is invalid or the test status is different from active or notInService, SRM does not create the test and removes it from the configuration file.
4. SRM passes the tests to the Jcollector process that starts the tests.
5. SRM updates the test results each 30 seconds.

You can change most of the test parameters through SNMP while the tests are running (except: name, class, and so on).