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

Edit the Build Properties File (In-place Upgrade)

Edit the Build Properties File (In-place Upgrade)

If ActiveVOS is installed in your MDM environment, you must perform upgrade tasks to edit the
build.properties
 file.
The following table describes the upgrade tasks required to edit the
build.properties
 file:
Upgrade Task
Details
Configure the database connection properties for IBM Db2
In IBM Db2 environments, before you upgrade, add the ActiveVOS database connection properties to the
build.properties
 file in
<
MDM Hub installation directory
>/hub/server/bin
.
The following sample shows the ActiveVOS database connection properties with sample entries: 
activevos.db.type=db2
activevos.db.server=localhost
activevos.db.port=50000
activevos.db.user=AVOS
activevos.db.dbname=INFA102
activevos.db.schemaname=AVOS
activevos.db.jdbc.url=jdbc:db2://localhost:50000/INFA102
activevos.b4p.url=http://localhost:9080/active-bpel/services/AeB4PTaskClient-taskOperations
Configure the ActiveVOS installation directory
If the upgrade process detects that the installed version of ActiveVOS does not meet the system requirements, the upgrade process installs the required version of ActiveVOS in a new directory.
To install ActiveVOS in the same directory as a previous installation, delete or comment out the following entry in the build.properties file: 
activevoslinstall.dir=<ActiveVOS installation directory>
Configure the ActiveVOS settings
Applicable for JBoss environments only. If the ActiveVOS settings property
sip.appserver.web.url
 is not set to the default port number
8080
, you must manually update the property and the port number to the following: 
-Dsip.appserver.web.url= http://localhost:8079
You can set the port number to
8079
 or another unused port number.
Update the properties in the
build.properties
 file in
<MDM Hub installation directory>/hub/server/bin
.
0 COMMENTS
We’d like to hear from you!