Configuring the SQL Server Data Source on WebSphere for LiveCycle Form Manager and LiveCycle Workflow

Transcription

1 Adobe Enterprise & Developer Support Knowledge Article ID: c4712 bc Configuring the SQL Server Data Source on WebSphere for This article describes how to configure a Microsoft SQL Server data source on IBM WebSphere for use with Adobe LiveCycle Form Manager and Adobe LiveCycle Workflow. To enable WebSphere to work with a SQL Server 2000 database, you must complete the following tasks before configuring and deploying the LiveCycle products: Obtain the SQL Server 2000 Driver for JDBC. Create a SQL Server database for storing LiveCycle run-time data, and then create a user account on the database. Configure the database so that it is XA-enabled to support distributed transaction processing. If running SQL Server 2000 on Microsoft Windows Server 2003, Enterprise Edition, enable XA transactions at the operating system level. Configure a SQL Server 2000 data source on WebSphere. Configure the JMS Queue and Topic Connection Factories on WebSphere so that they are XA-enabled. Obtaining the database driver To make the SQL Server database XA-enabled and to configure a SQL Server data source on WebSphere, you need to download and install the SQL Server 2000 Driver for JDBC from The downloaded file installs the required JDBC driver files (msbase.jar, mssqlserver.jar, and msutil.jar files) as well as the files required to make the database XA-enabled (sqljdbc.dll and instjdbc.sql). Creating the SQL Server database and user account You need to create a SQL Server database that LiveCycle products can use to store run-time and configuration data. For information on creating a SQL Server database, see the SQL Server documentation. LiveCycle products support SQL Server 2000 SP3a. When you create the database, you need to create a user account that is used to access the database when configuring the data source on the application server. The user account must have DB_OWNER privileges. For information on creating user accounts, see the SQL Server documentation. Note: The server collation must be set to SQL_Latin1_General_Cp1_CI_AS. If your server uses a different collation, you need to rebuild the master database to set the collation to the SQL collation of Dictionary order, case-insensitive, for use with 1252 Character Set (this is the SQL_Latin1_General_Cp1_CI_AS collation). To rebuild the master database, you must use the Rebuild Master utility that comes with SQL Server For information on using this utility, see the SQL Server 2000 documentation. Configuring the database to be XA-enabled You need to configure the SQL Server 2000 database that you created to use the XA protocol for distributedtransaction processing. You also need to ensure that Microsoft Distributed Transaction Coordinator (MS DTC) is started on SQL Server 2000.

2 2 To configure the database to be XA-enabled: 1. Copy the sqljdbc.dll file (from the SQLServer JTA directory from where you installed SQL Server 2000 Driver for JDBC) to the [install directory]\microsoft SQL Server\MSSQL\Binn directory, where [install directory] is the location where SQL Server is installed.[for the directory name SQLServer JTA, verify spacing] Log into SQL Server 2000 Query Analyzer using a user account that is a member of the sysadmin group (sa is the default member). Set the target database to master. Open the instjdbc.sql file from the SQLServer JTA directory from where you installed SQL Server 2000 Driver for JDBC, and then execute it. If this is the first time running this query, you will see several messages that indicate xp_xxx cannot be dropped. These messages are warnings and do not indicate that the installation failed. The last line should read instxa.sql completed successfully. En sure MS DTC is started for SQL Server 2000: Open SQL Server Service Manager. In the Services menu, select Distributed Transaction Coordinator. Click Start/Continue. If you want MS DTC to start automatically when the computer starts, select Auto-start service when OS starts. Enabling XA transactions for Windows Server 2003 If you are running SQL Server 2000 on the Windows Server 2003, Enterprise Edition operating system, XA transactions must be enabled at the operating system level. Before you perform the tasks in this section, you must verify whether XA transactions are already enabled. To enable XA transactions on the operating system, you need to perform the following tasks: Enable XA transactions for the MS DTC Create a registry entry for the sqljdbc.dll database drivers file that you are using Note: You copied the sqljdbc.dll file to the SQL Server 2000 directories during the Configuring the database to be XA-enabled task. To enable XA transactions for MS DTC: 1. Open Component Services. Expand the tree view to locate the computer that you want to support for XA transactions. Right-click the computer name and click Properties. Click the MSDTC tab and click Security Configuration. Under Security Settings, select the XA Transactions option. Click OK, and then click OK again.

