In this session we:
1. Lets get started and run a test:
After the EASAP window appears:
2. Locate the and select application that we just submitted in the testing table (you may need to refresh the browser to see the run).
3. Let’s look at the files that will help you diagnose problems we may encounter while getting an EASAP to run properly.
4. In this window, locate err1-runplate.txt in the list and assess whether there were errors.
In many cases benign 'error' messages are sent to a diagnostic file like err1-runplate.txt so it won't have zero length.
5. Finally, we check to see that our output file PLATE.OUT has been created.
If the input file does not look like the one above and the cause of the problem cannot be determined, contact the instructor or EASA support representative.
Back in the EASAP Builder we may need to:
At this point, hopefully we have successfully completed an EASAP run.
6. Let's confirm our report is correct:
The report will look similar to the image from our initial tour of EASA in Session 1.
If the report does not appear correctly, please contact your instructor or EASA support representative for assistance. Again, we may need to go back to EASAP Builder and make changes to the EASAP based on suggestions from the EASA support person. We will NOT have to resubmit the EASAP for another test: just save the changes in the EASAP Builder and then click on the Re-generate report using the latest version of this EASAP link to see an updated report. Iterate in this way until the report appears as expected.
7. It's time to publish the EASAP.
8. Check whether our EASAP is visible to other Users.
Congratulations we have successfully created a network application that runs a User's input into an underlying batch process and returns an HTML formatted report with the results from the analysis.