Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Multidomain MDM 10.5
  • All Products

Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Resource Kit Upgrade (In-place Upgrade)
  10. Post-Upgrade Tasks
  11. Search Configuration Upgrade
  12. Hierarchies Upgrade
  13. ActiveVOS Post-Installation Tasks for the Application Server
  14. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  15. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  16. Appendix A: Troubleshooting the Upgrade Process
  17. Appendix B: Frequently Asked Questions
  18. Appendix C: Processing Existing ActiveVOS Tasks
  19. Appendix D: Configuring Metadata Caching

Upgrading from Version 10.1, 10.2, 10.3, or 10.4

Upgrading from Version 10.1, 10.2, 10.3, or 10.4

Back Next

Prepare the Environment

Prepare the Environment

Perform the tasks for the upgrade process you chose.

Clean Upgrade

Perform the following tasks for a clean upgrade:
Task
Description
Verify minimum system requirements
Verify that the machines meet the hardware and software requirements for the
MDM Hub
 installation. The hardware requirements are dependent on the data, processing volumes, and business rules.
To install the MDM Hub, the machines must meet the following minimum requirements:
  • Disk space. 4.9 GB
  • RAM for the development environment. 4 GB
To verify the run-time physical memory requirements of the
MDM Hub
 components, use the following formula: 
Total run-time memory requirement for MDM Hub components = JDK JVM max heap size of the application server + operating system native heap size
Install Java Development Kit (JDK)
Install a supported version of the JDK on the machine on which you want to install the
MDM Hub
. The JDK is not bundled with the
MDM Hub
 installers.
In a JBoss environment, you must install the version of Azul Zulu JDK that Informatica provides. Contact Informatica Shipping to download Azul Zulu JDK.
Use the same Java version on the application server machines and on the machines on which you want to launch the Hub Console.
Install Visual C++ Redistributable for Visual Studio 2019 on Windows only
On Windows systems,
Multidomain MDM
 requires Visual C++ Redistributable for Visual Studio 2019 to support the name search feature and the matching feature.
Set environment variables
Set the environment variables for the
MDM Hub
 installation.
To use the correct JDK, set the following environment variables to point to the JDK directory:
  • JAVA_HOME. Required
  • PATH. Required
To set the correct locale behavior for Oracle, set the NLS_LANG environment variable for client application environments such as the Oracle loader, and the
MDM Hub
 components.
Specify the NLS_LANG parameter in the following format: 
NLS_LANG = <language>_<territory>.<character set>
To store and search for records that contain Chinese, Japanese, Korean, or accented characters, set the character set to UTF-8.
For more information about NLS_LANG settings, see the Oracle documentation.
Set the operating system locale
Set the same operating system locale for the Hub Server, the MDM Hub Master Database, Operational Reference Store, and the Hub Console.
Set up the X Window System on UNIX
If you want to run the installer in graphical mode on UNIX, set up an X Window System. An X Window System is a graphics display server. For more information about setting up an X Window System, see the documentation for your operating system.
Disable access to the root welcome page for your application server
To improve security, disable access to the root welcome page for your application server. For instructions, see the documentation for your application server.
Disable insecure TLS cipher suites
To improve security, in the Java runtime environment that is used with
Multidomain MDM
, disable insecure TLS cipher suites.
  1. Open the following file:
    ../jdk<version>/jre/lib//security/java.security
  2. Find the property
    jdk.tls.disabledAlgorithms
     and update the value to include the following list of insecure cipher suites:
    jdk.tls.disabledAlgorithms = SSLv3, RC4, MD5withRSA, DH keySize < 1024, EC keySize < 224, DES40_CBC, RC4_40, 3DES_EDE_CBC, EDH-RSA-DES-CBC3-SHA, ECDHE-RSA-DES-CBC3-SHA, DES-CBC3-SHA
