An EASAP may be integrated into other applications such as product lifecycle management systems, workflow tools, computer aided drafting, etc….
An EASAP interface may be integrated into or accessed from within another application. This method involves initiating and running an EASAP using a 'direct link' URL.
Another alternative is to access an EASAP's inputs and outputs non-interactively via custom software written in a high level programming language. This requires programming expertise and will utilize the Web Services Client API.
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.
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.
EASA's Web Service Client supports the following operations:
To help program an implementation of an EASA Web Services Client we have Java code and Java Doc files available from EASA Technical Services (email firstname.lastname@example.org).
Once the implementation has been written the EASA API classes and Apache Axis classes will be required.
In addition to Java, EASA supports other languages such as C, C++, VBA (for support please contact EASA Technical Services).
For a Java implementation:
Once these jarfiles are in place, compile and then test the implementation.
The EASA Server will need to be configured to accept the Web Services Client as a valid User .
Go to the page below and create an easaws user:
Obtain a license from EASA Technical Services that specifically activates the Web Services Client (email@example.com)