In DG3 there are two methods of deploying a new web application:

1. Local deployment
2. Remote deployment

The local deployment is used if you are running DG3 development on the same computer as you deploy web application. The remote deployment is used when deploying on another computer than the one you are working on (it is possible to use remote deployment on the same computer as you are working on to test it out by setting up the remote server as localhost or 127.0.0.1). The difference between the two are that remote deployment need DG3DS (DataEase Generation 3 Deployment Server) and local deployment don't.

Requirements to the DG3 deployment server

The DG3 application is run in a real production grade web server environment when deployed. This means that you can not have any other web servers (like IIS) using port 80. Please make sure any such server is uninstalled or at least disabled.

This is how a new local deployment is done

1. Make sure that all parts of you web application is saved.
2. Rebuild the application
3. Open DG3 deployment module
   
4. Find you application in the All applications list (if it is already in the Deployed application list, this is not a new deployment and this document do not apply as then you are updating a deployed application)
5. Open your application
   
6. Change "Web server name" to the named server you are going to use. If this is your first test application you might use localhost as the name.  If you have more than one application on the deployment server the other application can not have the same "Web server name" as your new application (that is you can't use localhost twice on application that is deployed to you local DG3 http server). To simulate different names on apps, simply locate your hosts file and add a new entry to 127.0.0.1 pointing on the name of choice. 
7. If you want your application deployed to another name than the one given in DG3, change the "Deployed name" field and press save (You must press the save button right after the change to commit the move on disk before deployment and have at least version 0.14.1031). The application is closed and reopened using the new name when save is done.
8. Press the deploy icon and you will see all files is copied and configuration is changed
9. Now press start the application and the web server and you are ready to test your deployed application

This is how a new remote deployment is done

1. Make sure that all part of your web application is save
2. Rebuild the application
3. Open DG3 deployment module
4. Make sure your DG3DS is running on the remote server you are going the deploy your application
5. Make sure you are allowed to access port 81 on this server by opening the firewall or connection using vpn
6. Find your application in the All applications list and make sure it is not in the deployed application list
7. Open your application
8. Change "Web server name" to the name the application is going to be using on the internet. Add it without any pre or post fix, only the server name as shown by the example (ex. www.dataease.com)
9. Set a check in the Deploy on remote server
   
10. Add the url to the deployment server (DG3DS) using a full URL (ex. http://www.myserver.com.1:81) 
11. if you want another name in the Deployed application list, now it the time to change Deployed name (it will create a new directory name on the deployment server, so you can not change this later without redeploying the full server). The reason for changing the name is to be able to deploy the same application to more than one server ex. a test and a live server
12. Make sure you press the Save button
    
13. Press the deploy icon and you will see files uploaded and the application created on the server
14. Now you can press Start application and Start server icon and the application is started on the remote server

Things to remember when doing a update to already deployed application

When you do changes to the settings like run as service for an application deployed on a remote server, make sure you always press the save button to commit the settings changes before you press the deploy button.

1.