You can access the development server for cs615 via ftp and, in your ftp client, ftp to utopia.csis.pace.edu. Your username is a combination of the first letter of your first name and your last name, and your password is your first name plus the number 16.
For example: My name is Thomas Lombardi and, if I were in cs615, my credentials would be as follows:
At that point you will find yourself in the web root of the server. Navigate into the class folder: cs615, and then into your team folder. Now you can move files to and from your teamís folder as needed.
Anyone can access the web server to view your pages. The default.htm page has a list of links that you can use to test the server software.
Simply type utopia.csis.pace.edu in the browser of your choice and you should see a test page with simple scripts in many web languages. To access your pages, you would type:
This will show the default.htm page for team 1 assuming team 1 placed a default.htm file in that location.
Every team has its own database instance on the server named team1, team2, etc. In addition to this, every team has a datasource name that references that database via ODBC. The datasource for Team1 is dsnTeam1, Team2 is dsnTeam2, etc.
When you want to create database tables, add data to tables, or query your database, you must achieve this via your ODBC datasource name. There are sample scripts in your Team folders and I have created one sample table in each team folder so you have an example to work from. If you need to work with other databases such as access, please contact me so that I can create a new ODBC source for your team.
We will install a graphical user interface to MySQL but I still recommend that you use scripts for backup and portability purposes.
No. We cannot guarantee the backup of your user files on utopia.csis.pace.edu.† Please be sure that you maintain your own backups of everything that you place on our server. We will make every attempt to keep this server up and running and we will maintain it as best we can but it is the ultimate responsibility of you and your team to maintain backups of all of your scripts including and especially your database creation scripts and your data population scripts. If you maintain copies of all of these, in the event of an emergency, we will be able to rerun your scripts and reconstruct your data. A pleasant by-product of this approach is that you will be able to transport your application to a new machine with relative ease.
If you have problems logging in or if you have other kinds of system problems (your team requires a new datasource name, etc), please send requests to me at email@example.com and I will process these requests as quickly as I can.