Challenge Overview
The purpose of this competition is to complete the architecture diagrams as well as build a game plan for completing all the doumcentation, test plans, code changes, testing and deploying to production.
1. complete any architectural diagrams that are not currently completed or does not exist.
2. Setup the game plan for the follow on competitions
a. build test plans
b. have 1 or more competitions to complete the changes defined in IBM_CI162_Web_Checklist_Compliance__EIRS.xls
c. another competition to run the test plan on completion
The end result is to make the EIRS website application ITCS162 compliant. This will require updating CGI and html code. The website currently does not follow any standards and we are not asking that any be introduced in this competition. The only changes being requested is to make the website compliant with the ITCS162 usability rules. The attached documents provide the detailed information on the current environment as well as the changes being requested for the competitions.
The production website url is : http://romulus.raleigh.ibm.com/eirs/
A competitor website url will be: http://{cloud url}/eirs/ where dst clould url will be a unique url that will be provided to each competitor.
If there is a ITCS162 finding that is outside of the url path of : http://romulus.raleigh.ibm.com/eirs then the solution to fix the issue would be to delete the html file.
For example a finding in http://romulus.raleigh.ibm.com/manual/ibm/en_US/sitemap.html would have a solution of deleting the sitemap.html file.
Final Submission Guidelines
All activity on the server needs to be performed as the eirs id which is already defined on the server. As root I would switch to the eirs id using the command:
sudo su - eirs
The application will be found in the path below on the cloud server:
/usr/IBM/WebSphere/HTTPServer/htdocs/en_US/eirs
The production code will be found in the path below on the cloud server:
/opt/eirs/Source/EIRS_TOD
An example of the steps to compile one of the CGI programs using sign_on as an example.
1. swith to the sign_on directory: /opt/eirs/Source/EIRS_TOD/sign_on
2. run the "make clean" command which will delete the prep, object and executable files.
3. to compile the program run the "make prod" command which will create the .cgi file which would be placed in the application directory.
file that was created: -rwxr-xr-x 1 eirs eirs 2618161 Jan 31 17:27 sign_on.cgi*