This document contains known issues and other information about Novell Designer 4.0.
The What's New section for Designer 4.0 for Identity Manager is included in the build. It will also be available online after Designer 4.0 is released.
The documentation for Designer 4.0 for Identity Manager is included in the build. It will also be available online after the latest version is released.
This Readme contains the known issues for Designer version 4.0. In addition to this Readme, there is a separate Identity Manager 4.0 Readme.
Additional documentation resources are also available for the following:
To browse the Designer help topics after Designer is installed:
In Designer, click.
Select a book, browse the table of contents, then click a topic.
To search for specific Designer information after Designer is installed:
Click, then enter text.
Press F1 on any page. (In Linux, press CTRL + F1.)
Type a topic in thefield, then click .
Designer includes User Interface translation for Brazilian Portuguese, Chinese (Simplified), Chinese (Traditional), Dutch, French, German, Italian, Japanese, and Spanish. The User Interface language can be chosen at install or at runtime through the Preferences dialog box.
This release does not include translation of Designer runtime help or product documentation. At this time, project documentation generated by Designer is available in English only.
Some plug-ins are provided by the metadirectory and are available only in languages supported by the metadirectory, including Chinese (Simplified), Chinese (Traditional), French, German, and Japanese. Some third-party plug-ins might be available in English only.
Some users have reported that they cannot install Designer on Windows. The install starts to run but closes with the following error:
"This Application has Unexpectedly Quit."
If you see this issue, do the following:
Right-click the Designer install.exe file and choose . Select the tab.
Under thesection, choose the option and select from the drop-down menu.
The Designer install should execute normally.
Designer 4.0 is officially tested and supported on Windows Vista. However, if you turn on User Account Control (UAC) in Windows Vista, programs might be unable to access some network locations and you cannot install Designer to a network drive. This problem might also occur when you use the command prompt to access a network location.
To resolve this problem, you need to configure the EnableLinkedConnections registry value by following instructions in an article entitled “After you turn on User Account Control in Windows Vista, programs may be unable to access some network locations” dated July 20, 2007, in the Microsoft Knowledge Base.
Follow these steps to apply the workaround to configure the EnableLinkedConnections registry value:
Click regedit in the box, then press .type
Locate and right-click the following registry subkey:
Select, then click .
Type EnableLinkedConnections, then press .
Right-click, then click .
In thedata box, type 1, then click .
Exit the Registry Editor, then restart the computer.
When you are installing to a path where there are double-byte characters and if your operating system is running the English version of Windows with the East Asian Language Packs installed, the install package throws an error, saying that it cannot extract the compressed file. There are known issues with using double-byte character sets (DBCS) in Windows file paths, to come from the OS vendor or the install framework vendor. As an alternative, you can install to DBCS paths when you are installing to a localized version of the operating system.
The following error occurs with some versions of Linux:
Invocation of this Java Application has caused an InvocationTargetException. This application will now exit.
The xhost program makes Linux more secure by not allowing other hosts and users to make connections to the X server. If you are logged in as a valid user and are trying to run the install as root, this error can occur. For more information on xhost, refer to the man page for xhost.
The following warning messages appear on the SUSE Linux Enterprise Desktop ( SLED 11) and openSUSE 11.1 platforms:
Gtk-Message: Failed to load module "gnomebreakpad": libgnomebreakpad.so: cannot open shared object file: No such file or directory
Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory
It is safe to ignore these messages.
To work around the issue, launch Designer through PuTTY and Xming:
Download PuTTY and save it in the Windows folder.
Download Xming and install it.
In the taskbar, click theicon .
At the command prompt, open PuTTY and paste "127.0.0.1:0.0" in the X display location.
In the category, go to.
In the category, go to the, click the default settings, and save them.
Open PuTTY and log in to a Linux system.
If you open the Designer 4.0 Readme during the Designer 4.0 installation, junk characters are displayed on the screen. It also shows an error. It is safe to ignore this error. The Readme opens correctly after the installation is successfully completed.
This issue occurs because a previous version of NICI might not have uninstalled properly and might have some residual files left on the file system.
To work around the issue, remove all the NICI files from the system and try reinstalling Designer and the Novell Client.
Passwords are obfuscated. However, if you have other sensitive data in your project file, it is not encrypted in any way, and you must take care to safeguard your information.
By default, Linux might be using a PDF reader (Evince) that doesn't support the embedded font we use to display double-byte characters. We recommend that you use the Adobe Acrobat Reader for Linux to support these languages.
To avoid a memory outage, generate documents individually for Identity Vaults, drivers, and driver sets.
The following sections provide information for known issues at the time of the product release.
When you run Designer in any language, by default you see only notification templates for the language that you are running in. To see templates in additional languages, change the filter settings for the Outline view:
Click the filter icon in the upper right corner of the Outline view.
Select the languages that you want to see.
Also, when creating new templates, you must add the correct language code to the template name so that your new templates are filtered correctly. For example, a German template should be named <TemplateName_de>. The language codes are as follows:
Windows Vista has implemented a new User Account Control feature that prevents applications from running as Administrator unless you specifically allow it.
If Designer does not install correctly or launch after installation on Windows Vista:
Right-click the Designer shortcut on the desktop.
For Designer auto updates to work on Windows Vista (Ultimate and Business versions), ensure that the logged-in user is an Administrator or equivalent.
When running Designer on Windows Vista, you might see poor performance when doing live operations against a Windows 2003 server. You can resolve this issue by disabling TCP Auto Tuning on Windows Vista. To do this, open a command prompt and enter the following:
netsh interface tcp set global autotuninglevel=disabled
If you get the following error message during the installation of Designer, one of the reasons could be that the path of the Designer executables is too long. In spite of the error message, Designer installation completes successfully, but NICI fails to install.
Error Executing the Specific Program C:\Users\Administrator\AppData\Local\Temp\pftE915~tmp\Disk1\Setup.exe -s -f1C:\Users\Administrator\Desktop\designer_cdimage_win\linux\final\designer_win32\designer_install\components\nici\wcniciu0.iss -f2C:\Users\Administrator\AppData\Local\Temp\designerNici.log
To work around this issue, manually install NICI by running the <Designer Install Location>\components\nici\wcniciu0.exe command.
Afte you perform any live operation in Designer on Windows Vista, the JVM might crash when you close Designer. This is because of an errant call in JClient. If this happens, no data is lost; simply close the error window.
This issue is being addressed.
An application schema is not automatically imported by default. You can always perform a refresh application schema operation on a particular application after the project has been imported:
Right-click the driver.
You can also change this preference by selecting, then select .
120 DPI is too large for text in standard Windows XP decorations. Adjust the Display settings:
In the Control Panel, select.
In, toggle to .
If you have a display that needs120+ DPI fonts, you need ClearType. In addition to the obvious anti-aliasing aspects, ClearType gives fonts better weight. Without ClearType, the fonts are too thin and light, decreasing readability.
Click, then click
In thefield, reduce the , , and sizes.
Reduce title bars and related controls to a preferred size.
Fix icon spacing and scroll bar width.
Make sure that you are running at a very high resolution.
This helps eliminate most of the display issues on an HD monitor.
If you want to maximize the performance on large-scale operations (for example, copying and pasting several objects), the performance is up to ten times faster if you hide or close the Outline view. You get even more performance if you also close the Properties view. To quickly restore these views, click.
If a project contains a JDBC 3.5 driver, you might notice the default driver name is JDBC 3\.5. This is normal and allows the driver to deploy correctly.
Designer 2.1.1 workspaces are not compatible with Designer 4.0. Designer stores projects and configuration information in a workspace. These workspaces are not compatible from one version of Designer to another. You need to point Designer 4.0 to a new workspace, and not to a workspace used by a previous version of Designer.
The Role Editor does not support the fan-out driver capability and cannot choose logical systems for SAP drivers. Although it displays entitlements, it cannot differentiate the logical systems.
To resolve this issue, convert the older projects first to Designer 3.0.1 and then import them into Designer 3.5.
The internal Web browser does not work as expected because of XULrunner issues.
To work around the issue, get the external browser from. This brings up the iManager URL through the system default Web browser, such as Mozilla Firefox or Microsoft Internet Explorer.
ECMAScripts should be deployed along with their linkages. Direct deployment of the ECMAScript does not deploy the linkages. You can only add the deployed (eDirectory) scripts to the provisioning request definition (PRD) if the links that connect the ECMAScript with the driver are present.
You can link the ECMAScript with a driver in one of these ways:
Deploy the linkages in the driver by right-clicking.
Clickto create the policy linkages on the driver. When the driver is imported into the next project, the ECMAScript linkages are also imported.
When you see the scripts in the Outline view of next project, go to the Driver Configuration, click thetab and manually add the script. This creates a linkage between the script and the driver.
When the entity type is not specified, the MVEditor lookup selection filters the search results and displays the correct values. When the entity type is specified, the DAL query no longer returns the correct values.
To work around the issue, don't specify the DAL entity key if you are specifying the global expression because the global query already references an entity key in the definition. You can either specify the DAL entity key lookup and map the display expression or specify the DAL query global expression, but not both at the same time.
The issue does not occur if you don’t use an underscore (_) in the attribute name. For example, attributes such as TestName or Test-Name work fine, but Test_Name does not.
The Local History Preferences that come with Designer are an Eclipse feature. They are not intended to cache the Designer data.
To minimize the history that it can cache:
Access the Local History Preference page by clicking
Set the following preference values:
Days to keep files: 1
Maximum entries per file: 1
Maximum file size (MB): 1
Restart Designer to apply the changed values.
Some installations have reported a JVM terminated exit code=1 error on SLED 10 SP1 workstations. You can apply a temporary workaround by changing the /etc/X11/xorg.conf file as follows:
Option "MIT-SHM" "no"
Be aware that disabling this extension degrades performance.
The GNOME interface in openSUSE 10.3 does not initially work with Identity Manager Designer. For example Designer doesn't launch under GNOME, or Designer crashes as soon as you hover over a tooltip, or Designer crashes when deleting objects from the Project view. In order for openSUSE 10.3 with GNOME to work with Designer 3., you need to update all of the libraries from openSUSE.org. Be sure to include the following:
If you are having problems when running the updates, or if you need to configure the update server, go to the YaST Online Update documentation site for additional help.
When starting Designer (on openSUSE 10.3) with StartDesigner.sh, you might receive the following error on the console:
"*** stack smashing detected ***: ~/designer/jre/bin/java terminated"
Designer fails to start. This error might be a result of using the Smart Common Input Method platform (SCIM) language input system on your Linux desktop, and specifically the scim-bridge-gtk module for GTK. You can fix this error in one of two ways:
Remove the scim-bridge-gtk module.
Export the GTK_IM_MODULE=xim environment variable (click export GTK_IM_MODULE=xim for further instructions).
Although we cannot officially support all Linux distributions, many customers have reported success running Designer on Debian-based distributions, such as Ubuntu. To do this, perform the following steps:
Download and extract (to a folder of your choice) Designer from the Cool Solutions Web site.
Use Ubuntu's synaptic package manager to install the alien, rpm, and gettext packages (or from the command line, enter sudo apt-get -f install alien rpm gettext.
Change directories to the designerInstallDir directory.
At the command line, enter sudo rpm -ivh --nodeps components/nici/nici.i386.rpm).
This adds an entry to the RPM database that the installer checks for when you enter rpm -qa at the command line.
The gettext RPM is also required for the standard Designer installer. Download any installable gettext.rpm version and install it, such as rpm -ivh --nodeps gettext[version].rpm. This adds the gettext entry to the RPM database.
Run the standard Designer ./install script as a normal desktop user.
If you are running eDirectory on Linux and also want to run Designer, you might need to run Designer as root. The eDirectory install requires you to install its base packages as root. This prevents a typical user from running them. Specifically, Designer crashes if you are running as a nonroot user when importing or deploying and when connecting to a tree.
We don't recommend running Designer with the gtk-qt-engine RPM installed. This RPM package is installed with SUSE Linux and some other Linux distributions. Known issues cause crashes and Designer theme issues when this package is installed.
If you must use this RPM package, obtain the latest version. You can download this version from http://www.kde-look.org.
Even with the latest version of the package, Designer theme functionality might not be present.
To determine whether you have the gtk-qt-engine RPM package installed, enter:
rpm -qa|grep gtk-qt
If gtk-qt-engine appears in the list, you should remove the package by issuing the following command as the root user:
rpm -e gtk-qt-engine
If you encounter display issues in GNOME.
Select the Applications menu.
Click> , then decrease the size of the application font.
You can also adjust the thematic elements to your liking.
Keep in mind that GTK thematic elements can cause performance issues with Designer. If Designer is running slowly, especially when you use pull-down menus and other widgets, you might try changing to a simplified GTK theme.
Normally, this process fixes display issues.
Because Eclipse (Designer) is a GTK application, you should use GTK themes rather than qt-based themes.
First, you need to prepare to use the themes.
You must remove the gtk-qt-engine package mentioned in the Section 7.6, Running Designer on Linux with gtk-qt-engine. This can be done through YaST or by using the instructions given above.
You need to have the following packages installed on your Linux system. If you installed the GNOME subsystem, you already have these packages installed:
control-center2 > Gnome Control Center
gtk2-themes > or the themes you downloaded, and all the related dependencies
gnome-themes > only needed if you are going to use Gnome Control Center to set your theme
After you have completed the prerequisites, do one of the following:
Set your GTK theme and font settings from the KDE SUSE menu.. You can set this control center application to automatically run each time KDE is started. The following command accomplishes this:
ln -s /opt/gnome/lib/control-center-2.0/gnome-settings-daemon /home/user/.kde/Autostart
for "user", use your username
Create a GTK control file (usually named .gtkrc-2.0) in your user home directory or the directory where your system is configured to look for GTK2_RC_FILES. Entering "set |grep gtk" shows how this environment variable is configured and which files it is looking for. You can use any font and GTK theme that you prefer.
For example: include "/opt/gnome/share/themes/Xfce-stellar/gtk-2.0/gtkrc" style "user-font"
/gtkrc" style "user-font"
font_name="Sans Serif 6"
widget_class "*" style "user-font" gtk-theme-name="Xfce-stellar"
gtk-font-name="Sans Serif 6"
These problems occur because the XULrunner is not up to date: The following is a list of the prerequisites required for Eclipse 3.4.2 that Designer runs on:
Mozilla 1.4 GTK2 - 1.7.x GTK2
XULrunner 1.8.x - 1.9.0.x
To launch Designer, add XULrunner 188.8.131.52 version to the Designer.ini file.
Check the XULrunner version in the /usr/lib directory.
Add the XULrunner information by modifying the Designer.ini file.
Open the Designer.ini file from the Designer installation directory.
Add the following line at the end of the Designer.ini file:
Save the Designer.ini file and launch Designer.
If the 32-bit version of XULrunner is installed on a 64-bit Linux distribution, the JVM might crash when you launch Designer, when the Welcome Page displays, or when you view a Help topic. To resolve this problem:
Open the Designer.ini file located in the Designer installation directory.
Add the following line to the end of the Designer.ini file:
Save the Designer.ini file and launch Designer.
If the Welcome page doesn't display correctly on Linux, it is probably because your version of XULrunner isn't compatible with Eclipse. Designer uses the embedded browser that XULrunner provides in a few places, including the Welcome page and Help system.
To download a compatible version of XULrunner:
If buttons in dialog boxes do not respond to mouse clicks, you can work around this issue in one of these ways:
Use the Space key or the Enter key to activate the buttons.
Add export GDK_NATIVE_WINDOWS=true to the StartDesigner.sh file.
At times you cannot select drop-down options when creating or configuring a driver. To avoid the problem, use the following workaround:
Click the drop-down menu, but continue to hold the left mouse button.
Continue to hold the left mouse button until the desired option is highlighted.
Release the left mouse button to select the option.
When you browse the Help content on openSUSE 11.2 platform, it throws an exception. This is probably because your version of XULrunner is not compatible with Eclipse.To avoid this exception, use the following workaround:
Download the xulrunner-184.108.40.206.en-US.linux-i686.tar file and install it on openSUSE 11.2.
See the installation steps from Welcome Page Doesn't Display on Some Linux Distributions.
Open the Designer.ini file from the Designer installation directory and add the following line at the end:
Save the Designer.ini file and restart Designer.
If a field on a form used by a workflow returns the value, “undefined” the form does not display an Error or Warning message. This situation results from a problem in the script. In general, if a form script evaluates to, “undefined” the script is considered to be in error. The workaround is to make sure you do not set “undefined” in the preactivity mappings. To do this, use a try/catch/finally block to ensure that there is always a valid value being sent to each control.
You might encounter the following error message when trying to set Trustee Rights on a provisioning request definition or when trying to access the Identity Vault via the ECMA expression builder:
Cannot connect to host 'xxx', verify the address is correct and the server is running.
If the address is correct and the server is running, this might be caused by a slow connection.
You can change the connection timeout by setting the Connection preference via.
When you connect to the Identity Vault from the provisioning request editor (for example, when you set Trustee rights on a provisioning request definition) you are prompted for your Identity Vault credentials. If you type an incorrect password and click thebutton in the Identity Vault credentials dialog box, you cannot connect to the Identity Vault and you are not prompted to retype your credentials.
To work around this issue, access the Modeler view and reconfigure the Identity Vault credentials for the project.
Under the Resources List in the Role Editor, a read-only list of the associated resources is available along with the role. The information in this list is obtained and updated for all the roles when the Role Catalog is imported from eDirectory. You can see new resource associations but not the resource associations that have been removed in the User Application.
To work around this issue, ensure that the deleted resource associations are removed from the Resources List.
Before performing a Live Import from the Role Catalog, go to the Navigator View and navigate to the \MyProject\Model\Provisioning\AppConfig\RoleConfig\ResourceAssociations folder.
Remove all the files in the folder except the ResourceAssociations.digest file.
From the Provisioning View, select the Role Catalog object and run the Live Import to import all of the resource associations again and to provide the updated correct information.
If you add a User Application driver to a project under version control, and you perform a compare, (after checking in the project again), you might see the following exception in the error log:
Unable to find a light item for the path: Model/Provisioning/AppConfig/.appconfig
You can safely ignore this error.
If you import a project archive file into Designer, you might not see existing team definitions. You also see the following error in the error log:
To make the team definitions available, restart Designer.
If you use both the User Application user interface and Designer to create roles, Designer's Live Compare feature might not display the expected results. To work around this problem, do the following:
Use only Designer to create, delete, or modify all roles.
Use the Compare window that displays during a deploy. The Compare window displays the correct results. You can cancel the deploy if you only want to see the compare results.
If you commit on any provisioning objects to version control when the Provisioning Request Definition (PRD) is open with unsaved changes, you receive a Null Pointer Exception error in the error log. You might not realize that the commit failed unless you have the Error Log view open. The easy workaround is to save the provisioning object before checking it into version control or to close the object without saving it.
If you revert a provisioning request definition (PRD) while it is open in the provisioning request definition editor, the editor closes, then reopens with the refreshed version of the PRD. This is a normal action of the provisioning request definition editor.
When you use the Locales and Localization Resource Groups window () to add and remove locales, then perform a version control , Designer might incorrectly indicate that the local object has changed. This happens if you have not made any changes, but you close the window by clicking . You can ensure that this does not happen by clicking instead of .
If you set trustees on one of the read-only provisioning request definitions (such as the Roles or Attestation objects) on a User Application driver migrated to 3.6.1, Designer creates an extra copy of the provisioning request definition. You see two objects with the same name in the Provisioning view.
To delete the extra object:
Back up your project.
With the project open, access the Navigator view, then navigate to the project's Model\Provisioning\AppConfig\RequestDefs folder.
The Navigator view displays the provisioning request definitions as .prd and .digest files. The extra copy of the provisioning request definition has the same name with a number appended to it. For example, the Attestation Report displays in the Navigator view as AttestationReport.prd and AttestationReport.digest. The extra copy displays as AttestationReport1.prd and AttestationReport1.digest.
Delete the files with the number appended to the name; for example, AttestationReport1.prd and AttestionReport1.digest.
Save the project.
Identity Manager 4.0 entitlements accept JSON expressions. However, the generated expression returns a simple parameter, for example:
Ensure that you edit the expression to be a JSON expression. For example, for an Active Directory driver, modify the expression as follows:
You should manually add and deploy the notification templates while working with the User Application drivers migrated from User Application versions prior to 3.7. Use the following steps to deploy the notification templates:
Go to the Outline view in the Designer.
Go to the Identity Vault where the migrated environment is created.
Clickthen right-click .
Go to theand deploy all the changes.
There is an intermittent problem that occurs when you compare a large project, or when you have a very slow connection when comparing a project. Compare takes a long time to run and not all of the items appear in the Compare window. Most of the time this problem goes away when you try again. If the problem persists, contact Novell Support for information about temporarily turning off the status thread.
If you add a driver to a driver set on one computer, save that update to a version control server, then perform Get Updates on a second computer, you won't see the driver added to the driver set. If this happens, refresh the Modeler view by closing and then reopening the view. Then run refresh on the Version Control view.
Copying and pasting or dragging and dropping operations in the Navigator View are not handling files properly if they are under version control. The workaround is to perform these operations from the Project view.
If you are automatically downloading packages from a site that requires authentication, the download fails. You can work around this problem by configuring Designer to automatically authenticate to the download site.
In Designer, click> .
Specify the server and port of the proxy server.
Specify the username and password used to authenticate to the site where you download packages.
Clickto save the changes.
The import of a license for a package fails on OpenSUSE 11.2. Steps to duplicate:
In a Designer project, right-click the Identity Vault.
Select, then click .
Create a new package.
Right click the new package, click.
Click License, then browse to and import the package license.
The import fails.
The reason the import fails is that the XULrunner is out of date. The following is a list of prerequisites for Eclipse 3.4.2 that Designer runs on:
Mozilla 1.4 GTK2 - 1.7.x GTK2
XULrunner 1.8.x - 1.9.0.x
You can download the most recent version of XULrunner from Mozilla FTP site.
Designer 4.0 is a full-fledged RCP application. It does not support upgrades from previous versions of Designer. You can still export Designer 3.0.1 workspaces into Designer 4.0, which triggers the project conversion and converts the project to a 4.0 version.
The Loading Help dialog box appears but the Help window does not appear. The Loading Help dialog box is not closed until Designer is restarted.
Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2010 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.