3 3 To create registry entries for the driver file: 1. Use your registry editor to navigate to the registry key named HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\XADLL. Create a new registry named value that has the following properties: Name: sqljdbc.dll Type: String (REG_SZ) Value: C:\Program Files\Microsoft SQL Server\MSSQL\Binn\ sqljdbc.dll Configuring a SQL Server data source on WebSphere You need to configure a data source that connects WebSphere Application Server to the SQL Server database that you created for LiveCycle products. If you are working in a clustered environment, you need to perform this task on all of the WebSphere application servers in the cluster. To configure a SQL Server data source on WebSphere: 1. In the ${WAS_INSTALL_ROOT} directory, create a directory named ojdbc, and copy the msbase.jar, mssqlserver.jar, and msutil.jar files into this directory. These files were installed with SQL Server 2000 Driver for JDBC In the WebSphere Administrative Console navigation tree, select Environment > Manage WebSphere Variables. In the Scope area, select Node and click Apply. The scope needs to be the same as the scope of the JDBC provider that you configure later in this task. Click MSSQLSERVER_JDBC_DRIVER_PATH.[should this be bold?] In the Value box, type ${WAS_INSTALL_ROOT}/ojdbc, click Apply, and then save the changes to the Master Configuration. In the navigation tree, select Security > JAAS Configuration > J2C Authentication Data. Click New. In the Alias box, enter a name for the alias, such as SQLServer. In the User ID box, enter the user name of the user account you created on the database and, in the Password box, enter the corresponding password. Click Apply, click OK, and then save to the Master Configuration. In the navigation tree, select Resources > JDBC Providers. 10. For Scope, select Node and click Apply. If you are working in a clustered environment, it is important to set the scope to Node Click New. From the JDBC Providers menu, select User-defined JDBC Provider and click Apply. In the Name box, type SQL Server JDBC Provider 1 In the Description box, type SQL Server JDBC0-compliant Provider configuration

4 4 1 1 In the Classpath box, enter the following values. You must press Enter after each value. ${MSSQLSERVER_JDBC_DRIVER_PATH}/msbase.jar ${MSSQLSERVER_JDBC_DRIVER_PATH}/mssqlserver.jar ${MSSQLSERVER_JDBC_DRIVER_PATH}/msutil.jar In the Implementation Classname box, type com.microsoft.jdbcx.sqlserver.sqlserverdatasource and click OK Click SQL Server JDBC Provider. Under Additional Properties, select Data Sources. Click New. In the Name box, enter a name for the data source, such as LiveCycleDS. In the JNDI Name box, type IDP_DS In the Datasource Helper Classname box, type com.ibm.websphere.rsadapter.connectjdbcdatastorehelper In the Component-managed Authentication Alias and Container-managed Authentication Alias menus, select the SQL Server alias that you created in step 6 (computer_name/alias name). 21. In the Mapping-Configuration Alias menu, select DefaultPrincipalMapping and click Apply. 2 Under Additional Properties, click Connection Pool, change the value of Max Connections to 30, and then click OK. 2 2 Under Additional Properties, click Custom Properties and select databasename. In the Value box, enter the name of your SQL Server database and click OK. 2 In Custom Properties, click servername. In the Value box, enter the name of the server where your SQL Server database resides and click OK In Custom Properties, click enable2phase. In the value box, enter true and click OK. Save your changes to the Master Configuration. 28. Test your connection by navigating to Resources > JDBC Providers > SQL Server JDBC Provider > Data Sources and clicking Test Connection. Configuring JMS queue and topic connection factories You need to configure the WebSphere JMS queue and topic connection factories to be XA-enabled. 1. In WebSphere Administration Console, click Resources > WebSphere JMS Provider or WebSphere MQ JMS Provider (depending on the JMS provider you are using), and then click Queue Connection Factories. Enable XA for each queue connection factory: Click the queue connection factory name. Select the Enable XA option and click OK. Click Resources > WebSphere JMS Provider or WebSphere MQ JMS Provider (depending on the JMS provider you are using), and then click Topic Connection Factories.

5 5 Enable XA for each topic connection factory: Click the topic connection factory name. Select the Enable XA option and click OK. Save your changes to the Master Configuration. Restart WebSphere. Configuring a data source for LiveCycle Workflow BAM LiveCycle Workflow BAM uses a separate database to store the application metadata that it uses in business activity reports. To create and configure the SQL Server 2000 metadata database for use with LiveCycle Workflow BAM running on WebSphere, you need to perform the following tasks: Create the metadata database. Initialize the metadatadatabase. Create the data source on WebSphere for the metadata database. Creating the BAM database The metadata database contains definitions for all of the objects in the BAM installation as well as the details of the alerts and object run-time data persisted to disk. You need to create a database with the following properties: The database must be named cqstmeta (all lowercase). At least 50 MB must be allocated for data storage. For production deployments, allocate at least 200 MB for data storage. Another database user account must be created that the BAM application can use to connect to the database. The user account must have a user name of cqstmeta, and must have create, modify, and update privileges on the database. Initializing the BAM database The BAM database needs to be initialized before it can be used with LiveCycle Workflow BAM. To initialize the database, you must use the cqinitmetadata.jar utility that is installed with LiveCycle Workflow. The utility uses the SQL Server 2000 Driver for JDBC to communicate with the database. This is the same driver that you used to create the database for holding LiveCycle run-time data. For more information, see Obtaining the database driver. The utility has a command-line interface that you use to run it with the appropriate arguments. The command has the following syntax: java -cp cqinitmetadata.jar<sep><classpath> com.celequest.metadata.upgrade. Upgrade SQLSERVER jdbcurl [-l loggingdir] [-d jdbcdriver] Arguments: Sep: A separator that is appropriate for your platform. For windows, use a semicolon (;) and, for UNIX, use a colon (:). classpath: The Java classpath for the database driver msbase.jar, mssqlserver.jar, and msutil.jar files. jdbcurl: The JDBC URL that connects to the database being initialized. The URL contains all of the information for connecting to the database and must set the select method to cursor. For information on formulating this URL, see the SQL Server 2000 Driver for JDBC documentation.

