IBM(R) InfoSphere(R) Master Data Management Collaboration Server Version 10.0.0, Test Fix 1 is now available. This release notes document addresses system requirements, installation, and known problems.
Contents
Description of this test fix
InfoSphere MDM Collaboration Server provides a highly scalable, enterprise Product Information Management (PIM) solution. InfoSphere MDM Collaboration Server is the middleware that establishes a single, integrated, consistent view of products and services information inside and outside of an enterprise.
Caution:
It is strongly recommended that you apply the test fix only to a test
system. Test fixes do not undergo official IBM testing.
This test fix addresses the following enhancements and fixes:
The following fixes were included in this test fix as a result of an authorized program analysis report (APAR). You can search for and view existing APARs here: InfoSphere MDM Collaboration Server Support site. You can also review the associated PMR (if one is identified) for the fix, with the Electronic IBM Service Request tool Web site: Service Requests.
Limitations:
Note: This test fix contains numerous fixes for UI and performance defects and it is recommended that you download and apply this test fix.
You can review the release notes of the previous maintenance release for
InfoSphere MDM Collaboration Server, version 10.0.0, to see what
enhancements or product fixes were included previously:
| Fix Release | Release Notes | Release Date |
|---|---|---|
| fix pack 1 | Release notes for fix pack 1 | 02/06/2012 |
System requirements
For information about hardware and software compatibility, see the detailed system requirements document at: http://www.ibm.com/software/data/infosphere/mdm_server_pim/requirements.html.
Installing test fix 1
Before you install this test fix , you must have installed InfoSphere MDM Collaboration Server, Version 10.0.0. In particular, make sure that you have applied all configuration changes. For example, any schema changes and common.properties updates as documented in the Requirements section of those release notes.
Important: Before starting the installation process, you must clean your browser cache. Additionally, all users must clean their browser cache before using the user interface for the first time after a fix pack, interim fix, or test fix has been applied. Frequently, JavaScript files that the user interface depends on are updated and installed with each release. These JavaScript files are cached by the browser when the user interface loads. So, in order to avoid incompatibilities and issues in using the user interface, you must clean your browser cache such that the latest JavaScript files are loaded and used by the user interface.
Important:
The steps for installing this test fix include:
Step 1. Preparing to install the test fix
Before you install the test fix, make sure to complete these steps:
$TOP/bin/go/svc_control.sh --action=stop --svc_name=scheduler
$TOP/bin/go/svc_control.sh --action=short_status--svc_name=workflowengine
If no events are running, shut down the workflow engine manually by running the following shell script:
$TOP/bin/go/svc_control.sh --action=stop --svc_name=workflowengine
$TOP/bin/go/abort_local.sh
Running the abort_local.sh shell script does not affect any of the other JVM services.
$TOP/bin/gdsmsg.sh stop
Wait for a few minutes to allow GDS message listener to finish processing the messages that it has already picked up, and then run this script:
$TOP/bin/gdsmsg.sh abort
The installation will overwrite your current files with updated versions from the test fix . If any issues occur when installing the test fix , you can use this backup copy to roll back the installation.
Important: For this test fix , there are no modification done in the configuration files, admin_properties.xml, and env_settings.ini.
Step 2. Installing the test fix
To install this test fix, you must perform the following steps:
For example: $TOP/10.0.0-WS-MDMCS-TF001.tgz
cd $TOP chmod -R 755 $TOP
For example, when using the GNU tar utility, the following command extracts and unzips the .tgz file by using an absolute path:
gtar zxvf $TOP/10.0.0-WS-MDMCS-TF001.tgz
Important: The InfoSphere MDM Collaboration Server files were packed using the GNU tar utility. Use the GNU tar utility to unpack the archive file for best results, especially on computers running the AIX operating system. If you use the AIX version of the tar command, you might not be able to unpack correctly all files in the archive. One indication of incorrect unpacking of the archive is the presence of the @LongLink file in the directory in which you unpack the archive.
Note: These properties are now being stored in a separate file.
If the encrypt_password parameter in the [db] section of the env_settings.ini file is set to yes, specify the dbpassword argument when invoking configureEnv.sh. If you do not specify the dbpassword argument, you will be prompted to enter the password.
$TOP/bin/configureEnv.sh -dbpassword=database_password
Note: For some configuration files, if you have customized the content of a configuration file and you choose to overwrite the file when running configureEnv.sh, you need to manually restore the values in the file that you have customized using the backup copy that is created. The file name of the backup copy is the name of the corresponding configuration file with the extension ".bak" appended to the end of the name. The exception to this overwriting behavior is common.properties file.
Please also note that by running configureEnv.sh two or more times, you can lose the original customized configuration files. This is because the backup copy of a configuration file gets replaced in place (same file name is used for a given configuration file every time configureEnv.sh is run).
The application server shell script, install_war.sh, installs InfoSphere MDM Collaboration Server into the WebSphere application server.
install_war.sh [ --wsadminUsername=<WAS admin user name> --wsadminPwd=<password for WAS admin user>]
The install_war.sh script will install the WAR file for each app server defined in the [services] section in env_settings.ini. When WebSphere Application Server security is enabled, add the wsadminUsername and wsadminPwd arguments to the install_war.sh command.
Note: When WebSphere Application Server security is enabled, the following
arguments are no longer required in the
$TOP/bin/start_local.sh,
$TOP/bin/start_rmi_appsrv.sh,
$TOP/bin/stop_local.sh, and
$TOP/bin/rmi_status.sh commands:
--wsadminUsername=<WAS admin user name> --wsadminPwd=<password for WAS admin user>
install_gds_war.sh
Step 3. Updating the configuration files
To successfully use the fixes and enhancements in this maintenance release you must modify InfoSphere MDM Collaboration Server configuration files.
InfoSphere MDM Collaboration Server uses the following configuration files:
Note: You must remove these properties from the common.properties file.
List of configuration file changes
New properties introduced in the common.properties file for version 10.0.0 test fix 1:
# set to true for filtering out non indexed attributes from being selected for rich search. # This will not affect existing search template(s) and saved search. rich_search_indexed_only=true
# Controls the number of background processor threads per parent worker thread to convert data into XML for saves # Can be set higher if operations like imports are cpu bound and there are more processors available. # See log.xml.default for changing the log level of the EntryXmlProcessor class to debug to see if more threads may help speed up imports. # Default value is 2 num_xml_processor_background_threads=2
Step 4. Enabling the Global Data Synchronization feature of InfoSphere MDM Collaboration Server (Optional)
Complete this step only if you plan to use the Global Data Synchronization feature of InfoSphere MDM Collaboration Server; otherwise, proceed to Step 5.
To enable the Global Data Synchronization feature of InfoSphere MDM Collaboration Server, Version 10.0.0, you must perform the following steps:
Step 5. Modifying the database schema
Follow the instructions for modifying the database schema to InfoSphere MDM
Collaboration Server V10.0.0, test fix 1 depending on your
current InfoSphere MDM Collaboration Server version as mentioned below:
| Current InfoSphere MDM Collaboration Server version | Instructions for modifying the database schema to InfoSphere MDM Collaboration Server V10.0.0, Test Fix 1 |
|---|---|
| InfoSphere MDM Collaboration Server, Version 10.0.0, Fix Pack 1 | No database migration necessary. You can skip this step and continue with the next step, Step 6 - Verifying the installation. |
| InfoSphere MDM Collaboration Server, Version 10.0.0 GA | Several changes have been made to the database; therefore, you must perform database, database schema and data migration for InfoSphere MDM Collaboration Server, Version 10.0.0, test fix 1. Follow the instructions mentioned below. |
| Any prior release of InfoSphere MDM Server for PIM. | Follow the instructions in the Migrating from prior versions documentation. |
You must complete each step sequentially.
Create new bufferpools and table spaces as mentioned below:
CREATE BUFFERPOOL XML_DATA_BP SIZE AUTOMATIC PAGESIZE 32K;
CREATE BUFFERPOOL XML_LARGE_BP SIZE AUTOMATIC PAGESIZE 32K;
CREATE BUFFERPOOL XML_INDX_BP SIZE AUTOMATIC PAGESIZE 32K;
CREATE REGULAR TABLESPACE XML_DATA PAGESIZE 32K MANAGED BY AUTOMATIC STORAGE
BUFFERPOOL XML_DATA_BP
NO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 100M;
CREATE LARGE TABLESPACE XML_LARGE_DATA PAGESIZE 32K MANAGED BY AUTOMATIC STORAGE
BUFFERPOOL XML_LARGE_BP
FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 100M;
CREATE REGULAR TABLESPACE XML_INDEX PAGESIZE 32K MANAGED BY AUTOMATIC STORAGE
BUFFERPOOL XML_INDX_BP
NO FILE SYSTEM CACHING AUTORESIZE YES INCREASESIZE 100M;
Note: The size of the XML_DATA tablespace should be equal to the space occupied by the TCTG_ITD_ITEM_DETAIL tablespace. You can find the approximate size of the table by using the following query:
select (fpages * 16) / 1024 megabytes from syscat.tables where tabschema = current schema and tabname like 'TCTG_ITD_ITEM_DETAIL';Database setup For Oracle databases
Create new table spaces then install Oracle XML DB component as mentioned below:
CREATE TABLESPACE XML_DATA DATAFILE '/u02/oracle/data/xml_data1.dbf' SIZE 1G REUSE AUTOEXTEND ON NEXT 500M MAXSIZE 30G; CREATE TABLESPACE XML_INDEX DATAFILE '/u02/oracle/data/xml_index1.dbf' SIZE 1G REUSE AUTOEXTEND ON NEXT 500M MAXSIZE 30G;
You can either use automatic storage management or replace the storage paths in the above statements as necessary.
Note: The size of the XML_DATA tablespace should be equal to space occupied by the TCTG_ITD_ITEM_DETAIL tablespace. You can find the approximate size of the table by using the following queries:
select (fpages * 16) / 1024 megabytes from syscat.tables where tabschema = current schema and tabname like 'TCTG_ITD_ITEM_DETAIL'; select (blocks * 8) / 1024 Megabytes from user_tables where table_name = 'TCTG_ITD_ITEM_DETAIL';
Installation of the XML DB component requires the following steps. These steps are for manual installation; you can also use Oracle's database configuration assistant for installation. For more information refer to Oracle documentation http://docs.oracle.com/cd/E11882_01/appdev.112/e23094/appaman.htm#ADXDB5700
In the Oracle database server:
@catqm.sql pass4xdb XML_DATA TEMP NO
Important: Ensure that the database user for InfoSphere MDM Collaboration Server application has appropriate database privileges as mentioned in the installation guide (DB2(R) privileges / Oracle privileges). If database privileges are modified for any reason, the migration script will fail.
To migrate your database schema:
migrateToInstalledFP.sh --fromversion=BASE [--dbpassword=<database password>]
For migrating to InfoSphere MDM Collaboration Server V10.0.0 Test Fix 1, the fromversion parameter must be BASE.
--dbpassword
This is an optional parameter that must be used if you are storing the encrypted database password in the InfoSphere MDM Collaboration Server.
All messages, such as the status of individual migration components and the overall migration summary, are displayed in the console.
After running the migration script, messages are displayed in the console that indicate whether the migration succeeded or failed. This message is displayed if the migration succeeded:
Generating database verification report... ___________________________________________________________ |Changed Tables |=========================================================== | There are no changed tables |___________________________________________________________ ___________________________________________________________ |Missing Tables |=========================================================== | There are no missing tables |___________________________________________________________ ___________________________________________________________ |Changed Indexes |=========================================================== | There are no changed indexes |___________________________________________________________ ___________________________________________________________ |Missing Indexes |=========================================================== | There are no missing indexes |___________________________________________________________
The following information from the database verification report can be ignored. If only the following tables are displayed, the migration process has completed successfully.
|Changed Tables |=========================================================== | TCTG_UDL_USER_DEFINED_LOGS | TCTG_CAX_CATEGORY_CONTENT | TCTG_ITX_ITEM_CONTENT |___________________________________________________________ ___________________________________________________________ |Missing Tables |=========================================================== | TCTG_ULE_USER_LOG_ENTRY_ |___________________________________________________________
This message is displayed if the migration failed:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Migration Failed : xxxx !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Please see the file for further details : /home/pimuser/mdmcs1000/logs/errfile.log
If database verification report indicates changed or missing tables or indexes other than the ones mentioned above, that also indicate migration failure.
This message is displayed if the migration of specific modules failed:
-------------------------------------- Summary of the migration: -------------------------------------- Migration of the following modules failed : <module names>
Review the errfile.log file for additional messages. For SQL errors, find the detailed error message from the SQL error code, correct the error, and run the migration script again. Contact IBM Software Support if the problem persists after correcting the errors.
Migration script can fail with the following reasons:
----------------------------------------------------------- Summary of the migration ----------------------------------------------------------- Migration of the following modules failed: data_maintenance_reports
$TOP/logs/errfile.log will have the following content:
net.sf.ehcache.distribution.MulticastKeepaliveHeartbeatReceiver$MulticastReceiverThreadrun SEVERE: Multicast receiver thread caught throwable. Cause was null. Continuing...
This is because there is an issue with the cache configuration parameters, but the migration script continued and completed successfully. Check your parameters in the Configuring cache parameters topic. There is no need to run the migration script again.
Database verification report indicates the following:
___________________________________________________________ |Changed Tables |=========================================================== | TAUD_OBH_OBJECT_HISTORY | TRSS_SST_SEARCH_TEMPLATE
Recommended action:
This is due to an issue with Oracle database. Please run the following script to fix the changed tables.
perl $PERL5LIB/migrateBlobTables.pl
After running the above script you can generate the database verification report by running the script mentioned below:
$TOP/bin/db/verify_tables_indexes.sh
Database verification report indicates the following:
___________________________________________________________ |Changed Tables |=========================================================== | TPFM_PPI_PROFILE_INFO | TPFM_PPR_PROFILE | TPFM_PSD_SCHEDULE_DETAIL | TPFM_PSI_PROFILE_SCHEDULE_INFO
Recommended action:
perl $PERL5LIB/runSQL.pl --sql_command="alter table tpfm_ppr_profile modify ppr_date date;" perl $PERL5LIB/runSQL.pl --sql_command="alter table tpfm_ppi_profile_info modify ppi_date date;" perl $PERL5LIB/runSQL.pl --sql_command="alter table tpfm_psi_profile_schedule_info modify psi_date date;" perl $PERL5LIB/runSQL.pl --sql_command="alter table tpfm_psd_schedule_detail modify psd_date date;"
After running the above scripts you can generate the database verification report by running the script mentioned below:
$TOP/bin/db/verify_tables_indexes.sh
Database verification report indicates the following:
___________________________________________________________ |Missing Tables |=========================================================== | TCTG_CAX_CATEGORY_CONTENT | TCTG_ITX_ITEM_CONTENT
Recommended action:
This may be due to some problems during database setup. Please verify you have the database setup correctly. Then rerun the migration script.
To migrate your data:
./delete_old_versions.sh --code=<company code> --end_date=<YYYY-MM-DD.HH24:MI:SS>
This parameter refers to the company code that is used to log on to the InfoSphere MDM Collaboration Server.
--end_date
This parameter refers to the current date.
Example
./delete_old_versions.sh --code=ibm --end_date=2012-01-24.13:00:00
perl $PERL5LIB/runSQL.pl --sql_command="delete from cad where cad_next_version_id <> 999999999;" perl $PERL5LIB/runSQL.pl --sql_command="delete from itd where itd_item_id not in select itm_id from itm);" perl $PERL5LIB/runSQL.pl --sql_command="delete from itd where itd_next_version_id <> 999999999;"
migrateDataToXml.sh --company=<company name> --threads=<number of threads>
This parameter refers to the company code that is used to log on to InfoSphere MDM Collaboration Server.
--threads
Use this option to improve speed by using more than one thread, but ensure that enough DB connections exist. The default is 2.
Note: The data migration script requires a certain number of DB connections, which is twice the number of threads used for execution. For example, if you use 4 threads then it will require 8 DB connections. The required DB connections are configured through the following two configuration parameters:
Both the parameters are available in the common.properties file. If the values of these parameters are already equal to or greater than the required DB connections, then you do not need to change the values. If the values of these parameters are less than the required DB connections, then you must increase the values to improve speed.
Example
migrateDataToXml.sh --company=ibm --threads=4
Important: Ensure that database user for InfoSphere MDM Collaboration Server application has appropriate database privileges as mentioned in the installation guide . If database privileges are modified for any reason, the migration script will fail.
Step 6. Verifying the installation
Every time that you install a test fix , verify that the installation was successful. To verify the installation of this test fix , complete these steps:
The shell script, start_local.sh, located in the $TOP/bin/go directory, starts all the services that you need to run InfoSphere MDM Collaboration Server.
The --redeploy command ensures that all Web services are properly re-deployed.
The svc_control.sh supports starting multiple services from the same command:
svc_control.sh --action=start --svc_name=<service name>[--svc_name=<service name>]
svc_control.sh --action=start --svc_name=appsvr --svc_name=admin --svc_name=scheduler
gdsmsg.sh start
This process should only take approximately 30-40 seconds, depending on the speed of your CPU processor.
Important: For InfoSphere MDM Collaboration Server running WebSphere Application Server, as part of a new installation or an upgrade to an existing installation, use the redeploy option when running the start_local.sh script to ensure the Web services are deployed to the InfoSphere MDM Collaboration Server application. In order to redeploy existing Web services, you need to select the redeploy option when restarting InfoSphere MDM Collaboration Server with WebSphere Application Server. When you use the redeploy option it ensures that the Web services are redeployed.
Important: For InfoSphere MDM Collaboration Server running on the Oracle WebLogic server, use the redeploy option when you run the start_local.sh script at startup. You need to use the redeploy and waitforappsvr command options as shown in the following syntax:
start_local.sh --redeploy --waitforappsvr=<number of seconds>
or
svc_control.sh --action=start --svc_name=admin --svc_name=scheduler [ --svc_name=appsvr --redeploy [--waitforappsvr=<number of seconds>] ]
- where the <number of seconds> is the number of seconds (positive integer) that the deployment command will wait for the appsvr services to become ready to initiate the re-deployment of Web services. The default value of this option is 5 seconds.
The waitforappsvr option must be used with the redeploy option. When the waitforappsvr option is omitted in a command with the "redeploy" option, the default value of waitforappsvr takes effect.
Users are advised to supply values slightly greater than the required startup time of the appsvr service, which can be monitored using the rm_status.sh command as shown in step 6.2 below. Too low a value for the waitforappsvr option can result in errors with stack dump on screen or log files.
The --svc_name=appsvr option in the svc_control.sh command must be accompanied by the redeploy and optionally the waitforappsvr command options.
Run the $TOP/bin/go/rmi_status.sh script and verify that the following services have started correctly:
Run the following script to verify that the GDS messaging services have started correctly:
$TOP/bin>./get_ccd_version.sh 10.0.0-TF001#02
Step 7. Enabling GDS Migration
You need to perform the steps of the migration process defined to migrate from a GDS V1.3.1.x environment to a GDS in IBM(R) InfoSphere(R) Master Data Management Server for Product Information Management, V9.1.x environment. Refer to Migrating Global Data Synchronization from V1.3.x to InfoSphere MDM Server for PIM V9.1.x for more information.
Known problems
Known problems are documented in the form of individual technotes in the Support knowledge base at http://www.ibm.com/support/entry/portal/Overview/Software/Information_Management/InfoSphere_Master_Data_Management_Server_for_Product_Information_Management. As problems are discovered and resolved, the IBM Support team updates the knowledge base. By searching the knowledge base, you can quickly find workarounds or solutions to problems.
You can search for and display a list of all published technotes for InfoSphere MDM Collaboration Server. For information about how to search all published technotes, see Searching knowledge bases
You can search for keywords within this complete list of technotes.
Contacting IBM Support
Before contacting IBM Support, your company must have an active IBM software maintenance contract, and you must be authorized to submit problems to IBM. For information about the types of maintenance contracts available, see "Enhanced Support" in the Software Support Handbook at: techsupport.services.ibm.com/guides/services.html
After you define the problem gather background and diagnostic information, and determine the severity of the problem, you can submit your problem to IBM Support in one of the following ways:
If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Software IBM Support provides a workaround that you can implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the IBM Support web site daily, so that other users who experience the same problem can benefit from the same resolution.
Notices
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
grant 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
J46A/G4
555 Bailey Avenue
San Jose, CA 95141-1003
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.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.
Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:
(C) (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. (C) Copyright IBM Corp. _enter the year or years_. All rights reserved.
If you are viewing this information softcopy, the photographs and color illustrations may not appear.
Trademarks
IBM, the IBM logo, and ibm.com(R) are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol ((R) or (TM)), indicating trademarks that were owned by IBM at the time this information was published. A complete and current list of IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml.
Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc., in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.