5.6 Importing the Rogue Administration Workflow

Use the following procedure if the rogue administration workflow does not exist in the DAL:

  1. In Designer, click Windows > Show View > Provisioning View in the toolbar.

  2. In the Provisioning view, right-click the Directory Abstraction layer, then click Import from File.

    Provisioning View in Designer

  3. In the warning message, click OK.

  4. Browse to and select the Rogue_Administration_Activity.xml file from the Resource Kit Designer project, then click OK.

    The file is located in location_of_designer_workspace/designer_workspace/RK12/Designer/Documents/Resources/provisioning_requests.

  5. Click OK to import the workflow.

  6. Verify that the workflow was imported by browsing to it under UserApplication > Provisioning Request Definitions > Accounts > Rogue_Administration_Activity.

    The Rogue Administration Workflow

  7. Verify that the LoginDisabled attribute exists on the User entity by right-clicking the Rogue_Administration_Activity, then select Validate to run the Project Checker.

    1. If the LoginDisabled attribute does not exist on the User entity, right-click the Directory Abstraction Layer > Entities > User, then select Edit.

      Editing the User Entity

    2. Right-click the User entity in the left pane, then select Add Attribute.

    3. Browse to and select the LoginDisabled attribute in the left pane.

    4. Click Add Attribute, then click OK.

  8. Press Ctrl+S to save the changes.

  9. Deploy the changes in the Identity Vault. For more information, see Deploying a Project to an Identity Vault in the Designer 3.0.1 for Identity Manager 3.6 Administration Guide.

  10. Restart the User Application and the User Application driver to apply the changes. To restart the User Application server:

    • Reboot the application server.

    • Redeploy the application WAR file.

    • Force the application to restart. The applications are JBoss* or WebSphere*.