Configure the Windows server
to enable XA transactions.
Perform these steps on every Microsoft SQL
Server that will contain a Content Platform Engine database.
- Download the Microsoft SQL
Server JDBC
Driver that is referenced in IBM FileNet P8 system requirements at IBM® FileNet® P8 system requirements at for Content Platform Engine SQL Server databases.
Tip: Installation procedures for JDBC settings can vary by release.
See the Microsoft website
for full details.
- Copy the sqljdbc_xa.dll from the JDBC
installation directory to the binn folder of
the instance, although a pre-2.0 version of the driver also functions
correctly from the tools\binn folder. For
the 32-bit version of Microsoft SQL
Server ,
use the sqljdbc_xa.dll file in the x86 folder.
For the 64-bit version of Microsoft SQL
Server,
use the sqljdbc_xa.dll file in the x64 folder.
- Log on as the sa administrator or as a user with equivalent
permissions and execute the database script xa_install.sql on
the master database on every SQL Server instance that will participate
in distributed transactions.
Important: Use SQL Server database credentials,
not Windows credentials,
to log on. Windows Integrated
Logon to SQL Server is not
supported with IBM FileNet P8.
This script installs sqljdbc_xa.dll as
an extended stored procedure and creates the SqlJDBCXAUser role in
the Master database.
- Add each database account (cpe_db_user)
that Content Platform Engine uses to access SQL Server to
the SqlJDBCXAUser role. This action grants permissions
to those accounts to participate in distributed transactions with
the JDBC driver.
- From Control Panel, open Administrative Tools, and then
open Component Services.
- Expand Component Services, right-click My Computer,
and then select Properties.
- Expand Distributed Transaction Coordinator and
right-click Local DTC.
- Click the MSDTC tab, and then click Security
Configuration.
- Select the Enable XA Transactions check
box, and then click OK to restart the Microsoft DTC service.
- Click OK again to close the Properties dialog
box, and then close Component Services.
- Stop and then restart the Microsoft SQL
Server.