IBM InfoSphere Master Data Management Custom Domain Hub Version 11 Release 0. Upgrade Guide GI

Transkript

1 IBM InfoSphere Master Data Management Custom Domain Hub Version 11 Release 0 Upgrade Guide GI

2

3 IBM InfoSphere Master Data Management Custom Domain Hub Version 11 Release 0 Upgrade Guide GI

4 Note Before using this information and the product that it supports, read the information in Notices and trademarks on page 19. Edition Notice This edition applies to version 11.0 of IBM InfoSphere Master Data Management and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Tables v Figures vii Upgrading InfoSphere MDM Custom Domain Hub What to back up before upgrade Installing Version Upgrading InfoSphere MDM Custom Domain Hub, version Migrating customizations to work with OSGi.. 4 Deploying additions and extensions in OSGi.. 4 Upgrading the existing database for InfoSphere Custom Domain Hub Recreating ILOG rules Updating other components Verifying your upgrade Upgrading your RDM installation Notices and trademarks Index Contacting IBM Copyright IBM Corp iii

6 iv Upgrade Guide

7 Tables 1. IBM resources Providing feedback to IBM Copyright IBM Corp v

8 vi Upgrade Guide

9 Figures 1. Upgrade overview: InfoSphere MDM Custom Domain Hub components in Copyright IBM Corp vii

10 viii Upgrade Guide

11 Upgrading InfoSphere MDM Custom Domain Hub You can upgrade to the current release of InfoSphere MDM Custom Domain Hub (CDH) from Version About this task You cannot currently upgrade to InfoSphere MDM CDH Version 11.0 from a version prior to If you are running a version prior to 10.1, first upgrade to Version 10.1, and then upgrade from 10.1 to See the upgrade instructions included with the 10.1 release. Note: If you do not already have InfoSphere Reference Data Management (RDM) Version 10.1 installed, you must install it before proceeding with your upgrade of InfoSphere MDM CDH. The installation of MDM RDM Version 10.1 creates tables that are required by MDM CDH Version Customers who are running MDM CDH Version 10.1 are entitled to download and install MDM RDM Version 10.1 as well. What to back up before upgrade Before you upgrade, back up the key assets of your InfoSphere MDM Custom Domain Hub environment. Installing Version 11.0 For all upgrades, you must install Version 11.0 in the custom installation deployment type and create a new database. Do not reuse an existing database. Upgrading InfoSphere MDM Custom Domain Hub, version 10.1 on page 2 A set of steps describes the process of upgrading from InfoSphere MDM Custom Domain Hub version 10.1 to version What to back up before upgrade Installing Version 11.0 Before you upgrade, back up the key assets of your InfoSphere MDM Custom Domain Hub environment. Because each installation is different, the documentation doesn't attempt to provide specific steps for backing up. Use your preferred archiving and backup tools. v Database (including the user repository if it is stored in the database) v LDAP repository (if users are stored outside of the installation) v Log files v The configuration settings within the CONFIGELEMENT database table Parent topic: Upgrading InfoSphere MDM Custom Domain Hub For all upgrades, you must install Version 11.0 in the custom installation deployment type and create a new database. Do not reuse an existing database. About this task Note: As part of the upgrade process, you install the Version 11.0 operational server with the new database schema. However, that schema is abandoned when Copyright IBM Corp

12 the operational server is re-pointed to the upgraded Version 10.1 schema. Do not install the Version 11.0 operational server into the 10.1 schema until you have upgraded the 10.1 schema. Procedure 1. Shut down any running instances of the prior release: servers, engine, applications, and so forth. 2. Install Version 11.0 by using the custom installation deployment type. For installation instructions, see the installation documentation. 3. During the installation, create a new database for Version Parent topic: Upgrading InfoSphere MDM Custom Domain Hub, on page 1 Related information: Installing a custom installation Upgrading InfoSphere MDM Custom Domain Hub, version 10.1 A set of steps describes the process of upgrading from InfoSphere MDM Custom Domain Hub version 10.1 to version About this task This section provides instructions for upgrading InfoSphere MDM Custom Domain Hub database and enterprise application. Note: Before you review any other documentation or upgrade the product, read the release notes and the installation instructions for the product. Upgrading your implementation often requires assistance from members of your own organization as well as IBM Services or an IBM consulting partner. Do not upgrade your implementation without first identifying the team and relying on guidance from that team. Release 11.0 represents several large-scale architecture changes to the InfoSphere MDM Custom Domain Hub product. The updated architecture uses an OSGi framework (Open Services Gateway initiative) in which you can install, start, stop, and update component bundles without rebooting the system. The bundles, which are referred to as component bundle archives (CBAs) create an architecture that is service-oriented, enabling the product to work within evolving enterprise service-oriented architectures. By contrast, users of earlier versions had to open, alter, and repackage the application EAR file to deploy the data model and any customizations. In the OSGi framework, users deploy such customizations as independent CBAs that communicate with the application without requiring changes to the application module itself. The new OSGi architecture also means that the embedded ILOG engine is no longer available. Instead the ILOG engine (now called ODM) can be called remotely. You can determine whether you use ILOG rules with your installation of Version 10.1 by running a script provided with Version You may want to recreate those rules in ODM. The existing rules cannot be exported. Note that the management of configuration information changes significantly with release In previous releases, configuration data was maintained within XML 2 Upgrade Guide

