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

Upgrading from Version 9.7.1

Upgrading from Version 9.7.1

Back Next

Configure JBoss

Configure JBoss

Configure the JBoss application server to use the database in IBM DB2 with Oracle-compatibility disabled.
  1. Open the
    standalone-full.xml
     file from the following JBoss installation directory:
    On UNIX.
    <
    JBoss_install_dir
    >/standalone/configuration/standalone-full.xml
    On Windows.
    <
    JBoss_install_dir
    >\standalone\configuration\standalone-full.xml
  2. Change the database name for the
    java:jboss/datasources/jdbc/siperian-cmx_system-ds
     JNDI to the name of the database that you created in IBM DB2 with Oracle-compatibility disabled.
    To change the database name, find the
    <xa-datasource>
     element for the JNDI name, and change the
    <xa-datasource-property name="">
     element for the database name to that of the new database.
    The following code shows the
    xa-datasource-property name
     element for the database name: 
    <xa-datasource jndi-name="java:jboss/datasources/jdbc/siperian-cmx_system-ds" pool-name="jdbc/siperian-cmx_system-ds" enabled="true" use-java-context="true" spy="false" use-ccm="true">
   .
   .
   .
   <xa-datasource-property name="<
    New Database Name
    >">
   .
   .
   .
<xa-datasource>
  3. Save and close the
    standalone-full.xml
     file.
  4. Start the JBoss application server.
  5. Calalog the database in IBM DB2 with Oracle-compatibility disabled and remove the catalog for the database that was created in the IBM DB2 Oracle-compatibility mode.
  6. Log in to the MDM Hub Console, start the Repository Manager tool, and run metadata validation.
0 COMMENTS
We’d like to hear from you!