Tasks completed by the physical MDM upgrade script
When you run the
upgrade_physical_mdm madconfig target, it performs a
number of tasks to complete the upgrade of the InfoSphere® MDM Advanced
Edition enterprise application and database.
Before performing each of the following steps in the upgrade, the upgrade utility provides details about the activities that it is about to perform and obtains your consent before proceeding. At any step, you can quit the upgrade and continue the remaining tasks at another time.
upgrade_physical_mdm madconfig target performs the following tasks:
- 1. Checks prerequisites
- Checks the application server status to ensure that the server where InfoSphere MDM V11.6 is installed is running (in a Started state). If it is not started, the upgrade will continue, but some of the following tasks cannot be performed.
- Checks database connectivity. This check also counts the number of virtual and physical MDM
tables available in the database. The upgrade target will fail if connectivity fails or if there are
no tables found in the database.Note: This check requires the ability to run command line utilities from a command prompt. If it does not have appropriate permissions, you will see a warning message.
- 2. Updates the virtual MDM configuration
upgrade_physical_mdmtarget completes configuration changes in the two main locations where InfoSphere MDM stores virtual MDM configuration:
- The configuration directory: <MDM_INSTALL_HOME>/mds
- The runtime directory:
<WAS_PROFILE_HOME>/installedApps/<cell>/MDM-native-<instance_id>/native.warNote: In WebSphere® Application Server cluster installations, the runtime directory exists on each node in the cluster.
- 3. Creates table spaces
When the database is DB2® or Oracle and is non-remote, the target creates the table spaces.Note: When the database is on a remote machine, you must manually run a script to create the table spaces.
- For DB2, go to <MDM_INSTALL_HOME>\database\CoreData\Full\DB2\Standard\ddl and run CreateTS.sql.
- For Oracle, go to <MDM_INSTALL_HOME>\database\CoreData\Full\Oracle\Standard\ddl and run create_schema_ora.sql.
- 4. Bootstraps the data source
This task creates the virtual MDM tables in the database being upgraded.
- 5. Encrypts the database password
When configuration values are first updated, the database password is in plain text in some configuration files. This task encrypts those passwords.
- 6. Merges Event Manager tables into the MDM schema
Depending on the version that you are updating from, this task might be required to merge Event Manager database objects and other related schema into the main schema where InfoSphere MDM are located in the current version.
- 7. Merges Configuration Management tables into the MDM schema
Depending on the version that you are updating from, this task might be required to merge Configuration Management database objects and other related schema into the main schema where InfoSphere MDM are located in the current version.
- 8. Upgrades the physical MDM database
This task upgrades the physical MDM database to the latest version. The target requires you to provide database information.Note: This task uses database command line utilities: db2 for IBM® Db2® and sqlplus for Oracle. Depending on your database type, the location of the corresponding utility must be present in your PATH variable. For Oracle, the environment variable ORACLE_HOME must also be populated with the location where Oracle is installed.The logs generated by this task are stored in <MDM_INSTALL_HOME>/database/Upgrade.Note: If your database contains a large amount of data, it can take a long time to complete this step. Specifically, the script called
populate_grouping_display_name.sqlcan take a long time to complete because of the triggers on the GROUPING table.To work around this issue:
- Drop the triggers from the GROUPING table before running
- Recreate the triggers after the script completes.
- Drop the triggers from the GROUPING table before running
- 9. Modifies the server configuration
The resources in WebSphere Application Server such as the data sources, Java™ authorization, and authentication service entries all point to the database with which InfoSphere MDM was installed. This task completes the following items in WebSphere Application Server:
- Updates data sources.
- Updates database credentials in the Java authorization and authentication service entries.
- When the messaging type is WebSphere Embedded Messaging:
- Updates the schema name in the message store for the Service Integration Bus.
- Drops SIB tables in the database.
- Updates the APPSOFTWARE table to point to the InfoSphere MDM instance.
- When the installation is on a cluster, inserts rows into the APPINSTANCE and CONFIGELEMENT tables for each cluster member.
- Updates matching engine details in the CONFIGELEMENT table.
- 10. Updates database properties in the Web Reports user interface
When the virtual MDM Web Reports user interface is installed, this task updates the database properties in the file <WAS_PROFILE_HOME>/installedApps/<cell>/webreports-<instance_id>.ear/webreports.war/WEB-INF/classes/webreports.properties.
- 11. Replaces database properties in the installation verification files
Certain files related to installation verification hold database details that are used to delete data that is inserted during testing. This task updates these files to point to the upgraded database.
- 12. Verifies the installation
This task runs installation verification testing (IVT) to ensure that the upgraded installation is operational. The results of physical MDM verification tests are stored in <MDM_INSTALL_HOME>/IVT/testCases/xml/response and <MDM_INSTALL_HOME>/IVT/testCases/xml_virtual/response. The results of virtual MDM tests are stored in <MDM_INSTALL_HOME>/mds/log.
- 13. Updates the mdm_install.properties file
The file <MDM_INSTALL_HOME>/properties/mdm_install.properties contains all configuration details for the InfoSphere MDM installation. This task updates the mdm_install.properties file to hold details of the upgraded database. This enables any post-installation configuration to properly interact with the upgraded database.
- 14. Generates log files
After completion of the madconfig target, the log files generated by the update tasks can be found in the following locations: