4.5 The Outline View

The Outline view provides an outline of the active editor. To open the Outline view, select the Outline tab in the upper left view of Designer, or if the view is not open, click Window > Show View > Outline.

The Outline view’s contents vary, depending on the editor you have open at the time.

Selecting items in the Outline view also selects them in the Modeler. If the selected item isn’t visible in the Modeler, it automatically scrolls into view. Similarly, as you add or remove items the Modeler, they are automatically added or removed in the Outline view.

The Outline view provides a standard menu of functions, which are available by right-clicking the Outline tab. The Outline view also provides an icon bar of additional functions specific to the Outline view.

Figure 8-13 shows a typical Outline view along with its icon bar.

Figure 4-10 The Outline View

Table 8-2 describes the project icons displayed in the Outline view.

Table 4-2 Project Icons Displayed in the Outline View

Icon Name

Description

Project Name

The name of the project when you create it. This is the name of the project stored in the \workspace\project name directory. Right-click the project name to do the following:

  • Under New, you can add an application, a Domain Group, or an Identity Vault.

  • Generate documentation on the project.

  • Through the Live option, you can import a driver set from the Identity Vault.

  • Check in the project into a version control server.

  • Delete the project.

  • See the Properties window associated with this object.

Version Control Project Name

The icon changes on a project when you commit the project to a version control server. Right-click the project name to do the following:

  • Under New, you can add an application, a Domain Group, or an Identity Vault.

  • Generate documentation on the project.

  • Through the Live option, you can import a driver set from the Identity Vault.

  • Check in the project into a version control server.

  • Update the project from a version control server.

  • Delete the project.

  • See the Properties window associated with this object.

Identity Vault

An Identity Vault represents the eDirectory™ tree that has Identity Manager installed on it. Right-click the Identity Vault to perform the following:

  • Under New, you can add a driver set, a library, or a server object to the project.

  • Manage Identity Vault schema.

  • The DirXML Script Tracing option enables you to turn on or off actions, conditions, and tokens on every policy at the Identity Vault level. This allows you to control how rules, conditions and tokens flow through policies.

  • Generate documentation on the Identity Vault.

  • Import a driver configuration file.

  • Import schemas from a file.

  • Export the Identity Vault configuration and schema to a file.

  • Under Live:

    • Import a driver set from eDirectory

    • Deploy the Identity Vault

    • Compare all driver sets

    • Import and deploy schema

    • Manage eDirectory objects

    • Run a live DS Trace

    • Open iManager

    • Manage the Identity Vault directory

    • Start, stop, and restart drivers, as well as show their status

  • Delete the Identity Vault.

  • See the Properties window associated with this object.

Domain Group

Domain groups allow you to group projects into granular portions. Right-click the Domain object to perform the following:

  • Under New, you can add an application, a Domain Group, or an Identity Vault.

  • Generate documentation on the Domain.

  • Under Live, you can import from the Identity Vault.

  • Delete the Domain Group.

  • See the Properties window associated with this object.

If you select to document this group, the generated document filters items that are outside the Domain Group. Drivers bordering the domain are included in the document.

Library

The Library object is a repository of commonly used policies that can be referenced from multiple locations. You can place a policy in the library that every driver in the driver set can reference. Right-click the Library object to perform the following:

  • Under New, you can add the following policy types:

    • Credential application

    • Credential repository

    • DirXML® Script

    • ECMAScript

    • Mapping Table

    • Resource

    • Schema Map

    • XSLT

    • Add a policy from a copy

  • The DirXML Script Tracing option enables you to turn on or off actions, conditions, and tokens on every policy at the Library level. This allows you to control how rules, conditions and tokens flow through policies.

  • Export the library to a configuration file.

  • Import a driver configuration file.

  • Under Live, you can:

    • Import a policy

    • Deploy a policy

    • Compare a policy

  • Delete the Library object.

  • See the Properties window associated with this object.

Server Object

The Server object is the server in the tree where you have Identity Manager installed. Right-click the Server object to perform the following:

  • Delete the Server object.

  • See the Properties window associated with this object.

Driver Set

The driver set is a collection of Identity Manager drivers that are stored in a single location. Right-click the driver set to perform the following:

  • Under New, you can create a new driver, a job, or a library.

  • Copy the driver set settings and global configuration values.

  • The DirXML Script Tracing option enables you to turn on or off actions, conditions, and tokens on every policy at the driver set level. This allows you to control how rules, conditions and tokens flow through policies.

  • Generate documentation on the driver set.

  • Import a driver configuration file.

  • Export the driver set to a configuration file.

  • Under Live:

    • Import a driver

    • Deploy a driver set

    • Compare the driver set in Designer to a deployed driver set in the Identity Vault

    • Import, deploy, and compare driver set configuration attributes

    • Start, stop, and restart drivers, as well as show their status

  • Delete the driver set.

  • See the Properties window associated with this object.

