Configuring JDBC data source/JNDI name in Rational application development Environment 6.0 for Oracle

Configuring the JDBC jndi name in RAD ia a lot harder than it needs to be.
Here is how to do it.

1. View the J2EE perspective
2. Under “Enterprise Applications” click on your EAR folder
3. Under META-INF
4. Double click “application.xml”. This allows you to edit the deployment descriptor.
5. Click on the deployment tab.
6. Now scroll down to the bottom of the window, and you will see arrow to the left of the word “Authentication”, click it.
7. You should now see the JAAS authentication list
8. Click “add”, fill out

a. Alias: headleyalias (made up name used later)
b. Username: headleyuser (Database user name)
c. Password: headleyuser (Database password)

9. Now under your “server” tab, deploy/publish your EAR and start your the Websphere 6.0 development environment
10. Right click the server and select “Run the administration console”. This will start admin console in a new window.
11. Click Login (any login will work)
12. Click “Resources”
13. Click “JDBC Providers”
14. Scroll to bottom of display and click “new”, and fill out the following fields

a. Name: Oracle JDBC Driver
b. Description: Oracle JDBC Driver
c. Class path: C:/Oracle/Ora92/jdbc/lib/classes12.zip (on my machine)
d. Implementation class name: oracle.jdbc.pool.OracleConnectionPoolDataSource
e. Apply and OK
f. Don’t forget to save.

15. Now from the JDBC provider window click “Oracle JDBC Driver” which you just created.
16. Now on the right side of the window under “Additional properties”, click “data sources”.
17. Click “new”, and fill out the following fields

a. Name: Oracle JDBC Driver DataSource
b. JNDI name: jdbc/myapp ( This is the JNDI name you need to use to look up this data source)
c. Data store class name: Select a data store helper -> Oracle 9i and prior data store helper
d. Component-managed authentication alias: select “headleyalias” (your alias)
e. Component-managed authentication: select “headleyalias” (your alias)
f. URL: jdbc:oracle:thin:@servername:1521:databasename
g. Test your connection
h. Apply and OK
i. Don’t forget to save.

18. Now under your “serv

er” tab, deploy/publish your EAR and restart your the Websphere 6.0 development environment.