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

Configuring the Properties File

Configuring the Properties File

Verify the values of the parameters in the properties file that affect the silent upgrade process.
  1. Find the properties file that you configured when you installed the Process Server.
  2. Use a text editor to open the file and verify the values of the parameters that affect the silent upgrade process.
    The following table describes the upgrade parameters to verify:
    Property Name
    Description
    USER_INSTALL_DIR
    Directory where you installed the Process Server.
    For example,
    C\:\\<
    MDM Hub installation directory
    >\\cleanse
    .
    You must escape backslash characters in the properties file. Use double backslashes when you specify the installation directory path.
    SIP.APPSERVER.PASSWORD
    Password to access WebLogic. For WebLogic environments.
    RUN_DEPLOYMENT_FLAG
    Runs the postInstallSetup script as part of the silent upgrade. Set to
    1
     if you want to run postInstallSetup at the end of the silent upgrade. Set to
    0
     if you do not want to run postInstallSetup.
  3. Add and configure the following product usage toolkit properties to the silent installation properties file: 
    #Product Usage Toolkit Installation
#CSM_TYPE is the type of Product Usage Toolkit installation.
# valid values are:Production,Test,Development. Should not be blank.
CSM_TYPE=Production

# If the network haa a proxy server, fill in the following parameters (leave empty if no proxy):
# proxy server host
CSM_HOST=
# proxy server port
CSM_PORT=
# Proxy server domain name (leave blank, if not applicable)
CSM_DOMAIN=
# Proxy server user name (leave blank, if not applicable)
CSM_PROXY_USER_NAME=
#Proxy server password (leave blank, if not applicable)
CSM_PROXY_PASSWORD=
0 COMMENTS
We’d like to hear from you!