Release notes for test fix 1


IBM(R) InfoSphere(TM) Master Data Management Server for Product Information Management Version 9.1.0, Test Fix 1 is now available. This release notes document addresses compatibility, system requirements, installation, and known problems.

Contents

Description

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:

Product fixes discovered by users

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

Compatibility issues with earlier versions

InfoSphere MDM Server for PIM, Version 9.1.0 no longer supports the following versions of software:

For a complete list of the supported hardware and software for Version 9.1.0, Test Fix 1, see the System requirements section.

A set of user interface functions were introduced in InfoSphere MDM Server for PIM Version 9.0.0 providing more intuitive, user-friendly and modern look-and-feel alternative to the functions (also known as "classic UI functions") which we delivered in the earlier versions of the product. At some appropriate time in the future as determined by IBM the classic functions will be removed from the product.

The "classic UI functions" that will be removed under this coverage include but are not limited to the following.

In InfoSphere MDM Server for PIM Version 6.0.0 a new home page, worklist user interface and simplified single edit user interface were introduced. With the introduction of a newer set of user interface functions in InfoSphere MDM Server for PIM Version 9.0.0 , the usefulness of the simplified single edit user interface quickly diminishes. At some appropriate time in the future as determined by IBM the simplified single edit user interface will be removed from the product. The home page and the worklist user interface will not be removed.

System requirements

For information about hardware and software compatibility, see the detailed system requirements document at: http://www.ibm.com/software/data/infosphere/mdm_server_pim/requirements.html.

Installing test fix 1

Before you install this test fix, you must have installed InfoSphere MDM Server for PIM, Version 9.1.0. In particular, make sure that you have applied all configuration changes. For example, any schema changes and common.properties updates as documented in the Requirements section of those release notes.

Important:

The steps for installing this test fix include:

  1. Preparing to install the test fix
  2. Installing the test fix
  3. Verifying the installation

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 Server for PIM 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 Server for PIM 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 Server for PIM instance. It might take several attempts to stop all Java processes, but continue stopping Java processes until they are all stopped.

  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 Server for PIM 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, common.properties, 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 InfoSphere MDM Server for PIM .tar file to the user or temporary directory.

      For example: WPC_HOME/tarFileTemp

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

      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.1.0-WS-MDMPIM-TF001-04_update_from_9100-43.tar

      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.

  2. Run the application server script.

    The application server shell script, install_war.sh, installs InfoSphere MDM Server for PIM into the WebSphere application server.

    1. Ensure that the default WebSphere application server (server1) is installed and 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.
    2. Run the application server shell script, install_war.sh, with optional parameters, which is located in the $TOP/bin/websphere/ directory:

      Syntax 
      install_war.sh 

      install_war.sh will install the WAR file for each app server defined in the [services] section in env_settings.ini.

  3. Optional: If you are using the Script Workbench for InfoSphere MDM Server for PIM, 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 Server for PIM Users guide for installation instructions.

Step 3. Verifying the installation

Every time that you install a fix pack, verify that the installation was successful. To verify the installation of this test fix, complete these steps:

  1. Start InfoSphere MDM Server for PIM:

    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.

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

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

      • For the WebLogic Server platform, run: 
        start_local.sh

        You are not required to use the --redeploy=yes command for WebLogic Server.

    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 

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

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

    Run the $TOP/bin/go/rmi_status.sh script and verify that the following services have started correctly:

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

Known problems

Known problems are documented in the form of individual technotes in the Support knowledge base at http://www.ibm.com/support/entry/portal/Overview/Software/Information_Management/InfoSphere_Master_Data_Management_Server_for_Product_Information_Management. As problems are discovered and resolved, the IBM Support team updates the knowledge base. By searching the knowledge base, you can quickly find workarounds or solutions to problems.

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

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