The VS 2010 project that houses the Process Specification Tool utilizes a post-build step which creates the necessary deployment folder structure and content. This guide walks the developer through the steps required to deploy the built application to the PSU servers on which it is hosted.
Note - it is assumed that the reader has a base proficiency in *nix command-line utilities (such as tar, ssh, scp, etc.) - if using a Windows machine, the developer may want to install Cygwin.
Web Site Deployment¶
The Process Specification Tool is deployed on the PSU server omseforge.cs.pdx.edu. This server runs the Apache2 web server, Mono framework and mod_mono plug-in that are required by the application, and is managed by PSU. The deployment is hosted via a dedicated service account - 'omse551p'. Credentials for this account can be obtained from the project team or PSU CAT team as needed.
- Create an archive of the project deployment folder
tar -zcvf ../proctool.tar.gz *
- Upload the archive to the PSU web server (file will be placed in the omse551p user account's home directory)
scp proctool.tar.gz firstname.lastname@example.org:
- Connect to the PSU web server via SSH
- Move the archive to the web server directory used to host the Process Specification Tool
mv proctool.tar.gz /stash/omse/processmodeling
- Navigate to that directory, expand the archive contents and delete the archive
cd /stash/omse/processmodeling tar -zxvf proctool.tar.gz rm proctool.tar.gz
- Ensure that permissions are correct on deployed files and folders
cd .. chmod -R 755 processmodeling/
- Ensure that the credentials in the Web.config are correct to connect to the database server
cd /stash/omse/processmodeling nano Web.config [... change <connectionString> as necessary, save and exit]
- If necessary, request that Apache is recycled on the server [requires CAT help - usually quickest path is via CAT IRC #support room]
The database for the Process Specification Tool is deployed on a central PSU database server db.cecs.pdx.edu. This server runs the MySQL database that is required by the application and is managed by PSU. The application database is called 'omse551p' and is accessed via a dedicated service account - 'omse551p'. As above, credentials for this account can be obtained from the project team or PSU CAT team as needed.
Note - the PSU database server is not addressable by IP addresses outside of PSU's network. Therefore, it is usually most convenient to execute any required database scripts via the application web server.
- Upload database scripts to the PSU web server
scp CreateDatabase.sql email@example.com: scp InsertTemplateData.sql firstname.lastname@example.org:
- Connect to the PSU database server via MySQL command line
mysql -h db.cecs.pdx.edu -u omse551p -p
- Execute database scripts to create and populate the database (with initial template data)
source CreateDatabase.sql source InsertTemplateData.sql
- Exit MySQL command line and remove the database scripts
exit rm *.sql