Warm-Up and Basic Setup Solution




Throughout this quarter, you will be gradually developing a blogging Web site, which can be considered as a simplified version of WordPress. The entire Web site will be built on the “MEAN stack” (MongoDB, Express, Angular, and Node.js) eventually, but the MEAN stack is hard to learn and appreciate unless you have some experience with a more “traditional” stack. In the first two projects, therefore, you will start development with a more “traditional” stack based on MySQL and Apache Tomcat. Hopefully this will give you enough experience to use the the MEAN stack in later projects.

In Project 1, you are asked to perform the following tasks:

  1. You will have to set up our project development environment on your machine, which is based on Docker.

  1. You will have to brush up with Unix Command-Line Interface (CLI).

  1. You will have to brush up with your MySQL knowledge.

    1. You will have to brush up with Java programming.

Part A: Setup Your Development Environment

Docker is a popular software development and deployment tool that implements container technology. It allows allows running multiple isolated OS environments on a single machine. As the first task of Project 1, you must go over the following tutorial and follow its step-by-step instruction:

Docker Setup and Basic Use

The page will guide you setting up the Docker App on your machine and teach the most important concepts and commands for using Docker.

The Docker image for Project 1 (and Project 2), “junghoo/cs144-tomcat”, has MySQL, Apache Tomcat, and Java JDK 7 installed.

Part B: Unix Command-Line Interface (CLI)

All of your project development should be done inside a Docker container that we provide, which is based on Linux operating system. For the most part, therefore, you will be using a Unix shell through a terminal app. If you are not familiar with Unix shell commands, read the Unix Tutorial for Beginners and learn the basic Unix commands.

http://oak.cs.ucla.edu/classes/cs144/project1/index.html 1/7

12/13/2018 Project 1: Warm-Up and Basic Setup

In playing with basic Unix commands, you can use the “tomcat” container created from the “junghoo/cs144-tomcat” image in Part A. As we explained in the Docker Setup and Basic Use page, you can start the “tomcat” container using the docker start command:

$ docker start -i tomcat

Your username inside the container is “cs144” with password “password”. There are a few important environment variables that have been set within the “junghoo/cs144-tomcat” container:

JAVA_HOME: The JAVA_HOME environment variable points to the JDK installation directory, which is /usr/lib/jvm/default-java in our container.

CATALINA_HOME: This variable specifies the location of the Tomcat installation, which is /usr/share/tomcat8.

CATALINA_BASE: This variable specifies the base directory of a Tomcat instance, which is /var/lib/tomcat8.

HOME: This variable specifies the location of your home directory, which is /home/cs144.

You can refer to the values of these variables in your shell, like $JAVA_HOME, $CATALINA_HOME, etc. For example, if you issue the following echo command inside the container

  • echo $JAVA_HOME /usr/lib/jvm/default-java

you will see the value of JAVA_HOME. To exit from the “tomcat” container, you just need to type


$ exit

Part C: MySQL Warm-Up

In this part, you get yourself familiar with the basic MySQL commands by creating and loading a table and issuing a few queries.

First, download the actors.csv file to the current directory of the container. To download any file, you can use the wget command in the container like the following:

$ wget http://oak.cs.ucla.edu/classes/cs144/project1/actors.csv

Then, read our basic MySQL tutorial to learn how you can interact with MySQL and issue SQL commands. In particular, the tutorial provides a brief explanation on CREATE TABLE, LOAD DATA and SELECT commands, which will be important to finish this part of the project. If you need to brush up on SQL commands other than the ones explained in the tutorial, you may find the How Does This RDBMS Thing Work? section of SQL for Web Nerds helpful.

http://oak.cs.ucla.edu/classes/cs144/project1/index.html 2/7

12/13/2018 Project 1: Warm-Up and Basic Setup

