8. Policy & Simulation: What's New

(Home)     Previous     Next


1. Multiple Drectories for External Java Classes

Designer 2.0 M5 enables you to specify multiple directories for your external Java classes that the Simulator uses. The directories are still configured on the Simulation tab in the Designer for IDM preferences. You can add or remove directories by using the buttons to the right of the Java Extensions directory list..



2. Policy Linkage Support

Designer 2.0 M5 has been updated to support Identity Manager 3.5. This engine version changed the manner in which policies are linked in the policy set of a driver or channel. In earlier releases, if a policy P1 was included in the Input policy set of a driver and was followed by policy P2, P1 needed to be followed by P2 in every other policy set it was contained in.

The following image illustrates P1 being included in both the Input and Output Transformation policy sets. In both policy sets, the policy P1 is followed by P2.



The new policy linkage removes this restriction by allowing policies to be included in any order within any policy set. For example, the Input policy set of a driver can contain policy P1, followed by P2, while the Output Transformation policy set can contain policy P1 followed by P3.

The following figure illustrates the new policy linkage. Policy P1 is included in both the Input and Output Transformation policy sets. However P1 is followed by P2 in the Input policy set and by P3 in the Output policy set.



The Policy Manager view prevents creating an invalid policy linkage when the server associated with a driver set is set to a pre-3.5 version. The following dialog box is displayed when an invalid policy linkage is encountered



It is possible for you to set up an Identity Manager 3.5 system and create policy links that are incompatible with a pre-3.5 environment. If you downgrade a server to a pre-3.5 version, project checks notify you that the policy linkage cannot be deployed.



3. Library Support (Identity Manager 3.5 Only)

Library objects were introduced in Identity Manager 3.5. They enable you to organize your shared Policy and Resource objects. Library objects can be contained by an Identity Vault or a driver set.

To create a Library object:

  1. Select an Identity Vault or a driver set in the Modeler.
    The Identity Manager version for a server in the Identity Vault or driver set list must be 3.5 or later. If you need to change the version of a server, edit the server's properties by selecting 3.5 from the drop-down menu. The following figure illustrates the properties page of a server with an Identity Manager version set to 3.5.



  2. Click Model > Library > New.




  3. Specify the name of the Library.


Library objects can contain DirXML Script, Stylesheet, Mapping Policies, ECMAScript, Mapping Table, and Resource objects. These objects can be added to the library by using the context menu in the Outline view.

If the version of the server on the driver set or Identity Vault is earlier than 3.5, Designer prevents you from creating a library and displays the following message:



If you create a Library object in an Identity Manager 3.5 system and then downgrade your server to a pre-3.5 version, Project Checker notifies you that the Library is not a compatible feature with the Identity Manager version.

The properties page of a Library object changes, depending on whether the Library is contained by an Identity Vault or a driver set. If the library is contained by an Identity Vault, a Context field specifies the Container object where the library should be deployed. Because the library is contained by the driver set when it is deployed, this field is not available when the library is contained by a driver set.



4. Resource Support (Identity Manager 3.5 Only)

Resource objects are a new object type, introduced in Identity Manager 3.5. You can create several types of Resource objects, including Mapping Table, ECMAScript and Credential Provisioning. Each type of object has a purpose. By using using a context menu, you can create Resource objects under a Library, Driver, Publisher channel, or Subscriber channel object.

The following figure illustrates the dialog box to create an ECMAScript Resource object.



For more information on the use and functionality of these objects, refer to the Policies in Designer 2.0 guide.



Other Enhancements & Bug Fixes
  1. Add icons next to policies in Edit Policy dialog - Click here for details...
  2. Copy / paste option for policy simulations - Click here for details...


(Home)     Previous     Next