Novell Identity Manager Designer 4.0.2 Readme

January 2014

This document contains known issues and other information about Novell Designer 4.0.2.

1.0 Documentation

1.1 What's New in Designer 4.0.2

The What's New section for Designer 4.0.2 for Identity Manager is included in the build. This section will also be available online after Designer 4.0.2 is released.

1.2 Finding Documentation

The documentation for Designer 4.0.2 for Identity Manager is included in the build. This documentation will also be available online after the latest version is released.

This Readme contains the known issues for Designer version 4.0.2. In addition to this Readme, there is a separate Identity Manager 4.0.2 Readme.

Additional documentation resources are also available at the following locations:

1.3 Browsing or Searching

To browse the Designer help topics after Designer is installed:

  1. In Designer, click Help > Help Contents.

  2. Select a book, browse the table of contents, then click a topic.

To search for specific Designer information after Designer is installed:

  1. Click Help > Search, then enter text.

    Or

    Press F1 on any page. (In Linux, press CTRL + F1.)

  2. Type a topic in the Search field, then click Go.

2.0 Localization

2.1 Available Languages

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 during installation or runtime, through the Preferences dialog box.

2.2 Non-Translated Components

This release does not include translation of the Designer runtime help or product documentation. At this time, the project documentation generated by Designer is available in English only.

2.3 Plug-Ins

Some plug-ins are provided by the metadirectory and are available only in the 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.

3.0 Installation Issues

3.1 Installing Designer to a Network Drive with UAC Turned On in Windows Vista

Designer 4.0.2 is officially tested and supported on Windows Vista. However, if you turn on User Account Control (UAC) in Windows Vista, the 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 the 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:

  1. Click Start, type regedit in the Start Search box, then press Enter.

  2. Locate and right-click the following registry subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.
    
  3. Select New, then click DWORD Value.

  4. Type EnableLinkedConnections, then press Enter.

  5. Right-click EnableLinkedConnections, then click Modify.

  6. In the Value data box, type 1, then click OK.

  7. Exit the Registry Editor, then restart the computer.

3.2 Installing on English Windows with the East Asian Language Pack and with a Double-Byte Install Path

When you are installing on 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 that 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.

3.3 Warning Messages When You Start Designer after Installing

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.

3.4 Establishing Communication with eDirectory within Designer 4.0.2 Causes an Error on Windows 7

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 reinstall Designer and the Novell Client.

3.5 Designer Doesn't Launch after Installation on Windows Vista

Windows Vista implemented a 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:

  1. Right-click the Designer shortcut on the desktop.

  2. Select Run as Administrator.

For Designer auto-updates to work on Windows Vista (Ultimate and Business versions), ensure that the logged-in user is an Administrator or equivalent.

3.6 NICI Fails to Install on Windows during Designer Installation

If you get the following error message during the installation of Designer, one of the reasons could be that the path of the Designer executable 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.

3.7 Installing Designer on openSUSE 10.3 with the GNOME Interface

The GNOME interface in openSUSE 10.3 does not initially work with Identity Manager Designer. For example, Designer doesn't launch under GNOME, 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.x or later, you need to update all of the libraries from openSUSE.org. Be sure to include the following:

  • bug-buddy

  • gtk2

NOTE:Designer requires the 32-bit version of the gtk2 RPM, even when you install Designer on a 64-bit system.

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.

3.8 Installer Does Not Create Designer Desktop Shortcut on Non-English openSUSE Servers

If you install Designer 4.0.2 on an openSUSE server in a non-English environment, the installer does not create a Designer shortcut icon on the desktop.

3.9 Designer Fails to Launch on SLES 10 Platform

After you install Designer 4.0.2 on a SLES 10 server, Designer crashes with the error message (Too many open files). To work around this issue, increase the number of open connections for the server from the default value of 1024 before you open Designer.

To increase the number of open connections allowed to 4096, execute the ulimit -n 4096 command in the terminal where configuration is invoked. Ensure that your console terminal shows open files (-n) 4096 when you run the ulimit -n command.

3.10 Uninstallation Does Not Remove Packages and Plugins Folders from Windows Server

When you run the installer to uninstall Designer from a Windows server, the installer might not remove all folders created during the installation process. In some environments, the installer does not remove the packages or plugins folders from the Designer installation folder.

4.0 General Issues

The following sections provide information for known issues at the time of the product release.

4.1 The Project Converter Does Not Support Remotely Mounted Workspace

