application mapper searches in the datastore and investigates the results, he strives to build a picture of the application out of the IT components he finds. This picture is called the prototype application map, and is the goal of the Prototype stage in the Collaborative Application Mapping (CAM) process.While the
A successful prototype is crucial to CAM, and it fulfills two purposes:
Before you can build the prototype map, ensure that you have started searching and investigating the items in the datastore that should be added to the prototype, using the techniques described in Searching and investigating the datastore.
The prototype is built using the Manual grouping functionality in BMC Atrium Discovery. The application mapper creates a manual group for the application he is mapping. The group is the workspace for the application map.
The prototype is built in the group by creating subgroups to correspond to the application tiers, also known as functional components. A functional component is a part of an application that you want to map as a separate section. Generally, an application has one functional component for each tier (web, business logic, and database), but there are some more complicated applications that might need multiple functional components per tier. For example, if an application consists of a web layer, some message-driven Enterprise JavaBeans (EJBs) in one set of J2EE containers, a message broker, and a spring-based Plain Old Java Objects (POJO) service in a different set of J2EE containers, you would consider creating four functional components to represent the application.
As the mapper finds items in the datastore that he wants to add to the prototype, he adds them to the appropriate subgroup that corresponds to the functional component that he wants the item to be modeled in.
Notes are a key component in the CAM process, even at this early prototyping stage. Writing down observations and questions in this stage helps you maintain your understanding of the application as the prototype potentially becomes increasingly complicated. The questions are useful for soliciting feedback from the application owner when the time comes.The Application Mapping channel enables you to create a manual group to use in application mapping and provides a list of links to existing manual groups.
Click the name of the group in the group list.
The Home page for the group displays the Application Mapping tab.
For more information, see Viewing created groups.
In the following example, Mike continues where he left off in the previous stage, having gathered enough information from his searching the Discovery datastore for seed data given to him by George.
After locating hosts, software instances (SIs), and DBs, Mike gathers all this information into subgroups to group application components into more refined blocks that represent the tiers in the application (one for the web tier, and one for the DB tier).
Video 2 that follows illustrates the first three stages in the CAM process and shows how, by starting with seed data, the application mapper can begin searching the discovery datastore and building the prototype map.
After you have created your prototype, you should have enough context in your applications to begin sharing information with the application owner in a PDF report. Creating a preview with context-driven notes enables the application mapper to communicate with the application owner efficiently on the map building process. Then mapper can apply the owner's feedback to refine the map before building it our further.