Release notes for test fix 1


IBM(R) InfoSphere(R) Master Data Management Collaboration Server Version 10.1.0, Test Fix 1 is now available. This release notes document addresses system requirements, installation, and known problems.

Contents

Description of this test fix

InfoSphere MDM Collaboration Server provides a highly scalable, enterprise Product Information Management (PIM) solution. InfoSphere MDM Collaboration Server is the middleware that establishes a single, integrated, consistent view of products and services information inside and outside of an enterprise.

This test fix addresses the following enhancements and fixes, and includes all the fixes and enhancements delivered in IBM(R) InfoSphere(TM) Master Data Management Server for Product Information Management, Version 9.1.0, test fix 6 and prior patches:

CAUTION: It is strongly recommended that you apply the test fix only to a test system. Test fixes do not undergo official IBM testing.

Product enhancements and issues discovered internally

The following defect was discovered by the development team and was included in this test fix. If you want to learn more about this defect, you can use the internal defect number for reference when speaking to someone from IBM Software Support:

Attention: You must recompile the solution Java(TM) code. Refer to Step 2. Installing the test fix section for specific instructions.

System requirements

For information about hardware and software compatibility, see the detailed system requirements document at: http://www-01.ibm.com/support/docview.wss?uid=swg27035486

Installing test fix 1

  1. You must delete the existing xbean jar. This file bears the name xbean-1.0.4.jar and is located in the $TOP/jars directory. In this test fix the xbean.jar file is upgraded to a newer version. Because your environment already has an older version of this file, inclusion of the newer version of the file will lead to a conflict of jar files in the classpath.
  2. You must have installed InfoSphere MDM Collaboration Server, Version 10.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.
  3. 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:

  1. Preparing to install the test fix
  2. Installing the test fix
  3. Updating the configuration files
  4. Enabling the Global Data Synchronization feature of InfoSphere MDM Collaboration Server (Optional)
  5. Modifying the database schema
  6. Verifying the installation
  7. Enabling GDS migration
  8. Enabling Advanced Catalog Management (ACM) Asset

Step 1. Preparing to install the test fix

Before you install the test fix, make sure to complete these steps:

  1. Stop the InfoSphere MDM Collaboration Server application on the local server.
    1. Check the scheduler to make sure that no critical jobs are running or need to complete. If the queue is clear, stop the scheduler manually by running the following shell script:

      $TOP/bin/go/svc_control.sh --action=stop --svc_name=scheduler

    2. Check the workflow engine to make sure no critical workflow events are running or need to complete by running the following shell script:

      $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

    3. For all applications that are deployed in a cluster environment, stop all remaining InfoSphere MDM Collaboration Server services:

      Syntax 
      $TOP/bin/go/abort_local.sh 

      Running the abort_local.sh shell script does not affect any of the other JVM services.

    4. Make sure that all processes have stopped using the ps command. Stop any other Java or RMI registry processes that remain after shutting down the InfoSphere MDM Collaboration Server instance. It might take several attempts to stop all Java processes, but continue stopping Java processes until they are all stopped.
    5. Optional: If you have the GDS feature enabled for a previous version of InfoSphere(tm) MDM Server for PIM, version 9.1.x, make sure to abort the GDS message listener. Abort the GDS message listener by running the following scripts in the given sequence:

      Syntax 
      $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 

  2. Backup your system.

    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.

    1. Create a full backup of all of your InfoSphere MDM Collaboration Server directories, especially the $TOP/etc/default and $TOP/bin/conf directories where the configuration files, common.properties, admin_properties.xml, and env_settings.ini are stored.

      Important: For this test fix, there are no modification done in the configuration files, admin_properties.xml, and env_settings.ini.

    2. Create a full backup of your database.

Step 2. Installing the test fix

To install this test fix, you must perform the following steps:

  1. To extract and update any new installation files into the current working directory, perform the following steps:
    1. Copy the 10.1.0-WS-MDMCS-TF001.tgz file to the user or temporary directory.

      For example: $TOP/10.1.0-WS-MDMCS-TF001.tgz

    2. Change the directory to $TOP (or the current working directory) then verify that the correct permissions exist for unpacking the .tgz file by running the following commands: 
      cd $TOP
