The Requirements Status tree appears in the left portion of the MPS Deployment Tool main window. The tree control categorizes MPS deployment components as requirements nodes or groups, with various requirements entities related to each group. For example, in the following Figure SPV.7, Customer Directory Integration is a requirements node and Initialize Customer Directory Integration beneath it is a requirements entity:

Replace Image - SPV_DT_Requirements_Status.gif

Figure SPV.7 MPS Deployment Tool Requirements Status pane

Similar to the hierarchical configuration of the Microsoft Management Console (MMC), components in the tree include subcomponents such as sub-nodes, configuration or initialization procedures, or lists of servers where the component will be deployed. For example, in Figure SPV.7, Core Platform is a requirements node, Core Configuration is a sub-node, and the five items beneath it are requirements entities:

In new deployments, the MPS Deployment Tool populates the tree view of the Requirements Status pane by retrieving data from the MpsRequirements.xml file and adding it to a blank configuration template (the MpsConfig.xml file). When the tool is run for verification or reconfiguration in a post deployment environment, the tree view is populated by retrieving data from the MpsConfig.xml file. When the tool is run in legacy MPS environments, the tree view is populated by retrieving data from the existing MPF configuration database.