If you convert the Designer 3.5 project to Designer 4.0.2 after mounting the Designer 3.5 workspace in the local machine where Designer 4.0.2 is installed, the Project Converter does not convert the Designer 3.5 project.

To work around this issue, copy the Designer 3.5 workspace to the local machine where Designer 4.0.2 is installed, then run the Project Converter.

4.2 The Internal Web Browser Does Not Work on Linux Platforms in Designer

The internal Web browser does not work as expected because of XULRunner issues.

To work around the issue, get the external browser from Designer > Windows > Preferences > General > Web Browser > Use External Web Browser. This brings up the iManager URL through the system default Web browser, such as Mozilla Firefox or Microsoft Internet Explorer.

4.3 Setting the LDAP Ports Correctly after Importing a Project into Designer

When you create a project after importing it from a live system in Designer, Designer does not correctly set the ports in the Identity Vault Properties view.

To work around this issue, change the LDAP ports in the Identity Vault Properties view prior to deploying the imported project.

4.4 Creating Icons in 64-bit Installation Requires 32-bit Libraries

When you create a new icon using a 64-bit SLES 11.x installation of Designer, Designer fails with a NoClassDefFoundError. If this occurs, Designer might require the 32-bit liblcms.so.1 and libjasper-1.701.so.1 libraries in order to launch the Icon Editor.

4.5 Designer Does Not Support Using dn-ref Job Parameters as Package Prompts

Designer does not support using job parameters of the dn-ref type as package prompts. In situations where you want to add a dn-ref job parameter as a package prompt, you must use a dn job parameter as a package prompt, instead.

4.6 Cannot Configure Query Token to Read Multiple Attributes Using Argument Builder

In the Policy Builder, when you create a new rule and use a Query token in an action within the rule, you can only use the Argument Builder to specify a single attribute for the query to read. If you add more than one attribute, Designer only uses the most recently added attribute in the query.

If you need to add multiple attributes to a Query token, you can either add attributes in Policy Builder without opening the Argument Builder or modify the XML to include the attributes you want to add.

To add attributes in Policy Builder, click the plus icon for each attribute you want to add and specify the attribute values you want to add into the Read attribute fields. Do not click the Edit the arguments icon. Click Finish, and Policy Builder appends the attributes to the expression rather than replacing the existing attribute.

To add attributes in the XML, open the policy in Policy Builder, click the XML Source tab, and manually add the additional attributes as new token-text elements within the token-query element.

4.7 Argument Builder May Not Successfully Remove Arguments from Specific Actions

If you previously upgraded your Designer installation to Designer 4.0.2 AU2 and then used the Argument Builder to remove an argument from one of several types of actions and add a new argument, the Argument Builder may not remove the previous argument from the action. With the duplicate argument, the action cannot function properly.

This issue affects the following actions:

  • append XML text (do-append-xml-text)

  • rename destination object (do-rename-dest-object)

  • rename source object (do-rename-src-object)

  • set operation class name (do-set-op-class-name)

  • set operation property (do-set-op-property)

  • set XML attribute (do-set-xml-attr)

  • status (do-status)

  • trace message (do-trace-message)

If you upgraded to 4.0.2 AU2 and modified one of the above actions in a policy rule, reopen the policy in Policy Builder, click the XML Source tab, and manually remove any duplicated arguments in the rule XML.

We also recommend you immediately upgrade your Designer environment to Designer 4.0.2 AU2a or later to avoid this issue when you modify any of the above actions in the future.

4.8 Designer May Not Properly Display User Application Driver Packages After Upgrading

If you create a non-base package for a User Application driver in Designer and then upgrade to Designer version 4.0.2 AU3, Designer does not display the package in the Available Packages list when you install the User Application driver.

To install the package, clear Show only applicable package versions, select the appropriate package, and click Next.

4.9 Designer Cannot Merge Different Global Configuration Value Versions During Driver Import

If you install a driver in Designer that includes at least one global configuration value (GCV) and then try to import a second version of the driver that has a modified version of the existing GCV, Designer displays a message saying the global variables could not be merged.

Designer does not currently support merging existing GCVs during the driver import process, whether the conflicting GCVs are located on the driver, in the driver set, or in any GCV resource objects.

4.10 Reports Specify Driver DN for Managed eDirectory Systems