chmod -R 755 $TOP
    3. Unpack the .tgz file.

      For example, when using the GNU tar utility, the following command extracts and unzips the .tgz file by using an absolute path: 

      gtar zxvf $TOP/10.1.0-WS-MDMCS-TF001.tgz

      Important: The InfoSphere MDM Collaboration Server files were packed using the GNU tar utility. Use the GNU tar utility to unpack the archive file for best results, especially on computers running the AIX operating system. If you use the AIX version of the tar command, you might not be able to unpack correctly all files in the archive. One indication of incorrect unpacking of the archive is the presence of the @LongLink file in the directory in which you unpack the archive.

  2. Perform the following updates to the $TOP/bin/conf/env_settings.ini file.
    1. If you choose to encrypt the database password, add the encrypt_password parameter to the [db] section of the env_settings.ini file, and set it to yes. Remove the password parameter from the [db] section of the env_settings.ini file. This ensures that the database password is not present anywhere in the text format. It will be present only in the encrypted format in the db.xml file. If you choose to leave the database password in plain format, add the encrypt_password parameter to the [db] section of the env_settings.ini file, and set it to no. Keep the password parameter in the [db] section of the env_settings.ini file as in earlier versions of InfoSphere MDM Collaboration Server.
      • Oracle WebLogic Server users: Cut the username and password properties in the [appserver.weblogic103] section and paste them to the [appserver] section.
      • WebSphere(R) Application Server users: If the admin_security property in the [appserver.websphere70] section of your env_setting.ini file in use is set to true, add the username and password properties to the [appserver] section and populate these two properties with the WebSphere Application Server admin user information.
  3. Remove the following properties from the common.properties file:

    Note: These properties are now being stored in a separate file.

  4. Run $TOP/setup.sh
  5. Run $TOP/bin/configureEnv.sh

    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).

  6. Verify that the db.xml file is created in the $TOP/etc/default directory. Refer to the Updating the configuration files section for more information about the db.xml file.
  7. Recompile the solution Java code using the latest product .jar files included in this patch.
  8. Redeploy InfoSphere MDM Collaboration Server to the application server.

  9. Optional: If you are using the Script Workbench for InfoSphere MDM Collaboration Server, when you install this test fix, the Script Workbench communication .jsp and .jar files are removed from your server configuration. To regain communication you must reinstall the docstore_tooling.jsp and docstore_tooling.jar files. See the Script Workbench for InfoSphere MDM Collaboration Server Users guide for installation instructions.

Step 3. Updating the configuration files

To successfully use the fixes and enhancements in this maintenance release you must modify InfoSphere MDM Collaboration Server configuration files.

InfoSphere MDM Collaboration Server uses the following configuration files:

common.properties
During system startup, the common.properties file is used to read in all system-level parameters and is located in the $TOP/etc/default directory.

admin_properties.xml
The admin_properties.xml file is used by the administrative utilities to configure clusters of the application and is located in the $TOP/etc/default directory.

env_settings.ini
The env_settings.ini file contains installation-specific parameters and is located in the <install dir>/bin/conf directory.

db.xml
The db.xml file contains all database related parameters and is located in the $TOP/etc/default directory. If you set the encrypt_password parameter to yes in the env_settings.ini file, the db_password_encrypted element will contain the encrypted database password. If you set the encrypt_password parameter to no, the db_password_plain element will contain the database password in plain text format. The elements in this file replace the following properties that were earlier stored in the common.properties file.

Note: You must remove these properties from the common.properties file.

flow-config.xml
The flow-config.xml file is the core configuration file for the UI framework. It must be present in the class path of your web application and is located in the directory PRODUCT_INSTALLED_DIR/etc/default. The flow-config.xml file is overwritten when you apply a patch. Therefore, if you have modified this configuration file for customization, you must make a backup copy of the file before you apply a patch. After you apply a patch, you need to manually copy the customization changes from the backup copy to the new copy of flow-config.xml. New properties introduced in thecommon.properties file for version 10.1.0 test fix 1:

List of configuration file changes

New properties introduced in the common.properties file for version 10.1.0 fix pack 1:

  1. rich_search_indexed_only 
    # set to true for filtering out non indexed attributes from being selected for rich search.
# This will not affect existing search template(s) and saved search.
rich_search_indexed_only=true
  2. num_xml_processor_background_threads 
    # Controls the number of background processor threads per parent worker thread to convert data into XML for saves
# Can be set higher if operations like imports are cpu bound and there are more processors available.
# See log.xml.default for changing the log level of the EntryXmlProcessor class to debug to see if more threads may help speed up imports.
# Default value is 2
num_xml_processor_background_threads=2

Step 4. Enabling the Global Data Synchronization feature of InfoSphere MDM Collaboration Server (Optional)

Complete this step only if you plan to use the Global Data Synchronization feature of InfoSphere MDM Collaboration Server; otherwise, proceed to Step 5.

To enable the Global Data Synchronization feature of InfoSphere MDM Collaboration Server, Version 10.1.0, you must perform the following steps:

  1. Configure the Global Data Synchronization parameters in order for InfoSphere MDM Collaboration Server to be able to exchange product data with a data pool. Follow the instructions in the Configuring the GDS feature topic in the information center.
  2. Load the Global Data Synchronization data model to enable InfoSphere MDM Collaboration Server to interact with data pool. Follow the instructions in the Load the Global Data Synchronization data model topic in the information center.

Step 5. Modifying the database schema

Follow the instructions for modifying the database schema to InfoSphere MDM Collaboration Server V10.1.0, test fix 1 depending on your current InfoSphere MDM Collaboration Server version as mentioned below:

