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

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!