IBM Security Verify Governance| Adapter 10.0.1 for SAP AS Java (UME) is available. Compatibility, installation, and other getting-started issues are addressed.
Welcome to the IBM Security Verify Governance Server Adapter for SAP AS Java (UME).
These Release Notes contain information for the following products that was not available when the IBM Security Verify Governance manuals were printed:
The IBM Security SAP AS Java (UME) Adapter is designed to create and manage accounts on a target SAP AS Java. The adapter runs in "agentless" mode and communicates using standard SPML (DSML V2) interface provided by SAP Application Server Java for UME.
The IBM Security Verify Governance Adapters are powerful tools that require Administrator Level authority. Adapters operate much like a human system administrator, creating accounts, permissions, and home directories. Operations requested from the IBM Security Verify Governance Identity Manager server and IBM Security Verify Governance server will fail if the Adapter is not given sufficient authority to perform the requested task .
Service Groups Management
The ability to manage service groups was a feature introduced prior to IBM Security Verify Governance. By service groups, IBM Security Verify Governance is referring to any logical entity that can group accounts together on the managed resource.
Managing service groups implies the following:
Create service groups on the managed resource.
Modify attribute of a service group.
Delete a service group.
Note that service group name change is not supported in IBM Security Verify Governance release.
The SDI Based SAP UME adapter does not support management of service groups
Review and agree to the terms of the IBM Security Identity 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 |
2025 June 19 23.11.01 |
|
Adapter Version |
10.0.1 |
|
Component Versions |
Adapter build: 10.0.1.003 Profile: 10.0.1.003 Connector: 10.0.1.003 Dispatcher 7.1.39 and above |
|
Documentation |
The following guides are available in the IBM Knowledge Centre: SAP AS Java (UME) Adapter Installation and Configuration Guide |
New Features
|
Internal# |
Enhancement # (RFE) |
Description |
|
|
|
Items included in current release 10.0.1 |
|
SVGAD-4532 |
ADAPT-184 |
Certify the adapter for use with IBM Security Verify Directory Integrator version 10.0.0 |
|
SVGAD-1359 |
ADAPT-I-40 |
Add support to set productive password |
|
|
|
Items included in release 7.1.8 |
|
|
|
None |
|
|
|
Items included in 7.1.7 release |
|
RTC-167426 |
As a SAP UME adapter developer, I should research if productive passwords can be set. For info regarding technical user refer to Corrections to Install Guide |
|
|
|
|
Items included in 7.1.6 release |
|
|
|
None |
|
|
|
Items included in 7.1.5 release |
|
|
|
None |
|
|
|
Items included in 7.1.4 release |
|
RTC 151785 |
Add Support for Identity Governance and Intelligence (IGI) v5.2.2 This adapter is now designed for use with IBM Security Identity Server, privileged Identity Manager, and Identity Governance and Intelligence. |
|
|
RTC 147658 Bugz 2002 |
PMR 69343,650,758 |
IBM Security Identity Adapter Reconciliation Issue. SAPUMEAdapter does not support a different ID format. |
|
|
|
Items included in 7.0.3 release |
|
RTC 147659 |
Added support for OSDB: SAP 7.50 |
|
|
|
|
Items included in 7.0.2 release |
|
|
Changed the behavior of the following multi-value attributes from replaceMultiValue to add/delete : ersapumeassignedroles=User Roles ersapumeassignedgroups=User Groups
Note: This change was done for IGI 5.2. |
|
|
|
|
Items included in 7.0.1 release |
|
|
Initial Release. |
Closed Issues
|
Internal# |
Case# / Known Issue# |
Description |
|
|
|
Items included in current release 10.0.1 |
|
SVGAD-3282 / Bug 4443 / VDEV-31622 |
In IGI, after recon account does not have group-membership data where target account is member of groups. |
|
|
SVGAD-3285 / Bug 4444 / VDEV-31627 |
In the IGI, on target accounts role membership is not removed on removing CD Users role entitlement. |
|
|
SVGAD-3274 / Bug 4441 / VDEV-31605 |
Reconciliation fails when the relative path provided in Attribute Map element of service form does not exist under <SDI_HOME>\timsol directory or when no value is provided on the service from for Attribute Map element and SAPUMEAttributeMap.properties file is not present in the default <SDI_HOME>\timsol\umeprop directory. |
|
|
SVGAD-3278 / Bug 4442 / VDEV-31621 |
After recon account status is shown as ACTIVE even though the status is SUSPEND on target. |
|
|
SVGAD-4526 |
|
Clear text of password should not be printed in the logs |
|
SVGAD-4488 |
|
Account form > DateInput for ersapumevalidfrom and ersapumevalidto not working |
|
|
|
Items included in release 7.1.8 |
|
RTC 181053 |
IJ11413/Bug 2631 |
PMR TS000177023 - ISIM 7 - SAP UME Adapter 7.1.7 NullPointer Exception |
|
|
|
Items included in 7.1.7 release |
|
|
|
None |
|
|
|
Items included in 7.1.6 release |
|
RTC 165277 |
IV98614/Bugz 2396 |
Attributes not found in schema definition US - As a SAP UME adapter developer, I need to ensure the 7.1 adapter supports the same attributes as 6.0 |
|
|
|
Items included in 7.1.5 release |
|
Internal |
|
Adding missing information back into the release notes |
|
|
|
Items included in 7.1.4 release |
|
RTC 151841
|
IV89222/Bugz 2164 |
IBM Security Identity SAP UME Adapter 7.0.2 does not delete account attribute values. |
|
|
|
Items included in 7.0.3 release |
|
|
IV88515/Bugz 2002 |
PMR 69343,650,758
IBM Security Identity SAP UME Adapter Reconciliation Issue. XML special characters in user/group/role names cause SAXParserException. |
|
|
|
Items included in 7.0.2 release |
|
|
|
None |
|
|
|
Items included in 7.0.1 release |
|
|
|
Initial Release. |
Known Limitations for SAP AS Java (UME) Adapter
|
Internal# |
APAR# |
PMR# / Description |
|
|
|
The Adapter for SAP AS Java (UME) does not cache the connection because it create new HTTP(S) request for each SPML requests. |
|
|
|
During add or modify operation, if any value of multiple valued attribute is wrong then, all the values passed by IBM Security Identity Server for that attribute will not be provisioned. |
|
|
|
The Adapter for SAP AS Java (UME) does not support Kerberos. |
|
|
|
Adapter can't process the reconciliation of support data for attributes like Country Name, Policies, Time zones, Languages. |
|
SVGAD-4662 |
|
Removal of Default groups/roles returned as success at Identity side but failing on target. |
See the Installation and Configuration guide for IBM Security Verify Governance Adapter for detailed instructions.
The following corrections to the Installation Guide apply to this release:
Chapter 1: Overview
Nothing to update
-> Prerequisites
Directory Integrator:
Update the description as below:
IBM Security Directory Integrator, consult the release notes for the currently
supported versions
Chapter 3: Installing
Installing ILMT-Tags File
(Please add new section "Installing ILMT-Tags" File under the section Installing > Installing ILMT-Tags in install guide.)
Before you begin:
- The Dispatcher must be installed
Procedure:
Copy the files in the ILMT-Tags folder to the specified location:
1. Windows: <SDI-HOME>/swidtag
2. Unix/Linux: <SDI-HOME>/swidtag
-> Installing in the Verify Governance
Virtual Appliance
For Verify Governance target management, you can install an IBM Security Verify Governance Adapters or a custom adapter on the built-in Security Directory Integrator in the virtual appliance instead of installing the adapter externally. As such, there is no need to manage a separate virtual machine or system.
About this task
This procedure is applicable to install this adapter on the virtual appliance.
Procedure
1. Download the adapter
package from the IBM Passport Advantage.
For example, Adapter-<Adaptername>.zip.
The adapter package includes the following files:
|
Table 1. Adapter package contents |
|
|
Files |
Descriptions |
|
bundledefinition.json |
The adapter definition file. It specifies the content of the package, and the adapter installation and configuration properties that are required to install and update the adapter. |
|
Adapter JAR profile |
A Security Directory Integrator adapter always include a JAR profile which contains: targetProfile.json o Service provider configuration o Resource type configuration o List of assembly lines A set of assembly lines in XML files A set of forms in XML files Custom properties that include labels and messages for supported languages.
Use the Target Administration module to import the target profile. |
|
Additional adapter specific files |
Examples of adapter specific files: Connector jar files Configuration files Script files Properties files The file names are specified in the adapter definition file along with the destination directory in the virtual appliance. |
|
|
|
2. From the top-level menu of the Appliance Dashboard, click Configure > SDI Management.
3. Select the instance of
the Security Directory Integrator for which you want to manage the adapters and
click Manage > SDI Adapters
The SDI Adapters window is displayed with a table that list the name,
version, and any comments about the installed adapters.
4. On the SDI Adapters window, click Install.
5. On the File Upload
window, click Browse to locate the adapter package and then
click OK.
For example, Adapter-<Adaptername>.zip.
6. Provide the missing 3rd party libraries when prompted.
a. On the File
Upload for Pre-requisite files window, click Select Files.
A new File Upload window is
displayed.
b. Browse and select all the missing libraries and files. For example, httpclient-4.0.1.jar
c. Click Open.
The selected files are listed in the
File Upload for Pre-requisite files window.
d. Click OK.
The missing files are uploaded, and the adapter package is updated with the 3rd
party libraries.
7. Enable secure communication.
a. Select the instance of the Security Directory Integrator for which you want to manage the adapter.
b. Click Edit.
c. Click the Enable SSL check box.
d. Click Save Configuration.
8. Import the SSL certificate to the IBM Security Directory Integrator server.
a. Select the instance of the Security Directory Integrator for which you want to manage the adapter.
b. Click Manage > Certificates.
c. Click the Signer tab.
d. Click Import.
The Import Certificate window is displayed.
e. Browse for the certificate file.
f. Specify a label for the certificate. It can be any name.
g. Click Save.
Note: While uploading the Adapter package, you may receive System Error: A file included in the SDI Adapter zip already exists on the system and the Server Message log under Appliance tab of VA will have a reference to error com.ibm.identity.sdi.SDIManagementService File ibm.com_IBM_Verify_Identity_Governance_xxxx.swidtag found in the adapter zip at location ILMT-Tags/ already exists in system. This is because, you can install the same swidtags only once. So, if another adapter of the same type is installed, remove the swidtags.
The ibm.com_IBM_Verify_Identity_Governance_Enterprise-xxxx.swidtag file is common to all adapters. In addition to the common swidtag file, an application adapter needs ibm.com_IBM_Verify_Identity_Governance_Application_Adapters-xxxx.swidtag file and an infra adapter needs ibm.com_IBM_Verify_Identity_Governance_Lifecycle-xxxx.swidtag and ibm.com_IBM_Verify_Identity_Governance_Compliance-xxxx.swidtag files. So, if an application adapter is already installed and this is an infra adapter, then only install the infra-specific swidtags and the other way around. Please visit Security Verify Governance Adapters v10.x link to identify the adapter type of the installed adapters.
Before you begin
The steps to install adapter and related files into the container can be performed using the adapterUtil.sh script, which is shipped with the dispatcher package. This script should be staged on the machine running Kubernetes cli. The adapterUtil.sh script is also readily available in the bin directory of ISIM IBM Security Verify Governance Identity Manager Container Starter Kit installation directory (If ISVDI was selected for installation during the ISIM container installation steps).
If, for any reason, the adapter util script cannot be executed or used, the below manual instructions must be followed to copy the files to the persistent volume.
Note: The container must be restarted after installing or uninstalling the adapter and any changes to the configuration yaml. To activate changes and restart the container run the following commands:
<path_to_starterkit>/bin/createConfigs.sh isvdi
For OpenShift container: oc -n isvgim rollout restart deployment isvdi
For kubernetes container: kubectl -n isvgim rollout restart deployment isvdi
Note: This document only describes the adapterUtil.sh command options that are required to install this adapter. For other command options, such as listing installed connectors and 3rd party jars, please refer to the Dispatcher10 Installation and Configuration Guide.
Installing / Upgrading / Re-installing / Downgrading the adapter
Using Script
Use the below command to install / upgrade/ re-install / downgrade the adapter:
/path/to/adapterUtil.sh -loadAdapter "/path/to/Adapter-<Adaptername>-*.zip" accept
Where /path/to/adapterUtil.sh is the location where the adapterUtil.sh script is installed and /path/to/Adapter-<Adaptername>-*.zip is the location where the Adapter zip file is staged on the machine running Kubernetes cli.
Manually copying files to Persistent Volume
Copy the files to the persistent volume mapped to the /opt/IBM/svgadapters directory of the container image as per the given directory structure:
SapUMEConnector.jar
Copy this file to the <Persistent_Volume>/jars/connectors directory.
ILMT-Tags
Copy below files to the <Persistent_Volume>/swidtag directory:
ibm.com_IBM_Verify_Identity_Governance_Compliance-xx.x.x.swidtag
ibm.com_IBM_Verify_Identity_Governance_Enterprise-xx.x.x.swidtag
ibm.com_IBM_Verify_Identity_Governance_Lifecycle-xx.x.x.swidtag
Insterting SAPUMEAttributeMap.properties file
Copy this file to the <Persistent_Volume>/timsol/properties directory.
Inserting SAPUMEAdapterSSL.properties file
1. Update file like below:
#TDI JVM trustStore location
javax.net.ssl.trustStore=/home/isvdi/serverapi/testadmin.jks
#TDI JVM trustStore password
javax.net.ssl.trustStorePassword=<Instert_Password>
#TDI JVM keystore location
javax.net.ssl.keyStore=/home/isvdi/serverapi/testadmin.jks
#TDI JVM keystore password
javax.net.ssl.keyStorePassword=<Instert_Password>
#TDI JVM trustStore file type
javax.net.ssl.trustStoreType=JCEKS
2. Copy the files to the persistent volume mapped to the <Persistent_Volume>/timsol/properties directory.
3. Create sapume.sh file and add below line in the file.
mkdir -p /opt/IBM/TDI/timsol/umeprop && cp /opt/IBM/svgadapters/timsol/properties/SAPUMEAdapterSSL.properties $_
4. Make file executation by command :
chmod +x sapume.sh
5. Configure sapume.sh script in the container
Copy
script to the <Persistent_Volume>/scripts directory manually
in the container or you can use below command:
/path/to/adapterUtil.sh
-copyToScripts /path/to/isva.sh <Persistent_Volume>/scripts
Refer https://www.ibm.com/docs/api/v1/content/SSCQGF_10.0.0/container/html/verify-directory-integrator.html#advanced page from SVDI to add an advanced configuration element (if it don t exist in current configuration) to the config.yaml file which is used as parameter for YAML_CONFIG_FILE environment variable of the container.
If the config.yaml file which is used as the YAML_CONFIG_FILE environment variable for the container doesn't have an advanced configuration element, follow the instructions that are provided in https://www.ibm.com/docs/api/v1/content/SSCQGF_10.0.0/container/html/verify-directory-integrator.html#advanced to add an advanced configuration section to the config.yaml file.
Add script (as mentioned in the SVDI guide) as below:
init:
aux-config-programs:
- command: /opt/IBM/svgadapters/scripts/sapume.sh
Configuring the SSL connection between the IBM Security Verify Directory Integrator Container and the SAP UME Target
Refer https://www.ibm.com/docs/api/v1/content/SSCQGF_10.0.0/container/html/verify-directory-integrator.html#keyfile_trusted-certificates page from SVDI
If the config.yaml file which is used as the YAML_CONFIG_FILE environment variable for the container doesn't have a trusted-certificates element, follow the instructions that are provided in https://www.ibm.com/docs/api/v1/content/SSCQGF_10.0.0/container/html/verify-directory-integrator.html#keyfile_trusted-certificates to add a trusted-certificates section to the config.yaml file.
To add a trusted-certificates element (if it doesn't exist in current configuration) to the config.yaml file which is used as parameter for YAML_CONFIG_FILE environment variable of the container, refer to the steps given in installing > Exporting and installing the Secure Sockets Layer (SSL) certificate to download the certificate ssl-credentials-cert.crt and place the certificate in the certs directory of the config volume which contains the config.yaml file. The default location for this config volume is /opt/IBM/dispatcher/config.
Provide this path of the certificate in config.yaml file as shown in the example below:
keyfile:
trusted-certificates:
- '@/opt/IBM/dispatcher/config/certs/ssl-credentials-cert.crt'
Enabling TLS 1.2
Refer https://www.ibm.com/docs/api/v1/content/SSCQGF_10.0.0/container/html/verify-directory-integrator.html#advanced page from SVDI to add an advanced configuration element (if it don t exist in current configuration) to the config.yaml file which is used as parameter for YAML_CONFIG_FILE environment variable of the container.
If the config.yaml file which is used as the YAML_CONFIG_FILE environment variable for the container doesn't have an advanced configuration element, follow the instructions that are provided in https://www.ibm.com/docs/api/v1/content/SSCQGF_10.0.0/container/html/verify-directory-integrator.html#advanced to add an advanced configuration section to the config.yaml file.
To enable TLSv1.2, add 2 attr and value key pair (as mentioned in the SVDI guide) as below:
- attr: com.ibm.di.SSLProtocols
value: 'TLSv1.2'
- attr: com.ibm.di.SSLServerProtocols
value: 'TLSv1.2'
Enabling debug logs and disabling json-logging
If the config.yaml file which is used as the YAML_CONFIG_FILE environment variable for the container doesn't have root-level and json-logging configuration elements, follow the instructions that are provided in https://www.ibm.com/docs/api/v1/content/SSCQGF_10.0.0/container/html/verify-directory-integrator.html#general_logging to the add root-level and json-logging configuration elements section to the config.yaml file.
Refer https://www.ibm.com/docs/api/v1/content/SSCQGF_10.0.0/container/html/verify-directory-integrator.html#general_logging page from SVDI to add root-level and json-logging configuration elements (if they don t exist in current configuration) to the config.yaml file which is used as parameter for YAML_CONFIG_FILE environment variable of the container.
To enable debug logs, set the value for root-level to debug. To disable json logging, set the value for json-logging element to false.
Uninstalling the adapter
Using Script
Use the below command to remove the adapter:
/path/to/adapterUtil.sh -removeAdapter Adapter-<Adaptername>
Manually copying / removing files to / from the Persistent Volume
Remove files from the given directory structure of the persistent volume mapped to the /opt/IBM/svgadapters directory of the container image.
Note: Some 3rd party jars and ILMT-Tags files might be common with other installed adapters, and hence should not be removed while uninstalling this adapter:
ILMT-Tags
Remove below files from <Persistent_Volume>/swidtag directory:
ibm.com_IBM_Verify_Identity_Governance_Compliance-xx.x.x.swidtag
ibm.com_IBM_Verify_Identity_Governance_Enterprise-xx.x.x.swidtag
ibm.com_IBM_Verify_Identity_Governance_Lifecycle-xx.x.x.swidtag
Chapter 4: Upgrading
No updates for the current release
Chapter 5: Configuring
(Add this section Adapter
Installation and Configuration Guide)
- 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
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 PMR 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_HOME_Directory>/etc/log4j2.xml
3. Modify the following line:
<Root level="info">
to
<Root level="debug">
Post-7.2.0-ISS-SDI-FP0011
4. To enable TCB block in debug
5. Append the line com.ibm.di.logging.close=false in
the the <SDI_HOME_Directory>/etc/global.properties file.
6. Start the SDI Server process
7. Re-create the problem and collect the <SDI_Solution_Dir>/logs/ibmdi.log
Logs are not getting printed in FP13 in Windows OS:
To fix this issue copy log4j2.xml file from <SDI_Home_Dir>/etc and add to the <SDI_Solution_Dir>/etc (which was missing there). Then configure <SDI_Solution_Dir>/ibmdiservice.props with
jvmcmdoptions=-Dlog4j2.configurationFile=etc\log4j2.xml
Chapter 6: Reference
Nothing to update
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 IBM Security Verify Governance server and IBM Security
Verify Governance Identity Manager server, the following SDI releases are the
officially supported versions:
- Security
Directory Integrator 7.2 + FP14
- Security Verify Directory Integrator 10.0.0 + FP05
Note: Earlier versions of SDI that are still supported may function properly, however to resolve any communication errors, you must upgrade your SDI releases to the officially supported versions by the adapters. Please refer to the adapter's installation and configuration guides for the latest update on IBM Security Directory Integrator versions and fix packs
Managed Resource:
The following SAP AS Java versions running anywhere on the network are supported:
SAP 730 EHP 1 NetWeaver Portal
SAP 740 NetWeaver Portal
SAP 750 NetWeaver Portal
SAP Patches:
The following minimum patch levels, by SAP release version, are required:
SAP Release Software Component Version
730 EHP 1 J2EE-Engine_DB6 (UMEADMIN) 1000.7.31.10.0
740 J2EE-Engine_DB6 (UMEADMIN) 1000.7.40.8.0
750 J2EE-Engine_DB6 (UMEADMIN)
Supported IBM Security Verify Governance servers:
IBM Verify Identity Governance v11.0
IBM Security Verify Governance Identity Manager v10.0*
IBM Security Verify Governance v10.0
* Unless this document specifies a specific fix pack version of ISVG Identity Manager v10, we expect the adapter to work with ISIM 6 as well. However, it will only be debugged and fixed from the perspective of ISVG-IM v10.
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.