If you select Document Selection, the generated document filters most items that are outside the driver set. Child objects are also included and parent objects are included in the document for perspective purposes.

ID Policy Container and ID Policy

An ID Policy container is created under an ID Provider driver and is a repository for ID policies. An ID policy allows the ID Provider driver to assign unique IDs to objects. When the ID Provider driver receives an ID request from a client, it generates an identification that is based on the ID policy specified in the request and passes it to the client.

Right-click the ID Policy container to perform the following:

  • Create a new policy.

  • Export the policy container object to a configuration file.

  • Under Live:

    • Import a policy

    • Deploy the ID Policy container

    • Compare the ID Policy container in Designer to a deployed ID Policy container in the Identity Vault

  • Delete the ID Policy container.

  • See the Properties window associated with this object.

Right-click the ID Policy to perform the following:

Driver Object

A Driver object is a collection of channels, policies, rules, and filters that connect an application to an eDirectory tree running Identity Manager. Each driver performs different tasks. Policies, rules, and filters tell the driver how to manipulate the data to perform those tasks. Right-click the Driver object to do the following:

  • Under New, you can add the following policy types:

    • Credential application

    • Credential repository

    • DirXML Script

    • ECMAScript

    • Entitlement

    • Job

    • Mapping Table

    • Resource

    • Schema Map

    • XSLT

    • Add a policy from a copy

  • Copy driver settings or server-specific driver settings.

  • Show the dataflow view.

  • The DirXML Script Tracing option enables you to turn on or off actions, conditions, and tokens on every policy at the driver level. This allows you to control how rules, conditions and tokens flow through policies.

  • Simulate policy transformation.

  • Show the driver’s IDS trace.

  • Run the Driver Configuration Wizard.

  • Synchronize passwords to an associated server.

  • Manage application schema.

  • Generate documentation for this driver.

  • Import a driver configuration file.

  • Export the driver to a configuration file.

  • Copy server-specific data between servers. To do this, you must have more than one server associated with the driver set. You can add a server to a driver set by going into the Driver Set Properties page. The replica data that you can copy includes:

    • Global configuration values

    • Named passwords

    • Driver authentication information

    • Driver startup option

    • Driver parameters

Driver Object, Continued.

Right-click the Driver object to perform the following:

  • Under Live:

    • Import a driver

    • Deploy a driver

    • Compare the driver in Designer to a deployed driver in the Identity Vault

    • Import, deploy, and compare driver configuration attributes

    • Refresh the application schema

    • Start, stop, and restart drivers, as well as show their status

    • Set up driver security

    • Set driver trace level

  • Delete the Driver object.

  • See the Properties window associated with this object.

If you select Document Selection, the generated document filters most items that are outside the driver. Child objects are also included and parent objects are included in the document for perspective purposes.

Publisher Channel

A channel is a combination of rules and policies, and Designer allows you to import a channel instead of the entire driver. The Subscriber and Publisher channels describe the direction in which the information flows.

The Publisher channel takes the event from the application, database, csv file, etc., and sends that event to the Identity Vault. Channel events do not need to be corresponding.

Right-click the Publisher or Subscriber channel to perform the following:

  • Under New, you can add the following policy types:

    • Credential application

    • Credential repository

    • DirXML Script

    • ECMAScript

    • Mapping Table

    • Resource

    • Schema Map

    • XSLT

    • Add a policy from a copy

  • The DirXML Script Tracing option enables you to turn on or turn off actions, conditions, and tokens on every policy at the channel level. This allows you to control how rules, conditions and tokens flow through policies.

  • Run the Simulate Policy Transformation program on the channel to ensure that it is working correctly.

  • Import a driver configuration file.

  • Export the channel configuration to a file.

  • Under Live:

    • Import objects into a driver

    • Deploy a channel

    • Compare the channel in Designer to a deployed driver channel in an Identity Vault

  • See the Properties window associated with this object.

Subscriber Channel

A channel is a combination of rules and policies, and Designer allows you to import a channel instead of the entire driver. The Subscriber channel takes the event from the Identity Vault and sends that event to whatever the receiving system is (application, database, CSV file, etc.). (See Publisher Channel for right-click actions.)

Policy

