Application Component Templates

Introduction

You can use Application Component Templates to create and define your own application components based on services discovered by Device42 Hypervisor /*nx/Windows autodiscovery jobs run against *nix and Windows platforms. Device42 adds any application components created based on your templates to the Application Components list page.

View Application Component Templates

Select Applications > Application Component Templates from the Device42 menu to display the templates list.

Device42 displays the Application Component Templates list page. On this page, you can Search by name, or filter the list by Enabled and also click +More to add a Last Changed filter.

Note: The Application Component Templates list page also includes an Advanced Search option you can use to construct more specific searches. See the Advanced Search Feature documentation page for instructions.

Click on a template Name to see details about that template. Click Edit at the upper right to change or update an existing template.

Add an Application Component Template

Click Add at the upper right of the template list page to add a new template.

Application Component Template Configuration

  • Enter a Template Name (required).
  • Select whether the template should be Enabled (Yes/No) for use in autodiscovery – this allows you to create a template but enable it only when you are ready to use it or disable it without having to delete it.

Characteristics

  • Select the Rule Type (Windows/*Nix) to select which platform Device42 autodiscovery will search for the service(s) on which the application component will be based.
  • Select, enter, or add (plus sign) the Service autodiscovery will look for to create the application component (required).
  • Enter a port in the Only services listening on this port field to optionally specify the service port to further filter services that are listening on the specified port. Leave the field empty to ignore the port.

Creation Rules

  • Enter an Application Name Pattern to specify how the application component will be named. You can enter static text for the name and also use the following variable to construct the application component name.

%(device_name)s, %(discovered_listening_ip)s, %(listening_port)s, %(app_template_name)s

  • Select, enter, or add (plus sign) any Related Software Components or Related Services that should associated with the application component. For Related Service, you can specify Only services listening on this port.
  • Enter a path in Configuration File Location to specify the directory in which Device42 should look for configuration files.
  • Enter a name or partial name in the Filename Filter (optional) field to identify the configuration file(s).
  • Select Traverse subdirectory (Yes/No) to have Device42 traverse the Configuration File Location directory.

Device42 Details

  • Select the Category for the application component ( e.g., Application Layer, Database, Load Balancer, Other, Web Server).
  • Enter What is impacted by the application component.
  • Select or add the Responsible Customer or Department.
  • Enter any Tags you want for the application component.

Custom Fields

  • Select or enter values for any Custom Fields you want for the application component. You can also add Notes for each Custom Field.

Click Save at the upper right of the Add/Edit page to save the template and add it to the application component template list.

Delete Application Component Templates

Select one or more templates from the list page, select Fast Background Delete from the Actions menu, and then click the lightning bolt icon.

Autodiscovery Options

The Windows /  *Nix autodiscovery jobs you run will check to see which application component templates are enabled and use them to create application components. When you create your discovery jobs, be sure to select the following options in the Software and Applications tab:

  • Discover Software
  • Discover Services
  • Discover Applications