An EASAP may be integrated into another application such as:
An EASAP interface may be accessed from within another application in one of two ways:
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:
Below demonstrates an EASAP URL with a login (' user= ') and password (' pwd= ') field in the query string.
http://localhost/easa/applink/redirect.easap?path=examples/tutorials_mort_calc&user=author&pwd=author
See An example, direct-link to an EASAP within an HTML <iframe> below.
This redirect URL may be aliased to an arbitrary string:
http://localhost/customer-123
To add a URL alias (we use 'customer-123') substitute your alias and EASAP path into the following example:
Below demonstrates an EASAP URL which will present the User with an authentication window before the EASAP opens.
http://localhost/easa/applink/standalone.easap?path=examples/plate
Arbitrary SCALAR values may be passed into the EASAP via the query string.
http://localhost/easa/applink/standalone.easap?path=examples/plate&foo=hello&bar=world
Names for these SCALARs must be listed in: APPLICATION > Startup DORs:
For example:
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):
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:
For implementation and configuration details see EASA Web Service Client