Sun Identity Manager 8.1 Release Notes

Chapter 2 Introduction

This section of the Sun^TM Identity Manager 8.1 Release Notes is organized as follows:

Announcements

The end-of-life for Sun Java^TM System Identity Manager 7.0, 7.1, and 7.1.1 will be May 15, 2010. The last ship date will be May 15, 2009.

For more information, see End of Service Life for Software Support.

Supported Software and Environments

This section lists software and environments that are compatible with Identity product software:

Note –

Because software product developers frequently ship new versions, updates, and fixes to their software, the information published here changes often. Review the release notes for updates before proceeding with installation.

Operating Systems

This release of Identity Manager supports the following operating systems:

AIX 5.2, 5L v5.3
HP-UX 11i v1, 11i v2
Microsoft Windows 2000 SP3, 2000 SP4
Microsoft Windows Server 2003, 2008

Note –
If you are running a 64–bit version of Windows 2008, you must use JDK^TM Version 6 Update 12 and later.
OpenSolaris^TM 2008.5, 2008.11
Solaris^TM 9, 10 SPARC and x86
Red Hat Linux Advanced Server 2.1
Red Hat Linux Enterprise Server 3.x, 4.x, 5
Novell SuSE Linux Enterprise Server 9 SP1, 10

Java Support

Identity Manager requires Java Platform, Standard Edition (SE) 5 or higher.

System Virtualization Support

System virtualization is a technology that enables multiple operating system (OS) instances to execute independently on shared hardware. Functionally, software deployed to an OS hosted in a virtualized environment is generally unaware that the underlying platform has been virtualized. Sun performs testing of its Sun Java System products on select system virtualization and OS combinations to help validate that the Sun Java System products continue to function on properly sized and configured virtualized environments as they do on non-virtualized systems. For information about Sun support for Sun products in virtualized environments, see “System Virtualization Support in Sun Java System Products.”

Caution –

Do not host the Identity Manager repository on a virtual system because performance (transactions per second) will be hindered significantly.

Application Servers

The application server you use with Identity Manager must be Servlet 2.2-compliant and installed with the included Java platform (unless noted as follows). Identity Manager requires Java SE Development Kit (JDK) 5 or 6 on the following application servers, if the application server supports these versions.

Apache Tomcat 5.5.x, 6.0.x
BEA WebLogic Server 9.1, 9.2, 10
IBM WebSphere 6.1
JBoss Application Server 4.2
Oracle® Application Server Enterprise Edition 10g Release 3 (10.1.3)
Oracle Application Server Standard Edition 10g Release 3 (10.1.3)
Sun Java^TM System Application Server 9.1 (GlassFish^TM v2 UR1, v2 UR2, v2.1 32-bit and 64-bit)
Sun Java System Application Server Platform Edition 8.1, 8.2, 9.0
Sun Java System Application Server Enterprise Edition 8.1, 8.2
Sun Java System Application Server Standard Edition 8.2

Note –

If your current application server does not support JDK 5, please check with your vendor to examine the implications of upgrading to one that does before installing Identity Manager.
Identity Manager requires a JDK that correctly handles the 2007 adjustments to U.S. Daylight Savings Time (DST). You must install any relevant DST patches for the JDK version you are using. For Sun JDK 5, Update 15 contains the necessary DST fixes. All versions of Sun JDK 6 contain the necessary DST fixes.
You can run Identity Manager on BEA WebLogic application servers with all WebLogic-supported 5 JDKs.

Repository Database Servers

Identity Manager supports the following repository database servers:

IBM DB2 Universal Database for Linux, UNIX®, and Windows (Version 8.1, 8.2, 9.1 using a type 4 driver, 9.5 using a type 4 driver)
Microsoft SQL Server 2005, 2008
MySQL Enterprise^TM Server 5.0.60 SP1, 5.1.30

Note –
- If you use MySQL Enterprise Server 5.1.30 as your Identity Manager repository, you might need to change to your my.cnf file. Due to recent changes in MySQL's InnoDB code, the default binary logging format is now STATEMENT. Identity Manager uses a READ-COMMITTED transaction isolation level, so binary logging in STATEMENT mode produces an error similar to the following: (ID-20460).
  com.waveset.util.IOException: java.sql.SQLException: Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
  If you enable binary logging, set the mode to MIXED by adding the following line to your my.cnf file:
  binlog_format=mixed
  With this configuration change, you can use 5.1.30 as your repository without the binary logging exception. For more details, see MySQL bug #40360.
