b. Go back to the top of the page and set the JNDI name for the data source to be used, jdbc/lree, from the menu. c. Click Apply. If you scroll back to the bottom of the page you should see jdbc/lree under JNDI name for the EJB. d. Scroll up a little and select the authentication alias from the Select authentication data entry menu. e. Click Next. 10.For step 6, perform the following steps: a. Scroll to the bottom of the panel and click the icon used to select all EJB modules form the list. b. Scroll back to the top and select jdbc/lree JNDI name for the data source to use with these modules. c. Click Apply. d. Scroll back down to select the authentication alias. e. Click Next. 11.Take the defaults from steps 7­10. If you get any security or resource warnings, ignore them by clicking Continue. 12.On the last page, click Finish. The deployed code must be created, so this takes some time. 13.When the application is successfully installed, save and synchronize. Starting the LREE applications Before continuing it is worth checking to make sure that all of the LREE application servers start successfully: 1. On the administrative console, go to Servers Application servers. 2. Select one or more of the LREECLUSTER application servers. Click Start. 3. After a few minutes you should see a message indicating the result of the operation. 4. Make sure that you test each LREECLUSTER. 6.4 Testing the Long-Running Environment You now have a long-running environment (LRS and LREE) configured on WebSphere Extended Deployment for zOS and you have verified that all of the LRE and LREE application servers and applications have started successfully. At Chapter 6. Establishing the long-running environment 135