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:
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.
In the Model Discovered Process as Software Instance section, specify the following information:
|Type||The type of software being modeled. The value entered in this field becomes the name of the pattern, and is prefixed with |
Publisher(s) of the SI.
|Category||From 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.
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.
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.
In the Actions list, select:
Deactivate module to deactivate the pattern and retain it on the system for potential further use.
Delete module to entirely remove the pattern from the system.