13 files embedded within the JAR files whose code the configuration settings controlled. The Configuration Manager read from the XML files and wrote the configuration settings into the CONFIGELEMENT table in the database. With release 11.0, configuration data is stored exclusively in the CONFIGELEMENT table. The XML files are no longer a part of configuration management. InfoSphere MDM Custom Domain Hub version 11.0 also includes security improvements compared to version Upgrade scripts included with the product configure the new installation to use the legacy security mode. To take advantage of the new security mode after upgrade, disable the TrustedClientMode setting within the CONFIGELEMENT table. The following overview diagram conceptually shows the upgrade process for the various components, where the grey boxes show components that are taken offline after the upgrade: 10.1 or earlier 11.0 CDH Install new server, move deployed apps and custom code, and decommission old CDH Operational server in application server Database Upgrade the database Database ILOG Recreate rules ILOG Figure 1. Upgrade overview: InfoSphere MDM Custom Domain Hub components in Migrating customizations to work with OSGi on page 4 Existing customizations must be migrated to use the OSGi framework. 2. Deploying additions and extensions in OSGi on page 4 After you have completed the migration of the customizations to work with OSGi, deploy them to the operational server instance. 3. Upgrading the existing database for InfoSphere Custom Domain Hub on page 4 You upgrade the existing database for IBM InfoSphere Custom Domain Hub instead of using a new CDH database. 4. Recreating ILOG rules on page 15 The new OSGi architecture means that the embedded ILOG engine is no longer available. Instead the ILOG engine (now called ODM) can be called remotely. Recreate existing ILOG rules as ODM rules. 5. Updating other components on page 16 As part of your upgrade to Version 11.0, consider migration to the OSGi framework and the migration of applications. 6. Verifying your upgrade on page 16 You finish the upgrade process by verifying that the 11.0 system is functional. 7. Upgrading your RDM installation on page 16 Now that you have completed your installation of InfoSphere MDM Custom Domain Hub to Version 11.0, you can upgrade your installation of InfoSphere Reference Data Management (RDM) from Version 10.1 to Version Upgrading InfoSphere MDM Custom Domain Hub 3

14 Parent topic: Upgrading InfoSphere MDM Custom Domain Hub, on page 1 Migrating customizations to work with OSGi Existing customizations must be migrated to use the OSGi framework. About this task If your customizations were created within version 10.1 or earlier of the InfoSphere MDM Custom Domain Hub Workbench, use version 11.0 of the Workbench to configure them to work with InfoSphere MDM Custom Domain Hub version For details, see the link at the end of this topic. By contrast, if you created your customizations without using the Workbench, migrate the customizations to OSGi manually. For details, see the link at the end of this topic. Parent topic: Upgrading InfoSphere MDM Custom Domain Hub, version 10.1 on page 2 Next topic: Deploying additions and extensions in OSGi Related concepts: Migrating an existing InfoSphere MDM development project to the OSGi framework Overview of OSGi migration Deploying additions and extensions in OSGi After you have completed the migration of the customizations to work with OSGi, deploy them to the operational server instance. About this task For details, see the link at the end of this topic. Parent topic: Upgrading InfoSphere MDM Custom Domain Hub, version 10.1 on page 2 Previous topic: Migrating customizations to work with OSGi Next topic: Upgrading the existing database for InfoSphere Custom Domain Hub Related concepts: Addition and Extension deployment Upgrading the existing database for InfoSphere Custom Domain Hub You upgrade the existing database for IBM InfoSphere Custom Domain Hub instead of using a new CDH database. Before you begin Before you begin the upgrade, ensure that: v You created a backup copy of your database and any additions or extensions that you created. 4 Upgrade Guide

15 v You installed InfoSphere Custom Domain Hub Version 10.1 or that you upgraded from a previous version to The upgrade is not available for versions of the product before v You read the InfoSphere Custom Domain Hub ReadMe for the hardware and software requirements and other information. 1. Creating and updating database objects To set up the database for Version 11.0 in the Version 10.1 database, run SQL scripts to create and update tables, indexes, foreign keys, and triggers. 2. Updating the data sources on page 14 As part of the upgrade process, edit the user, password, and other database information for the data sources. 3. Updating the J2C authentication data on page 14 As part of the upgrade process, configure the Java 2 Connector (J2C) authentication. 4. Updating the messaging engine on page 15 If your Version 10.1 installation is configured to use WebSphere Embedded Messaging, update the messaging engine as part of the upgrade process. Parent topic: Upgrading InfoSphere MDM Custom Domain Hub, version 10.1 on page 2 Previous topic: Deploying additions and extensions in OSGi on page 4 Next topic: Recreating ILOG rules on page 15 Creating and updating database objects To set up the database for Version 11.0 in the Version 10.1 database, run SQL scripts to create and update tables, indexes, foreign keys, and triggers. Upgrading an existing DB2 database for UNIX or Linux Follow the steps to upgrade the Version 10.1 database to Version 11.0 for DB2 on UNIX or Linux. Upgrading an existing DB2 database for z/os on page 8 Follow the steps to upgrade the Version 10.1 database to Version 11.0 for DB2 on z/os. Upgrading an existing Oracle database on page 11 Follow the steps to upgrade the Version 10.1 database to Version 11.0 for Oracle. Parent topic: Upgrading the existing database for InfoSphere Custom Domain Hub on page 4 Next topic: Updating the data sources on page 14 Upgrading an existing DB2 database for UNIX or Linux: Follow the steps to upgrade the Version 10.1 database to Version 11.0 for DB2 on UNIX or Linux. Before you begin Before you begin, make sure that you read: v The information on gold data deletes and data upgrade scripts in the topic about upgrading the existing database for IBM InfoSphere MDM Server. See the link at the end of this topic. v The notes on table spaces in the topic about manually installing the database in the IBM InfoSphere MDM Custom Domain Hub Installation Guide Upgrading InfoSphere MDM Custom Domain Hub 5

