Generating patterns for the application model
After you have created named values, you are ready to generate TPL to encode all the details of your map into BMC Atrium Discovery. The pattern is automatically uploaded to BMC Atrium Discovery through the pattern management interface, after which it will run during discovery and build the appropriate model whenever your application is discovered. BMC Atrium Discovery can discover and automatically build Business Application Instances (BAIs) based on the generated patterns that contain Functional Component Definitions, and it maintains the definitions in patterns so that it is ready to use in your environment.
Before you begin
Patterns are not generated for Software Instances, nor can you create custom SIs. To create custom SIs, you can use one of the template patterns available for download.
To generate patterns for the application model
- From the Application Mapping tab on the Group page, click Generate TPL.
BMC Atrium Discovery automatically activates the pattern that has been generated and submits it into the pattern management user interface, as illustrated in the following screen.
- From the Discovery tab, click Recent Runs.
- Click Rescan Now to scan the architecture again.
- Click the Applications tab.
- In the Application Summary section, click Application Instances.
The applications are displayed in the list.
- Click one of the application instances in the list.
The Application Instance page displays the complete BAI, detailing the functional components and software instances in the application.
In the second step the mapping stage, Mike was able to identify the name of the Friends application (representing the transformed values) to divide the results into different instances (PROD and DEV). Now, at discovery time, BMC Atrium Discovery can use the transformed identity to split discovered results into different instances of the Friends application being mapped.
Where Mike left off, the results of the identity change are displayed from the results of the Web and DB functional components that Mike has mapped.
The final step is for Mike to encode the definitions into TPL.
- Click Generate TPL.
The Pattern Management page displays showing the changes being applied to BMC Atrium Discovery. When the pattern is finished generating, a banner displays at the top of the Pattern Management page indicating that the requested changes were successful.
The Friends Application Model is listed on the Pattern Management: Browse Packages page.
- Scan the estate to take a look at the Friends application instances.
Don't forget to scan any Mainframe instances. Also, make sure that you see the number of instances you expected, and remember that you can filter the list to get a more granular view.
When Mike performs a scan, he notices that both the Friends instances DEV and PROD have been built. Drilling down into the DEV instance, he can see the functional components, software instances, software components, and hosts that make up the application. He can also see that the new pattern (applicationmodel.Friends.build_Friends) has been generated.
Mike has successfully mapped the Friends application and created the model in BMC Atrium Discovery.
Video 6 that follows demonstrates how the application mapper can generate TPL to encode the application map into patterns and complete the model.
Where to go from here
After you have generated TPL, you have mapped your application and created the model that will be used and maintained in BMC Atrium Discovery. At this point, you might also want to create a working back-up of your application map or a snapshot of the state of your application mapping work thus far. If so, export a single group or set of groups containing Functional Component Definitions you have created. The exporting function can also be a useful tool for troubleshooting any problems you had in the mapping process, because it gives you a full history of the definitions that you applied in the map.