Setting Up a Cloud Server - Part 3 - Transcript.pdf

Setting up a Cloud Server - Part III
Lets go to the client side for a moment and do some operations on your local machine, specifically file copy

$scp ~/rest-builder.properties
builder@ip.of.remote.server:/home/builder
From Desktop
✦ Use SCP from the desktop to copy the files
needed in the server
✦ If you use a Mac just copy using the “builder” user
to the home directory
© Codename One 2017 all rights reserved
SCP is secure copy. It allows us to copy a file from our desktop to the server or visa versa. On windows there are some visual SCP tools but on a Mac I like using the
command line which I find more convenient.

The syntax might seem odd. If you are familiar with the unix cp command this is roughly the same syntax only thru the network.

This code is executed on my local mac so the first argument copies my instance of rest-builder.properties which includes the server configuration settings. That’s the file
we will be copying. The second argument is the destination. Since it’s remote it starts with the user name on the remote machine followed by the at sign and the IP
address of the remote machine. Then a colon is used to give the destination path on the remote machine.  
You will be prompted for the password of builder at which point copy will proceed. This is a very useful command.

scp ~/dev/AppBackendServer/target/
AppBackendServer-0.0.1-SNAPSHOT.jar
builder@ip.of.remote.server:/home/builder
From Desktop
✦ Copy the actual app to the server
Now that we got that out of the way I can just copy the actual jar to the server. Same exact thing

$nano ~/rest-builder.properties
Commands
✦ Edit the properties file, make sure the values are
correct
✦ For now I set SERVER_URL to http://
server.ip.address
And now back on the server we can open a text editor and set the value of server URL to the current IP address. Nano is a reasonably easy to use text editor, at least
when compared to vi. You can use ctrl-X to exit, you will be prompted to save.

$mysql -p
Commands
✦ Login to mysql and execute “create database
backendapp”
Next lets login to mysql, we’ll be prompted for the password. We need to run the create database command, notice that the tables will be created implicitly by JPA.

$wget http://apache.spd.co.il//ant/
binaries/apache-ant-1.10.1-bin.zip
Commands
✦ Download Apache Ant
The next step is to download apache ant which we need in order to build the resulting application

$unzip apache-ant-1.10.1-bin.zip
Commands
✦ Unzip Apache Ant zip
We can unzip it in the users home directory thanks to the unzip command we installed previously

$mv apache-ant-1.10.1 ant
Commands
✦ We need ant to be in a directory with the name
“ant” so the build script will find it
Since the version number for ant is a bit problematic I’m renaming the directory ant so the build process can find it. The mv command represents move and works as a
rename.

$mv AppBackendServer-0.0.1-SNAPSHOT.jar
AppBackendServer.jar
Commands
✦ I’d rather not have the 0.0.1 jar name…
I also rename the backend server. It shouldn’t include the version as we’ll update it in the future and we don’t want it to carry an outdated version number. Technically it
might have been more “correct” to use a symlink but I want to keep things simple

$exit
Commands
✦ We need to go back to root. Notice using “su”
would work if we changed something in the
session
You might recall we did a su builder so I’m just exiting from that su command and returning to the root account. If I use exit from there I will logoﬀ from the server

#ln -s /home/builder/
AppBackendServer.jar /etc/init.d/
AppBackendServer
Commands
✦ We create a symbolic link to the /etc/init.d
directory which will allow us to start the app as a
service
This command might be confusing to windows users since there is nothing like this one Windows. The Unix file system supports a feature called symbolic links.
Essentially it creates what looks and acts like a file or a directory but it’s really a file system pointer at a file that resides elsewhere.

In this case I created a symlink in /etc/init.d named AppBackendServer. Notice that it doesn’t have the jar extension!

This points to the jar file we have in the builder home directory. If you know Linux or Unix this must look really weird…

#service AppBackendServer start
Commands
✦ This runs the server and it should now work, you
can stop it using the same command with “stop”
at the end
If you know Linux or Unix you might be thinking “what the hell just happened”?

Well, the jar is really a linux shell script too. So by placing the symlink in the init.d directory it starts working as a service just like mysql!

I can’t stress enough how amazing this is!

#cat /var/log/AppBackendServer.log
Commands
✦ Application logs are automatically stored under  
/var/log with the right name
Everything works exactly like you would expect from any other service on Linux. For instance you can see the output logs for the service under the /var/log directory

Setting Up a Cloud Server - Part 3 - Transcript.pdf

Recommended

Recommended

More Related Content

Similar to Setting Up a Cloud Server - Part 3 - Transcript.pdf

Similar to Setting Up a Cloud Server - Part 3 - Transcript.pdf (20)

More from ShaiAlmog1

More from ShaiAlmog1 (20)

Recently uploaded

Recently uploaded (20)

Setting Up a Cloud Server - Part 3 - Transcript.pdf