24.3 Extending the Schema Manually without Using the Wizard

This section provides instructions for installing the RBPM runtime infrastructure files and manually extending the eDirectory schema. Complete these steps only if all of the following circumstances are true:

  • You do not want to use the RBPM installation wizard.

  • You installed the Identity Vault in a non-default location.

  • You installed the Identity Vault and Identity Manager engine as a non-root user.

If these circumstances are not true, you might need to use a different process for extending the eDirectory schema or you might not need to extend the schema at all. For more information, see Section 24.1, Understanding the Roles Based Provisioning Module installation.

For these steps, you should copy the following additional files from the prerequisites.zip archive within the .iso image for Identity Manager to a location on the Identity Vault server:

File

Location

nrf-extensions.sch

./schema

nrfdriver.jar

./lib

srvprvUAD.jar

./lib

xcd-all.jar

./lib

dirxml.lsc

top-level folder

tmp folder

./lib

24.3.1 Extending the Schema on a Windows Server without the Wizard

Use NDSCons.exe to extend the schema on Windows servers. Schema files (*.sch) that come with eDirectory are installed by default into the C:\Novell\NDS directory.

  1. Log on as a user with administrative rights to the computer where you installed the Identity Manager engine.

  2. Click Start > Settings > Control Panel > Novell eDirectory Services.

  3. Click install.dlm, then click Start.

  4. Click Install Additional Schema Files, then click Next.

  5. Specify the path to and name of the schema file. For example, enter c:\Novell\NDS\nrf-extensions.sch.

    NOTE:You can copy this file from the ./schema folder within the prerequisitefiles.zip archive within the .iso image for Identity Manager.

  6. Click Finish.

24.3.2 Extending the Schema on UNIX or Linux without the Wizard

To extend the eDirectory schema for RBPM on a UNIX or Linux platform, you must add the RBPM schema file nrf-extensions.sch. To add the file, enter the following command from the command line:

ndssch [-h hostname[:port]] [-t tree_name] admin-FDN schemafilename.sch

24.3.3 Copying Additional JAR files

To ensure a successful installation, RBPM requires the following additional files be added to the server for the Identity Manager engine:

  • nrfdriver.jar

  • srvprvUAD.jar

  • xcd-all.jar

For more information about the location of these files, see Section 24.3, Extending the Schema Manually without Using the Wizard.

Copy these files to the following directory on the server:

  • Linux and UNIX (eDirectory 8.8.x): /opt/novell/eDirectory/lib/dirxml/classes

  • Windows: drive:\novell\nds\lib

24.3.4 Adding the User Application Schema to your Audit Server as a Log Application

If your Audit server will use the User Application as a log application, you must copy the dirxml.lsc file to the server. This section applies to Novell Identity Audit only.

  1. Locate the dirxml.lsc file.

    This file is located in the Identity Manager User Application installation directory after the install, for example /opt/novell/idm. For more information about the location of the dirxml.lsc file, see Section 24.3, Extending the Schema Manually without Using the Wizard.

  2. Use a Web browser to access an iManager with the Novell Identity Audit plug-in installed, and log on as an administrator.

  3. Go to Roles and Tasks > Auditing and Logging and then select Logging Server Options.

  4. Browse to the Logging Services container in your tree and select the appropriate Audit Secure Logging Server. Then click OK.

  5. In the Log Applications tab, select the appropriate Container Name, and then click the New Log Application link.

  6. In the New Log Application dialog box, complete the following steps:

    1. For Log Application Name, specify any name that is meaninful for your environment.

    2. For Import LSC File, browse to the dirxml.lsc file.

    3. Click OK.

  7. Click OK to complete your Audit server configuration.

  8. Ensure that the status on the Log Application is set to ON. (The circle under the status should be green.)

  9. Restart the Audit server to activate the new log application settings.