For more information about the property, see the documentation for your JDK.
Perform the following additional tasks for a clean upgrade:
Task
Details
Validate the metadata
Ensure the Operational Reference Stores (ORS) do not have any validation errors. If you upgrade the Hub Store when an ORS contains metadata that is not valid, the upgrade might generate unexpected results. Use the Repository Manager in the Hub Console to validate metadata. Resolve any validation issues and then validate the metadata again to confirm that you have resolved the validation issues.
Save a copy of the final validation results in the
upgradedoc
 upgrade documentation folder.
Use the Repository Manager tool in the MDM Hub Console to validate and then save the validation results.
Update persistent ID implementation
If you use persistent IDs, contact Informatica Global Customer Support. You must update the persistent ID implementation to be compatible with the upgraded version of
Multidomain MDM
.

In-place Upgrade

Perform the following tasks for an in-place upgrade:
Task
Details
Update the MDM environment to meet system requirements
You might need to update the operating system, application server, JDK, and database server. For system requirements, see the Product Availability Matrix for this version of
Multidomain MDM
 (MDM) on Informatica Network: https://network.informatica.com/community/informatica-network/product-availability-matrices/overview%20.
In a JBoss environment, you must install the version of Azul Zulu JDK that Informatica provides. Contact Informatica Shipping to download Azul Zulu JDK.
Update the machines that run MDM to be compliant with the current MDM system requirements.
Install Visual C++ Redistributable for Visual Studio 2019 on Windows only
On Windows systems,
Multidomain MDM
 requires Visual C++ Redistributable for Visual Studio 2019 to support the name search feature and the matching feature.
Validate the metadata
Ensure the Operational Reference Stores (ORS) do not have any validation errors. If you upgrade the Hub Store when an ORS contains metadata that is not valid, the upgrade might generate unexpected results. Use the Repository Manager in the Hub Console to validate metadata. Resolve any validation issues and then validate the metadata again to confirm that you have resolved the validation issues.
Save a copy of the final validation results in the
upgradedoc
 upgrade documentation folder.
Use the Repository Manager tool in the MDM Hub Console to validate and then save the validation results.
Update persistent ID implementation
If you use persistent IDs, contact Informatica Global Customer Support. You must update the persistent ID implementation to be compatible with the upgraded version of
Multidomain MDM
.
Back up the implementation
Back up your current implementation to retain your customizations and to allow you to restore the environment. If you encounter issues during the upgrade, you can restore your environment from the backup.
Back Up the Schema
Perform a full back up of the schema. You cannot roll back schema changes that the upgrade process makes. If you encounter upgrade issues, you can restore the schema from the backup. To back up your schema, see the documentation for the database.
Back up the Hub Server and Process Server installed directories
Before you install the Hub Server and Process Servers, back up the Hub Server and Process Server installation folders in your environment.
Back Up Your
Data Director
 Applications
For information about exporting
Data Director
 applications with subject areas, see the
Multidomain MDM Data Director Implementation Guide
.
Register or Back Up Customizations
Customizations that you register in the Hub Console such as custom queries, custom functions, and user exits are maintaining during the upgrade process.
Back up the latest source code of customizations that you do not register in the Hub Console. Unregistered customizations might be unavailable after you upgrade.
Back Up Customized Cleanse Engine Configuration Files
Back up any cleanse engine configuration files that you have customized.
Configure the JAVA_HOME environment variable
JBoss or WebLogic. If you apply the upgrade to the existing installation directory, perform the following steps:
  1. In a JBoss environment, manually remove the JAVA_HOME environment variable setting from the following file:
    • Windows:
      <
      MDM Hub installation directory
      >\setSiperianEnv.bat
    • UNIX:
      <
      MDM Hub installation directory
      >/setSiperianEnv.sh
  2. In a JBoss or WebLogic environment, set the JAVA_HOME environment variable to the path of a supported JDK version.
Disable access to the root welcome page for your application server
To improve security, disable access to the root welcome page for your application server. For instructions, see the documentation for your application server.
0 COMMENTS
We’d like to hear from you!