Current InfoSphere MDM Collaboration Server version Instructions for modifying the database schema to InfoSphere MDM Collaboration Server V10.1.0, Test Fix 1
InfoSphere MDM Collaboration Server, Version 10.1.0 GA No actions necessary, please continue with Step 6. Verifying the Installation.
Any prior release of InfoSphere MDM Server for PIM or InfoSphere MDM Collaboration Server Follow the instructions in the Migrating from prior versions documentation.

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:

  1. Start InfoSphere MDM Collaboration Server:

    The shell script, start_local.sh, located in the $TOP/bin/go directory, starts all the services that you need to run InfoSphere MDM Collaboration Server.

    1. Run the start_local.sh shell script:
      • For the WebSphere Application Server platform, run:
        start_local.sh
      • For the WebLogic Server platform, run:
        start_local.sh --redeploy

        The --redeploy command ensures that all Web services are properly re-deployed.

    2. Run the svc_control.sh shell script to start the individual services.

      The svc_control.sh supports starting multiple services from the same command:

      Syntax 
      svc_control.sh --action=start --svc_name=<service name>[--svc_name=<service name>] 

      Example 
      svc_control.sh --action=start --svc_name=appsvr --svc_name=admin --svc_name=scheduler 
    3. Optional: Run the gdsmsg.sh shell script, which is located in the $TOP/bin/ directory to start the GDS messaging service:

      Syntax 
      gdsmsg.sh start

    This process should only take approximately 30-40 seconds, depending on the speed of your CPU processor.

    Important: For InfoSphere MDM Collaboration Server running WebSphere Application Server, as part of a new installation or an upgrade to an existing installation, use the redeploy option when running the start_local.sh script to ensure the Web services are deployed to the InfoSphere MDM Collaboration Server application. In order to redeploy existing Web services, you need to select the redeploy option when restarting InfoSphere MDM Collaboration Server with WebSphere Application Server. When you use the redeploy option it ensures that the Web services are redeployed.

    Important: For InfoSphere MDM Collaboration Server running on the Oracle WebLogic server, use the redeploy option when you run the start_local.sh script at startup. You need to use the redeploy and waitforappsvr command options as shown in the following syntax: 

    start_local.sh --redeploy --waitforappsvr=<number of seconds>

    or 

    svc_control.sh --action=start --svc_name=admin --svc_name=scheduler [ --svc_name=appsvr --redeploy
	 [--waitforappsvr=<number of seconds>] ]

    - where the <number of seconds> is the number of seconds (positive integer) that the deployment command will wait for the appsvr services to become ready to initiate the re-deployment of Web services. The default value of this option is 5 seconds.

    The waitforappsvr option must be used with the redeploy option. When the waitforappsvr option is omitted in a command with the "redeploy" option, the default value of waitforappsvr takes effect.

    Users are advised to supply values slightly greater than the required startup time of the appsvr service, which can be monitored using the rm_status.sh command as shown in step 6.2 below. Too low a value for the waitforappsvr option can result in errors with stack dump on screen or log files.

    The --svc_name=appsvr option in the svc_control.sh command must be accompanied by the redeploy and optionally the waitforappsvr command options.

  2. Verify that all InfoSphere MDM Collaboration Server JVM services have started.

    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:

  3. Verify the InfoSphere MDM Collaboration Server installation by reviewing what the installed InfoSphere MDM Collaboration Server version displays as:

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 Collaboration Server, 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.

Step 8. Enabling Advanced Catalog Management (ACM) Asset

To install this asset, you must perform the following steps:

  1. Extract and update any new installation files into the current working directory. Perform the following steps:
    1. Copy the 10.1.0-WS-MDMCS-ACM-TF001.zip file to the user or temporary directory. For example, the $TOP directory.
    2. Extract files from the compressed file. There are three files in the compressed file:
      • README
      • acm.zip
      • acm.src.zip
  2. Follow the instruction in the README file and refer to WebSphere Commerce Server to install and configure the asset.

Known problems

Known problems are documented in the Support knowledge base at http://www-947.ibm.com/support/entry/portal/overview/software/information_management/infosphere_master_data_management_collaboration_server. As problems are discovered and resolved, the IBM Support team updates the knowledge base. By searching the knowledge base, you can quickly find workarounds or solutions to problems.

You can search for and display a list of all published technotes for InfoSphere MDM Collaboration Server. For information about how to search all published technotes, see Searching knowledge bases

You can search for keywords within this complete list of technotes.

Contacting IBM Support

Before contacting IBM Support, your company must have an active IBM software maintenance contract, and you must be authorized to submit problems to IBM. For information about the types of maintenance contracts available, see "Enhanced Support" in the Software Support Handbook at: techsupport.services.ibm.com/guides/services.html

After you define the problem gather background and diagnostic information, and determine the severity of the problem, you can submit your problem to IBM Support in one of the following ways:

If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Software IBM Support provides a workaround that you can implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the IBM Support web site daily, so that other users who experience the same problem can benefit from the same resolution.

Notices

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing 2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:


IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA 95141-1003
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:

(C) (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. (C) Copyright IBM Corp. _enter the year or years_. All rights reserved.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Trademarks

IBM, the IBM logo, and ibm.com(R) are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol ((R) or (TM)), indicating trademarks that were owned by IBM at the time this information was published. A complete and current list of IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml.

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc., in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.