Release notes for test fix 2

• ftp://ftp.software.ibm.com/software/websphere/mdmpim/fixpacks/6.0.0-FP004/constraint_data_verification_report.sh.

1. Run the following script to produce a report of all the possible violations:

   $TOP/bin/migration/constraint_data_verification_report.sh

2. Review the reported violations in the generated log file, which is available at the following location:

   $TOP/logs/constraint_data_verification_report.out

3. If no violations are found then proceed with the test fix installation.
4. If violations are found then contact IBM Support for assistance and do not proceed with test fix installation.

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/stop/stop_scheduler.sh

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/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

3. For all applications that are deployed in a cluster environment, stop all specified application servers by running the abort_local.sh shell script, which is located in the $TOP/bin/go/ directory:

   Syntax

   abort_local.sh --appservernames=CSV_file

   Parameter

   --appservernames

   CSV_file is the fully qualified file name of the comma-separated values (CSV) file. If you do not specify the --appservernames parameter, the abort_local.sh shell script will continue to abort the default application server that is specified in the init_ccd_vars.sh file.

   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.

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.

1. Create a full backup of all of your InfoSphere MDM Server for PIM directories.
2. Backup the database using native database utilities. Example database utilities include DB2 offline backup and Oracle Recovery Manager (RMAN).

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

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/v6r1/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 --appservername=appserver_Name --svc_name=svc_Name --conf_appsvr_port=appsvr_Port

   Parameters

   --appservername

   appserver_Name is the application server name. The default application server is specified in the init_ccd_vars.sh file.

   --svc_name

   svc_Name is the RMI service name. The default is appsvr_HOSTNAME.

   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.

   --conf_appsvr_port

   appsvr_Port is the port that the application server uses. The default port is the value specified for the appsvr_port parameter in the common.properties file.

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.

New Properties 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

Updated Property description

An additional warning has been added in the configuration file common.properties for the parameter must_save_before_paging_entries. It is recommended that you set this parameter to true. Setting this parameter to false may cause significant performance degradation. The corresponding section in common.properties has changed.

Section of common.properties in InfoSphere MDM Server for PIM, Version 6.0.0, fix pack 1:

# false -> (old behavior) no saving required

Same section of common.properties in InfoSphere MDM Server for PIM, Version 6.0.0, fix pack 2:

# false -> (old behavior) no saving required WARNING: this may introduce a significant
# performance degradation depending on how many items exist in the workflow step.

Updated Property description introduced in version 6.0.0 fix pack 2

Additional dictionary support has been made available. The corresponding section in the configuration file common.properties has changed.

Section of common.properties in InfoSphere MDM Server for PIM, Version 6.0.0, fix pack 1:

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

Same section of common.properties in InfoSphere MDM Server for PIM, Version 6.0.0, fix pack 2:

#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).]
#Other possible values are:: es_ES/fr_FR/it_IT/pt_BR [es_ES for Spanish, fr_FR for French, it_IT for Italian and pt_BR for Portuguese (Brazilian)]
#To enable dictionary for the above locales, required libraries must be present. Refer documentation for more details.
#If this value is not set then en_US will be taken as default dictionary language.

Updated Property description introduced in version 6.0.0 fix pack 4

The description of property entrypreview_refresh_entries_post_run has been updated.

From:

# Controls if the entry edit page is refreshed after an entry preview popup is closed
# true  = will refresh entry edit page when the popup is closed
# false = do not refresh entry edit page

To:

# Controls if the entry edit page is refreshed after an entry preview popup is closed
# true = will refresh entry edit page when the popup is closed only when hard coded
# attribute value is passed for implicit entry object in the script operations for setting entry attributes.
# false = will improve performance of Entry Preview Script and do not refresh entry edit page

Updated Property description introduced in version 6.0.0 fix pack 5

The description of property reset_schedule_when_enabled has been updated.

From:

# Set this property to true if you want a disabled schedule to be reset when it is enabled.
# Resetting would mean that when the schedule is enabled the next running time would be set for the schedule before it is enabled.

To:

# Set this property to true if you want a re-enabled job to be reset to its next scheduled time. 
# If this property set to true, the job's schedule is reset to run at it's scheduled time
 intervals starting with the next one that comes after the current time.
