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 Microsoft SQL Server for Distributed Transactions

Configuring Microsoft SQL Server for Distributed Transactions

Before you start Microsoft SQL Server, ensure that you configure it for distributed transactions. The
MDM Hub
requires a distributed transaction environment.
  1. To ensure that the Microsoft Distributed Transaction Coordinator (MS DTC) service starts when you start Microsoft SQL Server, mark MS DTC as Automatic in the Service Manager.
  2. Enable MS DTC for XA transactions.
  3. Enable MS DTC for SNA LU 6.2 transactions.
  4. Configure the JDBC distributed transactions component.
    1. Download and extract the Microsoft SQL Server JDBC driver from the Microsoft website to a directory on the machine.
    2. Copy the
      sqljdbc_xa.dll
      file to the
      Binn
      directory of the machine on which Microsoft SQL Server is installed.
    3. Run the
      xa_install.sql
      script on the Microsoft SQL Server instance as an administrator.
      The
      xa_install.sql
      script is in the
      xa
      directory of the JDBC driver.
    4. Verify that the script creates the SqlJDBCXAUser role in the Microsoft SQL Server master database.
For more information about how to install and configure Microsoft SQL Server for distributed transactions, see the Microsoft SQL Server documentation.

0 COMMENTS

We’d like to hear from you!