If you have not already done so, follow the steps to deploy the example Agency EJB from the Day04/exercise directory on the Web site using deploytool.

Examine the information displayed by deploytool and make sure that you can identify where the resource reference for the Agency JDBC connection is set, where the environment reference for the agency name is set, and where the JNDI name of the Agency EJB itself is set.

From within the Day04/exercise directory run the command “asant verify-j2ee-ri” to verify your application.

Use the appclient command shown in today's lesson and run the SimpleClient example. Make sure that this client runs without errors and successfully lists all the customers in the agency database.

Try changing the name under which the EJB is registered in JNDI using deploytool. Change the JNDI name used by your client to find the Agency EJB and make sure that it still works.

Use the asant build files instead of deploytool to compile, build, verify and deploy the example Agency application.

Edit the dd/agency/sun-j2ee-ri.xml file (make a backup first of course) and change the JNDI name for the Agency Session EJB. Change the JNDI name used by your client to find the Agency EJB and make sure that it still works.