- Identity Manager supports MySQL Enterprise Server 5.0.60 SP1 and 5.1.30 as a repository database in both development and production deployments. All other MySQL versions are only supported in a development deployment.
- Identity Manager only supports SQL Server 2008 using SQL Server 2005 JDBC drivers. SQL Server 2008 does not work with SQL Server 2000 drivers, and the SQL Server 2008 JDBC drivers are currently not released.
- Microsoft JDBC Version 1.2 drivers have Java assertions in the methods that connect to different database servers. These drivers assert Java when connecting to SQL Server 2000 if you enable Java assertions in the com.microsoft.sqlserver.jdbc package.
Oracle Database 9i, 10g Release 1, 10g Release 2, and 11g

Note –
Oracle RAC (Real Application Cluster) is supported in a two-node active-passive configuration. That is, a configuration where the active_instance_count parameter is set to 1. Used in conjunction with connection failover for the JDBC^TM driver, this configuration provides failover capability for the repository. (Refer to the Oracle documentation for instructions about how to configure this database server in your environment)

Oracle RAC is not currently supported in any other configuration.

Caution –
If you are using an Oracle repository, the Identity Manager 8.0 repository DDL uses data types that are not properly handled by older Oracle JDBC drivers. The JDBC drivers in ojdbc14.jar do not properly read all of the columns in the log table.

You must upgrade to the Oracle JDBC drivers for JDK 5 drivers for Identity Manager to work properly.

Sun Identity Manager Gateway

If you plan to set up Windows Active Directory, Novell NetWare, Remedy, Lotus Notes (Domino) or RSA ACE/Server resources, you must install the Sun Identity Manager Gateway.

Supported Resources

Identity Manager software supports these resources:

Customer Relationship Management (CRM)

Siebel version 7.0.4, 7.7, 7.8, 8.0 CRM software

Databases

Generic database table
IBM DB2 Universal Database for Linux, UNIX, and Windows 8.1, 8.2, 9.1 using a type 4 driver, 9.5 using a type 4 driver
Microsoft Identity Integration Server (MIIS) 2003
Microsoft SQL Server 2000, 2005, 2008

Note –
- Identity Manager only supports SQL Server 2008 using SQL Server 2005 JDBC drivers. SQL Server 2008 does not work with SQL Server 2000 drivers.
- Microsoft JDBC Version 1.2 drivers have Java assertions in the methods that connect to different database servers. These drivers assert Java when connecting to SQL Server 2000 if you enable Java assertions in the com.microsoft.sqlserver.jdbc package.
MySQL^TM 4.x, 5.0, 5.1

Note –
Identity Manager supports MySQL as a development and production database.
Oracle Database 9i, 10g Release 1, 10g Release 2, 11g
Sybase Adaptive Server 12.x
Scripted JDBC (manages resources using JDBC 3.0 drivers or later)

Directories

LDAP v3
RACF LDAP
Microsoft® Active Directory® 2000, 2003, 2008
Microsoft Active Directory Application Mode (ADAM) Windows 2003 SP1 and later
Novell® eDirectory 8.7.1, 8.8
Novell NetWare® 6.5
Open LDAP
Sun ONE Directory Server 4.x
Sun Java System Directory Server 5 (2004Q2, 2005Q1), 6.3

Note –

While Identity Manager is tested on Open LDAP and Sun Java System Directory Server, LDAP servers that are v3-compliant may work without any changes to the resource adapter.
Sun Java System Directory Server 5 2005Q1 requires a patch to the Directory Server retro changelog plugin if you are using Active Sync. This patch is required for “regular” replication only (not for MMR replication).

Enterprise Resource Planning (ERP)

MySAP ERP 2005 (ECC 6.0) Kernel version 7.00
Oracle E-Business Suite on Oracle Applications 11.5.9, 11.5.10, 12
Peoplesoft PeopleTools 8.1 through 8.4.2
Peoplesoft PeopleTools HRMS 8.0 through 8.8, 9.0
SAP R/3 Enterprise 4.7 (SAP BASIS 6.20)
SAP NetWeaver Enterprise Portal 2004 (SAP BASIS 6.40), 2004s (SAP BASIS 7.00)
SAP Governance, Risk, and Compliance (GRC) Access Enforcer 5.1, 5.2

Help Desk

BMC Remedy Action Request System Server 6.0, 6.3, 7.0
BMC Remedy Service Desk Application 7.0
Remedy Help Desk 6.0