As we explained in the MySQL tutorial, we have created the database “CS144” (note a database name is case sensitive) in the MySQL of our container. For your project work, use the MySQL user “cs144” (no password), which has full access to the “CS144” database. The MySQL user “root” with password “password” has full unrestricted access to everything and should be used only for special administrative operations, like creating new users and databases, etc.

Now take the following steps to create, load, and query a table in MySQL:

  1. Create a table called “Actors” in the database “CS144”. The “Actors” table should have the following schema:

Actors(name:VARCHAR(40), movie:VARCHAR(80), year:INTEGER, role:VARCHAR(40))

Please note that database, table, and attribute names are case sensitive in MySQL, so use the above schema EXACTLY as it is, including the case.

  1. Load the downloaded ./actors.csv file into the “Actors” table. Make sure that the double quotes enclosing some of the attributes in the data file are removed when they are loaded.

  2. Retrieve some loaded data from the “Actors” table. In particular, write a query that returns the answer to this question: “Give me the names of all the actors in the movie ‘Die Another Day’.” Feel free to experiment with other interesting queries.

  1. Once you are done, drop the “Actors” table from MySQL, so that it will not stay in the database for our later project.

Create a MySQL batch script file named actors.sql that shows every one of the above 4 steps. Again, the MySQL tutorial had a brief explanation on how to create and run MySQL batch script file. Make sure that your script is executable and has no error, meaning that we should be able to run your script by issuing the following command:

$ mysql CS144 < actors.sql

You MUST use ./actors.csv as the location of the data file inside your script. Do NOT use an absolute path. You may assume that there is no “Actors” table in the “CS144” database when we execute your script. If needed, use the tag to make comments within your SQL script.

Notes on CR/LF issue: If your host OS is Windows, you need to pay particular attention to how each line of a text file (including your script file) ends. By convention, Windows uses a pair of CR (carriage return) and LF (line feed) characters to terminate lines. On the other hand, Unix (including Linux and Mac OS X) uses only a LF character. Therefore, problems arise when you are feeding a text file generated from a Windows program to a Unix tool (such as mysql). Since the end of the line of the input file is different from what the tools expect, you may encounter unexpected behavior from these tools. If you encounter any wired error when you run your script, you may want

http://oak.cs.ucla.edu/classes/cs144/project1/index.html 3/7

12/13/2018 Project 1: Warm-Up and Basic Setup

to run the dos2unix command in the container on your Windows-generated text file. This command converts CR and LF at the end of each line in the input file to just LF. Type dos2unix — help to learn how to use this command.

Part D: Java Warm-Up

If you are new to Java or if it has been a while since your last Java programming, first read A Crash Course from C++ to Java. This excellent tutorial explains the basics of Java, including how you can name, compile, and run your Java program. (It is okay to skip the parts on BlueJ in the tutorial, since we will not be using it.) If you are quite familiar with Java, but you just want to brush up on minor details quickly, you may want to read slides on Java instead. All basic tools needed for Java programming (e.g., javac and java) are available on our container.

Now implement a Java program that computes the SHA-1 hash over the content of an input file. SHA-1 is a cryptographic one-way hash function that computes a 160 bit value (or 40-digit hex value) from a sequence of bytes. Your Java program should satisfy the following requirements:

  1. Your program should be implemented as a single Java class ComputeSHA. Your program should take the input filename as the first command line parameter. For example, a user should be able to execute your program like

$ java ComputeSHA filename.txt

where filename.txt is the name of the input file.

  1. Given the input file, your program should compute the SHA-1 hash value over the entire content of the file and print the computed hash value on screen as follows:


Your program should print the above hash value if you provide the sample-input.txt file as its input. Please ensure that the output is formatted exactly as above including its case. Print a newline at the end of the hash value. To test the accuracy of your implementation on other input files, you may compare your output against that of the sha1sum command. Please make sure that your program works for both text file and binary file of any size.

