Updating the DataSource value

In WebSphere Commerce releases prior to WebSphere Commerce 6.0, a global default DataSource reference was defined. All independent EJB projects that did not explicitly define a DataSource would use the default DataSource. In WebSphere Commerce 6.0 this default value is not set and all EJB projects must now define a specific DataSource.

About this task

It is recommended to check the DataSource value in all custom EJB projects and others that you modified based on IBM EJB projects. If you are basing your custom projects on IBM EJB projects you can accidentally overwrite the correct values. It is a good practice to double check it before generating the deployed code.

Procedure

In the Enterprise Explorer view , expand EJB Projects and then expand the EJB project that is being migrated. Double click on Deployment Descriptor to open up the deployment descriptor editor.
In the EJB Deployment Descriptor Editor, in the Overview tab, scroll down to the JNDI - CMP Connection Factory Binding section and in the JNDI name field enter the value that matches your database type. For example, if your instance name is demo, enter the following values:
- jdbc/WebSphere Commerce DB2 DataSource demo
- jdbc/WebSphere Commerce Cloudscape DataSource demo
- jdbc/WebSphere Commerce Oracle DataSource demo
Save your changes and Regenerate your deployed code .

Note: You may need to regenerate your CMP using Rational Application Developer Version 7.5.5.1, or a higher Version 7.5 fix pack when migrating to a significantly more current version of your database engine.