User Tools

Site Tools

Test and publish an EASAP

Introduction | Session 1 | Session 2 | Session 3 | Session 4 | Session 5

In this session we:

  • Test our EASAP from the previous sessions
  • Publish the EASAP and make it available for other Users at: EASA > User > Applications

1. Lets get started and run a test:

  • Start EASA, log in, and: EASA > Set Mode > Author
  • Find our EASAP under: EASA > Author > Applications > My EASAPs
  • Click on it
  • Go to: EASA > Authoring > Testing
  • Click: Test EASAP

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'
  • Close the EASAP window
  • Compare screenshot below with: EASA > Authoring > Testing

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).

  • Use the 'Date' and 'Application' columns to find it
  • Examine the 'Status' column for the run we just submitted, it may show a variety of messages
  • Click on the icon under 'Output' ()

3. Let’s look at the files that will help you diagnose problems we may encounter while getting an EASAP to run properly.

  • Under the 'Files' column for the latest EASAP submission
  • Click on the 'Browse Files' icon ()
    …A pop-up window should appear similar to the following.

4. In this window, locate err1-runplate.txt in the list and assess whether there were errors.

  • This file should have a 'Size' of 0.0 kb to the right of the file name
  • If the number is greater than zero click on the link to the file and examine the error messages
  • If you are unable to determine the cause of these messages, then contact your instructor or EASA support representative
  • We may need to return to the EASAP Builder and make changes based on suggestions from the EASA Support
  • Following any EASAP modification,
    1. Resubmit the EASAP for another test
    2. Iterate in this way until all errors in the err1-runplate.txt file are eliminated

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 it has not, then there is a problem with either the EASAP or the input file, plate.txt
  • Otherwise open this file and check if all object references (DORs) were replaced correctly it should look like the following:

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:

  • Make changes to the EASAP
  • Make modifications to the template 'plate.txt' file in the template editor
  • Then resubmit the EASAP for another test
    …Iterate in this way until the object references (DORs) in plate.txt are replaced and a valid PLATE.OUT is created

At this point, hopefully we have successfully completed an EASAP run.

6. Let's confirm our report is correct:

  • Close the file browsing window
  • Examine the resulting output, click the View Results button () in the 'Output' column

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.

  • Select: EASA > Authoring > Publish
  • Add a relevant comment in the input area
  • Click on the 'Publish' button
    …A new window will state 'The EASAP has been successfully published.'

8. Check whether our EASAP is visible to other Users.

  • In the browser set: EASA > Set Mode > User
  • Click: EASA > Applications
  • Select Category: Training
    …The EASAP should be visible at: EASA > Applications
  • Open up the EASAP,
  • Modify some inputs
  • Submit it… as a User the output from an EASAP run will appear at: EASA > Results > My Results
  • Finally 'Log Out' of EASA

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.

Introduction | Session 1 | Session 2 | Session 3 | Session 4 | Session 5