IBM(R) InfoSphere(TM) Master Data Management Server for Product Information Management, Version 6.0.0, Fix Pack 1 is now available. This release notes document addresses system requirements, installation, and known problems for this fix pack.
Contents
Description of this fix pack
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.
This fix pack addresses the following enhancements and fixes:
The following fixes were included in this fix pack as a result of an authorized program analysis report (APAR). You can search for and view existing APARs here: www-306.ibm.com/software/data/masterdata/product-info/support/. You can also review the associated PMR (if one is identified) for the fix, with the Electronic IBM Service Request tool Web site: www-306.ibm.com/software/support/probsub.html.
The following fixes were included in this fix pack as a result of an internal defect that was discovered by the development team. If you want to learn more about one of these fixes, you can use the internal defect number for reference when speaking to someone from IBM Software Support:
Version 5.3.2 fix pack 10 and 11, and interim fix 8, 9, 10, and 11 have been merged with version 6.0.0 fix pack 1. You can review the release notes of previous fix packs to see the enhancements or product fixes that were included.
Restrictions:
The table below provides you with the links to previous fix packs that have
been merged with version 6.0.0 fix pack 1:
| Fix Release | Release Date |
|---|---|
| interim fix 11 | 11/19/2008 |
| interim fix 10 | 10/28/2008 |
| fix pack 11 | 10/08/2008 |
| interim fix 9 | 08/19/2008 |
| fix pack 10 | 07/28/2008 |
| interim fix 8 | 06/02/2008 |
System requirements
For information about hardware and software compatibility, see the detailed system requirements document at: www-306.ibm.com/software/data/masterdata/product-info/requirements/.
Installing fix pack 1
Before you install this fix pack, you must have installed InfoSphere MDM Server for PIM, version 6.0.0.
Important: Apply the fix pack to a test system prior to applying it to your production system to identify any possible issues.
The steps for installing this fix pack include:
Step 1. Preparing to install the fix pack
Before you install the fix pack, make sure to complete these steps:
$TOP/bin/go/stop/stop_scheduler.sh
$TOP/bin/go/workflow_status.sh
If no events are running, shut down the workflow engine manually by running the following shell script:
$TOP/bin/go/stop/stop_workflowengine.sh
abort_local.sh --appservernames=CSV_file
Running the abort_local.sh shell script does not affect any of the other JVM services.
The installation will overwrite your current files with updated versions from the fix pack. If any issues occur when installing the fix pack, you can use this backup copy to rollback the installation.
Step 2. Installing the fix pack
To install this fix pack, 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/6.0.0-WS-MDMPIM-WS61_ORA-FP001-16_update_from_6000-88.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.
Run the application server script.
The application server shell script, install_war.sh, installs InfoSphere MDM Server for PIM into the WebSphere application server.
install_war.sh --appservername=appserver_Name --svc_name=svc_Name --conf_appsvr_port=appsvr_Port
The RMI service name should contain a number to indicate which application server it is and a host name. For example, appsvr2_hostName is named after the second application server in the cluster.
This optimizer script uses the catalog tables from a database to obtain information about the database, including the amount of data within the database and other characteristics. The optimizer script then uses this information to determine how to access the data. If your database statistics are not available, the optimizer might choose an inefficient access plan based on the default statistics, which is inaccurate.
You should use the analyze_schema.sh shell script to collect your current statistics from within the tables and indexes, especially if significant update activity has occurred since the last time you ran the analyze_schema.sh shell script.
To run the analyze_schema.sh shell script in DB2, refer to the InfoSphere MDM Server for PIM technote: Analyzing WebSphere Product Center schema and collecting statistics in DB2 located at: http://www-1.ibm.com/support/docview.wss?uid=swg21205939.
Important: Run the analyze_schema.sh shell script on your InfoSphere MDM Server for PIM databases at least once a week or when there has been at least a twenty percent increase or change in data on the database.
Tip: Oracle version 10g and 11g has automatic statistics gathering job enabled by default.
Step 3. Updating the property files
To successfully use the fixes and enhancements in this fix pack you must modify InfoSphere MDM Server for PIM configuration files.
InfoSphere MDM Server for PIM uses the following configuration files:
The following properties have been introduced in version 6.0.0 fix pack 1.
Add the following properties and description by copying and pasting the text to the end of your common.properties file:
#Default dictionary language for Spell Checker #possible values:: en_US/en_CA/en_GB [en_US for English(United States), #en_CA for English(Canada) and en_GB for English(United Kingdom).] #If this value is not set then en_US will be taken as default dictionary language. spell_default_locale= # set to true in order to activate filtering of non indexed attributes from # the rich search page default view. # This will not affect custom templates. rich_search_default_view_indexed_only=false # Controls whether to use the new attribute filter for improved performance # true = use the new filter # false = use the old filter medit_use_new_header_atr_filter=true # set to true to activate prefetch of lock information for items in the multiedit page. enable_medit_lock_prefetch=true
modify the description of property "must_save_before_paging_entries" from # false -> (old behavior) no saving required to # false -> (old behavior) no saving required WARNING: this may introduce a significant # performance degradation depending on how many items exist in the workflow step.
Step 4. Modifying the database schema
Several changes have been made to the database schema in the fix pack 1 release of InfoSphere MDM Server for PIM version 6.0.0; therefore, you must run a migration shell script to migrate to the database schema of InfoSphere MDM Server for PIM, version 6.0.0, Fix Pack 1.
To migrate your database schema:
migrate53211to6001.sh
migrateToInstalledFP.sh
While running the migration script, if you get any warning or error messages in the console, ignore them except the ones given below:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Migration Failed : xxxx !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Please see the file for further details : /home/mdmpimuser/mdmpim6001/logs/errfile.log
Then you must correct the error and run the same command again.
You might get an error stating that there is a failure in ACG migration, which is indicated by a message in the console such as the one below:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Migration Failed : ACG !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Please see the file for further details : /home/mdmpimuser/mdmpim6001/logs/errfile.log
If this error occurs, use a backed-up database copy to migrate again, after correcting the error. This is because a failure of ACG migration might lead to an inconsistent state of the database where users might have incorrect access privileges. Specify the original backed-up database copy from fix pack 1, and run the migration shell script that you ran in step 2.
The following log files include the expected log output for a successful
migration based on both the fix pack you migrated from and the database you
are using.
| Fix pack | The expected log file output for Oracle databases | The expected log file output for DB2 databases |
|---|---|---|
| version 6.0.0 | verifyFP1_Oracle.log | verifyFP1_DB2.log |
| version 5.3.2 fix pack 11 | verifyFP11toFP1Oracle.log | verifyFP11toFP1DB2.log |
For catalogs in a company:
For hierarchies in a company:
For items in a company:
In the example command provided below, the Index Regeneration Capability utility runs the items in the CSV file, $TOP/item-list.csv in the company named test_Co, using the utf8 encoding.
$TOP/bin/indexRegenerator.sh --items=$TOP/item-list.csv --company=test_Co --encoding=utf8
Parameters that contain spaces and special characters must be enclosed between quote characters (") and special characters alone, should be escaped with a backslash (\).
If you specify more than one file, the file number is placed before the file extension. Like items.csv becomes items-1.csv, items-2.csv, etc.
Restriction: Catalog and hierarchy arguments cannot be combined. For example, --catalog and --hierarchy cannot be used together, nor can --catalog and --categories. When arguments --catalog and --items are used together, only PK files are generated and no index regeneration is performed.
Step 5. Verifying the installation
Every time that you install a fix pack, verify that the installation was successful. To verify the installation of this fix pack, 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.
start_local.sh --redeploy=yes
The --redeploy=yes command ensures that all Web services are properly re-deployed.
start_local.sh
You are not required to use the --redeploy=yes command for WebLogic Server.
The start_local.sh shell script also supports starting multiple application servers from one individual InfoSphere MDM Server for PIM instance.
start_local.sh --appservername=appserver_Name
Multiple application servers can be specified by listing each application server separated by a comma (see the example below).
If these two application servers were specified during installation:
$TOP/bin/websphere/install_war.sh --svc_name=appsvr1_WPCSERVER --appservername=wpc_server1 --conf_appsvr_port=9188 $TOP/bin/websphere/install_war.sh --svc_name=appsvr2_WPCSERVER --appservername=wpc_server2 --conf_appsvr_port=9388
Then you can start both application servers by executing the following shell script:
$TOP/bin/go/start_local.sh --appservernames=wpc_server1,wpc_server2
The resulting application servers will start:
This process should only take approximately 30-40 seconds, depending on the speed of your CPU processor.
Run the $TOP/bin/go/rmi_status.sh script and verify that the following services have started correctly:
$TOP/bin>./get_ccd_version.sh 6.0.0-FP001#16
Known problems
Known problems are documented in the form of individual technotes in the Support knowledge base at http://www-01.ibm.com/software/data/infosphere/support/mdm_server_pim/. 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(R) and Windows(R) are trademarks of Microsoft Corporation in the United States, other countries, or both.
Java(TM) 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.