Table of Contents
Related Manuals for Novell IDENTITY MANAGER 3.6.1 - NULL SERVICE AND LOOPBACK SERVICE DRIVERS
Summary of Contents for Novell IDENTITY MANAGER 3.6.1 - NULL SERVICE AND LOOPBACK SERVICE DRIVERS
- Page 1 AUTHORIZED DOCUMENTATION Null Service and Loopback Service Drivers Implementation Guide Novell ® Identity Manager 3.6.1 June 05, 2009 www.novell.com Identity Manager 3.6.1 Null Service and Loopback Service Drivers Implementation Guide...
- Page 2 Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
- Page 3 Novell Trademarks For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/ trademarks/tmlist.html). Third-Party Materials All third-party trademarks are the property of their respective owners.
- Page 4 Identity Manager 3.6.1 Null Service and Loopback Service Drivers Implementation Guide...
-
Page 5: Table Of Contents
Contents About This Guide 1 Overview 2 Creating a New Null Service Driver Creating the Driver in Designer ..........11 2.1.1 Importing the Driver Configuration File . - Page 6 A.1.5 Driver Parameters ........... 29 A.1.6 ECMAScript (Designer Only) .
-
Page 7: About This Guide
For documentation on other Identity Manager drivers, see the Identity Manager Drivers Web site (http://www.novell.com/documentation/idm36drivers/index.html). Documentation Conventions In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® A trademark symbol ( , etc.) denotes a Novell trademark. - Page 8 Identity Manager 3.6.1 Null Service and Loopback Service Drivers Implementation Guide...
-
Page 9: Overview
Overview ® Novell Identity Manager includes two utility drivers, Null Service and Loopback Service, whose purpose is to implement custom behavior through policies established on the drivers’ Subscriber and Publisher channels. Like other service drivers such as Entitlement and Workflow, the Null Service and Loopback Service drivers do not connect to external applications or systems. - Page 10 Identity Manager 3.6.1 Null Service and Loopback Service Drivers Implementation Guide...
-
Page 11: Creating A New Null Service Driver
Creating a New Null Service Driver The Null Service driver files are installed on the Metadirectory server at the same time as the Metadirectory engine. No other installation configurations are supported; you cannot use the Remote Loader to run the Null Service driver. The installation program extends the Identity Vault’s schema and installs both the driver shim and the driver configuration file. -
Page 12: Configuring The Driver Settings
2.1.2 Configuring the Driver Settings After you import the driver configuration file, the Null Service driver will run. However, there are many configuration settings that you can use to customize and optimize the driver. The settings are divided into categories such as Driver Configuration, Engine Control Values, and Global Configuration Values (GCVs). -
Page 13: Creating The Driver In Imanager
8c Repeat Step 8a Step 8b for each object you want to exclude. 8d Click OK. 9 Click OK. 2.1.5 Starting the Driver When a driver is created, it is stopped by default. To make the driver work, you must start the driver and cause events to occur. - Page 14 Prompt Description Driver name Type a name for the driver. The name must be unique within the driver set. Define Security Equivalences The driver requires rights to User objects within the Identity Vault. The Admin user object is most often used to supply these rights.
-
Page 15: Configuring The Driver Settings
2.2.2 Configuring the Driver Settings After you import the driver configuration file, the Null Service driver will run. However, there are many configuration settings that you can use to customize and optimize the driver. The settings are divided into categories such as Driver Configuration, Engine Control Values, and Global Configuration Values (GCVs). -
Page 16: Activating The Driver
If you created the driver in a driver set that has not been activated, you must activate the driver within 90 days. Otherwise, the driver stops working. For information on activation, refer to “Activating Novell Identity Manager Products” in the Identity Manager 3.6.1 Installation... -
Page 17: Creating A New Loopback Service Driver
Creating a New Loopback Service Driver The Loopback Service driver files are installed on the Metadirectory server at the same time as the Metadirectory engine. No other installation configurations are supported; you cannot use the Remote Loader to run the Loopback Service driver. The installation program extends the Identity Vault’s schema and installs both the driver shim and the driver configuration file. -
Page 18: Configuring The Driver Settings
3.1.2 Configuring the Driver Settings After you import the driver configuration file, the Loopback Service driver will run. However, there are many configuration settings that you can use to customize and optimize the driver. The settings are divided into categories such as Driver Configuration, Engine Control Values, and Global Configuration Values (GCVs). -
Page 19: Creating The Driver In Imanager
8c Repeat Step 8a Step 8b for each object you want to exclude. 8d Click OK. 9 Click OK. 3.1.5 Starting the Driver When a driver is created, it is stopped by default. To make the driver work, you must start the driver and cause events to occur. - Page 20 Prompt Description Driver name Type a name for the driver. The name must be unique within the driver set. Define Security Equivalences The driver requires rights to User objects within the Identity Vault. The Admin user object is most often used to supply these rights.
-
Page 21: Configuring The Driver Settings
3.2.2 Configuring the Driver Settings After you import the driver configuration file, the Loopback Service driver will run. However, there are many configuration settings that you can use to customize and optimize the driver. The settings are divided into categories such as Driver Configuration, Engine Control Values, and Global Configuration Values (GCVs). -
Page 22: Activating The Driver
If you created the driver in a driver set that has not been activated, you must activate the driver within 90 days. Otherwise, the driver stops working. For information on activation, refer to “Activating Novell Identity Manager Products” in the Identity Manager 3.6.1 Installation... -
Page 23: Upgrading An Existing Driver
Upgrading an Existing Driver The driver shim files are installed when you update the Metadirectory server. The 3.6.1 version of the driver shim supports drivers created by using any 3.x version of the driver configuration file. You can continue to use these driver configurations until you want to upgrade them. The following sections provide information to help you upgrade an existing driver’s configuration to version 3.6.1: Section 4.1, “Supported Upgrade Paths,”... - Page 24 Identity Manager 3.6.1 Null Service and Loopback Service Drivers Implementation Guide...
-
Page 25: Chapter 5, "Managing The Driver
Managing the Driver As you work with the Null Service driver and the Loopback Service driver, there are a variety of management tasks you might need to perform, including the following: Starting and stopping the driver Viewing driver version information Using Named Passwords to securely store passwords associated with the driver Monitoring the driver’s health status Backing up the driver... - Page 26 Identity Manager 3.6.1 Null Service and Loopback Service Drivers Implementation Guide...
-
Page 27: A Driver Properties
Driver Properties This section provides information about the Driver Configuration and Global Configuration Values properties for the Null Service driver and the Loopback Service driver. These are the only unique properties for drivers. All other driver properties (Named Password, Engine Control Values, Log Level, and so forth) are common to all drivers. -
Page 28: Driver Module
If this option .jar is selected, the driver is running locally. The name of the Java class for the Null Service driver is: com.novell.nds.dirxml.driver.nulldriver.NullDriverShim The name of the Java class for the Loopback Service driver is: com.novell.nds.dirxml.driver.loopback.LoopbackDriverSh Native Used to specify the name of the file that is instantiated for the .dll... -
Page 29: Startup Option
A.1.4 Startup Option The Startup Option section enables you to set the driver state when the Identity Manager server is started. Option Description Auto start The driver starts every time the Identity Manager server is started. Manual The driver does not start when the Identity Manager server is started. The driver must be started through Designer or iManager. - Page 30 2 Open the driver set that contains the driver whose properties you want to edit. To do so: 2a In the Administration list, click Identity Manager Overview. 2b If the driver set is not listed on the Driver Sets tab, use the Search In field to search for and display the driver set.