When you drop an Identity Vault, the dialog box for configuring
your server is much simpler and now allows you to set the Identity Manager version.
Simple error checking makes sure you type a well-formed DN and that the server
name and context are unique. The server is added to the Identity Vault and associated
with the driver set, which is automatically created.
Driver Set. Whenever you create a driver set, you are
prompted for its server and are allowed to select the Identity Manager version.
If servers are available on the Identity Vault but aren't being used, they are
added to a drop-down combo box. If you select one of these servers, its Identity
Manager version is taken.
Application or System. In earlier Designer versions, if you dropped an
application or system into the Modeler, but no Identity Vault existed, the Modeler
tried to create one for you. As in earlier milestones, Designer 2.0 M5 prompts
you to specify a server and version. In M5, if you select Cancel, the application
or system is still created, but no Identity Vault is created, and the application
is not connected to anything.
Designer also prompts for a server if you drop the application or system near
an empty Identity Vault. The Identity Vault is highlighted. When you drop the
application, Designer asks you for a server and version, which are created and
auto-connected when you drop the application
Basically, Designer always tries to make sure that you have a server set up (even if it's a dummy one) with the correct Identity Manager version set. This is very important for the following reasons:
|
The following improvements have been made to the Modeler toolbar:
|
If a driver set is associated with a server, a server icon
is super-imposed on the driver set. If no servers are set up, the server icon
does not appear.
The following have been added:
|
Many sanple driver configuration files have been updated. A new generic Loopback driver configuration file has been associated with the LoopBack application. Also, JMS uses the new JMS3 driver configuration, and a driver configuration has been provided for Legacy Workflow..
The following improvements have been made the the Search dialog box::
|
Previously, Designer used the term "Resource" for objects
that can be used for generic modeling and diagramming purposes. These objects
have no direct correlation with Identity Manager or DirXML and don't get deployed,
but they are useful for diagramming. Because the Identity Manager engine is
introducing a new concept called a DirXML Resource (or IDM Resource), we decided
to rename what we were calling "Resource" to "Design Element". This change ensures
that terms don’t conflict and aren’t ambiguous.
In the Modeler, if you select a driver (or application) and press Ctrl+C or Ctrl+V, Designer copies the driver and all of it policies and resources. This feature has been working for several milestones. However, the copy never deep-copied the policies in the channels.
Designer 2.0 M5 now fully copies all policies and resources (including the new Identity Manager 3.5 object types) in the driver, and both the Subscriber and Publisher channels. This version also copies all jobs under a driver. Copy and paste have been extended to include the following:
|
 |
Other Enhancements & Bug Fixes |
|
