6.3 Configuring the LiveCycle database connectivity

To enable WebSphere and your LiveCycle deployment to connect to the LiveCycle database, you must create a database connection for LiveCycle by installing the database drivers and then setting up a data source.

You must install drivers for the type of database that you use for the LiveCycle database. The drivers should be placed in the installation directories of the application server.

You must configure the data source to connect to the database. For WebSphere, you can configure a DB2, an Oracle 11g, SQL Server 2005 SP2 or a SQL Server 2008 data source.

You will need the following information from tasks you did in Preparing to Install LiveCycle (Server Cluster):

  • Database name

  • Server name

  • Port number

  • User name

  • Password

Refer to the following section that applies to your database:

    6.3.1 Configuring the DB2 data source

    Configuring the DB2 data source requires you to install the DB2 database drivers, create a DB2 JDBC provider on WebSphere, create the data source on WebSphere, and then configure the corresponding connection pool.

    To install the DB2 database driver:

    1. On a WebSphere Application Server instance, in the [appserver root] directory, create a directory named db2libs.

    2. Copy the db2jcc.jar file from one of these locations to the [appserver root]\db2libs directory:

      • The java directory under your [dbserver root] directory, such as [dbserver root]/ibm/Sqllib/java (Windows) or [dbserver root]/java (Linux or UNIX)

      • [LiveCycle root]\lib\db\db2\

    3. Repeat steps 1 to 2 for each WebSphere Application Server in the cluster.

    To create a DB2 JDBC provider:

    1. On a WebSphere Application Server instance, in the WebSphere Administrative Console navigation tree, click Environment > WebSphere Variables and, in right pane, click DB2UNIVERSAL_JDBC_DRIVER_PATH.

    2. In the Value box on the next screen, type the path to the db2libs directory.

    3. Repeat steps 1 to 2 for each node scope as well as for the Cell Manager scope, inserting the path to the db2libs directory on the relevant node.

    4. Click OK or Apply and in the Messages box, click Save directly to master configuration.

    5. In the navigation tree, click Resources > JDBC > JDBC Providers.

    6. In the drop-down list above the table, select Cluster=<cluster name> as the scope, and then click New.

    7. In the Step 1 pane, set the following configuration and then click Next:

      • In the Database type list, select DB2.

      • In the Provider type list, select DB2 Universal JDBC Driver Provider.

      • In the Implementation type list, select Connection pool data source. Take note that for each Configuration Manager configuration script, the field implementation class name is com.ibm.db2.jcc.DB2ConnectionPoolDataSource.

      • In the Name box, keep the name DB2 Universal JDBC Driver Provider.

    8. In the Step 2 pane, enter the path to the db2libs directory (for example, [appserver root]/db2libs), and then click Next.

    9. In the Step 3 pane, click Finish and then click Save directly to master configuration.

    To create the DB2 JDBC data source:

    1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the provider.

    2. Under Additional Properties, click Data sources and then click New.

    3. In the Step 1 pane, set the following configuration and then click Next.

      • In the Data source name box, type Livecycle - DB2 - IDP_DS.

      • In the the JNDI name box, type IDP_DS.

    4. In the Step 2 pane, type a database name and server name.

      Note: If the port used by the database is not the default port (50000), also specify your alternative port in the Port number box.

    5. Ensure that Use this data source in container managed persistence (CMP) is selected.

    6. Click Next and set the following configurations in the Step 3 pane:

    7. Click Next and, in the Step 4 pane, click Finish.

    8. Click Save directly to the master configuration.

    Configure LiveCycle - DB2 - IDP_DS connection pools

    1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the DB2 Universal JDBC Driver Provider. See To create a DB2 JDBC provider.

    2. Under Additional Properties, click Data sources and, in the right pane, click Livecycle - DB2 - IDP_DS.

    3. On the next screen, under Additional Properties, click Connection Pool Properties and set the properties as follows:

      • In the Maximum connections box, type 30.

      • In the Minimum connections box, type 1.

    4. Click OK or Apply, and then click Save directlyto master configuration.

    Configure the custom property for DB2

    1. In the navigation tree, click Resources > JDBC > Data sources and, in the right pane, click the data source. See To create the DB2 JDBC data source.

    2. Under Additional Properties, click Custom properties and then click New.

    3. In the Name box, type useRRASetEquals and in the Value box, type true.

    4. Click OK or Apply and then click Save directly to master configuration.

    Create the DB2 JDBC data source for Adobe® LiveCycle® Rights Management 10

    Note: This procedure applies only if you have Rights Management installed.

    1. In the navigation tree, click Resources > JDBC > JDBC Providers and click the provider you created in To create a DB2 JDBC provider section.

    2. Under Additional Properties, click Data sources and then click New.

    3. In the Step 1 pane, set the following configurations and then click Next:

      • In the Data source name box, type Livecycle - DB2 - RM_DS.

      • In the JNDI name box, type EDC_DS.

      • In the list under Component-Managed Authentication and XA Recovery Authentication Alias, select the authentication alias created for this data source in 6.2.3 Creating a J2C authentication alias for the database.

    4. In the Step 2 pane, type the database name and server name of the database you created.

      Note: If the port used by the database is not the default port (50000), also specify your alternative port in the Port number box.

    5. Click Next and, in the Step 3 pane, click Finish.

    6. Select the data source you just created to modify additional parameters and set the following configuration:

    7. Click OK or Apply, and then click Save directly to master configuration.

    Configure LiveCycle - DB2 - RM_DS connection pools for Rights Management

    Note: This section applies only if you have Rights Management installed.

    1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the DB2 Universal JDBC Driver Provider you created in To create a DB2 JDBC provider section.

    2. Under Additional Properties, click Data sources and, in the right pane, click LiveCycle - DB2 - RM_DS.

    3. On the next screen, under Additional Properties, click Connection Pool Properties and set the properties as follows:

      • In the Maximum connections box, enter 20.

      • In the Minimum connections box, enter 1.

    4. Click OK or Apply, and then click Save directly to master configuration.

    Configure the custom property for DB2:

    1. In the navigation tree, click Resources > JDBC > Data sources and, in the right pane, click the data source you created in To create the DB2 JDBC data source for Rights Management section.

    2. Under Additional Properties, click Custom properties and then click New.

    3. In the Name box, type useRRASetEquals and in the Value box, type true.

    4. Click OK or Apply and then click Save directly to master configuration.

    6.3.1.1 Set default isolation level

    1. Log in to WebSphere Integrated Solutions Console.

    2. In the WebSphere Administrative Console navigation tree, click Resources > JDBC > Data Sources.

    3. From the drop-down list in the right pane, select Node=[appropriate node name]. All data sources under the node are displayed.

    4. Click LiveCycle - DB2 - IDP_DS with JNDI name IDP_DS.

    5. Click Custom Properties.

    6. Search for webSphereDefaultIsolationLevel property, and click to open it for edit.

    7. Set value as 2. The value 2 denotes Read Committed.

    8. Click Apply and then click OK.

    9. In the Messages box at the top of the page, click Save directly to master configuration.

    10. Restart WebSphere.

    6.3.2 Configuring the Oracle data source

    Configuring the Oracle data source requires you to install the Oracle database drivers, create an Oracle JDBC provider on WebSphere, create the data source on WebSphere, and then configure the corresponding connection pool.

    Install the Oracle Oracle 11g database driver

    1. For each WebSphere Application Server instance, in the [appserver root] directory, create a directory named db_driver.

    2. Copy the ojdbc6.jar for JDK 1.6 driver file from the [DVD_root]/third_party/db/oracle directory to the directory created in step 1.

    Create the Oracle JDBC provider

    1. On a WebSphere Application Server instance, in the WebSphere Administrative Console navigation tree, click Environment >WebSphere Variables and, in the right pane, click ORACLE_JDBC_DRIVER_PATH.

    2. Under General Properties, in the Value box, type the path to the ojdbc6.jar file you created in Configuring the Oracle data source and then click OK.

    3. Repeat steps 1 to 2 for each WebSphere Application Server instance, inserting the appropriate path to the db_driver directory for the node on which the WebSphere Application Server instance resides.

    4. Click Save directly to master configuration.

    5. In the navigation tree, click Resources > JDBC > JDBC Providers.

    6. In the drop-down list above the table, select Cluster=<cluster_name> as the scope and then click New.

    7. In the Step 1 pane, set the following configuration and then click Next:

      • In the Database type list, select Oracle.

      • In the Provider type list, select Oracle JDBC Driver.

      • In the Implementation type list, select Connection pool data source.

    8. In the Step 2 pane, accept the default database class path and then click Next.

    9. In the Step 3 pane, click Finish and then click Save directly to master configuration.

    Create the Oracle JDBC data source

    1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the provider you created in Configuring the Oracle data source section.

    2. Under Additional Properties, click Data sources and then click New.

    3. In the Step 1 pane, set the following configurations and then click Next:

      • In the Data source name box, type Livecycle - oracle - IDP_DS.

      • In the JNDI name box, type IDP_DS.

      • In the list, under Component-Managed Authentication and XA Recovery Authentication, select the authentication alias created for this data source in 6.2.3 Creating a J2C authentication alias for the database

    4. In the Step 2 pane, type the following line in the URL box and then click Next:
      jdbc:oracle:thin:@<server_host>:<port>:<SID>

      where <server_host> is the IP address of the database server, <port> is the port on which the database is listening (default 1521), and <SID> is the service ID of the database.

    5. In the Step 3 pane, click Finish and then click Save directly to master configuration.

    6. Select the data source you just created to modify additional parameters and set the following configuration options:

    7. Click OK or Apply, and then click Save directly to master configuration.

    Configure LiveCycle - oracle - IDP_DS connection pools

    1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the Oracle JDBC driverdata source. See, create the Oracle JDBC provider.

    2. Under Additional Properties, click Data sources and, in the right pane, click Livecycle - oracle - IDP_DS.

    3. On the next screen, under Additional Properties, click Connection Pool Properties and, in the Maximum connections box, type 30.

    4. Click OK or Apply, and then click Save directlyto master configuration.

    Configure the custom property for Oracle

    1. In the navigation tree, click Resources > JDBC > Data sources and, in the right pane, click the data source that you created in To create the Oracle JDBC data source section.

    2. Under Additional Properties, click Custom properties and then click New.

    3. In the Name box, type useRRASetEquals and in the Value box, type true.

    4. Click OK or Apply and then click Save directly to master configuration.

    Create the Oracle JDBC data source for Rights Management

    Note: This section applies only if you have Rights Management installed.

    1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the provider you created in create the Oracle JDBC provider section.

    2. Under Additional Properties, click Data sources and then click New.

    3. In the Step 1 pane, set the following configurations and then click Next:

      • In the Data source name box, type Livecycle - oracle - RM_DS.

      • In the JNDI name box, type EDC_DS.

      • In the list under Component-Managed Authentication and XA Recovery Authentication Alias, select the authentication alias created for this data source in 6.2.3 Creating a J2C authentication alias for the database.

    4. In Step 2 pane, type the following line in the URL box and then click Next:

      jdbc:oracle:thin:@<server_host>:<port>:<SID>

      where <server_host> is the IP address of the database server, <port> is the port on which the database is listening (default 1521), and <SID> is the service ID of the database.

    5. In the Step 3 pane, click Finish and then click Save directly to master configuration.

    6. Select the data source you just created to modify additional parameters and set the following configuration options:

    7. Click OK and then click Save directly to master configuration.

    Configure LiveCycle - oracle - RM_DS connection pools for Rights Management

    Note: This section applies only if you have Rights Management installed.

    1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the Oracle JDBC driver provider created in To create the Oracle JDBC provider section.

    2. Under Additional Properties, click Data sources and, in the right pane, click Livecycle - oracle - RM_DS.

    3. On the next screen, under Additional Properties, click Connection Pool Properties and set the properties as follows:

      • In the Maximum connections box, enter 20.

      • In the Minimum connections box, enter 1.

    4. Click OK or Apply, and then click Save directlyto master configuration.

    Configure the custom property for Oracle:

    1. In the navigation tree, click Resources > JDBC > Data sources and, in the right pane, click the data source that you created in To create the Oracle JDBC data source for Rights Management section.

    2. Under Additional Properties, click Custom properties and then click New.

    3. In the Name box, type useRRASetEquals and in the Value box, type true.

    4. Click OK or Apply and then click Save directly to master configuration.

    6.3.3 Configuring the SQL Server data source

    Configuring the SQL Server data source requires you to install the SQL Server database drivers, create a SQL Server JDBC provider on WebSphere, create the data source on WebSphere, and then configure the corresponding connection pool.

    Install the SQL Server database driver

    • If you have not done so, download and install the SQL Server JDBC Driver 3.0 from the Microsoft Download site by following the site instructions.

      Note: Use SQL Server JDBC Driver 3.0 for both Microsoft SQL Server 2005 SP2 and Microsoft SQL Server 2008.
      Note: Make note of the directory location where you install the driver on your system.

    Create the SQL Server JDBC provider

    1. In the WebSphere Administrative Console navigation tree, click Environment > WebSphere Variables and, in the right pane, click MICROSOFT_JDBC_DRIVER_PATH

    2. Under General Properties, in the Value box, type the path to the sqljdbc.jar file that you created and then click OK.

    3. In the Messages box, click Save directly to master configuration.

    4. In the navigation tree, click Resources > JDBC > JDBC Providers.

    5. In the Scope drop-down list in the right pane, select Cluster=<cluster name> as the level, and then click New.

    6. In the Create new JDBC provider pane, set the following configurations and then click Next:

      • In the Database type list, select SQL Server.

      • In the Provider Type list, select Microsoft SQL Server JDBC Driver.

      • In the Implementation type list, select Connection Pool Data Source.

      • In the Name box, type Microsoft SQL Server JDBC Driver, or accept the default value.

    7. In the Enter database class path information pane, replace the existing entry with one of the following, and then click Next:

      • ${MICROSOFT_JDBC_DRIVER_PATH}/sqljdbc.jar

      Note: If you have set the WebSphere variable MICROSOFT_JDBC_DRIVER_PATH, the database class path information is populated automatically.

    8. In the Summary pane, click Finish and then click Save directly to master configuration.

    Create the SQL Server data source for LiveCycle

    Follow the steps below to create the SQL Server data source for your application server version.

    1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the provider that you created in Create the SQL Server JDBC provider section.

    2. Under Additional Properties, click Data sources and then click New.

    3. In the Enter basic data source information pane, set the following configurations and then click Next:

      • In the Data source name box, typeLivecycle - SQLServer - IDP_DS.

      • In the JNDI name box, type IDP_DS.

    4. In the Enter database specific properties for the data source pane, enter the database name, server name, and port.

    5. In the Setup security aliases pane, set the following, and click Next.

      • In the Component managed authentication alias list, select the authentication alias that you created for this data source in To create a J2C authentication configuration for the data source section.

      • In the Mapping-configuration alias list, select DefaultPrincipalMapping.

      • In the Container managed authentication alias list, select the authentication alias that you created for this data source in To create a J2C authentication configuration for the data source section.

    6. In the Summary pane, click Finish, and then click Save directly to master configuration.

    7. Set the data store helper class for the data source. Do the following tasks:

      • In the navigation tree, click Resources > JDBC > Data sources and, in the right pane, click the data source that you created.

      • In the next screen, under Data store helper class name, select Specify a user-defined data store helper, and replace the existing entry with the following text:

        com.ibm.websphere.rsadapter.GenericDataStoreHelper

    8. Change the statement cache size. Do the following tasks:

      • In WebSphere Administrative Console, click JDBC > Data sources.

      • Click the data source you just created and under Additional Properties, click WebSphere Application Server data source properties.

      • Change the value of the Statement cache size field to 80.

      • Click OK or Apply and the click Save directly to master configuration.

    Configure LiveCycle - SQLServer - IDP_DS connection pools

    1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the provider that you created earlier.

      • Microsoft SQL Server JDBC Driver.

    2. Under Additional Properties, click Data sources and then select Livecycle - SQLServer - IDP_DS.

    3. On the next screen, under Additional Properties, click Connection Pool Properties and, in the Maximum connections box, type 30.

    4. 9. Click OK or Apply and then click Save directly to master configuration.

    Configure the custom property for SQL Server

    1. In the navigation tree, click Resources > JDBC > Data sources and, in the right pane, click the data source that you created in Create the SQL Server data source for LiveCycle section.

    2. Under Additional Properties, click Custom properties and then click New.

    3. In the Name box, type useRRASetEquals and in the Value box, type true.

    4. Click OK or Apply and then click Save directly to master configuration.

    Create SQL Server data source for Rights Management

    Follow the steps below to create the SQL Server data source for your application server version.

    1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the provider that you created in Create the SQL Server JDBC provider section.

    2. Under Additional Properties, click Data sources and then click New.

    3. In the Enter basic data source information pane, set the following configurations and then click Next:

      • In the Data source name box, type Livecycle - SQLServer - RM_DS.

      • In the JNDI name box, type EDC_DS.

    4. In the Enter database specific properties for the data source pane, in the Data store helper class name box, replace the existing entry with the following:

      com.ibm.websphere.rsadapter.GenericDataStoreHelper

    5. In the Setup security aliases pane, set the following, and click Next.

      • In the Component managed authentication alias list, select the authentication alias that you created for this data source in To create a J2C authentication configuration for the data source section.

      • In the Mapping-configuration alias list, select DefaultPrincipalMapping.

      • In the Container managed authentication alias list, select the authentication alias that you created for this data source in To create a J2C authentication configuration for the data source section.

    6. In the Summary pane, click Finish, and then click Save directly to master configuration.

    7. Change the statement cache size. Do the following tasks:

      • In WebSphere Administrative Console, click JDBC > Data sources.

      • Click the data source you just created and under Additional Properties, click WebSphere Application Server data source properties.

      • Change the value of the Statement cache size field to 80.

      • Click OK or Apply and the click Save directly to master configuration.

    Configure LiveCycle - SQLServer - RM_DS connection pools

    1. In the navigation tree, click Resources > JDBC > JDBC Providers and, in the right pane, click the provider that you created earlier

      • SQL Server Provider.

    2. Under Additional Properties, click Data sources and then select Livecycle - SQLServer - RM_DS.

    3. On the next screen, under Additional Properties, click Connection Pool Properties and, in the Maximum connections box, type 20.

    4. Click OK or Apply and then click Save directly to master configuration.

    Configure the custom property for SQL Server

    1. In the navigation tree, click Resources > JDBC > Data sources and, in the right pane, click the data source that you created.

    2. Under Additional Properties, click Custom properties and then click New.

    3. In the Name box, type useRRASetEquals and in the Value box, type true.

    4. Click OK or Apply and then click Save directly to master configuration.

    Configure integrated security on Windows

    1. In the navigation tree, click Resources > JDBC > Data Sources and, in the right pane, click IDP_DS.

    2. In the right pane, under Additional Properties, click Custom Properties, and on the next screen, click integratedSecurity.

    3. On the next screen, under General Properties, type true in the Value box.

    4. In the navigation tree, click Resources > JDBC > Data Sources and, in the right pane, click Livecycle - SQLServer - RM_DS.

    5. In the right pane, under Additional Properties, click Custom Properties, and on the next screen, click integratedSecurity.

    6. On the next screen, under General Properties, type true in the Value box.

    7. Click Apply and then click Save directly to master configuration.

    8. On the computer where WebSphere is installed, add the sqljdbc_auth.dll file to the Windows systems path (C:\Windows). The sqljdbc_auth.dll file is in the same location as the Microsoft SQL JDBC 3.0 driver installation (default is [InstallDir]/sqljdbc_3.0/enu/auth/x86).

    9. Modify the Log On As property of the Windows service that starts the WebSphere Application Server (node name) by doing the following tasks:

      • Click Start > Settings > Control Panel > Administrative Tools > Services.

      • Right click [node name] and select Properties.

      • On the Log On tab, select This account and select a valid user account other than Local System, then click OK.

    10. Change SQL Server’s Security from Mixed mode to Windows Authentication only.

    // Ethnio survey code removed