1. Application Framework: What's New

(Home)     Previous     Next


1. The Default Identity Manager Engine Version

The default Identity Manager Engine version is now Identity Manager 3.5. This means that whenever you create Identity Vaults or servers, Designer assumes that they have Identity Manager 3.5 capabilties. You are able to successfully deploy and run such configurations only on an actual Identity Manager 3.5 machine.

You can easily change this default setting in Designer's preferences or by directly setting the Identity Manager Engine version on any server in your configuration.


2. Designer Is Localized into Several Languages

Due to strong world demand, Designer is now internationalized. In addition to English, the following languages are available for Designer:

Chinese Simplified
Chinese Traditional
Dutch
French
German
Italian
Japanese
Portuguese
Spanish
When you install Designer, the installer asks you which language you want to use. The installer installs all languages but runs with the language that you select. When Designer is running, you can easily switch languages:

  1. Select Windows > Preferences.
  2. Select Designer for Identity Manager > Languages.
  3. Restart Designer, so that the changes can take effect.
    If you select Yes in the Apply changes prompt, Designer automatically restarts for you.


3. Add Class and Add Attribute Schema Wizards

New wizards step you through creating classes and attributes when you manage the Identity Vault schema. You use these wizards anytime you create a new class or attribute (for example, when you click Add Class in the Manage Schema dialog box).



These wizards help to ensure that all necessary information is filled out properly for the new class or attribute so that the schema can be exported without errors.



4. Heap Size Control

By default, the Heap Size control now shows on the bottom bar of Designer. This control indicates how much memory Designer is consuming and the maximum amount of memory that's allocated to Designer. You can free up memory by selecting the small garbage can icon. You can set a mark (or threshold) so that if the threshold is passed, the bar appears red, as a warning indicator.



Also, on the Designer icon that you click to run Designer, some arguments follow the executable. The arguments look like the following:

-Xms512m -Xmx1024m

The arguments specify the minimum amount of memory to allocate when Designer first loads and the maximum amount that Designer can possibly take. The -Xms setting is for the mininum, and the -Xmx setting is for the maximum. Both are done in terms of MB (512m means 512 MB). If you are on a low-memory machine, you might want to decrease the amounts. If you have abundant memory and typically don't simultaneously run other applications that require much memory, you might want to increase these settings. The default settings are already fairly high.

5. Project Checker

To help you better understand a problem, all project checks now have more information on each result.



6. Support for Large Fonts

Designer has much better support for larger system font sizes. See the Readme file for the recommended specifications.

7. Support for the New Daylight Savings Changes in North America

The JRE that ships with Designer has been updated to contain the latest changes to Daylight Savings Time in North America. A FAQ explains these changes.



Other Enhancements and Bug Fixes
  1. Fixed a converter problem with policies that were being reused. Click here for details.
  2. Removed extra delete, undo, and redo buttons on the main toolbar. Click here for details.
  3. Designer now automatically shows the Heap Status widget in Designer. Click here for details.
  4. Increased the maximum heap size from 512 MB to 1024 MB, allowing Designer more memory. Click here for details.
  5. Designer no longer runs out of memory while running Project Checker. Click here for details.
  6. Importing a project, even though manual check is enabled, no longer launches Project Checker. Click here for details.
  7. Project Checker no longer makes unneccessary checks on numerous drivers. Click here for details.
  8. Project Checker now automatically starts when you validate a project. Click here for details.
  9. Namespaces don't need to be declared in the DTD. Click here for details.
  10. Project Checker now reports correctly on Linux. Click here for details.
  11. Project Checker now runs on Save and displays results. Click here for details.
  12. Designer no longer prompts for the server refreshing the application schema when only one server is associated with the driver set. Click here for details.
  13. An incorrect password is no longer cached when authentication fails on driver status operations. Click here for details.
  14. An incorrect password is no longer cached when authentication fails on the Edit Server page. Click here for details.
  15. The Browse eDirectory button now works for all example configuration files when you use the Driver Configuration Wizard. Click here for details.


(Home)     Previous     Next