nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How do we configure configure Microsoft SQL Server for Vignette Content JDBC XA support?

Namit_Gupta

We are currently installing V8.0

Find more posts tagged with

Comments

Todd_Niederauer

Hello,

First, ensure that you're using a supported DB version. You can check that here:

http://knowledge.opentext.com/knowledge/cs.dll/Open/17081837

The steps to configure VCM with SQLServer can be found under your VCM installdir here:

Content/8_0/jdbc/SQLServer/ReadMe.html

If you have any problems configuring, feel free to open a ticket with support.

Thanks.

-Todd

chandrakanthr

Open Component Services.
Expand the tree view to locate the computer where you want to turn on support for XA transactions (for example, My Computer).
Right-click the computer name, and then click Properties.
Click the MSDTC tab, and then click Security Configuration.
Under Security Settings, click to select the check box for XA Transactions to turn on this support.

Follow below steps for XA enabled database.

Go to the Microsoft SQL Server installation directory and look in the Binn directories for the existence of the Vignette library vgnjdbcXA.dll. On SQL Server 2005, the location would be similar to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn. If vgnjdbcXA.dll does not exist in any of the Binn directories, continue with step 4.
Shut down SQL Server. This prevents the database from locking the existing vgnjdbcXA.DLL(s).
Remove or rename every instance of vgnjdbcXA.dll currently on the SQL Server database server. Write down the locations where the file had existed.
Note that this newer vgnjdbcXA.dll is backward compatible and so it can be used to replace all of the vgnjdbcXA.dll's that had existed on the database server.
Get vgnjdbcXA.sql and vgnjdbcXA.dll from either of the following locations:

Vignette_install_dir\Content\version\jdbc\SQLServer\32-bit

Vignette_install_dir\Content\version\jdbc\SQLServer\64-bit

Vignette_install_dir\Content\version\jdbc\SQLServer\x64-bit

Copy the appropriate files as follows:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn

Note: Choose the 32-bit or 64-bit DLL based on the whether the SQL Server you are running is 32-bit or 64-bit.

Start SQL Server if it is not already running.

Run the vgnjdbcXA.sql script in SQL Server.

NOTE: The vgnjdbcXA.sql script may generate many messages about being unable to drop the procedure. In general, these messages can be ignored; however, the database administrator should review the output for any actual errors.

Make sure the message vgnjdbcXA.sql completed successfully displays when the script is complete. Possible reasons for the script failing are insufficient space available in the master database to store the JDBC XA procedures or to log changes to existing procedures.
To verify that SQL Server has access to the DLL, log in to SQL Server to enter SQL commands.

    execute xp_jdbc_open2
    go
    execute xp_jdbc_close2
    go