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

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 Hub Server.
  2. If you are installing the bundled, licensed version of the ActiveVOS Server, add the ActiveVOS properties to your properties file.
    1. Open the
      silentInstallServer_sample.properties
      file that ships with this release.
    2. Search for ActiveVOS.
    3. Copy the ActiveVOS Installation section to your properties file.
      ############################################################################### #################### ActiveVOS Server installation ############################ ############################################################################### ## Do you want to install ActiveVOS (Yes/No) AVOS.INSTALL=Yes ## Path to ActiveVOS Installer (ActiveVOS_Server_windows_9.2.4.3.exe for Windows or ActiveVOS_Server_unix_9.2.4.3.sh for Linux/UNIX) AVOS_INSTALLER_PATH=c\:\\ActiveVOS_Server_windows_9.2.4.3.exe ## ActiveVOS server install directory AVOS_INSTALL_DIR=C\:\\infamdm\\avos\\server ## Database type is the same as for HUB (There is no ability to set a different database type for ActiveVOS) ## Oracle connection data ## Connection Type SID or Service Name AVOS.ORACLE.CONNECTION.TYPE="Service Name" AVOS.DB.SERVER=localhost AVOS.DB.PORT=1521 ## Oracle SID name or service name AVOS.DB.SID=orcl AVOS.DB.SCHEMA_NAME=avos AVOS.DB.PASSWORD=!!cmx!! ## DB2 connection data AVOS.DB.SERVER=localhost AVOS.DB.PORT=50000 AVOS.DB.DBNAME=AVOS AVOS.DB.SCHEMA_NAME=AVOS AVOS.DB.USER=avos AVOS.DB.PASSWORD=!!cmx!! ## MSSQL connection data AVOS.DB.SERVER=localhost AVOS.DB.PORT=1433 AVOS.DB.DBNAME=avos AVOS.DB.USER=avos AVOS.DB.PASSWORD=!!cmx!! ##If you are moving from standalone ActiveVOS to embedded ActiveVOS, enter the details for the standalone ActiveVOS schema.
    4. In your properties file, specify the information for your ActiveVOS database and remove the properties for the other supported databases. If you need help with properties, see the
      Multidomain MDM Installation Guide
      for your environment.
  3. If you use the licensed version of ActiveVOS server, add and configure the following properties in the silent installation properties file:
    SIP.APPSERVER.WEB.URL=http://localhost:8080 ## Avos console's administrator username AVOS.CONSOLE.USER=aeadmin ## Avos console's administrator password AVOS.CONSOLE.PASSWORD=admin ##The user name and password must be the same as the ActiveVOS Console user name and password that was created in the application server during the pre-installation process.

0 COMMENTS

We’d like to hear from you!