Challenge Overview
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 competition. This is assembly competition 2 of 2. The issues to be addressed are ONLY the ones found in IBM_CI162_Web_Checklist_Compliance_EIRS.xls and validated using EIRS CI 162 Compliance Part 2 Test Scenarios.xls
The production website url is : http://romulus.raleigh.ibm.com/eirs/
A competitor website url will be: http://{cloud ip}/eirs/ where dst clould url will be a unique url that will be provided to each competitor.
UPDATE: The competitor will be provided a IP address and possibly a URL. The DNS will not be updated in time for you to be able to use the URL so you will have th access the server using the IP provided.
EXAMPLE to access the EIRS website http://12.45.48.139/eirs/
EXAMPLE to access the EIRS server using putty or just ssh from the command line you would use the ip 12.45.48.139
NOTE: the ip provided 12.45.48.139 is just an example each competitor will be provided there personal ip, url and root password. But ensure you sudo to eirs before doing any code updates.
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.
Documents Included:
System Design Specification - Discusses the overall design of the application as it pertains to the CI162 compliance work effort.
IBM_CI162_Web_Checklist_Compliance_EIRS.xls - This is the actual document showing the actual fixes that need to be performed.
EIRS CI162 Compliance Part 2 Test Scenarios.xls - This is the test cases that must test successful for the acceptance of this competition.
EIRS CI162 Compliance_QAPlan_2.doc - This is the QA plan that documents the CI162 compliance.
EIRS_CI-162_Compliance.tcuml - UML diagram of the EIRS Application
EIRS Intranet Website User Guide V1.0 (Draft).doc - Documents website usage and directory structure, cgi use case diagram, cgi use cases and build sample. NOTE: the build has changed a little due to the requirements it the cloud.
Final Submission Guidelines
Each registered competitor will be provided a url once they have provided there public key This will be a personal provisioned server that the competitor will have all to themselves. This server should be used to make the corrections and perform unit testing using the test cases provided. Only a successful pass of each test case provided in the document EIRS CI 162 Compliance Part 2 Test Scenarios.xls
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. Switch 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*