21.4 Checking Your Projects

Designer provides a Project Checker tool to check your project. The project can be checked at any time, but you should run the Project Checker before deploying your project. The Project Checker checks for proper design, contexts, server associations, policies, missing user data, and dependency problems that would cause the deployment of project into the Identity Vault to fail. It only checks the objects in Designer; it does not check the current objects in the Identity Vault.

21.4.1 How to Check Your Project

  1. Select the project in the Modeler or in the Project view.

  2. Select Window > Show View > Other.

  3. Expand Designer for Identity Manager, then double-click Project Checker.

    The Project Checker Option

    You can also click the Project Checker icon The Project Checker Optionat the top of Designer to bring up the Project Checker view.

    The Project Checker is displayed in a new view.

    Figure 21-2 Project Checker

  4. Click the Run the Project Checker icon.

    If you haven’t saved the project, Project Checker prompts you to save it.

The Project Checker displays versioning conflicts, errors, warnings, and information messages about the project.

Figure 21-3 Errors Listed in the Project Checker View

To see more information, double-click an item.

Figure 21-4 Details of an Item

The expanded view lists a description of the message, the severity of the message, and which object caused the error. If there is a line number, it lists the line number where the problem occurred. If there is a known solution for the message, it is also listed.

You can use the Configure Filters icon to customize which object types are checked. For more information, see Customizing the Project Checker.

Figure 21-5 The Configure Filters Icon

You can save the results to a file. Browse to a location and specify a filename and file type, then click Save.

Figure 21-6 Saving the Results of the Project Checker

The Project Checker allows you to view the messages in a hierarchical format or in a flat format. It allows you to limit the object-specific messages that are displayed. Click the Menu icon for more choices.

Figure 21-7 Changing the View

The drop-down menu has the following options:

  • Hierarchical Layout: Displays the messages under Identity Manager and Provisioning headings.

  • Flat Layout: Displays all messages without the hierarchical structure.

  • Auto-check on Save: Automatically runs the Project Checker every time you save a project.

  • Configure Filters: Allows you to customize which objects are checked.

  • Preferences: Limits the number of messages that are visible. The default is 100 items.

Figure 21-8 Views

21.4.2 Customizing the Project Checker

You can customize the Project Checker by creating and editing filters. The filters allow you to receive messages about the items you want to verify. You can create multiple filters, but only one filter can be used at a time.

Figure 21-9 Customizing the Project Checker

To create a filter:

  1. In the Project Checker, click the Configure Filters icon .

  2. Click New Filter.

  3. Specify a name and description for the filter.

    You can select which items are checked, what types of messages are returned about the items, and use key words to limit the messages returned. For example, you can search for all messages about the Driver Set and Driver objects that contain the word “attribute”.

    Options to Create and Edit Filters

  4. Click OK.

To edit the name and description of the filter:

  1. Select the filter, then click Edit.

  2. After you have completed the changes, click OK.

To delete a filter:

  1. Select the filter.

  2. Click Delete.

21.4.3 Items That Are Checked

The Project Checker looks at specific items in the project. It checks the items in the User Application as well as the rest of Identity Manager.

The following table describes the specific items that are checked. The list will increase with each release of Designer.

Table 21-1 Identity Manager Items That Are Checked

Item

Description

Driver

  • Checks for the presence of a Schema Mapping policy.

  • Checks for an invalid Active Directory container.

  • Checks the trace level setting. If it is set to more than 0, an informational message is displayed.

  • Checks to see if the LoopBack driver is being used instead of the eDirectory™ driver.

  • Verifies that the GUID attribute is set to synchronize on the Subscriber channel.

  • Verifies that the GUID attribute is not set to synchronize on the Publisher channel.

  • Checks the classes on the Publisher and Subscriber channels that are set to Ignore and verifies that the attributes for these classes are not set to Synchronize.

  • Checks for the presence of a filter and makes sure it is not empty.

  • Checks to make sure that the Publisher Placement policy does not contain set operation destination DN or set xml attribute operations.

  • Checks for the presence of a Publisher Placement policy.

  • Checks to make sure that no policy on the Publisher channel contains set operation destination DN or set xml attribute operations.

  • Checks to make sure that the Subscriber Placement policy does not contain set operation destination DN or set xml attribute operations.

  • Checks to see if the Subscriber Placement policy is missing.

  • Checks to make sure that no policy on the Subscriber channel contains set operation destination DN or set xml attribute operations.

  • Checks to make sure that the npsmDistributionPassword attribute and the public-private key pair attributes do not simultaneously exist in the User class.

  • Checks to make sure that the authentication method on the Active Directory driver is set to Negotiate when synchronizing passwords.

  • Checks the filter for invalid data.

  • Checks the driver to see if it is publishing both NDS® and Distribution passwords. If it is, this is an invalid setting.

  • Checks for the presence of the nspmDistributionPassword attribute in the User class in the Filter, if password synchronization is enabled.

  • Checks that the nspmDistributionPassword attribute is set to sync or notify, if password synchronization is enabled.

Driver Set

  • Checks to make sure that the deployment context for the Driver Set object is set.

  • Checks to make sure that a server object is associated with the Driver Set object.

E-mail Template

Checks to see if the e-mail notification template is empty.

Entitlements

  • Checks to see if the driver supports entitlements.

  • Checks to see if the attribute DirXML-EntitlementRef is added to the Subscriber channel, if there are policies that use entitlements in the driver. The DirXML-EntitlementRef must be set to Notify or Synchronize for the entitlements to work.

ECMAScript

Checks to see that the ECMAScript object can run only on Identity Manager 3.5.

Identity Vault

  • Checks to see if the username to authenticate to the Identity Vault is missing.

  • Checks to see if the hostname for the Identity Vault server is missing.

  • Checks to see that the password for the user is not stored in the project.

Job

Checks to see that the job object can run only on Identity Manager 3.5.

Library

Checks to see that the library object can run only on Identity Manager 3.5.

Mapping Table

Checks to see that the mapping table object can run only on Identity Manager 3.5.

Policy

  • If there are global configuration values in the policy, it checks to make sure they exist on the Driver or Driver Set object.

  • Checks to see if local variables are defined before they are used.

  • Validates the policy against the DTD.

Schema

  • Checks to see if the class is missing from the schema.

  • Checks to see if the attribute is missing from the schema.

  • Checks to see if the attribute for the class is missing from the schema.

Table 21-2 Provisioning Items That Are Checked

Item

Description

Configuration

Verifies that the XML is well-formed and complies with the schema that defines the elements needed for entities, attributes, lists, relationships, and so on.

Entity

  • Checks every entity to ensure that references to other entities and global lists are valid.

  • Ensures that every entity has at least one attribute defined.

List

Ensures that every local and global list contains at least one item.

Org Chart Relationship

Verifies that the entities and attributes of a relationship have been deployed.

Provisioning Request Definition

Verifies that a workflow follows rules for activities and flow paths.