16 Procedure 1. For the scripts in CDH_INSTALL_HOME/Upgrade/CDH/Level-I/DB2/Standard/ddl, change the placeholder tags in all of the scripts: a. Replace <SCHEMA> with a schema name or owner with necessary privileges. This value must be in uppercase. b. Replace <TABLE_SPACE> with a tablespace name that refers to the tablespace where the data is located. c. Replace <INDEX_SPACE> with a tablespace name that refers to the tablespace where the indexes are located. 2. Connect to the database that you are upgrading. 3. From the command line, run the following scripts by using the following command: db2 -tvf script_name -l log_file_name. Note: Run the scripts in the order that is shown here. a. CreateTables.sql creates the tables. b. CreateTables_H.sql creates history tables. c. AlterTables.sql adds new columns, removes obsolete columns, and removes obsolete Foreign Keys. d. CreateFK.sql creates new foreign keys. e. CreateIndexes.sql creates new indexes. f. UpdateSuspect.sql populates the new column added in the suspect table with the value found in the contact table. The column name is access_token_value. 4. Run the following commands to update the triggers. a. If Simple triggers were installed, run the Simple triggers for updates script: db2 -v -td@ -f CreateTriggers_simple.sql -l log_file_name b. If Compound triggers were installed, run the Compound triggers for updates script: db2 -v -td@ -f CreateTriggers_compound.sql -l log_file_name c. If Simple delete triggers were installed, you can run the Simple delete triggers script: db2 -v -td@ -f CreateTriggers_delete_simple.sql -l log_file_name d. If Compound delete triggers were installed, you can run the Compound delete triggers script: db2 -v -td@ -f CreateTriggers_delete_compound.sql -l log_file_name 5. From the command line, run the ImpDataEN.sql script to load the gold data in tables APPSOFTWARE, CONFIGELEMENT, and INQLVLQUERY. Use this command: db2 -tvg script_name -l log_file_name 6. Replace the <SCHEMA> tag in the scripts in the following folders with a schema name or owner, in uppercase. CODE_LANG in the folder name is the language that is currently installed. If you are loading English data only, set CODE_LANG to en. Otherwise, set CODE_LANG to the language code of the language you are loading. Note: If any of the directories are empty, no data was generated and you do not need to run the scripts. v v CDH_INSTALL_HOME/Upgrade/CDH/Level-I/DB2/Standard/ddl/ data_req_code_lang/data CDH_INSTALL_HOME/Upgrade/CDH/Level-I/DB2/Standard/ddl/data_CODE_LANG/ data-industry 6 Upgrade Guide

17 v CDH_INSTALL_HOME/Upgrade/CDH/Level-I/DB2/Standard/ddl/ data_opt_code_lang/data 7. From the command line, to load the common data, English code table data, and configure the table in the language that you selected, run the scripts in the CDH_INSTALL_HOME/Upgrade/CDH/Level-I/DB2/Standard/ddl/ data_req_code_lang/data directory. Use the command: db2 -tvf script_name -l log_file_name. For script_name, use the following scripts: a. The insert.sql script inserts new data b. The update.sql script updates existing table data. c. The delete.sql deletes obsolete table data. 8. From the command line, to load the English industry data, run the scripts in the CDH_INSTALL_HOME/Level-I/Upgrade/MDM/DB2/Standard/ddl/data_en/dataindustry directory. Use the command: db2 -tvf script_name -l log_file_name. For script_name, use the following scripts: a. The insert.sql script inserts new data b. The update.sql script updates existing table data. c. The delete.sql deletes obsolete table data. 9. If you are loading industry data for a language other than English, from the command line, run the scripts in the CDH_INSTALL_HOME/Upgrade/MDM/Level-I/ DB2/Standard/ddl/data_CODE_LANG/data-industry directory. Use the command: db2 -tvf script_name -l log_file_name. For script_name, use the following scripts: a. The insert.sql script inserts new data b. The update.sql script updates existing table data. c. The delete.sql deletes obsolete table data. 10. If you are loading code table data for a language other than English, from the command line, run the scripts in the CDH_INSTALL_HOME/Upgrade/MDM/Level-I/ DB2/Standard/ddl/data_opt_CODE_LANG/data directory. Use the command: db2 -tvf script_name -l log_file_name. For script_name, use the following scripts: a. The insert.sql script inserts new data b. The update.sql script updates existing table data. c. The delete.sql deletes obsolete table data. 11. Repeat the previous two steps for each non-english language that is installed. 12. Note: If you have multiple deployments, before you run the following script, change the SQL clause DEPLOYMENT_ID <> 1000 to DEPLOYMENT_ID = DEPLOYMENT_ID where the DEPLOYMENT_ID is the ID of the instance you want to upgrade. From the command line, run the command: db2 -tvf QryUpdCfgMgrData.sql -l log_file_name. The script populates CONFIGELEMENT values based on previous deployment values. 13. From the command line, run the command: db2 -tvf UpdCfgMgrData.sql -l log_file_name. The script configures default values. The script is generated from the installation directories for version 11.0 for the following configurations in the table CONFIGELEMENT: v /IBM/DWLCommonServices/DataBase/OS v /IBM/DWLCommonServices/DataBase/type v /IBM/DWLCommonServices/DataBase/version Upgrading InfoSphere MDM Custom Domain Hub 7

