NetIQ Identity Manager Analyzer 4.5 provides several enhancements and resolves specific previous issues.
Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the Identity Manager Community Forums, our community Web site that also includes product notifications, blogs, and product user groups.
You can upgrade to Analyzer 4.5 from Analyzer 4.0.1 or later, or perform a new installation. Analyzer 4.5 includes all fixes and features addressed in Analyzer 4.0.2 and later patch releases. For information about what’s new in previous releases, see the “Previous Releases” section in the Identity Manager Documentation Web site.
The documentation for this product and the latest release notes are available on the NetIQ Web site on a page that does not require you to log in. If you have suggestions for documentation improvements, click comment on this topic at the bottom of any page in the HTML version of the documentation posted at the Identity Manager Documentation Web site.
To download this product, see the Identity Manager Product Web site.
This version of Analyzer does not include any new features.
For information about prerequisites, computer requirements, installation, upgrade or migration, see Considerations and Prerequisites for Installation in the NetIQ Identity Manager Setup Guide.
Analyzer 4.5 is built on Eclipse Standard 4.3.
Identity Manager 4.5 includes the following JREs versions:
JRE version for Identity Manager Framework and Integrated Installers
Linux: 1.7.0_65
Windows: 1.7.0_65
JRE version for Analyzer installer 1.7.0_65
After you purchased Identity Manager 4.5, log in to the Identity Manager Product Web site and follow the link that allows you to download the software. The following files are available:
Table 1 Identity Manager ISO Images
|
ISO |
Platform |
Description |
|---|---|---|
|
Identity_Manager_4.5_Windows.iso |
Windows |
Contains the DVD image for Identity Manager server, Designer, iManager, Analyzer, Identity Reporting Module, and Identity Applications. |
|
Identity_Manager_4.5_Linux.iso |
Linux |
Contains the DVD image for Identity Manager server, Designer, iManager, Analyzer, Identity Reporting Module, and Identity Applications. |
You can install Analyzer using the product installer or through integrated installation program that bundles the latest versions of all necessary components for Identity Manager. For more information about prerequisites, computer requirements, installation, or upgrade, see Installing Analyzer in the NetIQ Identity Manager Setup Guide.
To download the installation kits, see the NetIQ Downloads Web site.
You can upgrade to Analyzer 4.5 from Analyzer 4.0.2 or 4.0.1 using the Analyzer installation program. For the supported upgrade paths for 4.5, see Preparing to Upgrade Identity Manager in the NetIQ Identity Manager Setup Guide.
You cannot use the integrated installation process to upgrade an existing installation of Analyzer. For more information, see Upgrading Identity Manager in the NetIQ Identity Manager Setup Guide.
NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.
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. (893559)
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
Issue: 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.
Workaround: To avoid causing unintended problems in the source application, users should be careful when modifying data and sending those modifications to the source application.
Issue: 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.
Workaround: 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.
Issue: 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.
Workaround: 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. (379384)
|
Character |
Description |
|---|---|
|
+ |
Plus (addition) symbol |
|
* |
Asterisk |
|
. |
Period |
|
‘ |
Apostrophe |
|
? |
Question mark |
|
| |
Pipe symbol |
|
\ |
Backslash symbol |
|
( ) |
Left or right parentheses |
|
[ ] |
Left or right bracket |
Issue: 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. ( 368384)
Workaround: 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.
Issue: 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. (403735)
Workaround: 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. (437550)
Analyzer is not supported on Red Hat 6.5.
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. (728283)
Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.
For detailed contact information, see the Support Contact Information website.
For general corporate and product information, see the NetIQ Corporate website.
For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.
THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU.
For purposes of clarity, any module, adapter or other similar material (“Module”) is licensed under the terms and conditions of the End User License Agreement for the applicable version of the NetIQ product or software to which it relates or interoperates with, and by accessing, copying or using a Module you agree to be bound by such terms. If you do not agree to the terms of the End User License Agreement you are not authorized to use, access or copy a Module and you must destroy all copies of the Module and contact NetIQ for further instructions.
This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data.
This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time.
U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R. 227.7202-4 (for Department of Defense (DOD) acquisitions) and 48 C.F.R. 2.101 and 12.212 (for non-DOD acquisitions), the government's rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement.
© 2014 NetIQ Corporation. All Rights Reserved.
For information about NetIQ trademarks, see http://www.netiq.com/company/legal/.