IBM(R) InfoSphere(TM) Master Data Management Server for Product Information Management, Version 9.0.0, Test Fix 10 is now available. This release notes document addresses system requirements, installation, and known problems for this test fix.
Contents
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.
Note: All fixes done in InfoSphere MDM Server for PIM, Version 6.0.0, Fix Pack 9 have not been forward ported to this test fix release. The issues reported in the previous fix pack may occur in this test fix release.
Limitations:
You can review the release notes of previous maintenance releases for
InfoSphere MDM Server for PIM, version 9.0.0, to see what
enhancements or product fixes were included previously:
| Fix Release | Release Notes | Release Date |
|---|---|---|
| fix pack 5 | Release notes for fix pack 5 | 12/20/2010 |
| interim fix 4 | Release notes for interim fix 4 | 11/13/2010 |
| interim fix 3 | Release notes for interim fix 3 | 10/01/2010 |
| fix pack 4 | Release notes for fix pack 4 | 09/21/2010 |
| interim fix 2 | Release notes for interim fix 2 | 09/02/2010 |
| fix pack 3 | Release notes for fix pack 3 | 08/09/2010 |
| interim fix 1 | Release notes for interim fix 1 | 07/20/2010 |
| fix pack 2 | Release notes for fix pack 2 | 07/06/2010 |
| fix pack 1 | Release notes for fix pack 1 | 05/17/2010 |
System requirements
For information about hardware and software compatibility, see the detailed system requirements document at: http://www-01.ibm.com/software/data/infosphere/mdm_server_pim/requirements.html.
Installing test fix 10
Before you install this test fix 10, you must have installed InfoSphere MDM Server for PIM, version 9.0.0.
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.
Remember: This maintenance release is a cumulative patch. You can apply this patch from any previous maintenance release level of Version 9.0.0.
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 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 rollback 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: WPC_HOME/tarFileTemp
cd $TOP chmod -R 755 $TOP
For example, when using the GNU .tar utility, the following command extracts and unzips the .tar file by using an absolute path:
tar zxvf $TOP/9.0.0-WS-MDMPIM-TF010-01_update_from_9000-45.tgz
Important: The InfoSphere MDM Server for PIM files were packed using the GNU tar utility. For best results, use the GNU tar utility to unpack the files.
Remember: If you are migrating from InfoSphere MDM Server for PIM, Version 9.0.0, Fix Pack 3, Interim Fix 2, Fix Pack 4, Interim Fix 3, or Interim Fix 4 you can skip this step and continue with the Step 2.3.
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.
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.
Restart the WebSphere Application Server (server1) and ensure that it is running. You also need to verify that you can log into the server. For more information about the default WebSphere application server, see the administration information in the WebSphere Application Server information center at: http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp.
install_war.sh [ --wsadminUsername=<WAS admin user name> --wsadminPwd=<password for WAS admin user>]
install_war.sh 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: Starting with V9.0.0 fix pack 3, 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. 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 4.
Note: If you want to use the Global Data Synchronization feature on InfoSphere MDM Server for PIM version 9.0.0, you must apply interim fix 3 or later releases to configure the environment for Enabling GDS. Since interim fix 3 release of InfoSphere MDM Server for PIM, version 9.0.0, Global Data Synchronization conforms to Business Message Standard (BMS) 2.7 specifications and previous versions are conformed to BMS 2.3 specifications.
Important: The interim fix 3 or later releases do not provide any migration support to upgrade your Global Data Synchronization data model and data from BMS 2.3 to BMS 2.7 specifications. Therefore, you must create a new company, Load the Global Data Synchronization data model provided in InfoSphere MDM Server for PIM version 9.0.0, Interim Fix 3, and then add the data for this data model into the new company.
To enable the Global Data Synchronization feature of InfoSphere MDM Server for PIM, Version 9.0.0, you must perform the following steps:
Step 4. Updating the configuration files
To successfully use the fixes and enhancements in this maintenance release you must ensure to modify InfoSphere MDM Server for PIM configuration files.
InfoSphere MDM Server for PIM uses the following configuration files:
The following table includes all InfoSphere MDM Server for PIM fix versions, along with their corresponding configuration file changes that you must apply. Depending on the InfoSphere MDM Server for PIM fix version you are migrating from, use this table to determine which configuration file changes you must apply, then view the list of configuration file changes that follow for the specific details.
Remember: If you migrate from version V9.0.0, GA, you must apply the
configuration file changes defined in 1 of the list of configuration file
changes.
| Your fix version | List number of the configuration file change |
|---|---|
| 9.0.0 fix pack 5 | None |
| 9.0.0 interim fix 4 | None |
| 9.0.0 interim fix 3 | 1 |
| 9.0.0 fix pack 4 | 1 |
| 9.0.0 interim fix 2 | 1 |
| 9.0.0 fix pack 3 | 1 |
| 9.0.0 interim fix 1 | 1 |
| 9.0.0 fix pack 2 | 1 |
| 9.0.0 fix pack 1 | 1 |
| 9.0.0 GA | 1 |
List of configuration file changes.
# Parameter to control the behavior of search for non-indexed multi-occurring attributes. # If false, then the search results for non-indexed multi-occurring attributes # can be different from the behavior for indexed multi-occurring attributes in the following scenarios: # - "IS EMPTY" predicate: A non-indexed multi-occurring attribute will only match the "IS EMPTY" predicate if it has # zero occurrences, but an indexed multi-occurring attribute will match it if either # it has zero occurrences, or the attribute value is empty in every occurrence. # - "NOT IS EMPTY" predicate: for both non-indexed and indexed multi-occurring attributes: it matches "NOT IS EMPTY" # if and only if it doesn't match "IS EMPTY". # If true, then search results for non-indexed multi-occurring attributes # will be the same as those for indexed multi-occurring attributes. # Default is false, for backward compatibility. nonindexed_search_like_indexed=false # Controls whether "save-as-draft" functionality is enabled # When save-as-draft is enabled, saves in collaboration areas always save even if there are invalid values # Entries cannot move to the next step if there are validation errors. # Some customers prefer that invalid entries never save. Other situations have large numbers of required attributes # Thus, it makes sense to save frequently even before all required values are entered. # By default save-as-draft is enabled save_as_draft_enabled=true
The "enable_memorymonitor" default value is been set to "false" in common.properties.default , so all new installation with get that default setup.
Section of common.properties in InfoSphere MDM Server for PIM, Version 9.0.0, interim fix 4:
# Enable memory monitoring of session usage enable_memorymonitor=false
The default logging level of "info" for com.ibm.ccd.concurrency.* packages is been set to eliminate the excessive logging of ReleaseLocksForThread in default.log.
<category name="com.ibm.ccd.concurrency" additivity="false"> <priority value="info" /> <appender-ref ref="DEFAULT" /> </category>
No change in the common.properties file in version 9.0.0 fix pack 5.
Step 5. Modifying the database schema
Several changes have been made to the database schema in the test fix release of InfoSphere MDM Server for PIM version 9.0.0; therefore, you must run a migration shell script to migrate to the database schema of InfoSphere MDM Server for PIM, version 9.0.0, test fix 10.
Note: 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(R) privileges / Oracle privileges). If database privileges are modified for any reason, migration script will fail.
Remember: If you are migrating from InfoSphere MDM Server for PIM, Version 9.0.0, Fix pack 5, you are not required to run the migration shell script. You can skip this step and continue with the next step, Step 6. Verifying the installation.
To migrate your database schema:
migrateToInstalledFP.sh --fromversion=BASE|FP1|IF1|FP2|FP3|IF2|FP4|IF3|IF4|FP5
BASE, FP1, IF1, FP2, FP3, IF2, FP4, IF3, IF4, FP5 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.0.0.
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.0.0 GA |
| TF2 | V9.0.0 GA |
| TF3 | V9.0.0 - FP001 |
| TF4 | V9.0.0 - FP001 |
| TF5 | V9.0.0 - FP001 |
| TF6 | V9.0.0 - FP002 |
| TF7 | V9.0.0 - IF004 |
| TF8 | V9.0.0 - IF004 |
| TF9 | V9.0.0 - IF004 |
$TOP/bin/migration/migrateToInstalledFP.sh --fromversion=FP2
$TOP/bin/migration/migrateToInstalledFP.sh --fromversion=IF1
$TOP/bin/migration/migrateToInstalledFP.sh --fromversion=BASE
Add new DB2 temporary table spaces with 32K page size settings for InfoSphere MDM Server for PIM installations that use DB2 as the backend database.
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.0.0 successful.
This message is displayed if the migration failed:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Migration Failed : xxxx !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Please see the file for further details : /home/pimuser/mdmpim900/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>
Review the error.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: modify_sca_table $TOP/logs/errfile.log will have the following content: PK_CHECK ------------- ERROR: SCA_PK 1 record(s) selected.
This is because there are some duplicate records in the tctg_sca_selected_category table. Duplicate rows should be removed for migration script to complete successfully. Run the script $TOP/bin/migration/fix_sca_for_pk.sh without any parameters to remove duplicates.
----------------------------------------------------------- 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.
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 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=admin --svc_name=scheduler
gdsmsg.sh start
This process should only take approximately 30-40 seconds, depending on the speed of your CPU processor.
Note: InfoSphere MDM Server for PIM running on WAS platform preserves Web services already registered with PIM, so re-deployment of Web services is not necessary. But InfoSphere MDM Server for PIM running on Weblogic platform requires re-deployment of Web services at startup time. This re-deployment is accomplished using command options of "redeploy" and "waitforappsvr", as shown in the follow 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 value slightly greater than the required startup time of 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 9.0.0-TF010#01
Known problems
Known problems are documented in the form of individual technotes in the Support knowledge base at InfoSphere MDM Server for PIM Support site. 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.
The following link launches a customized query of the live Support knowledge base for all published technotes for InfoSphere MDM Server for PIM: View all known problems for InfoSphere MDM Server for PIM.
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.