6 6 loggingdir: (optional) The directory to write the log messages to during initialization. Omit this option to suppress logging. jdbcdriver: (optional) The JDBC driver class name to use instead of the default driver. The default driver for SQL Server 2000 is com.microsoft.jdbc.sqlserver.sqlserverdriver. The driver must be in the Java classpath. For example, the following command is appropriate for a database that is running on localhost with the driver files located in the same directory as the cqinitmetadata.jar file. The database name is cqstmeta, the user name is cqstmeta, and the password is Adobe. The operating system is Windows-based: java -cp cqinitmetadata.jar;msutil.jar;msbase.jar;mssqlserver.jar com. celequest.metadata.upgrade.upgrade SQLSERVER jdbc:microsoft:sqlserver://loca lhost:1433;selectmethod=cursor;databasename=cqstmeta;user=cqstmeta;password=a dobe To configure the metadata database: 1. Open a command-line utility and navigate to [LiveCycle_install_root]/ Workflow/bam/CQInitMetadata, where the cqinitmetadata.jar file was installed. Run cqinitmetadata.jar using arguments that are appropriate for your environment. Configuring a SQL Server data source on WebSphere for BAM You need to configure a data source that connects WebSphere Application Server to the SQL Server database that you created for LiveCycle Workflow BAM. If you are working in a clustered environment, you need to perform this task on all of the WebSphere application servers in the cluster. If you have not performed the task in this article for setting up the data source for the LiveCycle products, you should do so now before configuring the data source for BAM. Before performing the following task, you need to have made the database XA-enabled, and created the WebSphere variable that stores the location of the Microsoft SQL Server 2000 Driver for JDBC files..[break this paragraph into three bullets listing the tasks that need to be completed before performing the following task] To configure a SQL Server data source on WebSphere for BAM: 1. In the navigation tree of WebSphere Administration Console, select Resources > JDBC Providers. For Scope, select Node and click Apply. If you are working in a clustered environment, it is important to set the scope to Node. Click New. From the JDBC Providers menu, select WebSphere embedded ConnectJDBC driver for MS SQL Server (XA) and click Apply. In the Classpath box, enter the following values to add them to the existing list of files. You must press Enter after each value. ${MSSQLSERVER_JDBC_DRIVER_PATH}/msbase.jar ${MSSQLSERVER_JDBC_DRIVER_PATH}/mssqlserver.jar ${MSSQLSERVER_JDBC_DRIVER_PATH}/msutil.jar In the Implementation Classname box, type com.microsoft.jdbcx.sqlserver.sqlserverdatasource and click OK.

7 Click WebSphere embedded ConnectJDBC driver for MS SQL Server (XA). Under Additional Properties, select Data Sources. Click New. In the Name box, enter a name for the data source, such as com.celequest.metadata.metadatasource. In the JNDI Name box, type jndi/com.celequest.metadata.metadatasource Select the Container Managed Persistence option. 10. In the Datasource Helper Classname box, type com.ibm.websphere.rsadapter.connectjdbcdatastorehelper, and click Apply Under Additional Properties, click Custom Properties and click databasename. In the Value box type cqstmeta and click OK. 1 In Custom Properties, click servername. In the Value box, enter the name of the server where your SQL Server database resides and click OK. 1 1 In Custom Properties, click selectmethod. In the Value box, type cursor and click OK. In Custom Properties, click enable2phase. In the Value box, type true and click OK In Custom Properties, click New. In the Name box, type user, in the Value box type cqstmeta, and then click OK. In Custom Properties, click New. In the Name box type password, in the Value box enter the password for the database user cqstmeta, and then click OK. 18. Save your changes to the Master Configuration. 19. Test your connection by navigating to Resources > JDBC Providers > WebSphere embedded ConnectJDBC driver for MS SQL Server (XA) > Data Sources, selecting your data source, and then clicking Test Connection. Product Adobe LiveCycle Form Manager Adobe LiveCycle Workflow Published November 29, 2005 Adobe Systems Incorporated 345 Park Avenue, San Jose, CA USA Adobe, the Adobe logo, and Better by Adobe. are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. All other trademarks are the property of their respective owners. Copyright 2005 Adobe Systems Incorporated. All rights reserved.