Mapping the application

After you have generated a prototype and have solicited feedback through a PDF preview, you are ready to move to the next stage and map your application. In your prototype, the specifications are only in your internal configuration. You have to ensure that they are created into patterns so that, during discovery, BMC Discovery can build the Business Application Instances (BAIs) and push them into BMC Atrium Configuration Management Database (BMC Atrium CMDB). The Map Application stage transforms your static map to a dynamic mapping structure that enables BMC Discovery to recognize and maintain the application during and after your scans. The stage is divided into two steps:

1. Build rules by adding functional components.
2. Identify the environment by dividing into instances through named values.

Where to go from here

The first step in mapping the application is to create rules that help BMC Discovery understand how to build and maintain the application. For example, if you find a database named Payroll, then that database is supporting the Payroll business application. That is the rule that BMC Discovery uses to maintain the application dynamically. To do this, you create functional components that combine similar functionality into logical chuncks or blocks of information. Based on the traversal patterns you used to create groups and subgroups, functional components give more context for the map (for example, definining the business logic layer), thereby enabling BMC Discovery to dynamically discover and maintain your application.