User Tools

Site Tools

Integrate EASA into another application

An EASAP may be integrated into another application such as:

  • A product lifecycle management system (PLM)
  • A workflow tool
  • A computer aided drafting suite (CAD)
  • Customer relationship management software (CRM)

An EASAP interface may be accessed from within another application in one of two ways:

  1. A direct-link URL to the published EASAP (eg. an EASAP running inside an HTML <iframe>)
  2. Access an EASAP's I/O with custom software written in a high-level programming language (ie. implement a Web Service Client below)

To create a direct-link to open a particular EASAP in the browser, use one of the URL formats below.

There are two options for closing the EASA Server session when using a direct link:

  1. Leave session open until it times out after 120 minutes or until the User clicks 'Log Out' (this is the default behavior)
  2. Close the session automatically (ie. 'log the User out') when the EASAP is closed (append ' &sa=true ' to the direct link URL).

A. Launch an EASAP with a non-interactive login

Below demonstrates an EASAP URL with a login (' user= ') and password (' pwd= ') field in the query string.


See An example, direct-link to an EASAP within an HTML <iframe> below.

This redirect URL may be aliased to an arbitrary string:


To add a URL alias (we use 'customer-123') substitute your alias and EASAP path into the following example:

  1. Publish the EASAP ('examples/tutorials_mort_calc' in this example)
  2. Copy <EASAROOT>\webapps\ROOT to <EASAROOT>\webapps\customer-123
  3. Modify the '<meta..' line in <EASAROOT>\webapps\customer-123 to:
    <meta http-equiv=“refresh” content=“0;URL=/easa/applink/redirect.easap?path=examples/tutorial_mort_calc”>
  4. Confirm the Mortgage Calculator EASAP opens in a browser with the URL: http://localhost/customer-123

B. Launch an EASAP that prompts for user credentials

Below demonstrates an EASAP URL which will present the User with an authentication window before the EASAP opens.


C. Launch an EASAP with URL query string values

Arbitrary SCALAR values may be passed into the EASAP via the query string.


Names for these SCALARs must be listed in: APPLICATION > Startup DORs:

For example:

  • Set APPLICATION > Startup DORs: foo, bar
  • Access EASAP via: http://localhost/easa/applink/standalone.easap?path=examples/plate&foo=hello&bar=world
    …SCALARs foo and bar will be available within the EASAP with values 'hello' and 'world'

D. Launch an EASAP from within another EASAP

A customer may wish to launch a second EASAP with a data set selected in an EASAP that is already running.

For this case we use a type A. redirect URL and add a session ID to Launch a child EASAP from a parent.

Embed an EASAP GUI within other branded content using an HTML <iframe> (example follows):

  • Publish the Cantilever Plate Loading Analysis example EASAP that ships with EASA
  • Create an html file that contains with the html <body> element:
    <iframe width=“740” height=“549”
  • Open the file with a browser and the window below should appear:

A non-interactive EASAP: Web Service Client

An EASA Web Service Client uses a standard XML SOAP message or REST-ful HTTP format to communicate with a 'web service'.

This technology makes it possible to non-interactively utilize an EASAP.

The EASA Web Service supports many operations, for example it may:

  • Open an EASAP
  • Set a value of an input object
  • Upload or download a file
  • Submit a run of the EASAP
  • Monitor a run for completion
  • View output values after a run completes

For implementation and configuration details see EASA Web Service Client