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. Troubleshooting the Upgrade Process
  16. Frequently Asked Questions
  17. Processing Existing ActiveVOS Tasks
  18. Configuring Metadata Caching

Upgrading from Version 9.5.1

Upgrading from Version 9.5.1

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!