Setting Up JNDI

To set up the Java Naming and Directory Interface (JNDI), perform the following tasks:

Create the JDBC Provider for Delinea Driver

  1. Select WebSphere admin console > Resources > JDBC Provider > New.

    alt

  2. Enter the following information and select Next.

    • Database Type: User-defined database type.
    • Implementation class name: com.delinea.jdbc.DelineaConnectionPoolDataSource.
    • Name: Provide a name of your choice (for example, "Delinea JDBC Provider onlinebook").

    alt

  3. In the Class path box, enter the location of the Delinea Proxy driver JAR file (for example, the Delinea jar file in the WEB-INF/lib folder of the application) and select Next.

    alt

  4. When the summary information is displayed, select Finish.
    alt

Creating a Data Source for the Delinea JDBC Proxy Driver

  1. To create a data source, select WebSphere admin console > Resources > Data sources > New.

  2. Enter the following information and select Next:

    • Data source name: Provide a name of your choice.
    • JNDI name:JDBC/Delinea (this configures in the configuration file of the application).

    alt

  3. In the Select JDBC provider section, select Select an existing JDBC provider.

    alt

  4. In the Enter database specific properties for the data source section, select Use this data source in container managed persistence (CMP) and select Next.

    alt

  5. In the Setup security aliases section, select (none) and then click Next . Select Finish.

    alt

    The Summary is displayed.
    alt

  6. Select Resources > JDBC and select the created JDBC Provider.

  7. Select the Isolate this resource provider checkbox.

    alt

    The above-created data source and JDBC provider are displayed in the Data source section.

    alt

  8. Go to Applications > **JDBC > Data Source > Delinea Data Source (** for example, “jdbc/delinea” > WebSphere Application server data source properties > Statement Cache Size) to update the Statement Cache Size in the Delinea Data Source.

  9. Set Statement cache size to 0 because the Delinea driver does not implement any caching-specific logic. It is forwarded to the native driver to handle.

    alt

Update an Existing Native Data Source

If you have already configured the native JDBC Provider and data source (for example, jdbc/book, jdbc/student), use the following information for the Delinea Proxy Driver connection.

alt

  1. Select WebSphere admin console > Resources > JDCB > Data sources >; then select Created Data source > Security settings.

  2. From the Security settings window, select (none) for all the authentication alias parameters.

    alt

  3. Restart the WebSphere server and test the application.

If the JDBC Provider Database type is SQL Server

  1. Select SQL Server for the Database type.

    alt

    The database connection details of the native Data source are displayed.

    alt

If the JDBC Provider Database type is User-defined

  1. Select User-defined for the Database type.

    alt

  2. The Data Source using that JDBC provider must set the Custom Properties.

  3. Select DataSource > Data Source Name > Custom Properties.

  4. Enter the following information:

    • portNumber: Port number of the database.
    • relaxAutoCommit: Set to true.
    • databaseName: Database name that the application is using.
    • serverName: Server name in which the database was created.

    alt

Logs for a DataSource Connection

Logs should be written in the following sequence:

  1. CommonDataSource: Inside GetBaseDataSource
  2. DelineaDriverHelper: Inside DelineaDriverHelperinit
  3. DelineaDriverHelper: Driver configuration read successfully
  4. CommonDelineaDataSource: Database credential fetched successfully from Secret Server