NetIQ Identity Manager 4.5 Service Pack 1 improves usability, and resolves several 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 on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources.
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.
This service pack provides improvements to and resolves several previous issues for the following Identity Manager components:
Identity Manager engine
Remote Loader
Designer for Identity Manager
Identity applications, including the underlying framework
Identity Reporting
For the list of software fixes and enhancements in previous releases, see the Release Notes for that version on the Identity Manager Documentation page.
This release provides the following enhancements:
The installation log files now indicate whether you updated Identity Manager components on a Linux server as a root or non-root user:
Linux root: idmPatchInstall-root.log
Linux non-root: idmPatchInstall-nonroot.log
The installation process also changes the permission of the /tmp/logs file on a Linux server:
chown root:users /tmp/logs chmod +t /tmp/logs
The log file for a Windows server continues to be idmPatchInstall.log. Permissions for the file have not been changed. (Bug 943808)
This service pack improves the content in the NetIQ Identity Manager Patch Installer program for the Identity Manager engine and Remote Loader. For example, the program accurately identifies the operating system on which you run the update. (Bug 873938)
Also, when updating Remote Loader, you can now specify the path where you want to perform the update. The NetIQ Identity Manager Patch Installer allows you to browse to the installed version of Remote Loader. Previously, the patch installer might incorrectly detect the location of the installed Remote Loader 64-bit and would use a default path as if installing the 32-bit version. (Bug 921959)
Designer automatically generates the deprecated.properties file if the update site is created by using the Designer package build and publish mechanism. This file contains the required instructions for building the list of deprecated packages.
If you have created your own update site, create a deprecations folder on the site and include a deprecated.properties file in this folder.
Designer now allows you view and upgrade the already installed packages in your Identity Manager environment in a single consolidated view. The provision of a single view removes the need for you to separately go to each driver, driver set, or Identity Vault in your project to view or upgrade the packages that they contain. For more information, see “Upgrading Installed Packages” in the NetIQ Designer for Identity Manager Administration Guide. (Bug 912257)
You can convert a parameter for driver configuration to a Global Configuration Value (GCV). In this release, Designer preserves the specified value of the parameter during the conversion process. (Bug 808304)
This service pack improves your ability to perform the following types of comparisons:
You can compare any pair of resource objects in the same manner that you might compare two policies. For example, you can compare resources, mapping tables, or ecma scripts. (Bug 916906)
You can compare the customization capability of driver set packages, similar to comparisons for a driver. You can compare the package folder items from the package to the one in driver set for the following library items: policy, ECMA script, mapping table, DS object, resource, and GCV. (Bug 916912)
You can compare the customization capability of policy packages in the Identity Vault, similar to comparisons for a driver. You can compare the package folder items from the tree-level package to the one in the Identity Vault for the following library items: schema map, policy, ECMA script, mapping table, DS object, resource, and notification templates. (Bug 916913)
NetIQ provides a new update site for downloading the Designer updates and packages. NetIQ recommends that you start using the new update site even though it continues to support the existing update site for updating the older versions of Designer. To receive notifications from the new update site, include the new URLs in your Designer. (Bug 905397)
To include the new URL of the Designer update site in Designer, do the following actions:
Launch Designer.
From Designer’s main menu, click Windows > Preferences > NetIQ > Identity Manager > Updates tab and change the value of the URL field to https://nu.novell.com/designer/updatesite4_5_0/.
Click Apply, then click OK.
To verify whether the new URL is working,
Launch Designer.
From Designer’s main menu, click Help > Check for Designer Updates.
If your version of Designer is up‐to‐date, a prompt informs you that no updates are available. If an update is available, a prompt lists components that you can update.
If the updates are available, select the updates and then click OK.
To include the new URL of the package update site, do the following actions:
Launch Designer.
From Designer’s main menu, click Windows > Preferences > NetIQ > Package Manager > Online Updates and click the plus icon to add the new URL as https://nu.novell.com//designer/packages/idm/updatesite2_0_0/.
Click OK.
Select the required check boxes for the update sites in the Preferences window.
Click Apply, then click OK.
To verify whether the new URL is working,
Launch Designer.
From Designer’s main menu, click Help > Check for Package Updates.
If there are no package updates, Designer returns a message stating that no updates are available. If an update is available, a prompt lists the packages with newer versions.
From the list of available packages, select the required version for update and click Yes.
When configuring a report, you can specify the timezone for which you want to run the report. This change ensures that you can gather data from a source at the time appropriate for that source rather than the time on the reporting server.
For example, the data source resides on a server in Houston and the reporting server is in Delhi. You can configure the report to run at 2 AM Houston time. If the report runs at 2 AM in Delhi, which is 12:30 PM in Houston, it cannot capture all the changes that occur at the Houston office that day. (Bug 902453)
Identity Reporting now includes the name of user who generated the report. The name appears in the report header. (Bug 911849)
This release resolves the following major customer issues for the Identity Manager engine, Remote Loader, and the Identity Vault:
When you use NetIQ Sentinel to collect Add Group Member events from the Identity Vault, the TargetTrustDomain and TargetUserDomain fields now include the full domain name, such as \org\groups\test. Previously, the fields failed to include the name of the top-level container, such as \org. This change allows you to create more precise correlation rules within Sentinel. (Bug 914242)
This service pack resolves an issue where the Identity Vault might synchronize a ? character instead of a special character such as an umlaut for user-specified fields. For example, it synchronizes j?ppel instead of jäppel for a user’s name. This issue usually occurred after you rebooted the server that hosts the Identity Vault and the environment variable reverted to a non-UTF-8 character set. Now Identity Manager ensures that the JVM option file.encoding is set to UTF-8 before launching the JVM. (Bug 909406)
You can now update Identity Manager even when path of the installation program includes a space. Previous updates would fail if the installation path contained a space. (Bug 887378)
Identity Manager can now communicate with an SMTP server that does not require authentication while executing the policy do-send-mail-with-template. For example, you can now use the policy to send notifications from the Identity Manager engine without configuring SMTP authentication. (Bug 875033)
This service pack resolves an issue where you could not clear and set the SSO credential of an account that uses clear-sso-credentials actions. This issue occurred for accounts where you previously set the credential using NetIQ SecureLogin 6 or older. The clear-sso-credentials action failed with the following message:
Couldn't perform SSO operation <do-set-sso-credential>: '4444:ERROR (provisionNSLAccount): General Exception: java.lang.NullPointerException'
(Bug 904822)
This service pack resolves an issue where the Password Expiration Job fails after you run the NDSrepair utility on the same server that processes the job. The job would fail with the following error:
no object DCH for MIME type multipart/mixed
This issue occurred only if the Password Expiration Job used HTML format and you did not restart eDirectory after running the NDSrepair utility. (Bug 890229)
NOTE:NetIQ recommends running the NDSrepair utility only when you need to correct problems in the Identity Vault (eDirectory database), rather than running the utility as a scheduled activity. Corrections usually require a restart of eDirectory and Identity Manager, which can adversely affect user operations.
This service pack resolves an issue where eDirectory 8.8.8 Patch 3 generates the following warning in the ndsd.log when you load libvrdim:
Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /opt/novell/eDirectory/lib64/libdhutilj.so.3.0.500 which might have disabled stack guard
(Bug 907240)
This service pack resolves an issue where the Identity Manager engine incorrectly adds extra event information to operation data. (Bug 906276)
This release resolves the following major customer issues for Designer:
This service pack updates Designer so you can use the ECMAScript editor when you add a new script for a form in a workflow in Designer. In previous releases, you might have received an unhandled event loop exception error when attempting to launch the script editor. The launch failed because the JSEditor plugin was not initialized. (Bug 901510)
With this service pack, you can specify email addresses that begin with a numeric character. For example, when you specify the From address for Default Notification Collection. (Bug 907783)
Changing the icon for a driver in no longer causes high CPU utilization and Designer does not initiate a loop while trying to display the icon. (Bug 911470)
This service pack updates the Help to ensure that all appropriate content gets displayed upon request on Windows-based computers. In the previous release, some Help pages were not displayed as expected. (Bug 902975)
If you create the update site with the Designer package build and publish mechanism, Designer automatically generates the deprecated.properties file. This file contains the required instructions for building the list of deprecated packages.
If you have created your own update site, create a deprecations folder on the site and include a deprecated.properties file in this folder. (Bug 903087)
This service pack resolves an issue where you use attempt to add and remove one resource assignment in the Policy Builder using the remove resource action but Designer removes all resource assignments. This is occurred because Designer expected an instanceGUID to be associated with each remove resource action. Designer now prompts you to specify a value for instanceGUID when you perform the remove resource action. (Bug 902428)
The online documentation for Designer erroneously stated that you can browse to objects in an application for Source DN (if on publisher) or Destination DN (if on subscriber). However, Designer allows you to browse to the Identity Vault, not an application. The online help has been improved to reflect Designer behavior. (Bug 890716)
This release resolves the following major customer issues for the identity applications and Identity Reporting:
The Role Service now reports a “Cancelled” message when you search for role assignments for a user and the service attempts to return a retracted role assignment request. Previously, the service responded with an error. (Bug 895501)
This service pack resolves an issue where you use the Resource Request Portlet on a Shared Page to provide a form for a workflow. The browser responded with an unrecoverable error. (Bug 920641)
This service pack resolves an issue where fields in forms do not display appropriately in Internet Explorer 11 on a Windows computer. (Bug 920853)
This service pack resolves an issues where in WebSphere, the server.log file located in the WebSphere-install-dir/AppServer/profiles/profile-name (for example, /opt/IBM/WebSphere/AppServer/profiles/AppSrv01) might be truncated. (Bugs 900844, 899981)
This service pack requires the following product versions:
NetIQ Identity Manager 4.5
NetIQ One SSO Provider 4.5.0.2
NetIQ Self Service Password Reset 3.2.0.3
NetIQ eDirectory 8.8.SP8 Patch 5
To install this service pack, complete the installation steps in the following sections:
This service pack includes a IDM_engine_rl_IDM4.5SP1.zip for updating the Identity Manager engine and Remote Loader. Install this package on the Identity Manager engine server. For more information, see “Installing the Identity Manager Engine and Remote Loader Patch” in the NetIQ Identity Manager Setup Guide.
This service pack provides updates for the Remote Loader, Remote Loader .NET, and the Java Remote Loader. When you install the Remote Loader on supported platforms, the installation program includes all versions of the Remote Loader for the operating system.
Install the contents of IDM_engine_rl_IDM4.5SP1.zip package on each server where you have installed the Remote Loader, .Net Remote Loader, and the Java Remote Loader. For more information, see “Installing the Identity Manager Engine and Remote Loader Patch” in the NetIQ Identity Manager Setup Guide.
NOTE:If you previously used a manual process to install the Java Remote Loader, you must perform the procedure in Updating the Java Remote Loader Manually.
If you installed the Java Remote Loader manually on a server, you must manually upgrade the Java Remote Loader.
Shut down the Java Remote Loader:
../dirxml_jremote -config fileName -uExtract the contents of the IDM_engine_rl_IDM4.5SP1.zip file to a temporary location.
Replace the following files in the lib folder of your Java Remote Loader installation with the files extracted from the .zip file:
dirxml.jar
dirxml_misc.jar
dirxml_remote.jar
By default, the files are located in the /cd-image/patch/OS_platform/<architecture>/RL/lib folder of the installation package.
Restart the Java Remote Loader:
../dirxml_jremote -config fileName &Designer provides an in-built auto-update feature that notifies you of new features available at the Online Update Web site. This feature allows you to download Designer package and patch updates when the computer that has Designer installed and is connected to the Internet.
You also can perform an offline update of Designer when the computer that has Designer installed and is not connected to the Internet. To perform an offline update, first download the required contents from the Designer and Package Update Web sites on a local or remote computer and then point Designer to the directory containing the downloaded files.
To do this, create an offline copy of the Designer update files and then configure Designer to read the patch updates from the files copied to the local computer.
To create an offline copy of the Designer update files on Linux, perform the following actions:
Log in to the computer that has Designer installed and create a local directory.
Download the latest patch zip file for Designer version from the specified location and unzip the files into the local directory.
To configure Designer to read the patch updates from the files copied to the local computer, perform the following actions:
Launch Designer.
From Designer’s main menu, click Windows > Preferences.
Click NetIQ > Identity Manager and select Updates.
Select Do not check for updates and deselect all the other check boxes.
For URL, specify file:///path_to_files/updatesite4_5_0.
For a Linux mounted ISO, use the following URL format: file:///media/designer450offline/updatesite4_5_0.
Click Apply, then click OK.
From Designer’s main menu, click Help > Check for Designer Updates.
Select the required updates and click Yes to accept and update the Designer patch updates.
You need to launch Designer again for the changes to take effect.
To do this, create an offline copy of the package update files and then configure Designer to read the package updates from the files copied to the local computer.
To create an offline copy of the package update files on Linux:
Log in to the computer that has Designer installed and create a local directory.
In a shell, change to this directory and run the following commands to copy the Designer package update files:
wget -r -nH -np http://nu.novell.com/cached/designer/packages/idm/updatesite1_0_0/
wget -r -nH -np http://nu.novell.com/cached/designer/packages/idm/updatesite2_0_0/
To configure Designer to read the package updates from the files copied to the local computer:
Launch Designer.
From Designer’s main menu, click Windows > Preferences.
Click NetIQ > Package Manager > Online Updates.
To add a new URL, click the plus icon.
Provide information for the following fields:
Vendor: Specifies the vendor name for package update.
URL: Specifies the URL as file:///path_to_files/packages/idm/updatesite1_0_0.
For Linux mounted ISO, use the following URL format:
file:///media/designer450offline/packages/idm/updatesite1_0_0
file:///media/designer450offline/packages/idm/updatesite2_0_0
NOTE:If you have multiple package sites, repeat Step 5 and add multiple sites and URLs.
Click OK.
In the Preferences window, select the required check boxes for the sites.
NOTE:The new sites are selected by default.
Click Apply, then click OK.
From Designer’s main menu, click Help > Check for Package Updates.
Select the required updates and click Yes to accept and update the Designer package updates.
You need to launch Designer again for the changes to take effect.
This service pack requires the latest versions of NetIQ One SSO Provider and NetIQ Self Service Password Reset. To install these updates, download the following packages and perform the steps listed in the readme files:
This service pack includes an update to the identity applications. The process for installing the update depends on the web server that you use to support the applications. Also, ensure that you complete the post-installation steps.
NOTE:The identity applications require the latest versions of NetIQ One SSO Provider and NetIQ Self Service Password Reset. For more information, see Section 3.4, Updating One SSO Provider and Self Service Password Reset.
Copy the IDM45-Apps-SP-1.zip file to the server where you deployed the identity applications on JBoss.
Extract the contents of the .zip file for the identity applications to a temporary location on the server.
Stop JBoss.
Create a backup folder outside of the JBoss installation path.
Move the following files from the jboss/server/%context%/deploy folder to the backup folder:
dash.war
IDMProv.war
IDMPwdMgt.war (if it applies)
landing.war
Move the homepagelogging.xml file from the jboss/server/%context%/conf folder to the backup folder.
Delete all files and folders from the following locations:
jboss/server/%context%/tmp
jboss/server/%context%/work/jboss.web
Delete the permindex folder from the /tmp folder.
Move the following files from the JBoss/deploy folder of the extracted files to the jboss/server/%context%/deploy folder:
dash.war
IDMProv.war
IDMPwdMgt.war (if it applies)
landing.war
Move the homepagelogging.xml file from the JBoss/conf folder of the extracted files to the jboss/server/%context%/conf folder.
(Conditional) On a Linux server, change the ownership of the .war and homepagelogging.xml files to the user novlua and the group users. For example:
chown novlua:users ./IDMProv.war
Start JBoss.
Ensure that users remove all cookies and cache from their browsers before accessing the deployed identity applications.
NetIQ provides Apache Tomcat as a convenience for Identity Manager users. By default, NetIQ installs Tomcat in the following locations:
Linux: /opt/netiq/idm/apps/tomcat
Windows: C:\NetIQ\IdentityManager\apps\tomcat
To update the identity applications on a Tomcat server:
Copy the IDM45-Apps-SP-1.zip file to the server where you deployed the identity applications on Tomcat.
Extract the contents of the .zip file for the identity applications to a temporary location on the server.
Stop Tomcat.
Create a backup folder outside of the Tomcat installation path.
Move the following files from the tomcat/webapps folder to the backup folder:
dash.war
IDMProv.war
IDMPwdMgt.war (if it applies)
landing.war
Move the homepagelogging.xml file from the tomcat/conf folder to the backup folder.
Move the iac-datasource-factory-1.0.0.jar or iac-datasource-factory.jar file from the tomcat/lib folder to the backup folder.
If both files exist in the tomcat/lib folder, move them both.
Delete the following files and folders from the following locations:
dash folder from the tomcat/webapps folder
IDMProv folder from the tomcat/webapps folder
IDMPwdMgt folder (if it applies) from the tomcat/webapps folder
landing folder from the tomcat/webapps folder
localhost folder from the tomcat/work/Catalina folder
all files and folders from the tomcat/temp folder, including the permindex file if it exists
Move the following files from the Tomcat/webapps folder of the extracted files to the tomcat/webapps folder:
dash.war
IDMProv.war
IDMPwdMgt.war (if it applies)
landing.war
Move the homepagelogging.xml file from the Tomcat/conf folder of the extracted files to the tomcat/conf folder.
Move the iac-datasource-factory.jar file from the Tomcat/lib folder of the extracted files to the tomcat/lib folder.
(Conditional) On a Linux server, change the ownership of the following files to the user novlua and the group users:
.war
homepagelogging.xml
iac-datasource-factory.jar
For example:
chown novlua:users ./IDMProv.war
(Optional) Delete or move all of the existing logs in the tomcat/logs folder.
Start Tomcat.
Ensure that users remove all cookies and cache from their browsers before accessing the deployed identity applications.
You can apply this service pack to the identity applications deployed to a WebSphere server.
Copy the IDM45-Apps-SP-1.zip file to the server where you deployed the identity applications on WebSphere.
Extract the contents of the .zip file for the identity applications to a temporary location on the server.
Create a backup folder outside of the WebSphere installation path.
Move the following files from the identity applications folder to the backup folder:
dash.war
IDMProv.war
IDMPwdMgt.war (if it applies)
landing.war
log4j.xml
homepagelogging.xml
By default, the identity applications are installed in the following locations:
Linux: /opt/netiq/idm/apps/UserApplication
Windows: C:\NetIQ\IdentityManager\apps\UserApplication
Move the following files from the WebSphere folder of the extracted files to the identity applications folder:
dash.war
IDMProv.war
IDMPwdMgt.war (if it applies)
landing.war
log4j.xml
homepagelogging.xml
To add the log4j.configuration JVM system property, complete the following steps:
For Name, specify log4j.configuration.
For Value, specify the full path including the filename to the log4j.xml file that you updated in Step 5. For example:
file:///opt/netiq/idm/apps/UserApplication/log4j.xml
For Description, specify a description for the property. For example:
log4j configuration file
For more information about adding a JVM system property, see “Adding User Application Configuration Files and JVM System Properties” in the NetIQ Identity Manager Setup Guide.
Remove the IDMselector.jar from the shared library that you created when you installed the identity applications.
For more information, see “Creating and Applying a Shared Library” in the NetIQ Identity Manager Setup Guide.
Stop and then uninstall the following files:
dash.war
IDMProv.war
IDMPwdMgt.war (if it applies)
landing.war
Install, but do not start, the following files:
dash.war
IDMProv.war
IDMPwdMgt.war (if it applies)
landing.war
Stop WebSphere.
Restart WebSphere.
Ensure that users remove all cookies and cache from their browsers before accessing the deployed identity applications.
This section provides the final steps for updating for the identity applications where you remove the j2eevalidate.jar from the Identity Vault. (Bug 907429)
Stop eDirectory.
Move the j2eevalidate.jar to a backup folder from its current location, by default:
Linux: /opt/novell/eDirectory/lib/dirxml/classes
Windows: C:\Novell\IdentityManager\NDS\lib
Start eDirectory.
This service pack includes an update to Identity Reporting and a new Report Packaging Tool. The process for installing the updates depends on the web server that you use to support reporting.
NOTE:Identity Reporting requires the latest versions of NetIQ One SSO Provider and NetIQ Self Service Password Reset. For more information, see Section 3.4, Updating One SSO Provider and Self Service Password Reset.
This service pack includes an update to the Report Packaging Tool.
Copy the IDM45-Reporting-SP-1.zip file to the server where you installed Identity Reporting.
Extract the contents of the .zip file for Identity Reporting to a temporary location on the server.
Create a backup folder.
Move the existing reportpkg.jar file from the original installation to the backup folder.
Copy the reportpkg.jar file from root folder of the extracted files to your installation for Identity Reporting.
(Conditional) If you use the identity applications, apply the service pack to the identity applications.
For more information, see Section 3.5, Updating the Identity Applications.
Copy the IDM45-Reporting-SP-1.zip file to the server where you deployed Identity Reporting on JBoss.
Extract the contents of the .zip file for Identity Reporting to a temporary location on the server.
Stop JBoss.
Create a backup folder outside of the JBoss installation path.
Move the following files from the jboss/server/%context%/deploy folder to the backup folder:
IDMRPT.war
IDMRPT-CORE.war
easrestapi.war
Move the homepagelogging.xml file from the jboss/server/%context%/conf folder to the backup folder.
Delete all files and folders from the following locations:
jboss/server/%context%/tmp
jboss/server/%context%/work/jboss.web
Move the following files from the JBoss/deploy folder of the extracted files to the jboss/server/%context%/deploy folder:
IDMRPT.war
IDMRPT-CORE.war
easrestapi.war
(Conditional) On a Linux server, change the ownership of the .war files to the user novlua and the group users. For example:
chown novlua:users ./IDMRPT.war
Start JBoss.
Ensure that users remove all cookies and cache from their browsers before accessing the deployed Identity Reporting.
NetIQ provides Apache Tomcat as a convenience for Identity Manager users. By default, NetIQ installs Tomcat in the following locations:
Linux: /opt/netiq/idm/apps/tomcat
Windows: C:\NetIQ\IdentityManager\apps\tomcat
To update Identity Reporting on a Tomcat server:
(Conditional) If you use the identity applications, apply the service pack to the identity applications.
For more information, see Section 3.5, Updating the Identity Applications.
Copy the IDM45-Reporting-SP-1.zip file to the server where you deployed the Identity Reporting on Tomcat.
Extract the contents of the .zip file for the Identity Reporting to a temporary location on the server.
Stop Tomcat.
Create a backup folder outside of the Tomcat installation path.
Move the following files from the tomcat/webapps folder to the backup folder:
IDMRPT.war
IDMRPT-CORE.war
easrestapi.war
Delete the following files and folders from the following locations:
IDMRPT folder from the tomcat/webapps folder
IDMRPT-CORE folder from the tomcat/webapps folder
easrestapi folder from the tomcat/webapps folder
localhost folder from the tomcat/work/Catalina folder
all files and folders, except the permindex folder if it exists, from the tomcat/temp folder
Move the following files from the Tomcat/webapps folder of the extracted files to the tomcat/webapps folder:
IDMRPT.war
IDMRPT-CORE.war
easrestapi.war
(Conditional) On a Linux server, change the ownership of the .war files to the user novlua and the group users:
For example:
chown novlua:users ./IDMRPT.war
(Conditional) If you use Identity Reporting without the identity applications, complete the following steps:
Move the iac-datasource-factory-1.0.0.jar or iac-datasource-factory.jar file from the tomcat/lib folder to the backup folder.
If both files exist in the tomcat/lib folder, move them both.
Move the iac-datasource-factory.jar file from the Tomcat/lib folder of the extracted files to the tomcat/lib folder.
(Conditional) On a Linux server, change the ownership of the iac-datasource-factory.jar files to the user novlua and the group users. For example:
chown novlua:users ./iac-datasource-factory.jar
(Optional) Delete or move all of the existing logs in the tomcat/logs folder.
Start Tomcat.
Ensure that users remove all cookies and cache from their browsers before accessing the deployed Identity Reporting.
You can apply this service pack to Identity Reporting deployed to a WebSphere server.
(Conditional) If you use the identity applications, apply the service pack to the identity applications.
For more information, see Section 3.5, Updating the Identity Applications.
Copy the IDM45-Reporting-SP-1.zip file to the server where you deploy Identity Reporting on WebSphere.
Extract the contents of the .zip file for Identity Reporting to a temporary location on the server.
Create a backup folder outside of the WebSphere installation path.
Move the following files from the IdentityReporting folder to the backup folder:
IDMRPT.war
IDMRPT-CORE.war
easrestapi.war
By default, the Identity Manager installation process installs Identity Reporting in the following locations:
Linux: /opt/netiq/idm/apps/IdentityReporting
Windows: C:\NetIQ\IdentityManager\apps\IdentityReporting
Move the log4j.xml file from the IdentityReporting/conf folder to the backup folder.
Move the following files from the WebSphere folder of the extracted files to the IdentityReporting folder:
IDMRPT.war
IDMRPT-CORE.war
easrestapi.war
Move the log4j.xml file from the WebSphere folder of the extracted files to the IdentityReporting/conf folder.
(Conditional) If you use Identity Reporting without the identity applications, complete the following steps:
Add log4j.configuration to the JVM system properties, using the following information:
For Name, specify log4j.configuration.
For Value, specify the full path including the filename to the log4j.xml file that you updated in Step 7. For example:
file:///opt/netiq/idm/apps/IdentityReporting/log4j.xml
For Description, specify a description for the property. For example:
log4j configuration file
For more information about adding a JVM system property, see “Adding User Application Configuration Files and JVM System Properties” in the NetIQ Identity Manager Setup Guide.
Remove the IDMselector.jar from the shared library that you created when you installed Identity Reporting.
For more information, see “Creating and Applying a Shared Library” in the NetIQ Identity Manager Setup Guide.
Stop and then uninstall the following files:
IDMRPT.war
IDMRPT-CORE.war
easrestapi.war
Install, but do not start, the following files:
IDMRPT.war
IDMRPT-CORE.war
easrestapi.war
Stop WebSphere.
Restart WebSphere.
Ensure that users remove all cookies and cache from their browsers before accessing the deployed Identity Reporting.
NetIQ 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.
For the list of the known issues in Identity Manager 4.5 and Identity Manager Standard Edition 4.5, see the Release Notes for each version on the Identity Manager Documentation page.
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.
© 2015 NetIQ Corporation. All Rights Reserved.
For information about NetIQ trademarks, see http://www.netiq.com/company/legal/.