ppyordanov
commented
9 years ago In order to deploy the server code after the initial configuration, the FileZilla FTP client was used. I had to use an SFTP connection (Secure/SSH File Transfer Protocol) as the server would not let me connect using the regular /not so secure/ FTP I have been using for other websites that I am hosting elsewhere. I have setup an SSH key to be used for authentication but will be adding it to the server once deployment is 100% complete (using Putty and PuttyGen for public and private key generation). Using the "Interactive" login type I connected to my root directory and directly uploaded the source files (more convenient than Git at least on this stage).
- An ever-occurring issue were the timeouts that caused the need to reconnect to the server (meaning re-entering user credentials each time) every 30-50 seconds. Even after increasing the limit to 500 or 0 (disabling timeouts) those were still occurring but this might be due to a faulty router/ switch somewhere on the network. However, increasing the timeout duration is still much more convenient than the default settings.
- Before successfully running the Spring MVC application, Apache Maven needed to be installed. The deployment ran into some issues as Maven detected duplicate dependencies and there were some deprecated plugins (maven-compiler-plugin and maven-surefire-plugin) preventing it from starting; I updated those to their latest versions accordingly by checking the central Maven dependency repository http://search.maven.org/ (there are no problems running these on localhost):
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.2</version>
<configuration>
<source>1.6</source>
<target>1.6</target>
</configuration>
</plugin>
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.18</version>
<configuration>
<includes>
<include>**/*Tests.java</include>
</includes>
</configuration>
</plugin>Once those were fixed Maven started running normally and deployment succeeded. mvn clean install installed all of the dependencies from the project object model (pom.xml) successfully and was ready to run after installing the Jetty servlet: mvn jetty:run
- I quickly ran the 5000 samples population script : http://178.62.100.239:8080/data
- Then I opened the application's home page to verify it is functioning properly: http://178.62.100.239:8080/
NOTE: at the moment no domain name has been mapped to the hosting server as seen above: this is the hosting's IP address and relevant port the service is running on.
Prototype Server code needs to be deployed in order to enable the client (Android) application to communicate with the central data store (at the moment the storage type that is being used by the mobile application is local: meaning that all of the route/ personal user information is being saved in the "cache" system directory on the device).