Create a new application template by using an editor to identify the application processes and application service groups that you want to discover and monitor.

The .xml templates are loaded when the ESM server starts or during full discovery. All .xml templates in the BASEDIR/smarts/conf/applications directory and the BASEDIR/smarts/local/conf/applications directory are processed.

If syntax errors exist in the template, the template is not processed. The BASEDIR/smarts/conf/applications/apptemplate-config.dtd file controls the syntax and format.

To create a template:

  1. Use the sm_edit utility to open the BASEDIR/smarts/conf/applications/ apps-userdefined.xml file.

  2. Create the applicationGroupConfig section and provide the following information:

    • className—Target Class name for the ApplicationServiceGroup or user-defined application service group to be created. By default, the value is blank. Specify ApplicationServiceGroup so that application service group instances will be created during discovery for this template. If the value is not specified, application service group instances will not be created.

      • vendor — Required. Vendor name of the Application provider.

      • applicationName—Required. The unique name of the application or service. The applicationName value must be unique across all template definitions.

      • isEnabled—Enables or disables the template. By default, the value is TRUE. When the value is TRUE, the current application is discovered and monitored. If the value is set to FALSE, the template is not used for matching in subsequent discoveries.

      • templateType— The type of template. Specify USERDEFINED for templates created in the apps-userdefined.xml file. Other values PREBUILT and AUTOAPPLY are reserved for use by the ESM server.

      • vendorDescription—Description about the vendor. This is helpful to retain the details about the vendor.

      • versionDescription—Description about the current application version. This is helpful to retain the details about the current version.

      • applicationDescription—Description about the current application. This is helpful to maintain the details about the current application.

  3. Create the processConfig section for each individual process, provide the following information:

    • vendor —Vendor name of the current process provider.

      • isCritical—Indicates whether the process is critical for a given Application or ApplicationGroup. By default, the value is FALSE. If the value is TRUE, impact notifications are displayed for the ApplicationServiceGroup when the process is missing.

      • path—Directory location for the current process where it is running. The * matching pattern is used by default if you leave this field blank. This information helps you to locate the process if it has any issues.

        You can specify a pattern for matching on the process path. For example, the pattern /opt/*|/etc* matches the process paths that start with /opt or /etc.

      • arguments— Argument list of the process to monitor. The * matching pattern is used by default if you leave this field blank.

        You can specify a pattern for matching on the process arguments. For example, the pattern *--config=esm* matches the process arguments that contain --config=esm.

      • Minimum — Required. 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 — Required. 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.

      • processName —Required. Name of the process. You can specify a pattern for matching on the process name (for example, *server*).

  4. Save and close the file.

    The template is saved to the BASEDIR/smarts/local/conf/applications directory.

  5. Reload the template using the sm_esmctl utility. Go to “Load the application templates by using the sm_esmctl utility” on page 234.

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

  7. Go to “Creating a discovery filter for an application template” on page 226 to create a discovery filter.

    Note:

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