Adding an SQL database binding to the EGL deployment descriptor

An SQL database binding gives details necessary to access an SQL service.

1. Open the EGL Deployment Descriptor editor by double-clicking the name of an EGL deployment descriptor.
2. Click Resource Bindings. The Resource Bindings Configuration tab is displayed.
3. Click Add. The Add a Resource Binding page is displayed.
4. Click SQL database binding and then click Next. The Add a SQL Database Binding page is displayed.
5. On the Add a SQL Database Binding page, you have several options:
   • To specify where the binding details are stored, select one of the first three options:
     • To use connection details that are or will be specified in an Eclipse connection profile, select the first option. Reference an existing connection profile or press New to define one.
     • To specify connection details directly in the binding definition, select the second option instead.
     • To use an JNDI data source that is or will be defined in the application server, select the third option. In this case, the details that you specify are the only ones on this page.
   • If you intend to deploy your code to the Apache Tomcat server, you can configure a JNDI entry:
     • Define most of the binding details by specifying the first or second option.
     • Also select the fourth option. The JNDI name and other details that you specify here are associated with the details from the first or second option. The information is packaged during EGL deployment.

     The JNDI details result in a container-based authentication, which means that the server stores any user ID and password needed for database access.

   If you select the first option, any subsequent change to the Eclipse connection profile is available to your code at development and deployment time. After the EGL deployer has packaged the application, though, the changes have no effect on the deployed code unless you redeploy the application.