A policy is a collection of rules and arguments that allow you to configure an application to send or receive events to or from the Identity Vault. You use policies to manipulate the data you receive from eDirectory or from the application. Each driver performs different tasks, and policies tell the driver how to manipulate the data to perform those tasks.

Right-click the Policy object to perform the following:

  • Edit, copy, and save the Policy object.

  • The DirXML Script Tracing option enables you to turn on or off actions, conditions, and tokens on every policy at the policy level. This allows you to control how rules, conditions, and tokens flow through policies.

  • Run the Simulate Policy Transformation program on the policy to ensure that it is working correctly.

  • Export a policy configuration to a file.

  • Under Live:

    • Deploy a policy

    • Compare the policy in Designer to a deployed driver or channel policy in an Identity Vault

  • Open the policy with the Designer built-in editor, Novell XML editor, or text editor.

  • Delete a policy.

  • See the Properties window associated with this object.

Overlay Icons

Overlay icons have a symbol overlay in one of the corners to signify that the object is in a certain state. For example, the policy icon to the left signifies that the policy does not belong to a policy set. An application icon with an overlay signifies that there is more than one driver connected to the application. A driver set icon with a server overlay signifies that the driver set is connected to an Identity Manager server.

Overlay icons can be informational, warnings, or they can signify errors. In the Compare window, overlay icons tell you whether the object is on the server or in Designer.

Schema Mapping

Schema Mapping allows Identity Manager to synchronize information to the connected system without changing the connected system. Schema translates all classes and attributes for the connected system.

Right-click the Schema Mapping object to perform the following:

  • Edit, copy, and save the Schema Mapping object.

  • Run the Simulate Policy Transformation program on the object to ensure that it is working correctly.

  • Export a Schema Mapping policy configuration to an XML file.

  • Under Live:

    • Deploy a policy

    • Compare the policy in Designer to a deployed driver or channel policy in an Identity Vault

  • Open the object with the Designer built-in editor, Novell XML editor, or text editor.

  • Delete the object.

  • See the Properties window associated with this object.

Resource Objects

Resource objects include Application SSO objects and Repository SSO objects. Double-clicking a resource object brings up the object in an editor.

Right-click the Resource object to perform the following:

  • Edit and copy the Resource object.

  • Export a Resource policy configuration to a file.

  • Under Live:

    • Deploy a Resource policy

    • Compare the policy in Designer to a deployed driver or channel policy in an Identity Vault

  • Open the object with the Designer built-in editor, Novell XML editor, or text editor.

  • Delete the object.

  • See the Properties window associated with this object.

XSLT

XSLT represents XSLT style sheets, which are used instead of the DirXML Script.

Right-click the XSLT object to perform the following:

  • Edit, copy, and save the object.

  • Run the Simulate Policy Transformation program on the style sheet to ensure that it is working correctly.

  • Export an XSLT style sheet configuration to an XML file.

  • Under Live:

    • Deploy the style sheet

    • Compare the style sheet in Designer to a deployed driver or channel style sheet in an Identity Vault

  • Open the object with the Designer built-in editor, Novell XML editor, or text editor.

  • Delete the object.

  • See the Properties window associated with this object.

Filter

Filter allows the objects to be sent. It’s the gatekeeper that restricts the objects (groups, users, and the attributes associated with them) that can be sent to and from an Identity Vault.

Right-click the Filter object to perform the following:

  • Edit and save the object.

  • Run the Simulate Policy Transformation program on the filter to ensure that it is working correctly.

  • Export a filter configuration to an XML file.

  • Under Live:

    • Deploy the filter into an existing eDirectory tree.

    • Compare the filter in Designer to a deployed driver or filter in an Identity Vault.

  • Open the object with the Designer built-in editor, Novell XML editor, or text editor.

  • Clear the Filter object.

Application Object

The Application object represents a connected system, whether that system is a database, an application, or CSV files.

Right-click the Application object to do the following:

  • Show the dataflow view.

  • Manage application schema.

  • Set up remote control through VNC connectivity.

  • Generate documentation on the application object.

  • Under Driver:

    • Import objects into a driver

    • Deploy the driver

    • Compare a driver in Designer to a deployed driver in an Identity Vault

    • Set up driver security

  • Delete the object.

  • Under Distribute, you can select Horizontal or Vertical.

  • Under Live, you can create eDir-to-eDir certificates if this is an eDir-to-eDir connection.

  • If this is an eDir-to-eDir connection, you can configure the connections for SSL/TLS activation.

  • See the Properties window associated with this object.

If you select Document Selection, the generated document filters most items that are outside the driver. The driver object is also included, and parent objects above the driver object are included in the document for perspective purposes.

