Using Web Services in the ATE framework

When to use Web Services

Using Web Services in the Astra ATE framework can be a preferred option in certain circumstances, including:

 

•Your SIS data is stored in a non-traditional database

•Security concerns dictate that Astra cannot have access to the SIS database

 

The Web Service allows you to provide the integration behind an interface that Astra can call during ATE (import/export) processing. This allows you to have complete control over how the data is accessed behind the web service interface.

Resource Requirements for Successful Integration

•Solid software development skills and understanding of Web Service concepts

•Deep understanding of the SIS data and how it relates to Astra data

Overview

The ATE Web Service integration is a little different than other web service integrations. In typical web service integrations, code is written that connects to a web service interface exposed on the vendor software application.  In this model, the customer is in control of when to call the vendor interface.

 

The nature of the Astra ATE reverses this role. The Astra ATE jobs are configured to run on a user-defined schedule. It is during the running of these jobs that the ATE framework will call out to the web service to ask for the required data. Because the nature of ATE is to control the processing loop, Astra will need to make the call to the customer supplied web service at the right times during the ATE job.

 

Building the Web Service

The WSDL for the Web Service is provided in the Astra help documentation (located here: Web Service Definition Language). Modern development environments such as Visual Studio can read the WSDL and create stubbed out implementations of the web service. This stubbed out implementation can then be completed by your software development resources. The implementation will be comprised of two main use cases:

 

1.Retrieve the data from the SIS data source.

2.Map that retrieved data to the data structures defined in the WSDL.

 

Once the two main use cases are code complete, then typically there is a testing period to verify the code and data are as expected.