18 v /IBM/DWLCommonServices/MultiTimeZoneDeployment/defaultTimeZone v /IBM/DWLCommonServices/NLS/system_Default_Data_Locale v /IBM/ThirdPartyAdapters/EAS/dsrcCode v /IBM/ThirdPartyAdapters/EAS/exclusiveSourceSystem 14. From the command line, run the command: db2 -tvf UpdCfgMgrData.sql -l log_file_name. Run QryUpdCfgMgrData.sql to populate Config Manager values based on old deployment values. Before you run this script, replace the deployment ID from the instance that you want to upgrade. Parent topic: Creating and updating database objects on page 5 Related concepts: Manual installation of the physical MDM database Upgrading an existing DB2 database for z/os: Follow the steps to upgrade the Version 10.1 database to Version 11.0 for DB2 on z/os. Procedure 1. To connect to DB2 for OS/390 and z/os server from a DB2 Linux, UNIX, or Windows server, DB2 Connect must be installed on the server you are connecting from. Enterprise editions contain DB2 Connect. To connect to the database, enter the following information: v Host name or IP address v DB2 port (default = 446) v Database name v Subsystem location name v User ID and password 2. On the client server, catalog the database by running the following commands in this order: a. db2 catalog tcpip node YOUR_NODE_NAME remote Z/OS_HOSTNAME/ IP_ADDRESS server Z/OS_PORT b. db2 catalog db YOUR_DB_NAME at node YOUR_NODE_NAME authentication dsc c. db2 catalog dcs db YOUR_DB_NAME as Z/OS_LOCATION_NAME 3. If you are using this user ID to connect to the DB2 subsystem for the first time, rebind the packages for the database by following either of these steps: a. Rebind all the packages by running the command: db2rbind YOUR_DB_NAME all /u USER_NAME /p PASSWORD /r any b. Rebind individual packages by running the command: db2 bind package_name 4. In the CDH_INSTALL_HOME/database/Upgrade/Level-I/DB2/ZOS/ddl directory, change the placeholder tags in the all of the scripts: v Set <DBA_ACCOUNT> to an account with database admin authority. v Set <USER_ACCOUNT> to an account with user authority. v Set <STOGROUP_NAME> to the storage group name. For more information, see the CREATE STOGROUP statement in the create_dbs_zos.sql script. v Set <db_prefix> to three character database prefix that is assigned by the DBA. 8 Upgrade Guide