Entitlement Object

The Entitlement object represents an entitlement assigned to the Subscriber channel.

Right-click the Entitlement object to perform the following:

  • Edit, copy, and save the object.

  • Export an entitlement configuration to an XML file.

  • Under Live:

    • Deploy the entitlement

    • Compare the entitlement in Designer to a deployed entitlement in an Identity Vault

  • Open the object with the Designer built-in editor, Novell XML editor, or text editor.

  • Delete the object.

Job Object

The Job object represents a job that you can schedule to run either immediately or at a later date. Designer presently ships with three job types: Random Password Generator, Schedule Driver, and Subscriber Channel Trigger. You can also have custom jobs.

Right-click the Job object to perform the following:

  • Edit the job object.

  • Export a job configuration to an XML file.

  • Under Live:

    • Deploy the job

    • Compare the job in Designer to a deployed job in an Identity Vault

  • Open the object with the Designer built-in editor, Novell XML editor, or text editor.

  • Delete the object.

  • See the Properties window associated with this object.

ECMAScript Object

The ECMAScript object represents an ECMAScript assigned to the Subscriber Channel.

Right-click the ECMAScript object to perform the following:

  • Edit, and copy the object.

  • Export an ECMAScript configuration to an XML file.

  • Under Live:

    • Deploy the ECMAScript

    • Compare the ECMAScript in Designer to a deployed ECMAScript in an Identity Vault

  • Open the object with the Designer built-in editor, Novell XML editor, or text editor.

  • Delete the object.

  • See the Properties window associated with this object.

Mapping Table Object

The Mapping Table object represents a Mapping Table assigned to the driver.

Right-click the Mapping Table object to perform the following:

  • Edit, and copy the object.

  • Export a Mapping Table configuration to an XML file.

  • Under Live:

    • Deploy the Mapping Table

    • Compare the Mapping Table in Designer to a deployed Mapping Table in an Identity Vault

  • Open the object with the Designer built-in editor, Novell XML editor, or text editor.

  • Delete the object.

  • See the Properties window associated with this object.

User Application Object

The User Application object allows you to manage workflow provisioning. Right-click the User Application object to perform the following:

  • Show the Dataflow view.

  • Manage application schemas.

  • Set up remote control through VNC connectivity.

  • Generate documentation for the User Application.

  • Under Driver:

    • Import objects into a driver

    • Deploy the User Application object

    • Compare objects in Designer to deployed objects in an Identity Vault.

    • Set up driver security

  • Delete the User Application object.

  • Under Localize:

    • Export localization data

    • Import localization files

  • Under Configure:

    • Configure supported localization data

    • Configure default localization data

  • Under Live:

    • Deploy the User Application object to an Identity Vault.

    • Compare the User Application object in Designer to a deployed User Application object in an Identity Vault.

    • Import the User Application object from an Identity Vault.

  • Under Distribute, you can select Horizontal or Vertical.

  • Migrate the User Application object.

  • Export the User Application object to a file.

  • Import the User Application object from a file.

  • Validate the User Application object.

  • Show the Provisioning view.

  • See the Properties window associated with this object.

Default Notification Collection

Placeholder for all notification templates.

Right-click the Notification Collection object to perform the following:

  • Create a new notification template.

  • Edit Filter. (If you want to see e-mail templates in other languages, click this option and select the languages.)

  • Import a notification template from a file.

  • Add only the default notification e-mail templates in English to the Identity Vault. You can also select to overwrite existing templates.

  • Update all of the notification e-mail templates in all of the languages that are installed with Designer to the Identity Vault. You can also select to overwrite existing templates.

  • Under Live:

    • Import an e-mail template from an Identity Vault

    • Deploy e-mail templates

    • Compare the Notification Collection in Designer to a deployed Notification Collection in an Identity Vault

  • Under Localization:

    • Import localization data from a folder that stores localization data

    • Export localization data to a folder to store the exported localization data

  • See the Properties window associated with this object.

Notification Object

A notification template.

Right-click the Notification object to perform the following:

  • Under Live:

    • Deploy e-mail templates

    • Compare the Notification object in Designer to a deployed Notification object in an Identity Vault

  • Update all of the localized versions for the selected notification template that are installed with Designer.

  • Edit, copy, or save a template.

  • Open the object with the Designer built-in editor, Novell XML editor, or text editor.

  • Delete a template.

  • Under Localization:

    • Import localization data from a folder that stores localization data

    • Export localization data to a folder to store the exported localization data

  • See the Properties window associated with this object.