This document provides important information related to Novell Analyzer for Identity Manager. It includes the following sections:
The latest version of this Readme is available at the Novell Identity Manager documentation Web site.
This Readme contains the known issues for Novell Analyzer for Identity Manager 4.0.2. In addition to this Readme, separate Readmes are available for Identity Manager 4.0.2 and Designer 4.0.2:
Additional documentation resources are also available for the following products:
The following issues exist in the Analyzer 4.0.2 environment:
To start the Analyzer, perform the following steps to change the XULRunner mapping:
Navigate to the Analyzer installation directory, then open the Analyzer.ini file in the gedit editor.
Add the following line at the end of the list of the parameters given in the Analyzer.ini file:
-Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner-1.9/
The Analyzer.ini file should read as follows:
-vmargs -Xms256m -Xmx1024m -XX:MaxPermSize=128m -XX:+UseParallelGC -XX:ParallelGCThreads=20 -XX:+UseParallelOldGC -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner-1.9/
Save the Analyzer.ini file and launch Analyzer.
NOTE:The recommended version of XULrunner on SLED 11 is 1.9.0.19. On openSUSE 11.4, it is 1.9.0.2. These versions are shipped with the operating systems.
To use the SAP user driver, you must install the sapjco.jar library in Analyzer, and install the librfc32.dll and sapjcorfc.dll into the Windows %systemroot% folder (typically C:\windows\system32).
Restart Analyzer after installing these files.
The Analyzer DB2 driver requires the following two libraries to function properly. You can download these libraries from IBM.
db2java.zip
db2jcc.jar
Analyzer does not prevent users from modifying anything in a data set. If a user with appropriate rights to the source application modifies a value, for example a GUID or DN, Analyzer does not attempt to determine if the modification causes a problem when written out to the source application.
To avoid causing unintended problems in the source application, users should be careful when modifying data and sending those modifications to the source application.
When you attempt to push updated data to the source application from Analyzer’s Data Browser (by clicking ), you might get an error indicating there was a problem with the update operation. However, the Data Browser’s modified data indicators in the data table change to indicate that the updates were successful.
If this occurs, the data updates might have been unsuccessful. Re-import the data from the source application to make sure you know the true state of the data before making any other data modifications.
Problems with the update operation occur primarily when adding a value to a multi-valued attribute.
The following issues can prevent Analyzer from displaying data set content in the Data Browser view:
Analyzer does not support SQL reserved words as column names for data sets (For example, group or select.) If a column name is an SQL reserved word, no data displays in the Data Browser view. To avoid this, exclude the column (attribute) with a reserved-word name from the data set.
By default, Analyzer’s Subscriber channel is enabled so that you can perform data set queries. However, if a connection profile was synchronized from Designer with the Subscriber channel disabled, it remains disabled for Analyzer. If your data sets do not have any data, confirm that the connection profile’s Subscriber channel is enabled in Analyzer.
To do this, right-click the desired connection profile, then select . In the connection profile properties, select > > . Make sure that is set to (default).
The Pattern Frequency analysis metric does not work properly with data that includes the following characters. If you attempt to do a pattern frequency analysis on a data set that has values that contain any of these characters, the analysis fails and returns an empty result.
|
Character |
Description |
|---|---|
|
+ |
Plus (addition) symbol |
|
* |
Asterisk |
|
. |
Period |
|
‘ |
Apostrophe |
|
? |
Question mark |
|
| |
Pipe symbol |
|
\ |
Backslash symbol |
|
( ) |
Left or right parentheses |
|
[ ] |
Left or right bracket |
If connections do not import properly from Designer, the likely problem is that the server configuration associated with the driver set in Designer is incorrect or incomplete. For example, when you create a new driver set in Designer, the default server DN is server.context. If you attempt to import connection information that includes invalid information like this, the import fails.
Before importing connection information from Designer, make sure that the server information is valid.
If you have deleted values in the Data Browser that have not been updated to the application, the deleted values are still considered when running a Matching Analysis.
The Identity Vault schema does not support multiple classes with the same name. Some application schemas, such as Notes, do support duplicate class names. If you want to import an application schema that includes duplicate class names, you should first consolidate the duplicate class names into a single class that contains the attributes from all duplicate classes.
If you cannot resolve the duplicate classes in the application schema, you can manually resolve the duplicate class names in Analyzer by doing the following:
WARNING:This procedure is not recommended and can cause inconsistencies in the Identity Vault schema. It should only be used if absolutely necessary.
Open the IDS Trace view ( > > ).
In the Project view, right-click the appropriate connection, then select .
This captures the application schema in the IDS Trace. If the IDS Trace does not capture the entire schema, increase the IDS Trace window size by clicking the icon, then increasing the setting.
Open the Navigator view ( > > ).
In the Navigator view, expand the appropriate project, then browse to > .
Double-click the appropriate schema file (*ShimConfig.xml) to open it in an XML editor.
If there are multiple shim configuration files, you can identify the application associated with each file by opening the file and looking at the contents of the <class-name>, <auth-id>, and <auth-context> tags.
In the XML editor, search for the following elements. If they do not exist, add them to the schema immediately above the closing </shim-config> tag.
<app-schema-def> <schema-def> ... </schema-def> <app-schema-def>
In IDS Trace, locate the <NDS> tag, then paste the contents of the <NDS> tag into the <schema-def> tag in the *ShimConfig.xml file.
Make sure you do not include the <NDS> as part of what you copy and paste into the *ShimConfig.xml.
Search for any duplicate <ClassDef> elements in the schema definition and consolidate all attribute definitions <attr-def> under a single <ClassDef> element.
Save the changes to the schema file (Ctrl+S), then restart Analyzer.
If you are using HSQL as the back end database for Analyzer, matching is case sensitive. If you are using MySQL, the back end database is case insensitive.
If the 32-bit version of XULRunner is installed on a 64-bit Linux distribution, the JVM might crash when you launch Analyzer, when the Welcome Page displays, or when you view a Help topic. To resolve this problem:
Open the Analyzer.ini file located in the Analyzer install directory.
Add the following line to the end of the Analyzer.ini file:
-Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner-1.9/
Save the Analyzer.ini file and launch Analyzer.
You can try using Analyzer before purchasing the product. For trying the product, enter C064 0010 0000 E203 2CCA evaluation key in the License dialog box after launching Analyzer. The product evaluation key is valid up to 14 days after you start using the product.
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 © 2007 - 2012 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.