19 v Set <VCATNAME> to the actual vcatname value. For more information, see the CREATE STOGROUP statement in the create_dbs_zos.sql script. 5. From the CDH_INSTALL_HOME/database/Upgrade/Level-I/DB2/ZOS/ddl directory, run the following scripts in the order they are listed. Use the command db2 -tvf script_name-l LOG_FILE_NAME. a. Run the alter_tables_zos.sql script to add new columns and remove obsolete foreign keys. b. Run the export.sql script to back up APPSOFTWARE data. c. Run the create_tablespaces_zos.sql script to create new table spaces. Running this SQL file requires you to be connected as a SYSADM user. d. Run the create_tables_zos.sql script to create new tables and to drop and re-create APPSOFTWARE and CONFIGELEMENT tables e. Run the create_hist_tables_zos.sql script to create new history tables and to drop and re-create the APPSOFTWARE history table. f. Run the create_fk_zos.sql script to create new foreign keys. g. Run the create_ix_zos.sql script to create new indices. h. Run the import.sql script to reload APPSOFTWARE data. i. Run the UpdateSuspect_zos.sql script to populate new column (access_token_value) added to suspect table with data found in the CONTACT table. j. Run the DropTbsp.sql script to drop unused tablespaces. 6. Run the following commands to upgrade the triggers. v v v If Simple triggers were installed, run the Simple triggers for updates script: db2 -v -td@ -f create_triggers_simple_zos.sql -l log_file_name If Compound triggers were installed, run the Compound triggers for updates script: db2 -v -td@ -f create_triggers_compound_zos.sql -l log_file_name If Simple delete triggers were installed, you can run the Simple delete triggers script: db2 -v -td@ -f create_delete_triggers_simple_zos.sql -l log_file_name v If Compound delete triggers were installed, you can run the Compound delete triggers script: db2 -v -td@ -f create_delete_triggers_compound_zos.sql -l log_file_name 7. Run the ImpDataEN_zos.sql script to load the gold data in tables the tables APPSOFTWARE, CONFIGELEMENT, and INQLVLQUERY. 8. Update the APPSOFTWARE table to set the value of NAME to com.ibm.mdm.hub.server-app_name for the new deployment. For example, UPDATE APPSOFTWARE SET NAME=' com.ibm.mdm.hub.server-appname', LAST_UPDATE_DT=current_timestamp WHERE DEPLOYMENT_ID=1000; 9. Replace the <SCHEMA> tag in the scripts in the following folders with a schema name or owner in uppercase. In the folder name, CODE_LANG is the language that is currently installed: Note: If any of the directories are empty, no data was generated and you do not need to run the scripts. v v CDH_INSTALL_HOME/database/Upgrade/Level-I/DB2/ZOS/ddl/ data_req_code_lang/data CDH_INSTALL_HOME/database/Upgrade/Level-I/DB2/ZOS/ddl/data_CODE_LANG/ data-industry Upgrading InfoSphere MDM Custom Domain Hub 9

20 v CDH_INSTALL_HOME/database/Upgrade/Level-I/DB2/ZOS/ddl/ data_opt_code_lang/data If you are loading English data only, set CODE_LANG to en. Otherwise, set CODE_LANG to the language code of the language you are loading. 10. To load the common data from the command line, run the scripts in the CDH_INSTALL_HOME/database/Upgrade/Level-I/DB2/ZOS/ddl/data_req_en/data directory. Use the command: db2 -tvf script_name-l log_file_name: a. The insert.sql script inserts new data. b. The update.sql script updates existing table data. c. The delete.sql script deletes obsolete table data. 11. To load the English industry data from the command line, run the scripts in the CDH_INSTALL_HOME/database/Upgrade/Level-I/DB2/ZOS/ddl/data_en/dataindustry directory. Use the command: db2 -tvf script_name -l log_file_name: a. The insert.sql script inserts new data. b. The update.sql script updates existing table data. c. The delete.sql script deletes obsolete table data. 12. If you are loading industry data for a language other than English, from the command line, run the scripts in the CDH_INSTALL_HOME/database/Upgrade/ Level-I/DB2/ZOS/ddl/data_CODE_LANG/data-industry directory. Use the command: db2 -tvf script_name -l log_file_name a. The insert.sql script inserts new data. b. The update.sql script updates existing table data. c. The delete.sql script deletes obsolete table data. 13. If you are loading code table data for a language other than English, from the command line, run the scripts in the CDH_INSTALL_HOME/database/Upgrade/ Level-I/DB2/ZOS/ddl/data_opt_CODE_LANG/data directory. Use the command: db2 -tvf script_name -l log_file_name: a. The insert.sql script inserts new data. b. The update.sql script updates existing table data. c. The delete.sql script deletes obsolete table data. 14. Repeat the previous two steps for each non-english language that is installed. 15. Note: If you have multiple deployments, before you run the following script, change the SQL clause DEPLOYMENT_ID <> 1000 to DEPLOYMENT_ID = DEPLOYMENT_ID where the DEPLOYMENT_ID is the ID of the instance you want to upgrade. From the command line, run the command: db2 -tvf QryUpdCfgMgrData_zos.sql -l log_file_name. The script populates CONFIGELEMENT values based on previous deployment values. 16. Create and run the following SQL script: UpdCfgMgrData.sql: SET CURRENT SQLID=UPGRAD01; UPDATE CONFIGELEMENT SET VALUE_DEFAULT = Z/OS, LAST_UPDATE_DT = CURRENT TIMESTAMP, LAST_UPDATE_USER= INSTALLATION WHERE NAME = /IBM/DWLCommonServices/DataBase/OS ; UPDATE CONFIGELEMENT SET VALUE_DEFAULT = DB2, LAST_UPDATE_DT = CURRENT TIMESTAMP, 10 Upgrade Guide

