Defining business application definition

The application administrator naturally does not want to have to perform all of this manual mapping and discovery each time he wants to view and manage his business application. He knows that the vendor's documentation contains a logical architectural diagram of the business application, so to make his job easier, he uses SAV to create an business application diagram.

His first step is to create the logical tiers of the business application. He selects the Tiers tree and creates four main tiers for the business application: Web, Application, Database. He creates sub-tiers for authentication services and integration services. He then defines application signatures to add to each tier, specifying which tier a recognized signature should fall in.

In order to create reusable application signatures for each tier, he specifies the criteria used to recognize it, including process names, open files, listener ports, command line, environment variables, and so on.

He continues to do this for each tier in the business application, and then color codes the signatures in each tier. When the business application is visualized in the Tiers or Server maps, he will be able to see each tier of the business application in different colors. Next time he launches SAV, the business application will map and display according to his definition.

Finally, he saves his business application definition so it can be reused by others who want to work with the same business application.

For more information on creating a business application, see Creating business application definitions.