A.4 Driver Operations
The following figure illustrates Modeler operations that are available when you right-click a driver.
Figure A-4 Driver Operations
Table A-4 Driver Operations
|
Operation |
Description |
|---|---|
|
|
Returns an item to its previous status. |
|
|
Creates a new Application object, which stores static single sign-on parameters for a specific application. For more information, see NetIQ Identity Manager Credential Provisioning Guide. |
|
|
Creates a new Repository object, which stores static configuration information for an authentication credential repository such as either NetIQ SecretStore or NetIQ SecureLogin. For more information, see the overview section in the NetIQ Identity Manager Credential Provisioning Guide. |
|
|
Launches the Policy Builder, creates a policy, and creates a new DirXML Script. DirXML Script is the primary method of implementing policies in the NetIQ Identity Manager engine. |
|
|
Creates an ECMAScript object and opens the ECMAScript editor. |
|
|
Launches the Entitlement Wizard and adds an entitlement to the selected driver. For more information, see Section 13.0, Using Entitlements. |
|
|
Launches the Job Scheduler Wizard to create a job. |
|
|
Creates a Mapping Table object. A policy uses a Mapping Table object to map one set of values to another set of corresponding values. |
|
|
Creates a Resource object. Resource objects (for example, generic, ECMAScript, mapping table, application, or repository resources) store information that drivers use. The information can be arbitrary data in any format (for example, XML or text). |
|
> |
Creates a DS object that is part of packages. A DS object contains information that creates eDirectory objects in the Identity Vault. |
|
> |
Create a Resource object that stores global configuration values that can be applied in a package. |
|
|
Creates a schema map policy and launches the Schema Map editor. A schema map policy maps class names and attribute names between the Identity Vault namespace and the application namespace. The schema map policy is applied in both directions. |
|
|
Creates an XSLT policy. XSLT is a standard language for transforming XML documents. You can use the XSLT option to implement policies as XSLT style sheets. |
|
|
Creates a policy by copying from an existing object. |
|
|
Copies data from the selected driver to a target driver. A pasted copy overwrites data in the target driver. |
|
|
Copies data from the selected server to a target server. A pasted copy overwrites data in the target server. |
|
|
Enables you to mark where a driver is communicating through a firewall. Used in Developer mode. If driver icons are turned off, the firewall icon doesn't appear. |
|
|
Straightens a driver connection line. If a line is not within a few degrees of being horizontal or vertical, this option is dimmed. |
|
|
Displays the flow of information between the application and the driver in the Developer view. Launches the Dataflow view. For more information, see Section 8.0, Managing the Flow of Data. |
|
|
Displays the dataflow between the application and driver set. Appears only when dataflow view is activated. |
|
|
Turns on or off the tracing of rules, conditions, condition groups, actions, and tokens at the driver level. |
|
|
Launches the Policy Set and Policy Flow views. For more information, see |
|
|
Runs the Simulate Policy Transformation program against the selected driver. |
|
|
Guides you through creating a driver. After you fill in the wizard’s forms, Designer automatically generates policies that configure the driver to function as described in the forms. |
|
|
Enables you to select an entitlement that is associated with the driver and edit the entitlement’s settings. For more information, see Section 13.0, Using Entitlements. |
|
hronization |
Configures and displays the flow of password synchronization. For more information, see Integrating Passwords. |
|
|
Enables you to manage a copy of the managed system’s schema. You can make changes to a copy of the application schema so that you can test the Identity Manager drivers in Designer. See Managing a Copy of an Application Schema. |
|
|
Launches the Document Generation Wizard, which documents the selected driver. |
|
|
Exports the driver to a .xml file. iManager can consume this format, and Designer can re-import it. For more information, see Exporting to a File. |
|
|
Imports an exported .xml driver file. |
|
|
Enables you to connect to a server, browse to and select a driver, and import the objects into the driver. |
|
|
Prepares a deployment summary and then deploys selected objects and attributes. |
|
|
Compares selected drivers. Enables you to reconcile or update drivers. See Using the Compare Feature When Deploying. |
|
|
Imports attributes from an existing driver. |
|
|
Deploys the modified or imported attributes. |
|
|
Allows you to compare the attributes of a policy to the attributes that are already deployed. |
|
|
Specifies the server on an eDirectory tree where the schema is refreshed after an application’s schema changes. See Refreshing the Application Schema. |
|
|
Reports whether the driver is stopped or running. |
|
|
Starts the driver. |
|
|
Stops the driver. |
|
|
Specifies how much information to display in a trace level log from the driver. Settings go from 0-5. |
|
|
Restarts the drivers. |
|
|
Launches the Driver Security Equals/Exclusions dialog box. Enables you to configure the selected driver’s security equivalences and to exclude selected users from administrative roles. If you select multiple drivers, this dialog box lets you add, modify, and remove common security equivalences and exclusions of the selected drivers. |
|
Delete |
Deletes the selected driver and its policies. |
|
|
Launches the driver’s property pages. Enables you to configure the driver. |