IBM(R) InfoSphere(R) Master Data Management Server for Product Information Management Version 9.1.0, Test Fix 8 is now available. This release notes document addresses compatibility, system requirements, installation, and known problems.
Contents
Attention: Effective July 1, 2012 the InfoSphere MDM Server for PIM version 9.0.0 will be merged with version 9.1.0. To align fix pack numbers between the two versions, the next fix pack after fix pack 3 for version 9.1.0 is fix pack 9.
Description of this test fix
InfoSphere MDM Server for PIM provides a highly scalable, enterprise Product Information Management (PIM) solution. InfoSphere MDM Server for PIM 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 Server for PIM 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 Server for PIM, version 9.1.0, to see what
enhancements or product fixes were included previously:
| Fix Release | Release Notes | Release Date |
|---|---|---|
| fix pack 9 | Release notes fix pack 9 | 07/17/2012 |
| fix pack 3 | Release notes for fix pack 3 | 04/25/2012 |
| interim fix 7 | Release notes for interim fix 7 | 03/14/2012 |
| interim fix 6 | Release notes for interim fix 6 | 01/07/2012 |
| fix pack 2 | Release notes for fix pack 2 | 12/14/2011 |
| interim fix 5 | Release notes for interim fix 5 | 10/17/2011 |
| interim fix 4 | Release notes for interim fix 4 | 09/23/2011 |
| interim fix 3 | Release notes for interim fix 3 | 08/29/2011 |
| fix pack 1 | Release notes for fix pack 1 | 07/11/2011 |
| interim fix 2 | Release notes for interim fix 2 | 05/31/2011 |
| interim fix 1 | Release notes for interim fix 1 | 04/29/2011 |
Compatibility issues with earlier versions
InfoSphere MDM Server for PIM, Version 9.1.0 no longer supports the following versions of software:
For a complete list of the supported hardware and software for Version 9.1.0, test fix 8, see the System requirements section.
A set of user interface functions were introduced in InfoSphere MDM Server for PIM Version 9.0.0 providing more intuitive, user-friendly and modern look-and-feel alternative to the functions (also known as "classic UI functions") which we delivered in the earlier versions of the product. At some appropriate time in the future as determined by IBM the classic functions will be removed from the product.
The "classic UI functions" that will be removed under this coverage include but are not limited to the following.
In InfoSphere MDM Server for PIM Version 6.0.0 a new home page, worklist user interface and simplified single edit user interface were introduced. With the introduction of a newer set of user interface functions in InfoSphere MDM Server for PIM Version 9.0.0 , the usefulness of the simplified single edit user interface quickly diminishes. At some appropriate time in the future as determined by IBM the simplified single edit user interface will be removed from the product. The home page and the worklist user interface will not be removed.
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 8
Before you install this test fix, you must have installed InfoSphere MDM Server for PIM, Version 9.1.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, common.properties, 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/9.1.0-WS-MDMPIM-TF008.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/9.1.0-WS-MDMPIM-TF008.tgz
Important: The InfoSphere MDM Server for PIM 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(R) 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 Server for PIM 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 Server for PIM configuration files.
InfoSphere MDM Server for PIM uses the following configuration files:
Note: You must remove these properties from the common.properties file.
Starting with Version 9.1.0, interim fix 2, you can encrypt the database password.
Note: With the encrypt_password parameter set to yes, the database related scripts require the dbpassword argument to be specified when invoking the scripts. If the dbpassword argument is not specified, you will be prompted to enter the password. If the encrypt_password parameter is set to no or not set, you run the scripts without specifying the dbpassword argument as in earlier versions of InfoSphere MDM Server for PIM.
In this test fix, four new properties have been added to the gds.properties file. These properties are meant to ease CIN processing checks on item existence for CINs of type add (NEW & INITIAL LOAD) and update (CHANGE & CORRECT). The possible values are: "ON" and "OFF" - (value should be used without quotes). The default is ON.
The cases where these could be used are:
Note: ITEM_DELETE(s), if items are not synced already, should not be allowed to pass such validation and hence is not provided as an option. For more details about processing of ITEM_DELETE CINs, refer "delete_tradeitems" property.
VALIDATE_ITEM_EXISTENCE_FOR_NEW_ITEM=ON VALIDATE_ITEM_EXISTENCE_FOR_INTIAL_LOAD=ON VALIDATE_ITEM_EXISTENCE_FOR_ITEM_CHANGE=ON VALIDATE_ITEM_EXISTENCE_FOR_ITEM_CORRECT=ON
Note: If you modify the gds.properties file, and then configure the environment using the configureEnv.sh script, the gds.properties file will be overwritten with the default values. To avoid this situation, you can modify the gds.properties file as well as the gds.properties.default file. Both the files are located in the $TOP/etc/default directory.
Step 4. Enabling the Global Data Synchronization feature of InfoSphere MDM Server for PIM (Optional)
Complete this step only if you plan to use the Global Data Synchronization feature of InfoSphere MDM Server for PIM; otherwise, proceed to Step 5.
To enable the Global Data Synchronization feature of InfoSphere MDM Server for PIM, Version 9.1.0, you must perform the following steps:
Step 5. Modifying the database schema
Follow the instructions for modifying the database schema to InfoSphere MDM
Server for PIM V9.1.0, test fix 8 depending on your current
InfoSphere MDM Server for PIM version as mentioned below:
| Current(R) InfoSphere MDM Server for PIM version | Instructions for modifying the database schema to InfoSphere MDM Server for PIM V9.1.0, test fix 8 |
|---|---|
| Any fix pack release of InfoSphere MDM Server for PIM, Version 9.1.0 | Several changes have been made to the database schema; therefore, you must run a migration shell script to migrate to the database schema of InfoSphere MDM Server for PIM, version 9.1.0, test fix 8. Follow the instructions mentioned below. |
| Any fix pack release of InfoSphere MDM Server for PIM, Version 9.0.0 | Follow the instructions in the Migrating from prior versions and Migrating from V9.0.0 to V9.1.0 documentation. |
| Any fix pack release of InfoSphere MDM Server for PIM, Version 6.0.0 | Follow the instructions in the Migrating from prior versions and Migrating from V6.0.0 to V9.1.0 documentation. |
| Any fix pack release of WebSphere Product Center, Version 5.3.2 | Follow the instructions in the Migrating from prior versions and Migrating from V5.3.2 to V9.1.0. documentation. |
Note: For DB2 databases
If you are upgrading from an older version of DB2 to DB2 version 9.7, you must ensure that the CUR_COMMIT database configuration parameter is enabled. You must manually set this parameter because it is disabled by default for databases that are upgraded from older versions. You must also have the database administrator execute the following SQL commands before starting the migration of InfoSphere MDM Server for PIM:
alter tablespace blob_tbl_data convert to large; alter tablespace blob_tbl_data file system caching
If you are using custom tablespaces instead of the default USERS, INDX or BLOB_TBL_DATA tablespaces, then refer to Migrating from prior versions for more information.The migrations provided are for general InfoSphere MDM Server for PIM data structures and data, and do not provide the GDS data model modifications for compliance to the BMS 2.7 specifications.
Important: Ensure that database user for InfoSphere MDM Server for PIM application has appropriate database privileges as mentioned in the installation guide (DB2 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|IF1|IF2|IF3|FP1|IF4|IF5|FP2|IF7|FP3|FP9 [--dbpassword=<database password>]
BASE, IF1, IF2, IF3, FP1, IF4, IF5, FP2, IF7, FP3, or FP9 correspond to the fix pack you are migrating from. For example, you must use BASE if you have never installed a fix pack over the InfoSphere MDM Server for PIM, Version 9.1.0.
Restriction: If you are migrating from IF6, then you must use FP1 as the fromversion parameter.
--dbpassword
This is an optional parameter that must be used if you are storing encrypted database password in the InfoSphere MDM Server for PIM server.
Migrating from a Test Fix release: If you are migrating
from a Test Fix version use the table below to determine which Fix Pack the
Test Fix was built on. Use the Fix Pack version in the migration shell
script that corresponds to the Test Fix version you are migrating from:
| Test Fix Version | Version |
|---|---|
| TF1 | V9.1.0 GA |
| TF2 | V9.1.0 GA |
| TF3 | V9.1.0 FP1 |
| TF4 | V9.1.0 FP1 |
| TF5 | V9.1.0 IF3 |
| TF6 | V9.1.0 IF3 |
| TF7 | V9.1.0 IF5 |
$TOP/bin/migration/migrateToInstalledFP.sh --fromversion=BASE
$TOP/bin/migration/migrateToInstalledFP.sh --fromversion=BASE
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:
-------------------------------------- Summary of the migration: -------------------------------------- Migration to InfoSphere MDM Server for PIM 9.1.0 successful. 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 ___________________________________________________________ LOG FILE: $TOP/logs/default/default.log
This message is displayed if the migration failed:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Migration Failed : xxxx !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Please see the file for further details : /home/pimuser/mdmpim910/logs/errfile.log
This message is displayed if the migration of specific modules failed:
-------------------------------------- Summary of the migration: -------------------------------------- Migration of the following modules failed : <module names>
This message is displayed if there is a discrepancy in database tables or indexes.
Generating database verification report... ___________________________________________________________ Changed tables =========================================================== <table names> ___________________________________________________________ ___________________________________________________________ Missing Tables =========================================================== <table names> ___________________________________________________________ ___________________________________________________________ Changed Indexes =========================================================== <index names> ___________________________________________________________ ___________________________________________________________ Missing Indexes =========================================================== <index names> ___________________________________________________________ LOG FILE: $TOP/logs/default/default.log
Review the above mentioned log files 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 migration script continued and completed successfully. Check your cache configuration parameters. No need to re-run the migration script.
Note: It is recommended to run the test_db.sh script to verify the database connection. The test_db.sh script calls the database and confirms that the connection is working properly.
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 Server for PIM.
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 Server for PIM 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 that Web services are deployed to the InfoSphere MDM Server for PIM application. In order to redeploy existing Web services, you need to select the redeploy option when restarting InfoSphere MDM Server for PIM with WebSphere Application Server. Using the redeploy option ensures that Web services are redeployed.
Important: For InfoSphere MDM Server for PIM 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 rmi_status.sh script 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 9.1.0-TF008#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 InfoSphere MDM Server for PIM, 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.
GDS Demand Side customers must run the fix pack migration script, migrationScript.sh with the appropriate parameters and values:
$TOP/src/db/schema/gds/DEMAND-SIDE/WWRE/v6/migrationScript.sh --company_code=<CMP_CODE> --from_release=<FROM_RELEASE>
Note: No GDS migration is required if you are using InfoSphere MDM Server for PIM interim fix 5 or higher version.
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 Server for PIM. 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.