If you install a Bi-directional eDirectory driver in your Designer environment with the eDir2eDir Account Tracking package with the name NOVLEDIR2ATR_2.0.0.20120524121511.jar, upgrade to the package with the name NOVLEDIR2ATR_2.1.0.20130312104938.jar, and then run a report on a managed eDirectory system, the report returns the distinguished name (DN) for the driver.

If you install a new Bi-directional eDirectory driver using the package with the name NOVLEDIR2ATR_2.1.0.20130312104938.jar and run a report, the report displays correctly.

To resolve this issue, complete the following steps:

  1. Open Designer.

  2. In the Modeler, right-click the driver and select Driver > Properties.

  3. Click GCVs.

  4. Click the Account Tracking tab.

  5. In the Identifiers field, click the Add an item icon.

  6. Specify LDAPDN for the new list value and click OK.

  7. Click OK.

  8. Deploy the modified driver.

4.11 Designer Does Not Re-import Roles or Resources Previously Exported to XML

If you create a role or resource subcontainer in the Provisioning view Role Catalog, add a role or resource to that subcontainer, export the Role Catalog to an XML file, then delete the subcontainer and role or resource and attempt to recover the role or resource by importing from the XML file, the import does not recreate the role or resource.

To import Role Catalog subcontainers and objects from an XML file, you must create a new User Application driver and import the XML file into that driver’s Role Catalog.

4.12 Designer Overwrites Modified Package Linkage Order on Update

If you modify the order of linkages within a package, Designer does not recognize the package as being customized. If you then update the package, Designer overwrites the modified linkage order with the linkage order specified in the updated package.

4.13 Generating Checksums for Custom Packages Containing Jobs

Previous versions of Designer incorrectly generated checksums for custom packages containing jobs. Designer 4.0.2 AU4 now correctly calculates checksums for all packages, including packages that contain jobs.

To correctly generate checksums for packages, package developers must import and re-release their custom packages in a Designer 4.0.2 AU4 environment.

5.0 Linux Issues

5.1 Stack Smashing Error on openSUSE 10.3

When starting Designer with StartDesigner.sh on openSUSE 10.3, 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, 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.

5.2 Running Designer on Linux with gtk-qt-

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 use this RPM package, obtain the latest version. You can download this version from the KDE-Look Web site.

Even with the latest version of the package, the 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

5.3 Designer Launch Fails on SLED 10.3 or SLED/SLES 11

5.3.1 Designer Requires Specific Version of XULRunner in SLED/SLES 11 Environments

In SUSE Linux Enterprise Server and SUSE Linux Enterprise Desktop 11 environments, Designer requires version 1.9.2.24 - 2011110900 of the XULRunner runtime environment, which is included with SUSE Linux Enterprise Server and Desktop 11 Service Pack 2. If you have a different version of XULRunner installed, Designer may not launch properly.

5.3.2 Adding XULRunner to Designer.ini on SLED 10.3 or SLED 11 64-Bit

To launch Designer, you must add the appropriate version of XULRunner to the Designer.ini file using the following steps:

  1. Check the XULRunner version in the /usr/lib directory.

  2. Open the Designer.ini file from the Designer installation directory.

  3. If you are running SLED 10.3, add the following line at the end of the Designer.ini file:

    -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner-1.8.1.21/
    
  4. If you are running SLED 11, add the following line at the end of the Designer.ini file:

    -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner-1.9/
    
  5. Save the Designer.ini file, then launch Designer.

5.3.3 JVM Crashes When Launching Designer, the Welcome Page, or Opening Help on 64-Bit Linux

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:

  1. Open the Designer.ini file located in the Designer installation directory.

  2. Add the following line at the end of the Designer.ini file:

    -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner-1.9/
    
  3. Save the Designer.ini file, then launch Designer.

5.3.4 The Welcome Page Doesn't Display on Some Linux Distributions

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 the Help system.

To download a compatible version of XULRunner:

  1. Download the XULRunner installer for Linux from the Mozilla FTP site.

  2. Unregister your current version of XULRunner by running the following command as root:

    xulrunner --unregister-global
    
  3. Follow the instructions to install XULRunner.

  4. Restart Designer, then confirm that the Welcome page is working as expected.

5.4 An Exception Occurs while Browsing the Designer 4.0.2 Help System

When you browse the Help content on the 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:

  1. Download the xulrunner-1.8.1.3.en-US.linux-i686.tar file, then install it on openSUSE 11.2.

    For instructions, see the installation steps in the The Welcome Page Doesn't Display on Some Linux Distributions.

  2. Open the Designer.ini file from the Designer installation directory, then add the following line at the end:

    -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner
    
  3. Save the Designer.ini file, then restart Designer.

