Learn how to use a Solution Manager implementation project to create transaction analysis rules for your analysis projects. This process saves time compared with creating individual rules in the rules database.
Reading this article you will learn:
- How to leverage existing Solution Manager projects to accelerate the creation of a rule set known as an analysis project
- How to use a Solution Manager project to create an analysis project that is populated with the necessary transaction rules for evaluating a managed system from the transactions contained in the Solution Manager project
An analysis project contains the rules that guide the Solution Documentation Assistant (SDA) while analyzing a managed system in the solution landscape. These projects often contain hundreds, if not thousands, of rules. Analysis projects are quite different from Solution Manager projects (i.e., implementation or template projects) in that their purpose is to guide the systematic analysis of a running solution, whereas Solution Manager projects are used to design, build, deliver, and maintain the functionality of the solution.
The Solution Documentation Assistant (SDA) uses rules to analyze managed systems and to generate technical and process documentation on how the systems are being used. One of the rule types is a transaction rule. Creating transaction rules in the rule database is easy, but if you need to create a lot of them, it can be quite tedious using the rule database editor. I show you how to make short work of creating a large number of transaction rules for use in your analysis projects using a Solution Manager implementation project.