Note –

Many substantial differences between Help Desk 6.0 and Service Desk 7.0 exist in terms of their sample data, defaults, and out-of-the-box configuration. For example, the name of the “ticket” schema in Help Desk 6.0 is HPD:HelpDesk, while in Service Desk 7.0 it has been changed to HPD:Help Desk. Developers should consult the Remedy product documentation for details when upgrading.

Message Platforms

Sun Java System Messaging and Calender Service Java Enterprise System 2005Q1 and later
Lotus Notes (Domino) 6.5, 7.0, 8.0
Microsoft Exchange 2000, 2003, 2007

Note –
- Microsoft Exchange 2000, 2003, and 2007 are managed through the Active Directory resource adapter.
- Microsoft Exchange 2007 is supported on Windows 2003 only.
Novell GroupWise 7.0 (using the Novell NDS adapter)

Miscellaneous

Flat files
JMS Message Queue Listener (manages any JMS 1.0b or later compliant queue)
Generic UNIX Shell Script

Note –
The Generic UNIX Shell Script adapter runs scripts in supported shell types on supported UNIX operating systems.
Generic Windows Script Adapter

Note –
The Generic Windows Script adapter runs scripts in the cmd shell on supported Windows operating systems that host the Sun Identity Manager Gateway.
Microsoft Identity Integration Server (MIIS) 2003

Operating Systems

HP OpenVMS 7.2, 8.3
HP-UX 11.0, 11i v1, 11i v2
IBM AIX 4.3.3, 5.2, 5L, 5.3
IBM OS/400 V4r3, V4r5, V5r1, V5r2, V5r3, V5r4
Microsoft Windows 2000, 2003, 2008
Red Hat Linux 9.0
Red Hat Linux Advanced Server 2.1
Red Hat Linux Enterprise Server 3.0, 4.0, 5
Sun Solaris^TM 9, 10

Note –
If you manage NIS accounts on Solaris, install patch 126632-01 on the resource to improve the performance of the logins command and the Solaris adapter.
OpenSolaris 2008.5, 2008.11
SuSE Enterprise 9, 10

Role Management System

BridgeStream SmartRoles 2.7

Security Managers

eTrust CA-ACF2 Security
eTrust CA-Top Secret Security
IBM RACF
INISafe Nexess 1.1.5
RSA ClearTrust 5.5.2, 5.5.3
RSA SecurID 5.0, 6.0, 6.1.2
RSA SecurID for UNIX 5.1, 6.0, 6.1.2
Scripted Host

Web Access Control

IBM Tivoli Access Manager 4.x, 5.1, 6.0.0 FP09, 6.1
Netegrity Siteminder 5.5, 6.0
RSA ClearTrust, 5.5.2, 5.5.3
Sun ONE Identity Server 6.1, 6.2
Sun Java System Identity Server 2004Q2
Sun Java System Access Manager 6 2005Q1, 7 2005Q4 (Realms supported as of 2005Q4), 7.1
Sun OpenSSO Enterprise 8.0 using Sun Access Manager Realm resource adapter

Browsers

Identity Manager supports the following browsers:

Microsoft Internet Explorer 6.x, 7.x
Safari 2.0 and later for Mac OS X 10.3.3 and later, 3.0.x
Firefox 1.04, 1.05, 1.06, 1.5, 2.0.0.4, 3.0
Mozilla^TM 1.78s

Deprecated Identity Manager Features

The following Identity Manager features are deprecated. Support for these features will continue until the next major release of Identity Manager. Please contact your Customer Care representative or Customer Support if you have questions.

Business Process Editor (BPE) is deprecated, and will be removed in the next major release of Identity Manager. Please use the Sun Identity Manager Integrated Development Environment(Identity Manager IDE) instead. (ID-17693)
MetaView has been removed from new installations of Identity Manager. Customers who are using MetaView in a pre-8.0 version of Identity Manager will be able to continue using it. Please contact your Customer Care representative or Customer Support if you have questions. (ID-17244)
Request Resource type is deprecated, in favor of External Resources. You can no longer create new connections using the Request adapter. Use the External Resource adapter instead. For information about using the new External Resources feature, see Understanding and Managing External Resources in Sun Identity Manager 8.1 Business Administrator’s Guide. (ID-20080)
SAPResourceAdapter built with JC0 2.1.8 is deprecated with this Identity Manager Version 8.1 release. SAP announced a new SAP Java Connector, (SAP JCo), API, JCo 3.0.

