Configure the WAS data source

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 WebSphere Application Server. For access to a relational databases, applications use the JDBC drivers and data sources configured for WebSphere Application Server.

1. Start the WAS appservers administrative console.

2. Click Security -> Global security.

3. On the Configuration panel, under Authentication, expand Java Authentication and Authorization Service and click J2C authentication data.

4. Click New and enter the Alias, User ID and Password.

5. Click Ok.

6. On the WAS administrative console, expand Resources. Expand JDBC then click JDBC Providers.

7. In the Scope section, choose the Node level from the drop-down list.

8. Click New to create a new JDBC driver.

9. Select, in this order, the Database type, Provider type, Implementation type and Name. The Name automatically fills based on the implementation type we choose.

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

11. On the Summary page, click Finish.

12. Click Save to save the selections. The JDBC providers page then appears.

13. On the WAS administrative console, click Data sources.

14. Click 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 Apache Derby v10.2 embedded databases, leave the Component-managed authentication alias field set to NONE.

15. Click Next.

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

17. On the Summary page, click Finish.

18. The Data sources page displays. Click Save, and 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.

19. Click Environment > WebSphere Variables.

20. In the Scope section, select Cell from the drop-down list.

21. Click New to create a variable.

22. In the Name field, enter VMM_JDBC_CLASSPATH.

23. In the Value field, enter the complete path to the JDBC driver library files separated by a colon (:) for UNIX or Linux or a semicolon (;) for Windows. For example, the path to Linux or UNIX is as follows: /opt/IBM/SQLLIB/java/db2jcc.jar:/opt/IBM/SQLLIB/java/db2jcc_license_cu.jar.

24. Click OK. Additionally, copy the specified JDBC driver library files in the ${WAS_HOME}/lib directory of each installed WebSphere Application Server node.

25. Save the configurations, and restart WebSphere Application Server.

    In a clustered environment, we must also stop and restart the dmgr and the node agents.

Related tasks

Configure an entry mapping repository in federated repository

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 federated repository