Camel on Google App Engine Tutorial
Goal of this tutorial is to get a non-trivial Camel application running on Google App Engine (GAE). For developing that application the Camel Components for Google App Engine are used. The example web application generates a weather report for a city that is entered by the user into a form and sends the weather report via email to either the currently logged-in user or a user-defined receiver. The following figure gives an overview. Users of this application need to login with their Google account.
POSTed form data are dispatched to the Camel application via the ghttp component. The application transforms the report request and enqueues it with the gtask component for further background processing. It then generates an immediate HTML response containing information about the city and the receiver of the report. The response also contains a link logging out from the application. In the background, the application retrieves weather data from the Google Weather Service, transforms the data to generate a simple weather report and sends the report by email via the gmail component.
Clients other than web browsers may also interact with this application by POSTing the form data and an authentication cookie. At the moment the example application doesn't include a standalone Java client that demonstrates how to do that. This is work in progress. In the meantime, refer to this blog post for instructions how to access security-enabled GAE services using the Google ClientLogin API.
- Sign up for a Google App Engine accountif you don't have one.
- Create a new application via the admin console or reuse an existing one for uploading the example.
- Install the Google App Engine SDK for Java. This tutorial has been tested with version 1.3.0.
First, checkout the sources from the Camel code repository.
camel-example-gae/src/main/webapp/WEB-INF/application-web.xml file and replace the template application name
replaceme with the name of the application that you created in the previous section. Optionally, adjust the version number if needed.
Then go to the
camel-example-gae directory and enter
This will create the application
war file in the target directory. Finally use the
appcfg command-line tool of the App Engine SDK to deploy the application.
version needs to be replaced with the version of Camel you're using. You will be prompted for the email address and password of your Google App Engine account. After deployment the example application is ready to use.
In the following, the application name
camelcloud will be used as an example. If you deployed the example application somewhere else, use your application name instead. Go to
http://camelcloud.appspot.com. The application will redirect you to a login page (see also Security for Camel GAE Applications).
After login, the application displays the tutorial's main page where you can enter the name of a city and optionally enter an email address where to send the waether report. If you check
Send report to me the report will be send to the email address that you used for login.
Submit the response is
home link brings you back to the main page, the logout link is to logout from the application (which brings you back to the login page). In the background, the current weather conditions for the user-entered city will be retrieved from the Google weather service and a formatted weather report will be send by email. Submitting the form the first time initializes the application on Google App Engine which can take several seconds. Subsequent submissions (within a certain time frame) are served much faster. Check your emails and you should now see a new email with subject
Wheather report and content similar to this one:
The report is partly internationalized, depending on the language settings of your browser.
TutorialRouteBuilder implements the message processing routes shown in the #Overview section. Input form data are received via the ghttp component. After receiving the request a
RequestProcessor adds the form data and information about the current user to a
ReportData POJO. The
ReportData object is then serialized and queued for background processing. Queueing messages on GAE is done with the gtask component. After adding the
ReportData object to the queue an HTML response is generated with the
Background processing of the queued messages starts
from("gtask://default"). The first step is to enrich the previously generated
ReportData object with data from the Google weather service. The service URL is dynamically constructed by setting the
Exchange.HTTP_QUERY header to
weather=<city>. For example, if the user entered
London in the city field of the form the resulting URL is ghttp://www.google.com/ig/api?weather=London. The weather service is accessed with the ghttp component and the weather service response is aggregated into the
ReportData object using a custom aggregator returned by the
reportDataAggregator() method. Generating a simple weather report from
ReportData is done by the ReportGenerator. The report is then sent by email with the gmail component.