21 LAST_UPDATE_USER= INSTALLATION WHERE NAME = /IBM/DWLCommonServices/DataBase/type ; UPDATE CONFIGELEMENT SET VALUE_DEFAULT = , LAST_UPDATE_DT = CURRENT TIMESTAMP, LAST_UPDATE_USER= INSTALLATION WHERE NAME = /IBM/DWLCommonServices/DataBase/version ; UPDATE CONFIGELEMENT SET VALUE_DEFAULT = EST5EDT, LAST_UPDATE_DT = CURRENT TIMESTAMP, LAST_UPDATE_USER= INSTALLATION WHERE NAME = /IBM/DWLCommonServices/MultiTimeZoneDeployment/defaultTimeZone ; UPDATE CONFIGELEMENT SET VALUE_DEFAULT = true, LAST_UPDATE_DT = CURRENT TIMESTAMP, LAST_UPDATE_USER= INSTALLATION WHERE NAME = /IBM/DWLCommonServices/MultiTimeZoneDeployment/enabled ; UPDATE CONFIGELEMENT SET VALUE_DEFAULT = en, LAST_UPDATE_DT = CURRENT TIMESTAMP, LAST_UPDATE_USER= INSTALLATION WHERE NAME = /IBM/DWLCommonServices/NLS/system_Default_Data_Locale ; UPDATE CONFIGELEMENT SET VALUE_DEFAULT =, LAST_UPDATE_DT = CURRENT TIMESTAMP, LAST_UPDATE_USER= INSTALLATION WHERE NAME = /IBM/ThirdPartyAdapters/EAS/dsrcCode ; UPDATE CONFIGELEMENT SET VALUE_DEFAULT =, LAST_UPDATE_DT = CURRENT TIMESTAMP, LAST_UPDATE_USER= INSTALLATION WHERE NAME = /IBM/ThirdPartyAdapters/EAS/exclusiveSourceSystem ; COMMIT; connect reset; 17. Run the command: db2 -tvf UpdCfgMgrData.sql -l log_file_name Parent topic: Creating and updating database objects on page 5 Related concepts: Manual installation of the physical MDM database Upgrading an existing Oracle database: Follow the steps to upgrade the Version 10.1 database to Version 11.0 for Oracle. Before you begin Read the content for the link at the end of this topic about manual installation of the database. For Oracle, the use of table spaces for data, indexes and LOBs, such as CLOBs or XML, to improve database performance is supported. Look for the following placeholders in the scripts: <TABLE_SPACE>, <INDEX_SPACE>, and <LONG_SPACE>. Procedure 1. For the scripts in the CDH_INSTALL_HOME/database/Upgrade/Level-I/Oracle/ Standard/ddl directory, change the placeholder tags in the scripts: Upgrading InfoSphere MDM Custom Domain Hub 11

22 v v v Change <TABLE_SPACE> to a tablespace name that refers to the tablespace where the data is located. Change <INDEX_SPACE> to a tablespace name that refers to the tablespace where the index data are located. Change <TABLE_SPPMD> to a tablespace name that refers to the tablespace where the EME data is located. v Change <TABLE_SPPMI> to a tablespace name that refers to the tablespace where the EME index data is located. 2. From the command line, run the scripts by using the command: sqlplus >> <LOG_FILE_NAME> Note: Review the log files after you run each script. v Run the create_tables_ora.sql script to create new tables. v Run the create_hist_tables_ora.sql script to create new history tables. v Run the alter_tables_ora.sql script to add new columns, remove obsolete foreign keys, and remove unused columns from APPSOFTWARE table. v Run the create_fk_ora.sql script to create foreign keys. v Run the create_ix_ora.sql script to create new indexes. v Run the UpdateSuspect_ora.sql script to populate the new added column (access_token_value) to the suspect table with the value found in CONTACT table. 3. In the ImpClobData.script, replace the placeholder tags: v Replace the placeholder <SCHEMA> with the schema name or object owner with necessary privileges. This value must be in uppercase. v Replace the placeholder <NEWPASSWORD> with the schema password. v Replace the placeholder <DBNAME> with the name of the database you want to connect to. 4. Ensure that execute permissions are granted to the ImpClobData.script script. 5. Run the ImpClobData.script script from the command line. The script loads the updated inqlvlquery records. 6. Run the following scripts to update the triggers. v If Simple triggers were installed, run the Simple triggers for updates script: sqlplus <LOG_FILE_NAME> v If Compound triggers were installed, run the Compound triggers for updates script: sqlplus <LOG_FILE_NAME> v If Simple delete triggers were installed, you can run the Simple delete triggers script: sqlplus <LOG_FILE_NAME> v If Compound delete triggers were installed, you can run the Compound delete triggers script: sqlplus <LOG_FILE_NAME> 7. Replace the placeholder <SCHEMA> in the scripts in the following folders with a schema name or owner. Ensure that the name or owner is in uppercase. CODE_LANG in the folder name is the language that is currently installed. Note: If any of the directories are empty, no data was generated and you do not need to run the scripts. 12 Upgrade Guide