In implementing your Java program, you may find the Java class java.security.MessageDigest useful, which provides a number of cryptographic hash functions including SHA-1 and MD5. If you decide to use MessageDigest class, make sure you import java.security.* packages in your source code. If what we just said sounds Greek to you, again, read A Crash Course from C++ to Java. To learn how you may use MessageDigest class in Java, try a query like “Java MessageDigest

http://oak.cs.ucla.edu/classes/cs144/project1/index.html 4/7

12/13/2018 Project 1: Warm-Up and Basic Setup

example” on Google and look at the top few results. They are likely to contain good example codes that show you how you can use the class. If you want to learn about basic file I/O in Java, see Java File I/O tutorial.

Notes on editors for Java development: You can choose whatever editors you like for Java development. Options include:

Unix text editors in the container: You may use any text editor in the container (vi and nano are available) to edit text files directly.

Your favorite text editor on the host: You may use your favorite text editor from your host OS (e.g., Sublime Text or Visual Studio Code) and transfer the edited file to the container through the shared directory. Remember that the directory that you specified as the shared directory from the host (e.g., /Users/cho/cs144 from Mac) is available at $HOME/shared in the container. Again, be careful with the CR/LF issue if you use this option.

Your Final Submission

Your project must be submitted electronically before the deadline through our CCLE Course Website. Navigate to Sections on left of the page, and click on the Project 1 submission section. If you submit multiple times, we will grade only the latest submission.

What to Submit

The zip file that you submit must be named project1.zip, created using a zip compression utility (like using “zip -r project1.zip *” command in the container). You should submit this single file project1.zip that has the following packaging structure.



+- actors.sql


+- ComputeSHA.java


+- README.txt (Optionally)

Each file or directory is as following:

1. actors.sql: A copy of your MySQL batch script file from Part C of this project.

You must use ./actors.csv as the location of the data file inside your script.

The “Actors” table must the provided schema exactly as it is including its case.

http://oak.cs.ucla.edu/classes/cs144/project1/index.html 5/7

12/13/2018 Project 1: Warm-Up and Basic Setup

  1. ComputeSHA.java: The source code of you Java program for SHA-1 hash computation from Part D.

  1. (Optional) README.txt: A (plain text) README file containing anything else you find worth mentioning.

Please ensure that your submission is packaged correctly with all required files. Make sure that each file is correctly named (including its case) and project1.zip contains all files directly, not within a subdirectory. In other words, unzipping project1.zip should produce the files in the same directory as project1.zip. You may get as small as zero points for your work if the grader encounters an error due to incorrect packaging, missing files, and failure to follow our exact spec.

Testing of Your Submission

Grading is a difficult and time-consuming process, and file naming and packaging convention is very important to test your submission without any error. In order to help you ensure the correct packaging of your submission, we have made a “grading script” p1_test available. In essence, the grading script unzips your submission to a temporary directory and executes your files to test whether they are likely to run OK on the grader’s machine. Download the grading script and execute it in the container like:

$ ./p1_test project1.zip

(if your project1.zip file is not located in the current directory, you need to add the path to the zip file before project1.zip. You may need to use chmod +x p1_test if there is a permission error.)

You MUST test your submission using the script before your final submission to minimize the chance of an unexpected error during grading. Again, significant points may be deducted if the grader encounters an error during grading. When everything runs properly, you will see an output similar to the following from the grading script:

Running your actors.sql script…


Brosnan, Pierce

Cleese, John

Echevarria, Emilio

Ho, Thomas

Lee, Will Yun

Madsen, Michael

Makoare, Lawrence

Salmon, Colin

Stephens, Toby

Yune, Rick

Finished running actors.sql

Compiling ComputeSHA.java…


Grading Criteria

System setup (30%) – gets full credit if the submission was successful

No error in actors.sql (20%) – gets full credit if the script runs without any error

Correctness of actors.sql (10%) – gets full credit if the query returns the correct results

ComputeSHA compilation (10%) – gets full credit if the submission compiles without error

ComputeSHA correctness (30%) – based on several test cases