Configure the WAS data source

 

+

Search Tips   |   Advanced Search

 

Installed applications use data sources as resources to obtain connection to relational databases. To create these connections between an application and a relational database, WAS uses the driver implementation classes that are encapsulated by the JDBC provider, which is an object that represents vendor-specific JDBC driver classes to WAS. For access to a relational databases, applications use the JDBC drivers and data sources that you configure for WAS.

 

Procedure

  1. Start the console.

  2. Click...

    Security | Secure administration, applications and infrastructure | Configuration | Java Authentication and Authorization Service | J2C authentication data | New

    Enter the Alias, User ID and Password.

  3. Click Ok.

  4. On the console, expand...

    Resources | JDBC | JDBC Providers | Scope | Node | New

    ...to create a new JDBC driver.

  5. Select, in this order...

    1. Database type
    2. Provider type
    3. Implementation type
    4. Name

    The Name automatically fills based on the implementation type you choose.

  6. Click Next and configure the database class path. Click Next.

  7. On the Summary page, click Finish.

  8. Click Save to save your selections. The JDBC providers page then appears.

  9. On the console, click..

    Data sources | New

    ...to create a new data source. Enter the Data source name and the JNDI name, and choose the authentication alias from the drop-down list in Component-managed authentication alias. The JNDI name should match the datasourceName value set in wimconfig.xml. By default, it is jdbc/wimDS.

    For Cloudscape 10 V1 embedded databases, leave the Component-managed authentication alias field set to NONE.

  10. Click Next.

  11. Enter the Database name and deselect the checkbox, Use this data source in container managed persistence (CMP). Click Next.

  12. On the Summary page, click Finish.

  13. The Data sources page displays. Click Save, Then select the check box for the authentication alias previously created. Click Test Connection. The message should indicate that the connection is successful. Ignore any warnings, and then click Next.

  14. Save the configurations, and restart WAS.



Configure an entry mapping repository in a federated repository configuration
Set up an entry mapping repository, a property extension repository, or a custom registry database repository using wsadmin commands
Configure a property extension repository in a federated repository configuration