23 v v CDH_INSTALL_HOME/database/Upgrade/Level-I/Oracle/Standard/ddl/ data_req_code_lang/data CDH_INSTALL_HOME/Upgrade/MDM/Level-I/Oracle/Standard/ddl/ data_code_lang/data-industry v CDH_INSTALL_HOME/Upgrade/MDM/Level-I/Oracle/Standard/ddl/ data_opt_code_lang/data 8. Ensure that the ImpReqDataCfgMgr.script script has execute permissions. 9. Within the ImpReqDataCfgMgr.script script, change values for the parameters: v v v Replace the placeholder <SCHEMA> with the schema name or object owner with necessary privileges. This value must be in uppercase. Replace the placeholder <NEWPASSWORD> with the schema password. Replace the placeholder <DBNAME> with the name of the database you want to connect to. 10. Within the data/appsoftware_d.del file, replace the placeholder <APP_NAME> with the name of your Version 11.0 Application Name. Obtain the value of <APP_NAME> from the APPSOFTWARE table of the Version 11.0 database. An example of the data/appsoftware_d.del file follows: 1000,"com.ibm.cdh.hub.server-<APP_NAME>", "11.0.0"," ", "unknown" 11. Run the ImpReqDataCfgMgr.script script from the command line. The script loads the updated CONFIGELEMENT records. 12. To load the common data, to load the English code table data, and to configure the table in the language that you selected, run the following script in the CDH_INSTALL_HOME/database/Upgrade/Level-I/Oracle/Standard/ddl/ data_req_code_lang/data directory from the command line. Use the command: sqlplus >> <log_file_name> a. The insert.sql script inserts new data. b. The update.sql script updates existing table data. c. The delete.sql script deletes obsolete table data. If you are loading English data only, set CODE_LANG to en. Otherwise, set CODE_LANG to the language code of the language you are loading. 13. To load the English industry data, run the scripts in the CDH_INSTALL_HOME/ database/upgrade/level-i/oracle/standard/ddl/data_en/data-industry directory from the command line. Use the command: sqlplus >> <log_file_name> a. The insert.sql script inserts new data. b. The update.sql script updates existing table data. c. The delete.sql script deletes obsolete table data. 14. If you are loading data for a language other than English, run the scripts in the CDH_INSTALL_HOME/database/Upgrade/Level-I/Oracle/Standard/ddl/ data_<code_lang>/data-industry directory from the command line: a. The insert.sql script inserts new data. b. The update.sql script updates existing table data. c. The delete.sql script deletes obsolete table data. 15. If you are loading code table data for a language other than English, run the scripts in the CDH_INSTALL_HOME/database/Upgrade/Level-I/Oracle/Standard/ ddl/data_opt_code_lang/data directory from the command line: sqlplus >> <log_file_name> Upgrading InfoSphere MDM Custom Domain Hub 13

24 v The insert.sql script inserts new data. v The update.sql script updates existing table data. v The delete.sql script deletes obsolete table data. 16. Repeat the previous two steps for each non-english language that is installed. 17. Copy the UpdCfgMgrData.sql script from the CDH_INSTALL_HOME/database/ CoreData/Full/DB2/Standard/ddl directory into the CDH_INSTALL_HOME/ database/upgrade/level-i/oracle/standard/ddl/ directory. 18. Note: If you have multiple deployments, before you run the following script, change the SQL clause DEPLOYMENT_ID <> 1000 to DEPLOYMENT_ID = DEPLOYMENT_ID where the DEPLOYMENT_ID is the ID of the instance you want to upgrade. Run the following command: sqlplus >> <log_file_name> The QryUpdCfgMgrData_ora.sql script populates the Configuration Manager values based on previous deployment values. 19. Run the following command: sqlplus >> <log_file_name> Parent topic: Creating and updating database objects on page 5 Related concepts: Manual installation of the physical MDM database Updating the data sources As part of the upgrade process, edit the user, password, and other database information for the data sources. Procedure 1. Log in to the WebSphere Application Server Administration Console. 2. Navigate to Resources > JDBC > Data sources. 3. Select the data source DWLConfig. 4. Edit the database information under Common and required data source properties to point to the upgraded database schema. 5. Click on Custom properties and edit the user and password of the upgraded database schema. 6. Repeat steps 4 and 5 for the data source DWLCustomer. 7. Click on Customer properties to edit the database information of the upgraded database. Parent topic: Upgrading the existing database for InfoSphere Custom Domain Hub on page 4 Previous topic: Creating and updating database objects on page 5 Next topic: Updating the J2C authentication data Updating the J2C authentication data As part of the upgrade process, configure the Java 2 Connector (J2C) authentication. Procedure 1. Log on to the WebSphere Application Server Administration Console. 2. Navigate to Security > Global Security. 14 Upgrade Guide

25 3. Expand Java Authentication and Authorization Services > J2C authentication data. 4. Edit the user ID and password of the upgraded database schema for the alias: v application-name/db-user v application-name/db-user-config Parent topic: Upgrading the existing database for InfoSphere Custom Domain Hub on page 4 Previous topic: Updating the data sources on page 14 Next topic: Updating the messaging engine Updating the messaging engine If your Version 10.1 installation is configured to use WebSphere Embedded Messaging, update the messaging engine as part of the upgrade process. Procedure 1. Log on to the WebSphere Application Server Administration Console. 2. Navigate to Service integration > Buses > MDM.SIB.application-name > Message Engine > node-name.application-name-mdm.sib.application-name > Message Store. 3. Edit the Schema name field. 4. Stop the application server. 5. Drop all of the messaging engine tables. The messaging engine table names all begin with SIB: v SIB000 v SIB001 v SIB002 v SIBCLASSMAP v SIBKEYS v SIBLISTING v SIBOWNER v SIBOWNER0 v SIBXACTS 6. Restart the application server. Parent topic: Upgrading the existing database for InfoSphere Custom Domain Hub on page 4 Previous topic: Updating the J2C authentication data on page 14 Recreating ILOG rules The new OSGi architecture means that the embedded ILOG engine is no longer available. Instead the ILOG engine (now called ODM) can be called remotely. Recreate existing ILOG rules as ODM rules. About this task For information about creating ODM rules, follow the link at the end of this topic. Procedure To determine whether you use ILOG rules with version 10.1, run the following scripts. 1. For any ILOG-based Behavioral Extensions rules: Upgrading InfoSphere MDM Custom Domain Hub 15