5.5 Designer Does Not Display Welcome Page Properly in openSUSE 11.4

When you install Designer on an openSUSE 11.4 server, Designer does not display the Welcome page correctly.

To resolve this issue, install XULRunner 1.9.2 on the openSUSE server:

  1. Open the Designer.ini file located in the Designer installation directory.

  2. Add the following line at the end of the Designer.ini file:

    -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner-1.9.2/
    
  3. Save the Designer.ini file, then launch Designer.

5.6 Designer May Crash When You Perform Some User Application Operations on SLES 11.2 64-Bit Platform

To resolve this issue, modify the Designer.ini file as follows:

  1. Open the Designer.ini file located in the Designer installation directory.

  2. Add the following line at the end of the Designer.ini file:

    -DloadAWTOnDesignerStartup=true
    
  3. Save the Designer.ini file, then launch Designer.

6.0 Windows Issues

6.1 Live Operations on Windows Vista Are Slow

When you run Designer on Windows Vista, you might see poor performance when doing live operations on a Windows 2003 server. You can resolve this issue by disabling TCP Auto Tuning on Windows Vista. To do this, open a command prompt, then enter the following:

netsh interface tcp set global autotuninglevel=disabled 

6.2 The JVM Crashes When You Close Designer on Windows Vista

After 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.

6.3 Document Generator Requires Library Refresh to Generate Valid Documentation After Upgrade

If you upgrade from Designer 4.0.1 to Designer 4.0.2 on a Windows computer and then try to generate documentation for the project, you cannot open the generated PDF because of multiple errors.

To work around this issue:

  1. Close Designer 4.0.2.

  2. Back up the endorsed Java Runtime Environment (JRE) library directory to another location on your computer. By default, this directory path is <Designer installation directory>/jre/lib/endorsed.

    NOTE:If you installed Designer using the integrated installer, the path for the endorsed directory may be different. The default path when using the integrated installed is <Designer installation directory>/../jre/lib/endorsed.

    If you use a custom JRE, back up the folder from this path: <JRE directory>/jre/lib/endorsed.

  3. The path may be different for different versions of JRE.

  4. Delete the original endorsed directory.

  5. Start Designer.

  6. When Designer prompts you to install the missing .jar files included in the endorsed directory, follow the instructions to copy the correct set of .jar files.

  7. Restart Designer.

  8. Open the project and re-generate documentation.

For more information about generating documentation for projects, see “Documenting Projects” in the Designer 4.0.2 for Identity Manager 4.0.2 Administration Guide.

6.4 Designer Cannot Install Updates on Windows 7

If you install Designer on a computer running Windows 7, you may encounter an issue where you cannot update either Designer or packages installed in Designer. This issue indicates that Designer does not have the permissions necessary to add or modify files in the installation directory.

To work around this issue, open Designer using an account with Administrator access:

  1. Using an account that is a member of the local Administrators group, log onto the Windows 7 computer with Designer installed.

  2. Navigate to the desktop.

  3. Right-click the Designer shortcut and select Run as administrator.

  4. If the operating system prompts you for confirmation, click Yes.

  5. In Designer, click Help > Check for Package Updates or Help > Check for Designer Updates, as necessary.

6.5 Designer Displays Expand and Collapse Icons Only on Mouse Over by Default

If you install Designer on a computer running Windows 7 computer, Designer only displays the expand and collapse icons for an expandable list when you mouse over that list. When you move the mouse away, the expand and collapse icons fade and disappear. By default, Designer uses this standard Windows 7 behavior for expandable lists.

If you want to configure Designer to always display expand and collapse icons, complete the following steps:

  1. In Windows Explorer, navigate to the Designer.exe file.

  2. Right-click Designer.exe and select Properties.

  3. Click the Compatibility tab.

  4. Select Disable visual themes.

  5. Click OK.

6.6 Designer May Not Create Role Catalog on Windows 7

In some Windows 7 environments, when you install a new User Application driver in Designer, Designer may not automatically create the Role Catalog under the User Application container.

