User Tools

Site Tools

EASAP Builder and Compute Server Config Tool

The EASA Client is a locally installed Java application that currently supports two EASA tasks:

  • Authoring via the EASAP Builder
  • Administrator tasks via the Compute Server Configuration Tool

Historically, the EASA Client supported a User's interaction with a Published EASAP. Nowadays the Web Browser Client interface supersedes this EASA Client role. For Author documentation relevant to this now-unsupported User interface see the EASA 5.5 Help Pages.

Remove an Existing EASA Client

Before installing the EASA Client, any prior EASA Client from an EASA version of 3.1 or lower must be removed in one of the following ways,

  • On Windows, run the Uninstall EASA Client.exe executable,
    • (in <EASACLIENT>/UninstallerData )
  • On UNIX, run the Uninstall_EASA_Client script,
    • (in <EASACLIENT>/UninstallerData )

Alternatively, from within Windows,

  • Select Settings→Control Panel from the Start menu.
  • Select Add/Remove Programs on the Control Panel.
  • Select EASA Client:
    • Click on the Change/Remove button.

Any of these methods launches the EASA Installation Wizard, the Uninstall window will appear. Click the Uninstall button, eventually, click Done to remove the EASA Client.

Install an EASA Client

The EASA Client is automatically installed on the EASA Server during installation. Install the EASA Client on any User computer that is not going to use the web browser client. The EASA Client can be installed directly from the EASA Server via:

  • EASA→User→Install Client

Use an account with administrator priveledges to install the EASA Client on a client computer.

  • To install the EASA Client software,
    • Click on EASA→EASAP Builder
    • Select 64-bit or 32-bit executable.
    • Log into Windows as 'administrator'
    • Open the executable.
    • A 'Welcome window' appears with an introduction to the installation process.
    • Click Next
    • A License Agreement window opens.
    • Select ‘I accept the agreement’
    • Click Next.
    • A 'Select Destination Directory' window appears
    • Choose a folder for the EASA Client.
    • Click Next
    • Click Finish

Proxy Server Settings

If Internet access is via a proxy server, configure the proxy server settings.

  • Click the link,
    • EASA→Install Client→proxy server settings
  • A form appears,

  • Provide both,
    • Proxy address
    • Port number of the HTTP Proxy Server
    • If EASA is in Secure (HTTPS) mode, then also provide,
      • Proxy address
      • Port number of the Secure Proxy Server.

A valid User Name and Password may be needed to access the Proxy Server.

Testing EASA Client Applications

To test an EASA Client application, follow the instructions below. An EASA Server must be up and running for this test.

  • Log on to EASA from a client computer as any valid user, see Client Computer
  • Open a web browser and type either of the case-sensitive EASA web addresses below,
    • http://domain_name/easa
    • http://domain_name:port_number/easa

Where domain_name is the domain name of EASA and port_number is the port number entered during installation. If no domain name was explicitly specified during installation, then it defaults to the computer name of the EASA Server. The EASA Evaluation installation defaults to port 8080. The EASA Log In page should appear in the browser window.

  • If the EASA Client has not been installed,
  • Log in to EASA as an Administrator:
    • EASA→Log In
      • login→admin
      • password→admin (by default)
    • EASA→Set Mode→Adminstrator
  • Select,
    • EASA→Configure→Compute Servers
  • Click on the compute server configuration link near the top of the page

A new window will appear with a progress bar showing the status of the loading process. The application may take up to a minute to load, and when it is finished loading, it should look like the window pictured below.

  • If the application appears as expected, the test was successful.
  • Select File→Exit
  • Click EASA→Log Out
  • If the application does not appear as expected,
    • Confirm a locally installed EASA Client
    • Otherwise contact an EASA support office for assistance
    • EASA support may ask for the log files stored in,
      • <EASAROOT>/webapps/easa/client/

Page Tools