Note –
See SAP note 1077727: SAP JCo 3.0 release and support strategy. (Note date: 2008/11/18). Reason and Prerequisites: SAP JCo 3.0 is replacing SAP JCo 2.0 and SAP JCo 2.1 and is released for Java 5. Note that SAP JCo 3.0 is incompatible with former versions of SAP JCo. For details and migration instructions read the SAP JCo 3.0 documentation.

The JCo 3.0 adapter is incompatible with former versions of SAP JCo and requires a minimum JVM version of 1.5. JCo 2.1.8 is only supported for use with JVM 1.4.2, and SAP has not officially announced support for JCo 2.1.8/JVM 1.5. Due to this constraint, the default SAPResourceAdapter that was built using JCo 2.1.8, is deprecated with this Identity Manager Version 8.1 release.

A new default SAPResourceAdapter is planned for the Identity Manager Version 9.0 release. This new adapter will be built against SAP JCo 3.0 or higher and will adhere to Identity Manager's minimum JVM requirements, such as JVM 1.5. In addition, this new SAP JCo 3.0 adapter will be added to upcoming patch releases for both Identity Manager 8.0 and Identity Manager 8.1. Identity Manager 8.0 and Identity Manager 8.1 patches will continue to ship the default SAP JCo 2.1.8 adapter (SAPResourceAdapter).

Discontinued Software

Identity Manager operating systems, application servers, database repositories and managed resources included in the following tables are deprecated.

Next Major Identity Manager Release

Identity Manager will continue support of deprecated software in the following table until the next major Identity Manager release. Please contact your Customer Care representative or Customer Support if you have questions about moving to newer versions of these software packages.

Table 2–1 Deprecated Software and Environments


Software Category	Software Package
Operating Systems	Red Hat Linux Advanced Server 2.1, 3.0 Red Hat Linux Enterprise Server Solaris 8 Windows 2000 SP3, 2000 SP4
Application Servers	JBoss Application Server 4.0.x Sun Java System Application Server Platform Edition 8.0
Repository Database Servers	Oracle 9i
Resources	BridgeStream SmartRoles HP OpenVMS 7.2 IBM AIX 4.3.3 IBM Tivoli Access Manager 4.x INISafe Nexess Microsoft Active Directory 2000 Microsoft Exchange 2000 Microsoft SQL Server 2000 Microsoft Windows Server 2000 MySQL 4.x Lotus Notes 6.5 Oracle 9i Red Hat Linux Enterprise Server SAP Governance, Risk and Compliance Access Enforcer 5.1 SAPResourceAdapter built with SAP JCo 2.1.8 SecurID 5.0, 5.1 Siebel 7.0.4 Solaris 8 Sun Access Manager 6 (2005Q1) Sun Java System Identity Server 2004Q2 Sun ONE Identity Server 6.1, 6.2 Sun ONE Directory Server 4.x Windows 2000 SP3, 2000 SP4
Browsers	Firefox 1.0.x Mozilla

Identity Manager 8.1

Identity Manager 8.1 does not support the following discontinued software packages:

Table 2–2 Software and Environments Discontinued in Identity Manager 8.1


Software Category	Software Package
Operating Systems	IBM AIX 4.3.3 Solaris 7
Application Servers	Apache Tomcat 4.1.x, 5.0.x BEA Weblogic Express 7, 8.1 BEA Weblogic Server 7, 8.1 IBM Websphere Application Server - Express Version 5.1.1 IBM Websphere 4, 4.5, 5, 6.0 iPlanet 6.5 Sun ONE Application Server 7
Repository Database Servers	IBM DB2 Universal Database for Linux, UNIX, and Windows 7.x Microsoft SQL 2000 MySQL 4.1 Oracle 8i SQL Server 2000
Resources	ActivCard 5.0 Blackberry RIM Enterprise Server 4+ (uses generic Windows script adapter) and Blackberry Enterprise Server scripts IBM DB2 7.x Lotus Notes (Domino) 5.0, 6.0.x Microsoft Exchange 5.5 Microsoft Windows NT 4.0 MySQL 4.1 Natural Novell GroupWise 5.x, 6.0, 6.5 Novell eDirectory on Novell NetWare 5.1, 6.0 Oracle 8i (through the Oracle resource adapter) Red Hat Linux 8.0 Remedy Help Desk 4.5, 5.0 SAP R/3 v4.5, v4.6 Siebel 6.2 Sun Identity Manager Gateway running on Microsoft Windows NT 4.0 Sun ONE Identity Server 6.0
Browsers	Internet Explorer 5.x Safari 1.2.1+

