After completing the one-time steps detailed at Deployment with GXcloud Deployment Services, follow these steps for every new application you need to deploy: select environment, build, and deploy.
Open your Knowledge Base in GeneXus and activate the Version and Environment from which you want to deploy. Typically this is not your development environment, it is your Test or Pre-production environment; the one from which you get ready to deploy to production.
: This environment should not be built using Cloud Prototyping (i.e. Deploy to cloud property
] should be set to No) because of the associated SLA (target webapps and databases are deleted when not used).
Make sure that the Environment is up to date: Rebuild, Build or Run your application, Test it.
Enter your GeneXus Account user name and password
The name will be used for the Virtual Directory. For example, if you enter "LightCRMDemo" as application name, its URL will be similar to http://sandboxnet.genexusnet.com/LightCRMDemo
For the Cloud field, select the Sandbox, or the name of your own GeneXus Cloud subscription.
Finally, select a target compatible to your environment. For example, if your environment is C# / SQL Server and you are deploying to the Sandbox cloud, select "NetSQL"
To deploy the first version using GXcloud MSBuild Tasks you use the DeployNewApp task.
Check for one of the samples exposed here.
In this case, first of all, you need to create a GAM Package File using GAM Deploy Tool: Export Data option (*).
And then follow the steps 1,2 and 3 above mentioned. The wizard will let you enter the GAM credentials. Note that Manager User and Manager Password are the ones of the original GAM installation, and Admin Password is the one you want to set in the target (production) GAM installation.
(*) In GeneXus X Evolution 3 Upgrade 5 or lower, use the standalone GAM Deploy Tool, not the one included in GeneXus IDE.
In this case, first of all, you need to create a Business Process Deploy File using GXflow Production Environment.
And then follow the steps 1,2 and 3 above mentioned. The wizard will let you enter the BP Deploy file.
Note that all the fields you enter using the Extension, have their corresponding ones in the GXcloud MSBuild Tasks.
GeneXus Cloud detects that your KB has smart devices and in that case, for compatibility reasons, it generates a specific Services URL.
For example, if your application name is "MyApp", it will generate a URL like example.com/MyApp and another example.com/MyApp_Services.
After Deploying the applications, you have to Set Services URL property to the generated Services URL (e.g. example.com/MyApp_Services), build your Android or iOS app again and then deploy it.
Why does it create a Services URL ? Because of compatibility reasons. This helps you maintain services compatibility in further updates. More Information HowTo: Update a production Environment with GXcloud Deployment Services
If you use the Extension, once you hit 'Deploy' your app will get Deployed. Check the output window for details. Once the deployment process finishes, you'll get URLs to open or manage your app.
If you use the MSBuild tasks, after deploying, open GXcloud Manager Console, log in, and click on the link of the Main branch of your Application.