P. 1
Develop and Deploy Web App Using Google App Engine Demo

Develop and Deploy Web App Using Google App Engine Demo

|Views: 8|Likes:
Published by Pratik Bothra

More info:

Published by: Pratik Bothra on Nov 05, 2012
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





Google AppEngine tutorial

Eclipse Indigo version

Hello world

1. Assumptions
Java and Eclipse already installed. I used installation of v 3.6 Helios for Java EE Developers, but anything from 3.3 should be Ok. If this assumption happens to be wrong – visit http://www.eclipse.org/downloads/.

2. Google Plugin for Eclipse
Plugins for Eclipse could be installed from very logical place in the menu: Help->

com/eclipse/plugin/3..6 for Eclipse 3.google.Install New Software and [Add.google.5 (Galileo) it’s http://dl.] button Location is specific for Eclipse version – for Eclipse 3.4 (Ganymede) or where it will be for 3.com/eclipse/plugin/3. Next step = actually install it .7 (Indigo) once Google will release it.6 (Helios) it’s http://dl.5 You got the idea and can guess url for Eclipse 3.

Google Plugin will add new toolbar .

so you might want to check availability of app.google. id before hand . In turn it’s requires gmail and ability to receive SMS (Google will text you a verification code). or at least to deploy your application to the Google cloud you need a AppEngine account at http://appengine. 3. There a loot of apps already created.with New Web Application Project and Deploy App Engine Project buttons.com/ . AppEngine account Before creating “New Web Application Project “ via [g+] button.

As you see from “Create an Application” screen. “Application Identifier” will be part of the url. it also will show up on administration console of AppEngine .


config files for JDO. just few pre-generated files and libraries specific for AppEngine . in web artifacts it will create lib folder with bunch of jars. Log4j.html and few more configuration files: java logging. web.4. New Web Application Project AppEngine “New Web Application Project” is not very different from regular web project – structure is really the same.xml .xml and appengine-web. index. It will create for you Servlet named after project.

name (have to match Application Identifier from step 3) and version.100}$' For example version ‘b’ .xml provides app.appengine-web. Version is cool way to have multiple instances of application to be deployed simultaneously. So. you can test several versions and promote/rollback any them with button click BTW version doesn’t have to be number – just confirm to regex '^(?!-)[a-z\d\-]{1.

but recompiled class wouldn’t get updated by another RunAs. you’ll also have to stop Jetty.regular Eclipse way it will start Jetty and show console where messages from Jetty and stdout of your app will go. 6. Let’s Run There several ways to run: Locally in Jetty – just right-click in project explorer and select Run As->Web Application . Unfortunately Jetty will not show up in the servers view. hence control ower it rather limited – html changes in project will be reflected immediately on localhost:8888. Deploy to appspot.5.com As easy as click on “Deploy App Engine Project” button .

appspot.com (app-enghw.com in our case) and [version].appspot.com – particular version.App Engine project settings allows you to change App ID and Version Now Default (not latest!) version available at [appname] .appspot.[appname] . .

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->