To resolve this issue, complete the following steps:

  1. Save your project and close Designer.

  2. Navigate to your Designer installation folder and open the plugins subfolder.

  3. Move the following subfolders from the plugins folder to a safe location on your local drive:

    • com.novell.prov.roles_4.0.0.201104051747

    • com.novell.prov.roles_4.0.0.201206110753

    NOTE:If your plugins folder contains the com.novell.prov.roles_4.0.0.201307181204 subfolder, do not move that folder.

  4. Start Designer and install a new User Application driver.

7.0 Workflow/Provisioning Issues

7.1 Resources Associated with Roles Are Not Deleted from the Resources List of the Role Editor

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:

  1. Before performing a Live Import from the Role Catalog, go to the Navigator View, then navigate to the \MyProject\Model\Provisioning\AppConfig\RoleConfig\ResourceAssociations folder.

  2. Remove all the files in the folder except the ResourceAssociations.digest file.

  3. From the Provisioning View, select the Role Catalog object, then run the Live Import to import all of the resource associations again and to provide the updated correct information.

7.2 Designer Returns Error When Deploying Role Catalog After Deleting Role or Resource Subcontainers

If you create a role or resource subcontainer, add one or more objects to the subcontainer, deploy the Role Catalog, and then delete the subcontainer and try to re-deploy the Catalog, Designer returns a java.lang.NullPointerException error message.

This issue occurs because Designer does not immediately delete role or resource objects when you delete those objects in the Role Catalog. Instead, Designer marks the objects for deletion by the Role and Resource Service Driver when the driver deploys the Catalog to the Identity Vault.

To resolve this issue, complete the following steps:

  1. In the Provisioning view, right-click the role or resource object located in the subcontainer you want to delete and select Delete.

  2. Select Delete object in identity vault on deploy of parent container, then click OK.

  3. Right-click Role Catalog and select Live > Deploy All.

  4. Click Deploy, then click OK.

  5. To verify the Role and Resource Service Driver has deleted the role, log into iManager.

  6. In iManager, click View Objects.

  7. In the Tree, navigate to your User Application driver and expand AppConfig > RoleConfig > RoleDefs.

  8. Click the container where the role was previously stored. If the role is still in the container in the Identity Vault, refresh until the Role and Resource Service Driver removes the role.

  9. In the Provisioning View in Designer, right-click the subcontainer you want to remove and select Delete, then click OK.

  10. Right-click Role Catalog and select Live > Deploy All.

  11. Click Deploy, then click OK.

7.3 Designer Displays Incorrect Status When Deleting Roles

Designer currently displays deployment status incorrectly when you delete a role from the Role Catalog in Designer and then deploy the Catalog to the Identity Vault. In some instances, when the Role and Resource Service Driver successfully deletes a role from the Identity Vault, Designer incorrectly displays a failure message. At the same time, if the Role and Resource Driver is stopped, Designer incorrectly displays a success message.

To verify that the Role and Resource Driver removed the role you deleted from the Identity Vault, complete the following steps:

  1. Log in to iManager and click View Objects.

  2. In the Tree, navigate to your User Application driver and expand AppConfig > RoleConfig > RoleDefs.

  3. Click the container where the role was previously stored.

  4. When finished, close iManager.

7.4 Updating Any User Application Package Causes Designer 4.0.2 AU4 to Create Duplicate Objects and Block Deploying the Driver

If you install Designer 4.0.2 AU4 in your environment, import or create the User Application driver, and then upgrade or downgrade any of the User Application driver packages, Designer creates duplicate objects in the DAL, including objects in the User, Provisioning, Role, and Resource categories. Because of the duplicate objects, Designer then cannot deploy the driver to the live environment, and the driver cannot function properly.

To resolve this issue, complete the following steps:

  1. Start Designer.

  2. When prompted to check for Designer updates, select Yes and click OK.

  3. Update your Designer installation to the 4.0.2 AU4a version.

  4. Delete the existing User Application driver.

  5. (Conditional) If the Identity Vault contains a previous version of the User Application driver, complete the following steps:

    1. In the Modeler, right-click the driver set and select Live > Import.

    2. Click Browse.

    3. Select the User Application driver in your Identity Vault and click OK, then click Continue.

    4. Click Yes to confirm.

    5. Click Import, then click OK when finished.

  6. (Conditional) If you have a previous backup of the User Application driver, complete the following steps:

    1. In the Modeler, right-click the driver set and select Import from Configuration File.

    2. Click Browse, then navigate to the location of the backed-up User Application driver configuration file.

    3. Select the XML file and click OK, then click OK again.

    4. Provide the requested information for the imported driver and click Next.

    5. Click OK when finished.

  7. In the Modeler, right-click the User Application driver and select Driver > Properties.

  8. Click Packages.

  9. Perform any necessary upgrade or downgrade procedures, then click OK.

  10. Right-click the driver and select Driver > Live > Deploy, then follow the steps in the Deployment Summary.

