User Tools

Site Tools


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

Session 5: Test & Publish an EASAP

Estimated completion time → 10 minutes.

In this practical session, we will Test our EASAP from the previous sessions. Then we will Publish the EASAP and make it available for other Users at EASA→User→Applications.

  • Lets get started,
    • Start EASA, log in, and EASA→Set Mode→Author.
    • Find our EASAP under EASA→Author→Applications→My EASAPs.
    • Click on it.
    • 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.
            • Close the EASAP window,
            • Return to EASA→Authoring→Testing page, which will look something like the following,

  • 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.
  • Examine the Status column for the run we just submitted, it may show a variety of messages,
    • ‘Queued’ implies the job is waiting for some other jobs to finish before starting to run.
    • A percentage value implies the job is currently running.
    • ‘Completed’ implies the job is done
      • → Click on the icon under Output ().
  • 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 run,
      • Click on the Browse Files icon ()
        • → 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,
      • 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.
      • We may need to return to the EASAP Builder and make changes based on suggestions from the EASA Support.
        • Following EASAP modification
          • Resubmit the EASAP for another test.
          • Iterate in this way until all errors in the err1-runplate.txt file are eliminated.

Note, In many cases benign 'error' messages are sent to diagnostic files like err1-runplate.txt in which case it won't be zero length.

  • 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 object references (DORs) were replaced correctly.
        • → This file 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.

  • We may need to either go back to EASAP Builder
    • 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 the plate.txt file get replaced and a valid PLATE.OUT is created.

At this point, hopefully we have successfully completed an EASAP run. We may close the file browsing window now examine the reported results by clicking on 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 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.

The EASAP will now be ready for publishing.

  • 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.’

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

  • Set EASA→Set Mode→User in the browser.
  • Click on the EASA→Applications tab
  • Select ‘Training’ as the Category.
  • The EASAP should be visible in the EASA→Applications table.
  • We may open up the EASAP,
    • Modify some inputs
    • Submit it to run as a User.
      • → As a User the output from an EASAP run will appear in 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


Page Tools