26 SELECT * FROM EXTENSIONSET WHERE (JAVA_CLASS_NAME IS NULL OR JAVA_CLASS_NAME = ) AND (RULE_SET_NAME IS NOT NULL OR RULE_SET_NAME!= ) 2. For any ILOG-based External Rules: SELECT * FROM RULEENGINEIMPL WHERE EXT_RULE_IMPL_ID IN (SELECT EXT_RULE_IMPL_ID FROM EXTRULEIMPLEM WHERE EXT_RULE_TP_CODE= R ) Parent topic: Upgrading InfoSphere MDM Custom Domain Hub, version 10.1 on page 2 Previous topic: Upgrading the existing database for InfoSphere Custom Domain Hub on page 4 Next topic: Updating other components Related information: IBM Operational Decision Manager Version Information Center Updating other components As part of your upgrade to Version 11.0, consider migration to the OSGi framework and the migration of applications. About this task For detailed information about upgrading to use the new OSGi framework, see the links to more information at the end of this topic. Parent topic: Upgrading InfoSphere MDM Custom Domain Hub, version 10.1 on page 2 Previous topic: Recreating ILOG rules on page 15 Next topic: Verifying your upgrade Related concepts: Migrating an existing InfoSphere MDM development project to the OSGi framework Understanding migration of an application Overview of OSGi migration Verifying your upgrade You finish the upgrade process by verifying that the 11.0 system is functional. Procedure 1. Verify that the 11.0 operational server can access the upgraded database. 2. Ensure that your Version 10.1 customizations are available in the new Version 11.0 environment. Parent topic: Upgrading InfoSphere MDM Custom Domain Hub, version 10.1 on page 2 Previous topic: Updating other components Next topic: Upgrading your RDM installation Upgrading your RDM installation Now that you have completed your installation of InfoSphere MDM Custom Domain Hub to Version 11.0, you can upgrade your installation of InfoSphere Reference Data Management (RDM) from Version 10.1 to Version Upgrade Guide

27 About this task See the upgrade instructions for InfoSphere MDM RDM, which are currently delivered as a PDF file available from the same location where you obtained the PDF file for upgrading InfoSphere MDM CDH. Parent topic: Upgrading InfoSphere MDM Custom Domain Hub, version 10.1 on page 2 Previous topic: Verifying your upgrade on page 16 Upgrading InfoSphere MDM Custom Domain Hub 17

28 18 Upgrade Guide

29 Notices and trademarks This information was developed for products and services offered in the U.S.A. Notices This information was developed for products and services offered in the U.S.A. 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 U.S.A. For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd , Shimotsuruma, Yamato-shi Kanagawa 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. Copyright IBM Corp

30 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 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 document 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. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information is for planning purposes only. The information herein is subject to change before the products described become available. 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: 20 Upgrade Guide

31 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. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample 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. Privacy Policy Considerations IBM Software products, including software as a service solutions, ("Software Offerings") may use cookies or other technologies to collect product usage information, to help improve the end user experience, to tailor interactions with the end user or for other purposes. In many cases no personally identifiable information is collected by the Software Offerings. Some of our Software Offerings can help enable you to collect personally identifiable information. If this Software Offering uses cookies to collect personally identifiable information, specific information about this offering s use of cookies is set forth below. Depending upon the configurations deployed, this Software Offering may use session and persistent cookies that collect each user s name, user name, password, profile name, or other personally identifiable information for purposes of session management, authentication, enhanced user usability, single sign-on configuration, or web page identification that the user tried to load prior to login. These cookies can be disabled, but disabling them will also likely eliminate the functionality they enable. If the configurations deployed for this Software Offering provide you as customer the ability to collect personally identifiable information from end users via cookies and other technologies, you should seek your own legal advice about any laws applicable to such data collection, including any requirements for notice and consent. For more information about the use of various technologies, including cookies, for these purposes, see IBM s Privacy Policy at and IBM s Online Privacy Statement at the section entitled "Cookies, Web Beacons and Other Technologies" and the "IBM Software Products and Software-as-a-Service Privacy Statement" at product-privacy. Notices and trademarks 21

32 Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at The following terms are trademarks or registered trademarks of other companies: Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. ITIL is a registered trademark, and a registered community trademark of The Minister for the Cabinet Office, and is registered in the U.S. Patent and Trademark Office. UNIX is a registered trademark of The Open Group in the United States and other countries. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries. 22 Upgrade Guide