Homepage | About EASA | Contact
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.
The first URL allows non-interactive login. The second URL prompts the User with a login window.
If &user and &pwd are not filled and correct, the User will be prompted with a login window.
For the first, non-interactive login append &sa=true to the query string of the url if it will be launched from within an EASAP using the second, interactive url.
Once logged on, the User will remain logged on until 30 minutes of inactivity, by default. If the User closes the EASAP, the session is closed but is not logged out of the EASA Server until the idle period above has passed.
Embed an EASAP GUI within other branded content using an HTML <iframe> (example follows):
The window below should appear:
An EASA Web Service Client uses a standard XML SOAP message 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 a client implementation may:
For implementation and configuration details see EASA Web Service Client.