Use the console to modify an existing user-defined template only if the template was initially created with the console. Templates that are saved in .xml files, except for those defined in the apps-userdefined.xml file, cannot be modified in the console. Use the procedure in “Creating a new application template by using an editor” on page 224 to make changes to an existing template in an .xml file.

Prerequisite

Obtain the template name from the Application Templates tab. To access the tab, select the ESM server (INCHARGE-ESM by default) in the Domain Manager Administration Console. You will need to specify name for step 4 .

Procedure

To modify an existing user-defined template:

  1. In the Domain Manager Administration Console topology tree,

  2. Expand the Host class.

  3. Right-click the host instance and select the Configure Process Monitoring option.

    The Configure Process Monitoring window appears displaying all the retrieved processes from the host.

  4. Type the following information in the Configure Process Monitoring window:

    Either click Add a Row to add a new row or double-click in an existing row to add the details.

    • For each row, select the checkbox for the process to discover and monitor it.

      If you added a row by mistake, select the checkbox again to remove the checkmark, so the unwanted row will not be included in the template.

      • Name — The name for the process. Patterns for matching criteria are not allowed.

      • Process — A name for the process. Matching patterns are allowed in rows that were added using the Add Row option. You can specify a pattern for matching on the process name (for example, *server*).

      • Arguments — The argument of the process. You can type a matching pattern (for example, *--config=esm*). The * matching pattern is used by default if you leave this field blank.

      • Minimum — The minimum number of the instances of the process that you want to run. This is the threshold value for the CountThresholdViolated event for the application if the number of running processes falls below the threshold.

      • Maximum — The maximum number of the instances of the process that you want to run. This is the threshold value for the CountThresholdViolated event for the application if the number of running processes exceeds the threshold.

        The ApplicationGroup and TemplateName fields are populated after the template is saved and if the template gets applied to the host due to a matched filter.

      • ApplicationGroup — The name of the application service group if the process belongs to one.

      • TemplateName — The name of the .xml template if the process is configured in one. Blank if the process is configured using the console.

        The Current, CPU, and Memory fields are for informational purposes. They are read-only and are not saved in the template. The CPU and Memory fields have values other than -1 only if the Host’s aggregate CPU/Memory exceeds the threshold.

        Note:

        Do not use the ! symbol (exclamation mark) in Process Application name, Application Group name, Template name, and in Template description.

  5. If processes from other templates are listed and you do not want to include them in your new template, select the checkbox for the process row to remove the checkmark. The unwanted row will not be included in the template.

  6. Replace the template with the same name. Type the template name in the field next to the Save as template button and click Save as template.

    Only templates created from the console can be replaced. An error displays if other types of template names are specified.

    Changes to the template are also updated in the BASEDIR/smarts/local/conf/applications/apps-userdefined.xml file.

  7. Click Yes when prompted for confirmation to replace template.

  8. In the Specify Information for template window, select class name to create an application service group (ApplicationServiceGroup), type the vendor name, version description, and application description, and click Continue saving template.

    Note:

    The ApplicationServiceGroup will be created only if a class name value is selected. If no class name is selected, application service groups will not be created during discovery and only Application instances will be created on Hosts.

    Do not use the ! symbol (exclamation mark) in Process Monitoring Application name, Application Group name, Template name, and in Template description.

  9. Click OK.

    The template is saved and the Configure Process Monitoring window closes.

  10. View the template to verify it. Go to “Display template information” on page 232.

  11. Go to “Creating a discovery filter for an application template” on page 226 to create a discovery filter if the template is not associated with a filter.

    If the template is already part of a discovery filter, no changes to the filter configuration are needed.

    Note:

    The template will not be applied to any host unless a discovery filter is created for it in the console.

  12. Start a rediscovery so that the changes in the modified template are applied to the hosts. In the Domain Manager Administration Console, select your ESM server (INCHARGE-ESM by default), and select Topology > Discover All.