10.5 Stopping and Starting Identity Manager Drivers

You might need to start or stop the Identity Manager drivers to ensure that an upgrade, migration, or an installation process can modify or replace the correct files. This section explains the following activities:

10.5.1 Stopping the Drivers

Before you modify any files for a driver, it is important to stop the drivers.

Using Designer to Stop the Drivers

  1. In Designer, select the Identity Vault identity vault object in the Outline tab.

  2. In the Modeler toolbar, click the Stop All Drivers icon Stop All Drivers icon.

    This stops all drivers that are part of the project.

  3. Set the drivers to manual start to ensure that the drivers do not start until the upgrade process is complete:

    1. Double-click the driver icon driver icon in the Outline tab.

    2. Select Driver Configuration > Startup Options.

    3. Select Manual, then click OK.

    4. Repeat Step 3.a through Step 3.c for each driver.

Using iManager to Stop the Drivers

  1. In iManager, select Identity Manager > Identity Manager Overview.

  2. Browse to and select the location in the tree to search for Driver Set objects, then click the search icon Search icon.

  3. Click the Driver Set object.

  4. Click Drivers > Stop all drivers.

  5. Repeat Step 2 through Step 4 for each Driver Set object.

  6. Set the drivers to manual start to ensure that the drivers do not start until the upgrade process is complete:

    1. In iManager, select Identity Manager > Identity Manager Overview.

    2. Browse to and select the location in the tree to search for Driver Set objects, then click the search icon Search icon.

    3. Click the Driver Set object.

    4. In the upper right corner of the driver icon, click Edit properties.

    5. On the Driver Configuration page under Startup Options, select Manual, then click OK.

    6. Repeat Step 6.a through Step 6.e for each driver in your tree.

10.5.2 Starting the Drivers

After all of the Identity Manager components are updated, restart the drivers. NetIQ recommends that you test the drivers after they are running to verify that all of the policies still work.

Using Designer to Start the Drivers

  1. In Designer, select the Identity Vault identity vault object in the Outline tab.

  2. Click the Start All Drivers icon Start All Drivers icon in the Modeler toolbar. This starts all of the drivers in the project.

  3. Set the driver startup options:

    1. Double-click the driver icon driver icon in the Outline tab.

    2. Select Driver Configuration > Startup Option.

    3. Select Auto start or select your preferred method of starting the driver, then click OK.

    4. Repeat Step 3.a through Step 3.c for each driver.

  4. Test the drivers to verify the policies are working as designed. For information on how to test your policies, see Testing Policies with the Policy Simulator in NetIQ Identity Manager - Using Designer to Create Policies.

Using iManager to Start the Drivers

  1. In iManager, select Identity Manager > Identity Manager Overview.

  2. Browse to and select the location in the tree to search for Driver Set objects, then click the search icon Search icon.

  3. Click the Driver Set object.

  4. Click Drivers > Start all drivers to start all of the drivers at the same time.

    or

    In the upper right corner of the driver icon, click Start driver to start each driver individually.

  5. If you have multiple drivers, repeat Step 2 through Step 4.

  6. Set the driver startup options:

    1. In iManager, select Identity Manager > Identity Manager Overview.

    2. Browse to and select the location in the tree to search for Driver Set objects, then click the search icon Search icon.

    3. Click the Driver Set object.

    4. In the upper right corner of the driver icon, click Edit properties.

    5. On the Driver Configuration page, under Startup Options, select Auto start or select your preferred method of starting the driver, then click OK.

    6. Repeat Step 6.b through Step 6.e for each driver.

  7. Test the drivers to verify the policies are working as designed.

    There is no policy simulator in iManager. To test the policies, cause events to happen that make the policies execute. For example, create a user, modify a user, or delete a user.