Windows stand-alone: Install SQL Server

Complete the following prerequisites:

• You should have completed reviewing the Planning for SQL Server topic.

• Install SQL Server separately from WebSphere Portal.

• WebSphere Portal requires Microsoft SQL Server JDBC Driver. We can obtain the Microsoft SQL Server JDBC Driver from Microsoft.

  See the Microsoft SQL Server product documentation for installation details

  The driver must be a JDBC 4.0 compliant driver.

The following section provides instructions for installing SQL Server for use with IBM WAS and WebSphere Portal.

1. Install SQL Server and all required patches.

2. Select the Mixed Mode (Windows Authentication and SQL Server Authentication) authentication mode for this installation.

   Mixed Mode authentication allows either a Windows user or an SQL Server user, or both, to log in to the SQL Server; however, WebSphere Portal requires the user to be an SQL Server user.

3. In the SQL Server Set up panel...
   Components to Install

   ...select the following components, which are required services for WebSphere Portal:

   • SQL Server Database Services

4. Complete the installation using SQL Server documentation as a guide.

5. Enable TCP/IP connectivity in the SQL Server Configuration Manager.

6. Install the JDBC driver using Microsoft SQL Server JDBC drivers and enabling XA connections:

   1. Download and install the Microsoft SQL Server JDBC driver; see Microsoft Download Center for information.

   2. Copy file sqljdbc_xa.dll from the xa subdirectory to the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqljdbc_xa.dll directory of the SQL Server installation.

   3. Start the database server.

   4. Ensure that the Distributed Transaction Coordinator has been started. The status can be verified in the list of services in the Computer Management console.

   5. Start the Microsoft SQL Server Management Studio and connect to the local database engine as the system administrator, sa.

   6. Select File > Open > File and select xa_install.sql from the subdirectory of the downloaded and extracted JDBC driver.

   7. Execute the script by selecting Query > Execute.

      Any warnings that appear in the messages section of the application window that say that stored procedures cannot be found can be safely ignored.

   8. For Microsoft SQL Server JDBC drivers: If we are running Windows XP SP2, Windows XP 64-Bit Edition, or Windows Server 2003, refer to the Registry Entries Are Required for XA Transaction Support document for information on a new security constraint and how to set SQL Server on Windows XP SP2, Windows XP 64-Bit Edition, or Windows Server 2003.

      Create a additional value in the Windows registry for WebSphere Portal by following these steps:

      1. Open theWindows Registry Editor (regedit) and navigate to the element HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\XADLL

      2. From the menu bar, select Edit > New > String Value to create a new parameter named sqljdbc_xa.dll is that element.

      3. Change the value of the new parameter to the location of the sqljdbc_xa.dll file copied in the previous substep, for example: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqljdbc_xa.dll

7. To enable XA Transactions in Windows Component Services:

   1. Click Start > Settings > Administrative Tools > Component Services.

   2. Expand the tree view to locate the computer where to turn on support for XA transactions (for example, My Computer).

   3. Display the menu for the computer name and click Properties.

   4. Click Options and tune the Transaction Timeout that suits the environment. (The recommended minimum is 180 seconds).

   5. Click MSDTC and click Security Configuration.

   6. Under Security Settings, select XA Transactions to enable this support.

   7. Click OK to save the changes.

8. Start SQL Server.

Parent: Windows stand-alone: Set up a remote SQL Server database
Next: Windows stand-alone: Modify SQL Server database properties