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.3 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. 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.0, 10.1, 10.2, or 10.3

Upgrading from Version 10.0, 10.1, 10.2, or 10.3

Back Next

Upgrading the Process Server in Graphical Mode

Upgrading the Process Server in Graphical Mode

To upgrade the Process Server in graphical mode, run the Process Server installer.
  1. Log in using the user name that was used to install the
    Process Server
    .
  2. Start the application server on which the
    Process Server
     is deployed.
  3. Open a command prompt and navigate to the Process Server installer in the distribution directory. By default the installer is in the following directory:
    • On UNIX.
      <
      MDM Hub distribution directory
      ><
      operating system name
      >/mrmcleanse
    • On Windows.
      <
      MDM Hub distribution directory
      >\windows\mrmcleanse
  4. Run the following command:
    • On UNIX.
      hub_cleanse_install.bin
    • On Windows.
      hub_cleanse_install.exe
  5. From the
    Introduction
     window, click
    Next
    .
    The
    License Agreement
     window appears.
  6. Select the
    I accept the terms of the License Agreement
     option, and then click
    Next
    .
    The
    Choose Install Folder
     window appears.
  7. Select the location of the Process Server installation. The Process Server installation folder contains the
    siperian-mrm-cleanse.ear
     file.
    • To choose the default location, click
      Next
      .
    • To choose another location, click
      Choose
      , and then click
      Next
      .
    The
    Version Warning
     message appears.
  8. Click
    OK
     to confirm that you want to proceed.
    The
    Enter Location of License File
     window appears.
  9. Select the location of the license file, and then click
    Next
    .
  10. If the previous installation uses WebLogic as the application server, the
    Process Server
     Installer prompts you to provide the WebLogic Admin password. Enter the WebLogic password.
  11. On the Product Usage Toolkit page, select the
    Environment Type
    .
  12. If you have a proxy server, select
    Yes
    , and enter the proxy server details. Otherwise, select
    No
    , and click
    Next
    .
    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.
  13. Click
    Next
    .
    The Deploy page appears.
  14. Select whether to deploy automatically or manually. click
    Yes
     to deploy automatically, or click
    No
     to deploy manually, and then click
    Next
    .
    • On WebSphere standalone environments or JBoss standalone environments, click
      Yes
       to deploy automatically, and then click
      Next
      .
    • On WebLogic or clustered environments, click
      No
       to deploy manually, and then click
      Next
      .
    The
    Pre-Installation Summary
     window appears.
  15. To change any options, click the
    Previous
     button to change your previous selections.
  16. After the summary window displays the options you want, click
    Install
     to start the installation process.
    The
    Process Server
     installer displays the
    Please Wait
     screen while the installer configures the system. The
    Process 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: 
    Siperian Hub Cleanse Match Server-2010-05-12_18-09.jar
    When the installation completes, the
    Install Complete
     window appears.
  17. Click
    Done
     to exit the
    Process 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.
  18. If you selected
    No
     in step 14, repackage and manually deploy the EAR file.
    1. Run the following command to repackage the EAR file:
      On UNIX. 
      cd <
      MDM Hub installation directory
      >/hub/cleanse/bin
./sip_ant.sh repackage
      On Windows. 
      cd <
      MDM Hub installation directory
      >\hub\cleanse\bin
sip_ant.bat repackage
    2. From the application server administration console, manually deploy the Process Server EAR file. Refer to the application server documentation.
  19. Copy the SSA-Name3 library files from
    <
    MDM Hub installation directory
    >/hub/cleanse/lib/upgrade/SSA
     to
    <
    MDM Hub installation directory
    >hub/cleanse/lib
    .
  20. Restart the application server.
0 COMMENTS
We’d like to hear from you!