API Support

The Identity Manager 8.1 Application Programming Interface (API) includes any public class (and any public or protected method or field of a public class) listed in the following table.

Note –

The com.waveset.object.RepositoryProxy is intended for internal use only.

API Type	Class Names
Session	com.waveset.msgcat.* com.waveset.util.* com.waveset.object.* com.waveset.exception.* com.waveset.expression.* com.waveset.config.* com.waveset.session.SessionUtil com.waveset.session.ScriptSession com.waveset.session.SessionFactory com.waveset.session.Session com.waveset.session.UserViewConstants
Adapter	com.waveset.adapter.* com.waveset.util.Trace
Policy	com.waveset.policy.PolicyImplementation com.waveset.policy.StringQualityPolicy
Report	com.waveset.report.BaseReportTask
Task	com.waveset.task.Executor com.waveset.task.TaskContext
UI	com.waveset.ui.FormUtil com.waveset.ui.util.RequestState com.waveset.ui.util.html.*
Workflow	com.waveset.provision.WorkflowServices com.waveset.session.WorkflowServices com.waveset.workflow.WorkflowApplication com.waveset.workflow.WorkflowContext

Sun Identity Manager Service Provider additionally includes the public classes listed in the following table.

API Type	Class Names
SPE	com.sun.idm.idmx.api.* com.sun.idm.idmx.txn.TransactionPersistentStore com.sun.idm.idmx.txn.TransactionQuery com.sun.idm.idmx.txn.TransactionSummary

These classes are the only classes that are officially supported. If you are using classes that do not appear in these tables, contact Customer Support to determine whether you will be required to migrate to a supported class.

Deprecated APIs

The Chapter 6, Deprecated APIs section in these Release Notes lists all Identity Manager Application Programming Interfaces (APIs) deprecated in this release and their replacements (if available).

Upgrade Paths and Support Policies

This section provides information about the upgrade paths you should follow when upgrading Identity Manager, and describes Identity Manager’s End of Service Life (EOSL) policy for the products software support.

Identity Manager Upgrade Paths

Use the following to determine the upgrade path you must follow when upgrading to a newer version of Identity Manager.

Note –

Upgrading to the latest version of Identity Manager is recommended. When you upgrade to the latest software release, you get the latest new features, bug fixes, and supported resource versions.

Current Identity Manager Version	Target Identity Manager Version
Current Identity Manager Version	7.0	7.1	7.1 Update 1	8.0	8.1
2005Q4M3 (6.0)	7.0	7.1	7.1 > 7.1 Update 1	7.1 > 8.0	7.1 > 8.1
Identity Manager 7.0		7.1	7.1 > 7.1 Update 1	8.0	8.1
Identity Manager 7.1			7.1 Update 1	8.0	8.1
Identity Manager 7.1.1				8.0	8.1
Identity Manager 8.0					8.1

Note –

When upgrading Identity Manager, you do not have to install Updates (formerly called Service Packs or SPs) within a major release to upgrade to the next major release. For example, when upgrading from Identity Manager 5.0 to 6.0, you do not have to install any of the 5.0 Service Packs.
Updates for a major release are cumulative. After upgrading to the major release, you can install the latest Update without having to install all of the Updates (or Service Packs) for that release. For example, if you upgraded to Identity Manager 5.0, installing SP6 gives you all of the functionality provided in SP1 through SP5.
Identity Manager Installation Pack 2005Q4M3 (version 6.0) was a major release. If you are upgrading from a pre-6.0 version of Identity Manager, Identity Auditor, or Identity ManagerService Provider, you must upgrade to Identity Manager Installation Pack 2005Q4M3 before advancing to later releases.

Updates to the Identity Manager documentation are provided as follows:

For Every release (including Service Packs): Release Notes are provided to describe bug fixes, product enhancements, new functionality, and other important information.
For Major releases (x.0): The complete Identity Manager documentation set is updated and republished.
For Minor releases and updates: Individual publications are updated and republished or Documentation Addendum are provided.

End of Service Life for Software Support

During the End of Service Life (EOSL) period, Identity Manager software support is offered in two phases:

Phase 1: Full Support
Phase 2: Limited Support

Note –

