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 HotFix 2
  • 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. Post-Upgrade Tasks
  10. Search Configuration Upgrade
  11. Hierarchies Upgrade
  12. ActiveVOS Post-Installation Tasks for the Application Server
  13. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  14. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  15. Appendix A: Troubleshooting the Upgrade Process
  16. Appendix B: Frequently Asked Questions
  17. Appendix C: Processing Existing ActiveVOS Tasks
  18. Appendix D: Configuring Metadata Caching

Upgrading from Version 10.1, 10.2, 10.3, 10.4, or 10.5

Upgrading from Version 10.1, 10.2, 10.3, 10.4, or 10.5

Back Next

Upgrading the Hub Server in Graphical Mode

Upgrading the Hub Server in Graphical Mode

To upgrade the Hub Server in graphical mode, run the Hub Server installer.
If you use embedded ActiveVOS, the upgrade process requires you to install the updated version of ActiveVOS in a new directory. If you prefer to overwrite your existing ActiveVOS installation, before you begin the upgrade, open the
../hub/server/bin/build.properties
 file and comment out the following property:
activevos.install.dir = <AVOS installed path>
. For other pre-upgrade tasks, see Prepare the BPM Upgrade.
  1. Log in using the user name that was used to install the Hub Server.
  2. Start the application server on which the Hub Server is deployed.
  3. Open a command prompt and navigate to the Hub Server installer in the distribution directory. By default the installer is in the following directory:
    • On UNIX.
      <
      MDM Hub distribution directory
      >/<
      operating system name
      >/mrmserver
    • On Windows.
      <
      MDM Hub distribution directory
      >\windows\mrmserver
  4. Run the following command:
    • On UNIX.
      hub_install.bin
    • On Windows.
      hub_install.exe
  5. From the
    Introduction
     page, click
    Next
    .
    The
    Review the license agreement
     page appears.
  6. Review and accept the terms of the license agreement. Click
    Next
    .
  7. Select the location of the Hub Server installation. The Hub Server installation folder contains the
    siperian-mrm.ear
     file. Click
    Next
    .
  8. If use Customer 360 or Supplier 360, perform the following tasks:
    1. Ensure that all the draft records are submitted in Customer 360 or Supplier 360.
      If you do not submit the draft records, you can confirm to delete them and proceed with the upgrade.
    2. Click
      Proceed
      .
  9. If you get the version warning message, click
    OK
     to upgrade an existing Hub Server installation.
  10. On the
    Configure server details for the Hub Console
     page, enter the following details:
    • Publicly Accessible Host Name. IP address or publicly accessible host name (FQDN) of the server to which the application server binds.
    • HTTP port. HTTP port of the server that the Hub Console must use.
      If HTTPS is enabled for the application server, after the upgrade, configure the Hub Console client by editing the properties in the
      build.properties
       file.
  11. If the previous installation uses WebLogic as the application server, the Hub Server installer prompts you to provide the WebLogic Admin password. Enter the WebLogic password.
  12. If you use, or want to use, ActiveVOS for business process management, install the embedded ActiveVOS version that is supported for this version of
    Multidomain MDM
    .
    Standalone ActiveVOS is not supported. If you already have a supported version of embedded ActiveVOS installed, you can skip some of the substeps in this step. Perform substep c. to enter database details and substep 12f. to specify the user name and password for the ActiveVOS Server Administration Console.
    1. Select
      Yes
      .
    2. On the
      Select an ActiveVOS installation directory
       page, accept the default path or select another location. Click
      Next
      .
    3. On the
      Configure the ActiveVOS J2EE data source
       page, enter the database details that you specified when you created the ActiveVOS database schema, and click
      Next
      .
      If you are moving from standalone ActiveVOS to embedded ActiveVOS, enter the details for the standalone ActiveVOS schema.
    4. On the
      Specify the ActiveVOS web service URL
       page, accept the default URL or specify the URL that you want to use to call ActiveVOS web services. Ensure the URL contains the correct port number for the connection to the application server. Click
      Next
      .
      The post installation setup script uses the URL to call ActiveVOS web services, deploy the predefined MDM workflows to ActiveVOS, and create the URN mapping.
    5. On the
      Select the ActiveVOS installer
       page, click
      Choose
      . Browse to the ActiveVOS_Server installation file in the distribution package. Click
      Next
      .
    6. Enter the administrative user name and password to create an administrative user for the ActiveVOS Console.
      The user name and password must be the same as the ActiveVOS Console user name and password that was created in the application server.
    7. Click
      Next
      .
  13. On the
    Configure the MDM Product Usage Toolkit
     window, select the industry to which the organization belongs and the environment type.
  14. If you want to use a proxy server, select
    Yes
    , and enter the proxy server details. Otherwise, select
    No
    .
    You can enter the following proxy server details:
    • Proxy server name/IP
    • Proxy server port
    • Proxy server domain name. Leave blank if not applicable.
    • Proxy server user name. Leave blank if not applicable.
    • Proxy server password. Leave blank if not applicable.
  15. Click
    Next
    .
    The
    Deploy the Hub Server
     page appears.
  16. Select whether to deploy the
    Hub Server
     EAR file automatically or manually, and then click
    Next
    .
    Option
    Conditions
    Yes, run the script during this installation
    Deploys the
    Hub Server
     EAR file automatically after a successful installation.
    Select this option if you use one of the following application server environments with one of the ActiveVOS scenarios:
    Application server environments:
    • JBoss standalone environment
    • WebSphere standalone environment
    ActiveVOS scenarios:
    • You chose to install ActiveVOS and no other version of ActiveVOS is installed in this environment.
    • You chose to install ActiveVOS and the environment includes a supported version of ActiveVOS. Check the product availability matrix (PAM) for supported versions.
    • You chose not to install ActiveVOS.
    If you chose to install ActiveVOS but you have an unsupported version of ActiveVOS in your environment, select
    No, I will run it later
    .
    No, I will run it later
    You package and deploy the
    Hub Server
     EAR file manually.
    Select this option if you use one of the following application server environments, with or without ActiveVOS:
    • WebLogic standalone environment
    • WebLogic clustered environment
    • JBoss clustered environment
    • WebSphere clustered environment
    If you are using any application server environment that includes an unsupported version of ActiveVOS, select this option. You must upgrade the ActiveVOS schema to the supported version and then deploy manually.
    The
    Summary
     window appears.
  17. To change any options, click the
    Previous
     button to change your previous selections.
  18. After the summary window displays the options you want, click
    Install
     to start the installation process.
    The Hub Server installer displays the
    Please Wait
     screen while the installer configures the system. The Hub Server installer backs up critical files to an archive that is stored in the
    backup
     folder in the MDM Hub installation directory. The file name of the archive uses the format shown in the following example: 
    Informatica MDM Hub Server-2010-09-27_12-13.jar
    When the installation completes, the
    Install Complete
     window appears.
  19. Click
    Done
     to exit the Hub Server installer.
    If the upgrade does not complete successfully, a window appears that states that the upgrade failed and displays the location of the log file that contains the failure messages.
  20. If you selected
    No, I will run it later
    , repackage and deploy the Hub Server EAR file.
    1. If you have an unsupported version of ActiveVOS in your environment, update the ActiveVOS schema to the supported version.
    2. Run the following command to repackage the EAR file:
      On UNIX. 
      cd <
      MDM Hub installation directory
      >/hub/server/bin
./sip_ant.sh repackage
      On Windows. 
      cd <
      MDM Hub installation directory
      >\hub\server\bin
sip_ant.bat repackage
    3. From the application server administration console, manually deploy the Hub Server EAR file. Refer to the application server documentation.
  21. Restart the application server.
0 COMMENTS
We’d like to hear from you!