IBM Security Verify Governance SAP HR Feed Adapter 10.0.1 is available. Compatibility, installation, and other getting-started issues are addressed.
Welcome to the IBM Security Verify Governance SAP HR feed Adapter.
These Release Notes contain information for the following products that was not available when the IBM Security Verify Governance manuals were printed:
The SAP HR feed Adapter is designed to reconcile Person and Organizational information from the SAP ABAP server. The adapter runs in "agentless" mode and communicates using standards BAPI and RFC methods supplied with the SAP server. Communication to these BAPI and RFC methods is enabled by the SAP Java Connector (Jco) API.
Review and agree to the terms of the IBM Security Verify Governance Adapter License prior to using this product.
The license can be viewed from the "license" folder included in the product package.
Adapter Version
|
Component |
Version |
|
Build Date |
2023 March 16 06.10.49 |
|
Adapter Version |
10.0.1 |
|
Component Versions |
Adapter build: 10.0.1.2 Profile: 10.0.1.2 Connector: 10.0.1.2 Dispatcher 7.1.39 or higher (packaged separately) SAP NW connector version: 10.0.5 |
|
Documentation |
The following guides are available in the IBM Knowledge Center
SAP HR Feed Adapter Installation and Configuration Guide |
New Features
|
Internal # |
Enhancement # (RFE / Idea) |
Description |
|
|
|
Items included in current release (10.0.1) |
|
RTC 191290 |
ISIM-103/ADAPT-124 |
Add support for IBM Security Verify Governance Identity Manager (ISVGIM) starting v10.0.1 FP4 release onwards |
|
RTC 191337 |
|
Build with Sap NW connector version 10.0.5 |
|
RTC 191337 |
|
Add support for JCo 3.1.7 |
|
|
|
Items included in 7.1.4 release |
|
Internal |
|
Added support for JCo 3.0.17. |
|
Internal |
|
Build with Sap NW connector version 7.1.29 |
|
|
|
Items included in 7.1.3 release |
|
|
|
None |
|
|
|
Items included in 7.1.2 release |
|
RTC 154245 |
|
Added support for JCo 3.0.16. |
|
|
|
Items included in 7.1.1 release |
|
RTC 152293 |
|
Add Support for Identity Governance and Intelligence (IGI) v5.2.2 |
Closed Issues
|
Internal # |
APAR # /Case # |
Description |
|
|
|
Items included in current release (10.0.1) |
|
RTC 191303 |
Internal - Even after suspending and terminating employee in SAP HR Target system the status is still shows as active in ISVG and ISVGIM |
|
|
|
|
Items included in 7.1.4 release |
|
RTC 171786 |
IJ03346/BUG 2531
|
PMR TS000079006 SAP Adapter: Request is not retried and fails immediately when SAP server is not available
US - As a SAP NW adapter developer, I need to provide correct error messages |
|
|
|
Items included in 7.1.3 release |
|
RTC 162843 |
|
OUs and Users are missing after SAP recon |
|
|
|
Items included in 7.1.2 release |
|
RTC 156200 |
|
Added support for Type B connection. |
|
|
|
Items included in 7.1.1 release |
|
|
|
None |
Known Limitations
|
Internal # |
APAR # |
Case # / Description |
|
|
|
None |
Multi Byte Character Support Limitations
All character data transferred between IBM Security Identity Manager Server, the adapter, and SAP ABAP server are encoded as UTF-8. The adapter supports provisioning of multi byte characters to and from a directly connected SAP ABAP Unicode server. Provisioning of ASCII characters is supported for Non-Unicode SAP ABAP servers. The adapter does not support provisioning of multi byte characters to any Non-Unicode ABAP server. Extended ASCII characters are not tested or supported for Non-Unicode SAP ABAP servers.
See the Installation Guide for IBM Security Verify Governance SAP HR adapter for detailed instructions.
Corrections to Install guide:
Chapter 1: Overview
No Updates for the current release
Chapter 2: Planning
Prerequisites:
Please consult the release notes for the currently supported versions of the below products (Add this line just before the "Table 1. Prerequisites to install the adapter" begins)
Directory Integrator:
Remove IBM Security Directory Integrator Version 7.1.1 + 7.1.1-TIV-TDI-FP0004 + 7.2.0-ISS-SDI-LA0008 from description
Update from IBM® Security Directory Integrator Version 7.2 to IBM® Security Directory Integrator in description
Identity
Server Verify Governance Server:
Remove current description and update the same as below:
The following servers are supported
- IBM Security Verify Governance Identity Manager
- IBM Security Verify Governance
SAP Netweaver Application Server ABAP with SAP Basis Component with SAP HR module installed.:
Remove the description
Chapter 3: Installing
Adapter profile
Below description is only for IBM Security Verify Governance Identity Manager
There are three adapter profiles included in the SAP HR Feed Adapter distribution package: IdentityManager\BPPerson\SapHRProfile.jar, IdentityManager\Person\SapHRProfile.jar and ISVG\SapHRProfile.jar
The difference between the three profiles is that the IdentityManager\BPPerson\SapHRProfile.jar and IdentityManager\Person\SapHRProfile.jar can be only used with IBM Security Verify Governance Identity Manager instance whereas ISVG\SapHRProfile.jar can only be used with IBM Security Verify Governance instance.
If Business Partner entity is in scope then IdentityManager\BPPerson\SapHRProfile.jar should be used in IBM Security Verify Governance Identity Manager instance else IdentityManager\Person\SapHRProfile.jar should be used. It is not possible for both IdentityManager\BPPerson\SapHRProfile.jar and IdentityManager\Person\SapHRProfile.jar profiles to exist in the same IBM Security Verify Governance Identity Manager instance.
Below description is only for IBM Security Verify Governance
There are three adapter profiles included in the SAP HR Feed Adapter distribution package: IdentityManager\BPPerson\SapHRProfile.jar, IdentityManager\Person\SapHRProfile.jar and ISVG\SapHRProfile.jar
The difference between the three profiles is that the IdentityManager\BPPerson\SapHRProfile.jar and IdentityManager\Person\SapHRProfile.jar can be only used with IBM Security Verify Governance Identity Manager instance whereas ISVG\SapHRProfile.jar can only be used with IBM Security Verify Governance instance.
For IBM Security Verify Governance instance IdentityManager\BPPerson\SapHRProfile.jar and IdentityManager\Person\SapHRProfile.jar profiles should not be used.
Installing ILMT-Tags File
Before you begin:
The Dispatcher must be installed
Procedure:
Copy the files from ILMT-Tags folder to the specified location:
1. Windows: <SDI-HOME>\swidtag
2. UNIX/Linux: <SDI-HOME>/swidtag
Service/Target form details
Adapter Details tab (Below additional attributes are applicable only for IBM Security Verify Governance Identity Manager)
Person profile name
This is a read only field with "SapHRPerson" value.
Use workflow
If this check box is checked, then an identity policy needs to be created for the IBM Security Governance Identity Manager account for the new person. By default, Use workflow check box is checked.
Evaluate separation of duty policy when workflow is used
This check box should be check if evaluation of separation of duty policy is required when the workflow is used.
Placement rule
Provide details for Placement rule. If you do not specify, the default org is used.
SAP Connection Details Tab
Target Client (Update description for this attribute)
The SAP instance client number. This field is mandatory if no value is supplied for Optional RFC Connection Parameters.
Login ID (Update description for this attribute)
The SAP User account login ID that adapter uses to connect to the SAP instance. This field is mandatory if no value is supplied for Optional RFC Connection Parameters.
Password (Update description for this attribute)
Password for SAP User account. This field is mandatory if no value is supplied for Optional RFC Connection Parameters.
SAP System (DNS hostname or IP) (Update description for this attribute)
Host name of the SAP server host computer only if DNS is set up correctly. Otherwise, use the IP address. This field is mandatory if no value is supplied for Optional RFC Connection Parameters.
SAP System Number (Update description for this attribute)
The SAP server system number. This field is mandatory if no value is supplied for Optional RFC Connection Parameters.
SAP Gateway (DNS host name or IP) (This is new attribute to be added)
Host name of the SAP gateway host computer only if DNS is set up correctly. Otherwise, use the IP address. This host is typically the same host that contains the SAP server. This parameter is optional.
Optional RFC Connection Parameters (This is new attribute to be added)
This attribute allows for alternative SAP connectivity parameters to be specified. The value of this attribute is a formatted string of name-value pairs. Each pair must be separated by a single pipe (|) character. The name parts must be in lowercase characters. The general format of the value of this attribute is shown in this example:
<name1>=<value1> <name2=value2> ... <nameN>=<valueN>
For example, the following string value would set the SAP Message Server to messageserver.com with System ID PR0 and Group SPACE:
mshost=messageserver.com|r3name=PR0|group=SPACE
The names and values are those supported directly by the SAP RFC API. A summary of the names is supplied in the following table:
|
Table 1. Names supported by SAP RFC API |
|
|
Name |
Description |
|
client |
SAP client |
|
user |
User name for logon. Set to $MYSAPSSO2$ if you are using SSO logon. Set to $X509CERT$ if you are using X509 certificates. |
|
alias user |
Alias for user name |
|
passwd |
Password of the user. If you are using SSO or X509 certificates, supply base64 encode value of SSO ticket or X509 certificate. |
|
lang |
Log on language to be used |
|
sysnr |
System number of the target SAP system |
|
ashost |
Host name of the target SAP application server |
|
mshost |
Host name of message service |
|
gwhost |
Host name of the SAP gateway service |
|
gwserv |
Gateway service name |
|
r3name |
R/3 name |
|
group |
Name of SAP application server group |
|
tpname |
Program Id of external RFC server program |
|
tphost |
Host name of external RFC server program |
|
trace |
Set to 1 to enable RFC API trace logging |
|
codepage |
SAP code page |
|
getsso2 |
Set to 1 to obtain SAP SSO ticket |
|
mysapsso2 |
SAP Cookie version 2 as logon ticket |
|
x509cert |
X509 certificate as logon ticket |
|
snc_mode |
Set to 1 to enable secure network connection |
|
snc_partnername |
SNC name |
|
snc_qop |
SNC strength, 1 - 9 |
|
snc_myname |
SNC name. Overrides partner name |
|
snc_lib |
Path name to SNC library implementation |
|
extiddata |
External authentication (PAS) data |
|
extidtype |
External authentication type |
Type B (Load balancing) connection
The mandatory attributes for Type B connection are client, user, passwd, lang, type, mshost, r3name, and group.
To establish Type B (Load Balancing) connection, add the following value under Optional RFC Connection Parameters:
type=B|mshost=<Message Server Name>|r3name=<SYSTEM ID>|group=<Name of SAP application server group>
For example: type=B|mshost=SAPPR0|r3name=PR0|group=SPACE where message server name is SAPPR0 with systemID as PR0 and group SPACE.
Note:
- The dispatcher must be restarted for each change in the Optional RFC Connection Parameters field.
- To establish a Type B (Load Balancing) connection, enable RFC Load balancing in SAP system.
Enable TDI Debugging (This is new attribute to be added)
Flag to enable IBM Security Directory Integrator debugging trace output.
Attribute Mapping (This is applicable only for IBM Security Verify Governance)
Remove existing content of this section and add below details:
Attribute mapping is required to define which target attributes correspond to the Verify Governance User or OU attributes.
About this task
This task involves either an user or OU attribute mapping definition file, which is included in the HR adapter package.
The file consists of Verify Governance User or OU attributes and their equivalent attributes in the managed HR target. The file is structured as <IGI_attribute> = <HR_target_attribute>.
The <IGI_attribute> is fixed and must not be modified. Edit only the <HR_target_attribute>. Some <IGI_attribute> already has a fixed equivalent <HR_target_attribute>. For example:
GIVEN_NAME=ersaphrgivenname
Some <IGI_attribute> do not have a defined <HR_target_attribute> and you can assign the mapping. For example:
USER_TYPE=USER_TYPE
ATTR1=ATTR1
Note:
- The default mapping is already included out-of-the box. If there are no changes to the attribute mapping, there is no need to import the attribute mapping files.
- It might take up to 10 minutes for the attribute mapping changes to take effect once the file is imported.
Procedure
1. Open the mapping definition file by using any text editor.
2. Edit the mapping.
3. If the target attribute has a list of predefined values, use the following syntax to convert its values to the corresponding Verify Governance attribute values.
[conversion].<HR_target_attribute>.<IGI_attribute>
=
[<HR_target_attribute_value1>=<IGI_attribute_value1>;...;<HR_target_attribute_valuen>=<IGI_attribute_valuen>]
For example:
[conversion].ersaphrgender.GENDER=[M=0;F=1]
4. For attributes that contains date and time, use the following syntax to convert its values.
For example:
[conversion.date].ersaphrdob.BIRTHDAY=[yyyyMMdd=dd/MM/yyyy HH:mm:ss]
[conversion.date].ACCOUNT_EXPIRY_DATE.ACCOUNT_EXPIRY_DATE=[dd/MM/yyyy HH:mm:ss=dd/MM/yyyy HH:mm:ss]
5. Import the updated mapping definition file through the Enterprise Connectors module. For more information, see Attribute-to-permission mapping service in the IBM Security Verify Governance product documentation.
Chapter 4: Upgrading
Upgrading the adapter binaries or connector
Take backup of adapter binaries or connector
Procedure:
Take backup of below files before performing upgrade:
<SDI-HOME>/jars/connectors/SapNWSupport.jar
<SDI-HOME>/jars/connectors/SapNWUserConnector.jar
<SDI-HOME>/jars/functions/SapNWRfc.jar
Note: Stop the dispatcher service before upgrading the connector and start it again after the upgrade is complete.
Upgrade adapter binaries or connector
Procedure:
Copy tdi/connectors/*.jar from the adapter package to the <SDI-HOME>/jars/connectors directory
Copy tdi/functions/*.jar from the adapter package to the <SDI-HOME>/jars/functions directory
Upgrading the xsl files
Take backup of xsl files
Procedure:
Take backup of below directory before performing upgrade:
<SDI-HOME>/timsol/xsl
Upgrade xsl files
Procedure:
Copy tdi/xsl directory from the adapter package to the <SDI-HOME>/timsol directory.
Upgrading the adapter profile
Below description is only for IBM Security Verify Governance Identity Manager
Read the adapter Release Notes for any specific instructions before you import a new adapter profile.
There are three adapter profiles included in the SAP HR Feed Adapter distribution package: IdentityManager\BPPerson\SapHRProfile.jar, IdentityManager\Person\SapHRProfile.jar and ISVG\SapHRProfile.jar
The difference between the three profiles is that the IdentityManager\BPPerson\SapHRProfile.jar and IdentityManager\Person\SapHRProfile.jar can be only used with IBM Security Verify Governance Identity Manager instance whereas ISVG\SapHRProfile.jar can only be used with IBM Security Verify Governance instance.
If Business Partner entity is in scope then IdentityManager\BPPerson\SapHRProfile.jar should be used in IBM Security Verify Governance Identity Manager instance else IdentityManager\Person\SapHRProfile.jar should be used. It is not possible for both IdentityManager\BPPerson\SapHRProfile.jar and IdentityManager\Person\SapHRProfile.jar profiles to exist in the same IBM Security Verify Governance Identity Manager instance.
Below description is only for IBM Security Verify Governance
Read the adapter Release Notes for any specific instructions before you import a new adapter profile.
There are three adapter profiles included in the SAP HR Feed Adapter distribution package: IdentityManager\BPPerson\SapHRProfile.jar, IdentityManager\Person\SapHRProfile.jar and ISVG\SapHRProfile.jar
The difference between the three profiles is that the IdentityManager\BPPerson\SapHRProfile.jar and IdentityManager\Person\SapHRProfile.jar can be only used with IBM Security Verify Governance Identity Manager instance whereas ISVG\SapHRProfile.jar can only be used with IBM Security Verify Governance instance.
For IBM Security Verify Governance instance IdentityManager\BPPerson\SapHRProfile.jar and IdentityManager\Person\SapHRProfile.jar profiles should not be used.
Note: Restart the Dispatcher service after importing the profile. Restarting the Dispatcher clears the assembly lines cache and ensures that the dispatcher runs the assembly lines from the updated adapter profile.
Chapter 5: Configuring
Enabling TLSv1.2 in Security Directory Integrator
Procedure:
1. Apply recommended fix packs and limited availability (LA) versions on the Security Directory Integrator. See Recommended fixes for IBM Tivoli Directory Integrator (TDI) & IBM Security Directory Integrator (SDI).
2. After applying the appropriate updates, modify the /solution.properties file by appending the following text to the bottom of the file:
#####################
# # Protocols to enforce SSL protocols in a SDI Server
# # Optional values for com.ibm.di.SSL* property (TLSv1, TLSv1.1, TLSv1.2). # # This can be a multi-valued comma separated property
# # Optional values for com.ibm.jsse2.overrideDefaultProtocol property (SSL_TLSv2, TLSv1,TLSv11,TLSv12).
# # This is a single value property.
#####################
-
com.ibm.di.SSLProtocols=TLSv1,TLSv1.1,TLSv1.2
com.ibm.di.SSLServerProtocols=TLSv1,TLSv1.1,TLSv1.2
com.ibm.jsse2.overrideDefaultProtocol=TLSv1
com.ibm.jsse2.overrideDefaultTLS=true
#####################
Customizing the adapter profile (For IBM Security Verify Governance Identity Manager)
You can customize the adapter profile to change the account form or the service form. To customize the adapter profile, you must modify the adapter JAR file.
About this task
Use the the CustomLabels.properties file to change the labels on the forms. Each adapter has a CustomLabels.properties file.
The JAR file is included in the adapter package that you downloaded from the IBM® Passport Advantage® website. The JAR file and the files in the JAR file vary depending on your operating system.
Note: You cannot modify the schema for this adapter. You cannot add or delete attributes from the schema.
The adapter JAR file includes the following files:
- CustomLabels.properties
- erSapHRPerson.xml
- erSapHRService.xml
- SapHRSearch.xml
- SapHRTest.xml
- schema.dsml
- service.def
Procedure
1. Edit the JAR file.
a. Log on to the workstation where the SAP HR feed adapter is installed.
b. Copy the JAR file into a temporary directory.
c. Extract the contents of the JAR file into the temporary directory by running the following command.
The following example applies to the SAP HR feed adapter profile. Type the name of the JAR file for your operating system.
Windows
cd c:\temp
jar -xvf SapHRProfile.jar
UNIX
cd /tmp
jar -xvf SapHRProfile.jar
The jar command extracts the files into the SapHRProfile directory.
d. Edit the file that you want to change
After you edit the file, you must import the file into the IBM Security Verify Governance Identity Manager server for the changes to take effect.
2. Import the file.
a. Create a JAR file by using the files in the directory.
Run the following commands:
Windows
cd c:\temp
jar -cvf SapHRProfile.jar SapHRProfile
UNIX
cd /tmp
jar -cvf SapHRProfile.jar SapHRProfile
b. Import the JAR file into the IBM Security Verify Governance Identity Manager server.
c. Stop and start the IBM Security Verify Governance Identity Manager server.
d. Restart the adapter service.
Customizing the adapter
The adapters can be customized or extended or both. The type and method of this customization varies depending on the adapter.
Customizing and extending adapters requires a number of skills. The developer must be familiar with the following concepts and skills:
- IBM Security Verify Governance Identity Manager administration
- IBM Security Verify Governance administration
- IBM Security Directory Integrator management
- Security Directory Integrator Assembly Line development
- LDAP schema management
- Working knowledge of Java™ scripting language
- Working knowledge of LDAP object classes and attributes
- Working knowledge of XML document structure
Note: If the customization requires a new Security Directory Integrator connector, the developer must also be familiar with Security Directory Integrator connector development and working knowledge of Java programming language.
Support for custom adapters
The integration to IBM Security Verify Governance servers "the adapter framework" is supported. However, IBM does not support the customizations, scripts, or other modifications. If you experience a problem with a customized adapter, IBM Support may require the problem to be demonstrated on the GA version of the adapter before a Support Case is opened.
Chapter 6: Troubleshooting
Enabling DEBUG Logs on SDI Server
Procedure:
1. Stop the SDI Server process
Pre-7.2.0-ISS-SDI-FP0008
2. Edit the <SDI_Solution_Directory>/etc/log4j.properties
3. Modify the following line:
log4j.rootCategory=INFO, Default
to
log4j.rootCategory=DEBUG, Default
Post-7.2.0-ISS-SDI-FP0008
2. Edit the <SDI_Solution_Directory>/etc/log4j2.xml
3. Modify the following line:
<Root level="info">
to
<Root level="debug">
4. Start the SDI Server process
5. Re-create the problem and collect the <SDI_Solution_Dir>/logs/ibmdi.log
Chapter 7: Reference
No Updates for the current release
Configuration Notes
The following configuration notes apply to this release:
Installation Platform
The IBM Security Verify Governance Adapter was built and tested on the following product versions.
Adapter Installation Platform:
Due to continuous Java security updates that may be applied to your ISVG or ISVGIM servers, the following SDI releases are the officially supported versions:
Note: Earlier SDI supported version may function properly, however to resolve any communication errors, you must upgrade your SDI releases to the officially supported versions by the adapters
Managed Resource:
The following SAP ABAP Basis versions running anywhere on the network are supported:
SAP Release: - SAP Netweaver 730
Component version:-SAP ECC 6.0
SAP HR Fix Pack: - Fix pack 22
IBM Security Verify Governance Servers:
IBM Security Verify Governance Identity Manager (v10.0.1 FP4 release or later)
IBM Security Verify Governance v10.0
SAP JCo certified:
JCo 3.1.7
Note:
SAP HR Feed Adapter was tested and certified using JCo v3.1.7. SAP may have
released a newer version of JCo since then and for reasons unknown, SAP may not
make JCo v3.1.7 available for download. The newer version of JCo may work as is
with the adapter. However, if there are any issues related directly to
the newer version of JCo, it will be addressed in the next release of the
adapter. On Windows platforms, JCo 3.1 requires the Visual Studio 2013
C/C++ runtime libraries to be installed on the system. If not present, download
and install the "Visual C++ 2013 Redistributable Package" from the
Microsoft knowledge base article 4032938 and choose the package, which
corresponds to the used Locale and JVM bit-width (x64 for 64-bit or x86 for
32-bit).
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged should contact:
IBM Corporation
2ZA4/101
11400 Burnet Road
Austin, TX 78758 U.S.A.
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
Trademarks
IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both.
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.
Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.
Other company, product, and service names may be trademarks or service marks of others.