The length of the Full Support Phase varies by product.

Full Support Phase

During the Full Support Phase (Phase 1), Sun Microsystems, Inc. provides software support in accordance with the customer’s support contract with Sun (including the applicable Service Listing) as set forth at:

http://www.sun.com/service/servicelist/

However, when a software product’s EOL date is announced, customers will no longer have access to software updates and upgrades for that software product.

Limited Support Phase

During the Limited Support Phase (Phase 2), Sun Microsystems, Inc. provides software support in accordance with the customer’s support contract with Sun (including the applicable Service Listing) as set forth at:

http://www.sun.com/service/servicelist/

However, customers are not entitled to submit bugs or to receive new patches from Sun Microsystems, Inc. As with Full Support Phase, after the software product’s announced EOL date, customers will no longer have access to software updates and upgrades for that software product.

The following table provides information about the Phase 1 and Phase 2 (EOSL) end dates for older versions of Identity Manager.

Product Name	Product Status	Last Ship Date	Phase 1(Full Support)End Date	Phase 2(Limited Support)End Date	EOL Announcement
Sun Java System Identity Manager 7.1.1	Post RR	May 15, 2009	May 15, 2010	May 2014	Nov. 11, 2008
Sun Java System Identity Manager 7.1	Post RR	May 15, 2009	May 15, 2010	May 2014	Nov. 11, 2008
Sun Java System Identity Manager 7.0	Post RR	May 15, 2009	May 15, 2010	May 2014	Nov. 11, 2008
Sun Java System Identity Manager 6.0 2005Q4	EOL	May 25, 2007	May 25, 2008	May 2012	Nov. 20, 2006
Sun Java System Identity Auditor 1.0 2005Q1	EOL	Feb. 2, 2007	Feb. 2008	Feb. 2012	Aug. 1, 2006
Sun Java System Identity Manager Service Provider Edition 1.0 2005Q3	EOL	Feb. 2, 2007	Feb. 2008	Feb. 2012	Aug. 1, 2006
Sun Java System Identity Manager 5.0 2004Q3	EOL	Aug. 11, 2006	Aug. 2007	Aug. 2011	Feb. 7, 2006
Sun Java System Identity Manager 5.0 SP`x` 2004Q3	EOL	Aug. 11, 2006	Aug. 2007	Aug. 2011	Feb. 7, 2006
Sun Java System Identity Manager 5.5	EOL	Aug. 11, 2006	Aug. 2007	Aug. 2011	Feb. 7, 2006
Waveset Lighthouse 4.1			March 2006	March 2010

Identity Manager Deprecation Policy

See Identity Manager Deprecation Policy in Sun Identity Manager 8.1 Upgrade for a complete description of the Identity Manager deprecation policy for removing interfaces or changing behaviors.

Redistributable Files

Sun Identity Manager 8.1 does not contain any files that you can redistribute.

How to Report Problems and Provide Feedback

If you have problems with Sun Identity Manager, contact Sun customer support using one of the following mechanisms:

Sun Software Support services online at http://www.sun.com/support

This site has links to the Knowledge Base, Online Support Center, and ProductTracker, as well as to maintenance programs and support contact numbers.
The telephone dispatch number associated with your maintenance contract

So that we can best assist you in resolving problems, please have the following information available when you contact support:

Description of the problem, including the situation where the problem occurs and its impact on your operation
Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem
Detailed steps on the methods you have used to reproduce the problem
Any error logs or core dumps

You must also collect the information described in the following table:

Information to Collect	How to Get this Information
Product version, including A list of all installed patches, hotfixes, and e-fixes A list of customizations	Use the following commands from the Identity ManagerConsole: `installed` `inventory`
Identity Manager topography, including: How your Identity Manager cluster is configured Environment localization of the issue and any extra information about your environment A list of servers	The information Must be manually determined Must be manually determined Can be obtained by selecting Configure -> Servers from the Identity Manager Administrator interface on a running Identity Manager server
Recent changes to your environment	Must be manually determined
Java version and type	Use the following Java command: `java -version`
Application server version and type	Depends on the Application Server being used, but must be manually determined
Operating system level and information	Must be manually determined
Default XML output, which is a list of all repository objects	Use the `export default.xml default` command from the Console
Task instance data, including A list of all running tasks The size of all current task instances	Use the following commands from the Console: `listTasks` `showSizes TaskInstance`
System Logs	Note – You might be asked to provide additional system logs based on the type of issue you are reporting.