Skip to main content
Jump to: navigation, search

EDT:Tutorial: RUI With Database Lesson 11

Access a database with EGL Rich UI

< Previous | Next >

Lesson 11: Deploy and test the payment application

During the deployment process, EGL creates HTML files and server-specific code to match your target environment.

Deployment is a two stage process:

  1. Internal deployment, when you deploy your handlers to a web project.
  2. External deployment, when you deploy the web project to an application server.

After you deploy the tutorial application internally, you can run it on an application server in the workbench.

Edit the deployment descriptor

The EGL deployment descriptor manages the internal deployment and is created automatically in each EGLSource folder. The main handler is in the PaymentClient. You use the EGL deployment descriptor in the PaymentClient/EGLSource folder.

To edit the EGL deployment descriptor:

  1. In the EGLSource folder, double-click the PaymentClient.egldd file. The EGL deployment descriptor opens in the deployment descriptor editor. EGL automatically added the embedded handlers to the list of Rich UI handlers to deploy.
  2. Because you are using a dedicated service, you do not need to add information to the Service Bindings Configuration section. The list is empty.
  3. Under Deployment Target, next to the Target project field, click New.
    The Overview page of the EGL deployment descriptor shows no services to generate, and shows the list of your handlers under Rich UI Deployment. The Dynamic Web Project wizard opens.
  4. In the Project Name field, enter the name PaymentWeb. Any web project is acceptable. You are creating a simple one for the purposes of the tutorial.
  5. For Target runtime, select Apache Tomcat v6.0. The value of the Configuration field changes automatically to match the new runtime environment.
  6. Add the SQL database binding to the deployment descriptor as you did for the ServiceProject deployment descriptor as described in the section Create binding to database connection . If you chose to use runtime binding using an application server JNDI name to reference the database resource instead of hard coded binding, make sure that you have copied the derbyclient.jar file to the lib directory in the Tomcat install directory.
  7. Click Finish. EGL creates the web project and re-displays the deployment descriptor.
  8. Save and close the deployment descriptor.

Deploy the Rich UI application

You can now launch the deployment process:

  1. In the EGLSource folder, right-click the PaymentClient.egldd file.
  2. Click Deploy EGL Descriptor.
    The Deploy EGL Descriptor option
    The deployment process requires no further action on your part. The process copies many files and might take several minutes.
  3. If the Tomcat server shows a status of Restart, consider that statement a directive: restart the server by right-clicking the server name and click Restart. When the server has restarted, the status is Started, Synchronized.

Run the generated code

  1. To run the internally deployed code, focus your attention on the target project, PaymentWeb. In the PaymentWeb/WebContent folder, find PaymentFileMaintenance.html.
  2. Right-click the file name and click Run As > Run on Server
    The Run on Server option is shown in the menu
    The Run On Server window opens.
  3. In the Run On Server window, select the appropriate server and click Always use this server when running this project. Click Finish.
    The Run On Server window for Tomcat
  4. If you are using Tomcat and see a page not found error (404), check whether the server is showing a Restart status. If so, restart the server and refresh the page.
    The Server window asks you to restart the server.
    The page opens.
  5. Test the application by adding, deleting, and modifying payment records.

Related concepts

  • Help topic: Introduction to EGL generation and deployment

Lesson checkpoint

You learned how to complete the following tasks:

  • Edit a deployment descriptor to deploy a Rich UI handler.
  • Run the application on an application server.

< Previous | Next >

Back to the top