8.0 Document Generation Issues

8.1 The Document Generator Does Not Generate Documentation for Roles-Based Objects

Designer 4.0.2 does not generate documentation for roles-based entitlement policies or roles-based provisioning module resources. For more information about generating documentation for projects, see “Documenting Projects” in the Designer 4.0.2 for Identity Manager 4.0.2 Administration Guide.

8.2 Cannot Generate Documentation for Projects with Large Numbers of Drivers or Large RBPM Deployments

In Designer projects with more than 40 drivers installed or very large roles-based provisioning module deployments, the Document Generator fails with an out-of-memory error.

This error occurs due to limitations of the Apache FOP print formatter Designer uses to generate documentation. For information on the memory-usage limitations of the FOP formatter and suggestions for improving memory usage, see “Memory Usage” on the Apache FOP Project page .

9.0 Backwards Compatibility Issues

9.1 Designer 4.0.2 Does Not Support 2.1.1 Workspaces

Designer 2.1.1 workspaces are not compatible with Designer 4.0.2. 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.2 to a new workspace and not to a workspace used by a previous version of Designer.

9.2 Designer 4.0.2 Does Not Support Conversion of Projects Older than Designer 3.0

To resolve this issue, convert the older projects to Designer 3.0.1, then import them into Designer 3.5.

10.0 Upgrade Issues

10.1 Upgrading from Designer 3.0.1 to Designer 4.0.2 is Not Supported

Designer 3.5 and later is a full-fledged RCP application. It does not support upgrades from versions of Designer prior to 3.5. If you import a Designer 3.0.1 project into the latest release of Designer, Designer automatically converts the project to version 4.0.2 so that the project can be used in the latest Designer release.

10.2 Manually Modify and Deploy Schema Changes After Upgrading to Designer 4.0.2 AU4

If you create a project using a previous version of Designer and then upgrade your environment to Designer 4.0.2 AU4, you must manually update and deploy the schema to be able to work with the project.

In addition, if you create a project using a previous version of Designer and then import that project into a Designer 4.0.2 AU4 environment, you must also perform the schema update and deploy the updated schema.

To modify and deploy Designer 4.0.2 AU 4 schema changes, complete the following steps:

  1. In the Modeler, right-click the Identity Vault and select Manage Vault Schema.

  2. In the Classes list, select DirXML-PkgItemAux.

  3. In the Attributes window for the DirXML-PkgItemAux class, click the Add Optional icon.

  4. In the Select Optional Attribute window, select DirXML-pkgLinkages and click OK.

  5. Click OK.

  6. Save your Designer project.

  7. Right-click the Identity Vault and select Live > Schema > Compare.

  8. Click the drop-down menu and select Show all.

  9. Expand Attributes and select DirXML-pkgLinkages.

  10. If the Compare Status is Unequal, select Update eDirectory.

  11. Expand Classes and select DirXML-PkgItemAux.

  12. If the Compare Status is Unequal, select Update eDirectory.

  13. Click Reconcile, then click No.

  14. Click OK when finished.

10.3 Migrating Package Linkages to New Structure After Upgrading to Designer 4.0.2 AU4

After you update and deploy the schema with the new package linkage class and attribute, you should migrate all package linkages to the new linkage structure implemented with Designer 4.0.2 AU4.

To migrate your Package Catalog to the new linkage structure, complete the following steps:

  1. (Conditional) If you have not already imported your project into Designer 4.0.2 AU4, click File > Import and follow the steps in the Import Wizard.

  2. (Conditional) If you want to update an existing project, we recommend you back up your project:

    1. Click Project > Export Project.

    2. In the Export Project window, select the project.

    3. Select To archive file.

    4. (Conditional) Click either Save in zip format or Save in tar format, as appropriate for your environment.

    5. Click Browse and navigate to where you want to save the backup file.

  3. In the Outline view, right-click Package Catalog and select Migrate Linkages.

  4. Click Yes to confirm you have already backed up your project.

  5. Click OK.

11.0 Help Issues

11.1 Help Continues Loading for Extended Period of Time

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.

12.0 Legal Notices

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. Please refer to 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 © 2013 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.