#For example, consider a disabled hourly job originally scheduled to run at 15 min past every hour is now enabled at 20 min past the hour.
#If this property is set to false, the job runs immediately and then the next running time is set to 15 min past next hour. 
#If this property is set to true, the next running time is set to 15 min past next hour and the job will run at 15 min past next hour
reset_schedule_when_enabled=false

1. If you are migrating from version 6.0.0, then run the migration shell script migrateToInstalledFP.sh that is located in the $TOP/bin/migration/ directory.

   Syntax

   migrateToInstalledFP.sh --fromversion=BASE|FP1|IF1|FP2|FP3|FP4

   Parameter

   --fromversion

   BASE, FP1,IF1,FP2 correspond to the fix pack you are migrating from. For example, you must use BASE if you have never installed a test fix over the InfoSphere MDM Server for PIM version 6.0.0.

   Fix pack migration example:

   In this example the migration shell script will migrate from FP2:

   $TOP/bin/migration/migrateToInstalledFP.sh --fromversion=FP2

   Interim fix migration example:

   In this example the migration shell script will migrate from IF1:

   $TOP/bin/migration/migrateToInstalledFP.sh --fromversion=IF1

   Limited availability patch example:

   If you are migrating from a limited availability patch (LA), use the fix pack version that corresponds to the LA version you are migrating from. For example, to migrate from LA1, the migration shell script migrates using the IF1 parameter:

   $TOP/bin/migration/migrateToInstalledFP.sh --fromversion=IF1

1. Locate and open your verify.log file located in the $TOP/logs directory.
2. Click on the respective log file to compare the content of your verify.log file against the log file that corresponds to the fix pack you migrated from.

The shell usage

IndexRegenerator.sh --company=COMPANY_NAME RUN-OPTIONS [TUNING-OPTIONS]

Only one RUN-OPTIONS combination can be used at a time. However, zero or more TUNING-OPTIONS may be used together.

RUN-OPTIONS include

Full Container:

--catalog=CATALOG_NAME
--hierarchy=HIERARCHY_NAME

Container subset:

--items=FULL_PATH_CSV_FILE (2 columns: PK, CATALOG_NAME)
--categories=FULL_PATH_CSV_FILE (2 columns: PK, HIERARCHY_NAME)

Generate PK files for multiple machines (numFiles - default is 1)

--catalog=NAME --items=FULL_PATH_TO_DESIRED_FILE --numFiles=NUMBER_FILES
--hierarchy=NAME --categories=FULL_PATH_TO_DESIRED_FILE --numFiles=NUMBER_FILES

TUNING-OPTIONS include

--nodePaths=FULL_PATH_TO_NODES_SEPARATED_BY_COLONS speed performance by
 specifying node paths, default is all paths. example:
 --nodePaths="SpecName/Node1:SpecName/Node2"

--lockContainer=[YES|NO] speed performance by locking container, 
disadvantage is this locks out other users; default is true

--threads=NUMBER_THREADS speed performance by using more than one thread,
 but be careful enough DB connections exist! default is 1

Example

In this example, the Index Regeneration Capability utility runs the items in the CSV file, $TOP/item-list.csv in the company named test_Co, by using 2 threads.

$TOP/bin/indexRegenerator.sh --company=test_Co --items=$TOP/item-list.csv --threads=2

Parameters containing spaces and special characters must be enclosed in escaped quotes (\").Also special characters should be escaped by back slash (\).

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.

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 start_local.sh shell script to start your application servers:

   The start_local.sh shell script also supports starting multiple application servers from one individual InfoSphere MDM Server for PIM instance.

   Syntax

   start_local.sh --appservername=appserver_Name

   Parameters

   --appservername

   appserver_Name specifies the application server. If it is not specified, the default application server, which is specified in init_ccd_vars.sh file, will be used.

   Multiple application servers can be specified by listing each application server separated by a comma (see the example below).

   Example

   In this example, WebSphere Application Server is the platform and the start_local.sh shell script is started on a host called wpcserver that has wpc_server as the defined value for WAS_APPSERVERNAME.

   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:

   • wpc_server1, with RMI name appsvr1_WPCSERVER.
   • wpc_server2, with RMI name appsvr2_WPCSERVER.

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

• Run the get_ccd_version.sh shell script that is located in the $TOP/bin directory. For example:

  $TOP/bin>./get_ccd_version.sh
  6.0.0-TF2#1

• View the installation version through the InfoSphere MDM Server for PIM user interface. Go to: Help > About Current PageID.