Template related and configuration tasks for Process Monitoring summarizes the tasks that you need to perform to implement discovery and monitoring for processes and application groups. The console method is preferred because using the console reduces syntactical template errors. The editor method allows you to specify additional advanced fields.
| Task order |
Console method |
Editor method |
|---|---|---|
| 1. Create the application template. |
“Creating a new application template by using the console” on page 222 |
“Creating a new application template by using an editor” on page 224 |
| 2. Load the template, if necessary. |
Not applicable. |
“Load the application templates by using the sm_esmctl utility” on page 234 |
| 3. View the template to verify it. |
||
| 4. Create the discovery filter and apply it. |
“Creating a discovery filter for an application template” on page 226 |
|
| 5. Rediscover the processes and ApplicationServiceGroup topology. |
In the Domain Manager Administration Console, select your ESM server (INCHARGE-ESM by default), and select Topology > Discover All. |
|
| 6. Configure performance thresholds for monitoring. The availability thresholds are configured by default. |
|
|
| 7. Monitor your network. |
||
To modify an application template that is created by using the console, you can:
-
Modifying an existing user-defined application template on page 230.
-
Modify the apps-userdefined.xml file using the sm_edit utility if any fields in the template need to be changed. Then, reload the changes on the ESM server by using the sm_esmctl utility with the --load-templates option. Follow the instructions in “Creating a new application template by using an editor” on page 224 and “Load the application templates by using the sm_esmctl utility” on page 234.
