Deploying an application on Google App Engine from Studio
The gadget spec URL could not be found

Is deploying the application as simple as developing it on Studio?

If easy-to-use, intuitive spreadsheet interfaces, visual modeling environment and point-and-click selectors simplified application development using OrangeScape, then click-to-deploy feature makes application deployment a breeze. The application can be deployed on Google App Engine by the click of a button.

Let’s give it a try and see for ourselves!

If you are using Studio for the first time and haven’t read the chapter "Getting started with OrangeScape", then it is recommended that you read the sections “Creating your application on OrangeScape Trial Studio” and “Creating an application on Google App Engine” before you proceed further.

  Deploying your first application

In the earlier chapter "Creating an application on OrangeScape Trial Studio", we created an application using an existing template "Learning Guide App Template". In this section, we will deploy that application on Google App Engine from OrangeScape Studio. This application deployment exercise serves two purposes:
  1. A trial run to test your development environment and also get familiarized with the deployment process
  2. An opportunity to deploy the example application and explore it to understand the template application
The application can be deployed on Google App Engine by the click of a button. In the “Deploy Dialog” box, enter your application name i.e. the domain name from where the application will be served, Google App Engine Id associated with that domain name (in our case, your ID) and password, and click on the deploy button.

Follow the directions given below to deploy the application.

 Log into OrangeScape Trial Studio.

Click on the "launch" link to open the application workspace of your online tee design application.

The "Click-to-deploy" button (highlighted at the top of the page) is enabled only within the studio perspectives. Hence, any one of the data models must be opened to deploy the application.
  You can see that there are two folders under the root application folder: Customer and System folder. Click on the customer folder.

The customer folder contains the customer and customer address models implemented as part of the template application, while the system folder contains the default system models, which gets automatically created for every new application.

Double-click on the customer model. The parameters in the customer model will be displayed and an option to open the model will be available.

Click on the open button to open the customer model.

Opening a model allows you to navigate to any of the other perspectives. Also, the deploy button is enabled.

Click on the "Deploy" button.
 "Deploy Dialog" box will be displayed.
  Enter the application name i.e. the appspot domain that you created on Google App Engine, your Google App Engine id and password, and then click on the "Deploy" button.
While deploying, you can avoid re-typing the authentication details by selecting the "Remember me" check box.

How do I check the deployment status?

The information about the deployment status is displayed on the Studio page as shown in the screen captures below.  Updates are provided at three different stages:
  • Firstly, while establishing connection with the server.
  • Secondly, while deploying into Google App Engine.
  • Thirdly, on successful completion of the deployment.
Should the need arise, these messages help you isolate and identify the cause of deployment failure. In the event that you get stuck and not able to proceed due to issues with deployment, here's where you can find help

Click here to learn more about how you get help.

Connecting to server...

Deploying into Google App Engine...

Successfully Deployed!

What's Next?

Congratulations! You have deployed your first application on Google App Engine. You now have an application running on Google App Engine live on the web at In the next section, we will explore the template application and review its functionality.