A Typical Windows Modeling Process

Windows application components are usually managed as a whole units, rather than as a collections of distinct resources.

These are the steps typically involved in modeling Windows applications.

1. Define and configure hosts.

2. Check in components.

   • Install a Remote Agent on the gold server or development system with the components you want to model.

   • Select the components you want to model. The N1 Service Provisioning System software includes model templates for the most common Windows application components (see Table 1–2 for a list). In many cases, once you have selected the resource template for the Windows component, no further modeling will be necessary.

3. If appropriate, add additional resources to components.

   • In addition to defining the resources that make up a component, you can create variables for configuration parameters, add information about component dependencies, etc.

4. Write plans for deploying and configuring components.

5. Run plans.

6. Run comparisons as necessary to analyze your application environment.