Estimated completion time = 10 minutes.

In this practical session, you will test the EASAP from the previous sessions. Then you will publish your EASAP for other users on EASA→User→Applications.

Lets get started:

• Start EASA, log in, and Set Mode→Author.

• Select EASA→Applications→My EASAPs and find your EASAP.

• Click on it and you will be taken to a new page.

• Under EASA→Authoring→Testing click on the Test EASAP link on the page that appears.

• After the EASAP window appears, click on the Submit EASAP button () in the upper right corner. A pop-up window will appear when the EASAP has been submitted successfully. Click OK.

• Now close the EASAP window, and focus back on the EASA→Authoring→Testing which will look something like the following:

• Now locate the application that you just submitted in the testing table. You may need to click your browser’s refresh button to see the run. The Date and Application columns should provide enough information to find it.

• Now examine the Status column for the run you just submitted, there are various messages.

If you see ‘Queued’ then the job is waiting for some other jobs to finish before starting to run. If you see a percentage number, then your job is currently running. Finally, if you see ‘Completed’ then your job is done and you can view the results by clicking on the icon under Output ().

Now let’s look at the files that will help you diagnose problems you may encounter getting an EASAP to run properly.

• Under the Files column for your latest EASAP run, click on the Browse Files icon () and a pop-up window will appear that will look like the following:

• In this window, look for the err1-runplate.txt file in the list.

This file should have a Size of 0.0 kb to the right of the file name. If the number is greater than zero, then click on the link for the file and examine the error messages given in the file. If you are unable to determine the cause of these messages, then contact your instructor or EASA support representative. At this point, you may need to go back to EASAP Builder and make changes to your EASAP based on suggestions from the EASA support person. You will then resubmit the EASAP for another test. Iterate in this way until all errors in the err1-runplate.txt file are eliminated.

Note: Depending on the type of underlying software driven, not all messages captured in the diagnostic files, such as err1-runplate.txt, will need to be eliminated. Often, software applications send other types of messages to the standard error stream.

• Finally, look to see that a PLATE.OUT file has been created.

If not, then there is a problem with either the EASAP or the input file, plate.txt.

• Open this file and check if all DORs were replaced correctly.

The file should look like the following:

If the input file does not look like the one above and you are unable to determine the cause of the problem, contact your instructor or EASA support representative. At this point, you may need to either go back to EASAP Builder and make changes to your EASAP or make modifications to your template plate.txt file in the template editor. You will then resubmit the EASAP for another test. Iterate in this way until the DORs in the plate.txt file get replaced properly and a valid PLATE.OUT file is produced.

At this point, you have successfully completed an EASAP run. You can close the file browsing window now, and if you haven’t already done so, you can now examine the reported results by clicking on the View Results button () in the Output column. The report will look similar to what you saw in your initial tour of EASA in Practical Session 1 and when you developed the Output branch in Practical Session 5.

If the report does not appear correctly, please contact your instructor or EASA support representative for assistance. Again, you may need to go back to EASAP Builder and make changes to your EASAP based on suggestions from the EASA support person. You will NOT have to resubmit the EASAP for another test: just save your changes in the 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.

Your EASAP will now be ready for publishing.

• Select EASA→Authoring→Publish, add a relevant comment in the input area and then click on the 'Major Revision' button. A new window will state ‘The EASAP has been successfully published.’

Let's check whether our EASAP will be visible to Users on the EASA system.

• Set EASA→Set Mode→User in the browser.

• Now click on the EASA→Applications tab and then select ‘Training’ as the Category.

Your EASAP will now be visible in the EASA→Applications table. If you like, you can open up your EASAP, modify some inputs and then submit it to run as a User. As a User the output from an EASAP run will appear in EASA→Results→My Results.

• Finally, you can Log Out of EASA.

Practical Session 4