Modeling a piece of running software as a Software Instance (SI) is a fundamental part of understanding and mapping your business applications. SIs to represent off the shelf software are usually created using base patterns shipped with BMC Atrium Discovery, or subsequent TKU releases. For custom or in-house developed software, you can either write TPL patterns and upload to the appliance using the Knowledge UI, or you can create them as part of the wider Collaborative Application Mapping (CAM) process.

If you do not want to write TPL, or you do not want to complete all the steps required to map a business application when you are only interested in creating a particular SI, you can use the Generate Software Instance Pattern page to generate a pattern to create SIs from discovered processes or services. Once the pattern has been generated and successfully activated, a new Software Instance is generated every time a process that matches the rules is discovered.

You need sufficient permissions to activate and deactivate patterns to create SIs from discovered processes, for example, the system user. If you have insufficient permissions, the Generate Software Instance Pattern option is not displayed in the Actions drop down.

This topic contains the following sections:

To create an SI pattern by supplying conditions

  1. Click the Applications tab in the Primary Navigation Bar.
  2. Select either Create Software Instance pattern from Discovered Processes or Create Software Instance pattern from Discovered Services from the Application Mapping channel. The following page is displayed.

  3. In the Model Discovered Process as Software Instance section, specify the following information:

    FieldDescription
    TypeThe type of software being modeled. The value entered in this field becomes the name of the pattern, and is prefixed with software_instance_model for the pattern module name. It is also the name of any SI created by the pattern.
    Publisher

    Publisher(s) of the SI.

    CategoryFrom the drop-down list, select the Category of the SI. The generated pattern is placed in the pattern module hierarchy according to this selection.

    The fields are the same for discovered services.

  4. In the Query Constructor tab, select the attributes, their values and a simple positive condition that identifies the processes of the SI and filters them out from other processes. 
    The Query Constructor tab in this page is simpler than the usual Query Builder.  T
    raversals are not supported and there is no refine search option for SI modeling.
  5. Check the trigger condition in the Generate pattern section to ensure that the pattern that is to be generated is valid and that you have included all of the necessary conditions.
  6. Ensure the results preview display only the processes you need for the SI. 
  7. Click Generate TPL in the Generate pattern section.
    The system generates the pattern for creating SIs of this type, loads it to the Knowledge Management module, activates it, and links the generated pattern to the model definition. From now on, a new Software Instance is generated every time a process that matches the rules is discovered.
     

To create an SI pattern from known processes or services

If you know that a particular process or services are running on a host, the list of processes or services is available from the Discovery Acess page for that host.From the list, select the processes or services and then select Generate Software Instance Pattern from the Actions drop-down menu. The Generate Software Instance Pattern page is displayed, populated with the conditions which match the process or service.

To view generated SI patterns

  1. Click the Discovery tab in the Primary Navigation Bar and then click Knowledge Management in the top menu.
  2. In the Pattern Modules section, filter the patterns to find the one you just generated:
    1. Select only active in the display option.
    2. In the Filter box, enter the SI type that you specified when created the pattern. 
    3. Ensure that the Generated option is selected.
    4. Click  Apply.
    5. If necessary, expand the pattern module groups by clicking the + sign. 
    6. Expand the pattern details by clicking the down arrow to the left of the pattern.
      The following example shows an example filtered pattern module.
  3. Click the pattern module name in the most left column to see the details of the pattern as in the following example.
     

To modify generated SI patterns

  1. At the filtered pattern module, as shown here:

    Open the Generate Software Instance Pattern page.
    To do this, click the pattern module name link, labelled Software Mapping Definition. 
  2. Modify the pattern details and triggering conditions and click Generate TPL in the Generate pattern section. The updated pattern is uploaded, activated and linked to the module definition.

    Changing pattern name creates new pattern

    The pattern name, which is entered in the Type field (it also determines the software instance type), acts as an ID for the pattern. If you change the pattern name, this does not update the name of the existing pattern, it generates a new pattern with the new name. As patterns do not deactivate other patterns, you must deactivate the previous pattern manually.

To delete generated SI patterns

  1.  View the pattern, that creates a Software Instance from discovered process.

  2. In the Actions list, select:

    1. Deactivate module to deactivate the pattern and retain it on the system for potential further use.

    2. Delete module to entirely remove the pattern from the system.

Was this page helpful? Yes No Submitting... Thank you
  • No labels
© Copyright 2004 - 2019 BMC Software, Inc.
Legal notices