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.4 HotFix 1
  • 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

Upgrading the Hub Server in Console Mode

Upgrading the Hub Server in Console Mode

You can upgrade the Hub Server in console mode in UNIX.
If you use embedded ActiveVOS for business process management, the upgrade process requires you to install the updated version of ActiveVOS in a new directory. If you prefer to overwrite the 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>
.
  1. Start the application server.
  2. Navigate to the following directory in the MDM Hub distribution:
    On UNIX.
    <
    MDM Hub distribution directory
    >/<
    operating system name
    >/mrmserver
  3. Run the following command from the command prompt: 
    ./hub_install.bin -i console
  4. Enter the number of the locale you want to choose for the upgrade, and then press
    Enter
    .
    The introduction information about the upgrade appears.
  5. Press
    Enter
    .
    The license agreement appears.
  6. Read the License Agreement. Type
    Y
     to accept the terms of the license agreement, or type
    N
     if you do not want to accept the license agreement and want to exit the installation program.
  7. Press
    Enter
    .
    If you entered
    Y
     in the preceding step, information about the installation folder appears.
  8. Specify the directory where you installed the Hub Server.
    • To choose the default folder, press
      Enter
      .
    • To change the path, type the absolute path of the installation folder, and press
      Enter
      .
  9. Confirm the location of the installation folder. Type
    Y
     to confirm the installation folder, or type
    N
     to change the installation folder.
    The version warning message appears.
  10. Press
    Enter
     to confirm that you want to proceed.
  11. Configure the server details for the Hub Console:
    • IP address or fully qualified host name (FQDN) of the server to which the application server binds.
    • 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.
  12. In WebLogic environments, enter your WebLogic password, and press
    Enter
    .
  13. If you use, or want to use, embedded ActiveVOS for business process management, install the embedded ActiveVOS version that is recommended 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. Press
      Enter
       for y=Yes.
    2. Specify the location where you want to install the ActiveVOS Server.
    3. 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. Specify the URL that you want to use to call MDM and ActiveVOS web services. Ensure the URL contains the correct port number for the connection to the application server.
    5. On the ActiveVOS Installer page, select
      Choose
       and browse to the ActiveVOS_Server installation file in the distribution package.
    6. Enter a user name and password to create an administrative user for the ActiveVOS Server Administration 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.
  14. Press
    Enter
    .
    The Informatica platform installation prompt appears.
  15. If you want to install the Informatica platform, press
    Enter
     for Yes. Otherwise, type
    2
     for No and press
    Enter
    .
    The prompts for the Informatica platform installation response file and archive file locations appear.
  16. Enter the locations of the Informatica platform installation response file and archive file, and press
    Enter
    .
  17. Specify the Product Usage Toolkit options.
    1. Enter the industry to which the organization belongs , and then press
      Enter
      .
    2. Enter the environment type. Type
      1
       for Production, type
      2
       for Test/QA, or type
      3
       for Development, and then press
      Enter
      .
  18. Select whether you have a proxy server. Press
    Enter
     for Yes. Otherwise, type
    2
     for No and then press
    Enter
    .
    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.
    The summary of the installation choices appears.
  19. Choose whether you want to run the
    postInstallSetup
     script as part of the installation, or run it manually later.
  20. Choose whether you want to run the
    postInstallSetup
     script as part of the installation, or run it manually later.
    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.
  21. Press
    Enter
    .
    The summary of the upgrade choices appears.
  22. Verify the information in the pre-upgrade summary. If the information is correct, press
    Enter
     to start the upgrade. If you need to make changes, type
    BACK
     to the specific information and make changes.
    When the process is complete, the upgrade completion information appears.
  23. Press
    Enter
     to exit the installer.
0 COMMENTS
We’d like to hear from you!