WebSphere Product Center, Version 5.3.2, Fix Pack 9 is now available. This release notes document addresses system requirements, installation, and known problems for this fix pack.
WebSphere Product Center provides a highly scalable, enterprise Product Information Management (PIM) solution. WebSphere Product Center is the middleware that establishes a single, integrated, consistent view of products and services information inside and outside of an enterprise.
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 ESR Web site: www-306.ibm.com/software/support/probsub.html.
The following enhancements were included in this fix pack as a result of a Problem Management Report (PMR). You can search for and view existing PMRs with the Electronic Service Request (ESR) 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 Support:
| Fix Release | Release Date |
|---|---|
| Fix Pack 8 | 03/28/2008 |
| Interim Fix 7 | 02/29/2008 |
| Interim Fix 6 | 02/18/2008 |
| Fix Pack 7 | 02/11/2008 |
| Fix Pack 6 | 01/09/2008 |
| Fix Pack 5 | 12/12/2007 |
| Interim Fix 5 | 11/09/2007 |
| Fix Pack 4 | 11/08/2007 |
| Interim Fix 4 | 10/29/2007 |
| Interim Fix 3 | 10/22/2007 |
| Fix Pack 3 | 10/05/2007 |
| Fix Pack 2 | 09/12/2007 |
| Fix Pack 1 | 07/26/2007 |
| Interim Fix 2 | 05/25/2007 |
| Interim Fix 1 | 04/12/2007 |
For information about hardware and software compatibility, see the detailed system requirements document at: www-306.ibm.com/software/data/masterdata/product-info/requirements/.
Before you install this fix pack, you must have installed WebSphere Product Center, version 5.3.2, or any previous fix packs for version 5.3.2. 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.
Step 1. Preparing to install the fix pack
$TOP/bin/go/stop/stop_scheduler.sh
$TOP/bin/go/workflow_status.sh
Then, 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 occurs when installing the Fix Pack you can use this backup copy to rollback the installation.
Step 2. Installing the fix pack
For example: {HOME_OF_WPC}/tarFileTemp
cd $TOP chmod –R 755 $TOP
tar zxvf $TOP/5.3.2-WS-WPC-WS6_ORA-FP003-08_update_from_5320-53.tgz
The application server shell script, install_war.sh, installs WebSphere Product Center into the WebSphere® Application Server server.
>>-install_war.sh--+-------------------------------------+------> '- --appservername--=--appserver_Name-' >--+--------------------------+---------------------------------> '- --svc_name--=--svc_Name-' >--+-------------------------------------+--------------------->< '- --conf_appsvr_port--=--appsvr_Port-'
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.
Step 3. Updating the property files
To successfully use the fixes and enhancements in this fix pack you must modify WebSphere Product Center configuration files.
The following table includes all WebSphere Product Center fix versions, both Fix Packs and Interim Fixes, along with their corresponding configuration file changes that you need to apply. Depending on the WebSphere Product Center fix version you are migrating from, use the table to determine which configuration file changes you need to apply, then view the list that follows for the specific details:
| Your fix version | List number of the configuration file change |
|---|---|
| 5.3.2-FP008 | 7 |
| 5.3.2-IF007 | 7 |
| 5.3.2-FP007 | 7 |
| 5.3.2-IF006 | 7 |
| 5.3.2-FP006 | 7 |
| 5.3.2-FP005 | 6, 7 |
| 5.3.2-FP004 | 5, 6, 7 |
| 5.3.2-IF005 | 4, 5, 6, 7 |
| 5.3.2-IF004 | 4, 5, 6, 7 |
| 5.3.2-IF003 | 4, 5, 6, 7 |
| 5.3.2-FP003 | 4, 5, 6, 7 |
| 5.3.2-FP002 | 4, 5, 6, 7 |
| 5.3.2-FP001 | 3, 4, 5, 6, 7 |
| 5.3.2-IF002 | 2, 3, 4, 5, 6, 7 |
| 5.3.2-IF001 | 1, 2, 3, 4, 5, 6, 7 |
Add the following property and description by copying and pasting the text to the end of your common.properties file:
# The following are needed for MQ version 6. They can be # overridden by specifying a username and password when # calling the jmsGetQueueConnection script operation mq_username= mq_password=
Add the following properties and descriptions by copying and pasting the text to the end of your common.properties file:
# Can multiple ctg files (for image/binary attributes) exist # with the same name? If false, will store files in ctg_files # within the supplier base. If true, will store files in # subdirectories within ctg_files with timestamps for names. allow_multiple_files_with_same_name=false # This property decides whether the Web Services would be # session enabled or not. A true value will enable sessions # for Web Services. A Web Service needs to be saved after # changing the value of this property. enable_webservice_session=true # This property decides the session timeout period for the # Web Services session. The value is in seconds. webservice_session_timeout=300 # Key combination to trigger shortcuts. If more than one is # set to true, then all set to true will be needed to trigger # the shortcut. Default is CTRL-ALT, but if languages that # use ALT GR for some characters, such as Polish, are in use # then we advise that this should be changed, e.g. to always # have the same functionality (except CTRL-SHIFT or ALT-SHIFT, # since in Microsoft Windows, CTRL-ALT and ALT GR when used # with DEL).We strongly advise against setting all of CTRL, ALT # and SHIFT to false, since this would cause shortcuts to be # triggered by normaltyping! It is recommended that at least # two of these be set to true. use_ctrl_in_shortcuts=true use_alt_in_shortcuts=true use_shift_in_shortcuts=false # The width of the popup window for Lookup table entry input # widget. This will be set to default value which is 800 pixels # if the width is either too high (greater than 1680) or too # low (less than 800). The allowed value can be any integer # between 800 and 1680. lookup_table_entry_input_popup_width=900 # The height of the popup window for Lookup table entry input # widget. The allowed value can be any integer between 400 to # 1050. This will be set to default value which is 400 pixels # if the height is either too high (greater than 1050) or too # low (less than 400). lookup_table_entry_input_popup_height=500
Replace the max_script_cache_timeout=60 property with:
max_script_cache_timeout_in_seconds=60
Remove the following properties and description by deleting the from your common.properties file:
# Rich search: maximum number of items allowed to be searched # on in real time. If the number of items returned by the # initial query estimate is greater than this number, the # search will be scheduled as a background search. max_number_items_for_realtime_search=1000
Add the following description by copying and pasting the text above the category_item_count_disabled property in your common.properties file:
# Set to true in order to disable the UI from producing a count # of the items mapped under categories. With this property # enabled the categories would not be expandable to show child # items. However search and rich search will still work. This # count shows up in different pages of the UI such as left nav, # basic selection, link attribute popup, etc. Set to false to # enable this count feature. category_item_count_disabled=false
Add the following property and description by copying and pasting the text to the end of your common.properties file:
# Spec Cache flushing # =================== # The standard behavior when saving a spec is to flush the # entire spec cache. For installations with a large number # of pre-cached specs, this can cause a reduction in system # performance. Setting the parameter below to true will # prevent the cache being flushed. inhibit_spec_cache_flush_on_save=false
Add the following property and description by copying and pasting the text to the end of your common.properties file:
# Can users modify their own usernames via the My Profile # page? Default value is true. If set to false, then # Administrators and users whose roles allow them to modify # other users will be able to modify their own usernames # anyway. allow_users_to_modify_own_username=true
Add the following property and description by copying and pasting the text to the end of your common.properties file:
# Controls if the entry edit page is refreshed after an # entry preview popup is closed: # true = refresh entry edit page when popup is closed # false = do not refresh entry edit page entrypreview_refresh_entries_post_run=false
Add the following property and description by copying and pasting the text to the end of your common.properties file:
# 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
Step 4. Modifying the database schema
>>-migrateToInstalledFP.sh-- --fromversion--=--+-BASE-+-------->< +-IF1--+ +-IF2--+ +-FP1--+ +-FP2--+ +-FP3--+ +-IF3--+ +-IF4--+ +-IF5--+ +-FP4--+ +-FP5--+ +-FP6--+ +-IF6--+ +-FP7--+ +-IF7--+ '-FP8--'
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.
Example: If you migrate from IF6, then you compare your $TOP/logs/verify.log file to the FP6_IF6_FP7.log file.
| Fix Pack | The expected log file output for Oracle databases | The expected log file output for DB2 databases |
|---|---|---|
| BASE, IF1, IF2 | BASE_IF1_IF2.log | BASE_IF1_IF2.log |
| FP1, FP2, FP3, IF3, IF4, IF5, FP4, FP5 | FP1_FP2_FP3_IF3_IF4_IF5_FP4_FP5.log | FP1_FP2_FP3_IF3_IF4_IF5_FP4_FP5.log |
| FP6, IF6, FP7 | FP6_IF6_FP7.log | FP6_IF6_FP7.log |
| IF7 | IF7.log | IF7.log |
| FP8 | Migration not required | FP8.log |
>>-indexRegenerator.sh-- --items--=--CSV_file-------------------> >-- --company--=--companyName--[-- --encoding--=--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 (\).
A description of both the Index Regeneration Capability and Rich Search for Co-Occurrence of Multi-Occurrence Value facilities are described in the Release notes of the WebSphere Product Center Information Center under New Features at http://publib.boulder.ibm.com/infocenter/wpc/v5r3m2/topic/com.ibm.wpc.doc/rn/rn_2.0.html.
Step 5. Verifying the installation
The shell script, start_local.sh, located in the $TOP/bin/go/ directory, starts all the services that you need to run WebSphere Product Center.
>>-start_local.sh-- --redeploy--=--yes-------------------------><
The parameter and value, --redeploy=yes, ensures that all Web Services are properly re-deployed.
>>-start_local.sh----------------------------------------------><
You are not required to use the --redeploy=yes parameter and value for WebLogic.
The start_local.sh shell script also supports starting multiple application servers from one individual WebSphere Product Center instance.
>>-start_local.sh--+-------------------------------------+----->< '- --appservername--=--appserver_Name-'
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
This process should only take approximately 30-40 seconds, depending on the speed of your CPU processor.
$TOP/bin>./get_ccd_version.sh 5.3.2-FP009#10
Installation verification should be done every time you upgrade or refresh your existingWebSphere Product Center installation.
Known problems are documented in the form of individual technotes in the Support knowledge base at http://www-306.ibm.com/software/data/masterdata/product-info/support/. 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 WebSphere Product Center: View all known problems for WebSphere Product Center
You can search for keywords within this complete list of technotes.
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
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.
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 Director
of Licensing
IBM Corporation
North Castle Drive
Armonk,
NY 10504-1785
U.S.A.
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
Silicon Valley Lab
Building 090/H-410
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:
© (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © 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.
IBM, the IBM logo, and ibm.com 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 (® or ™), 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.