The SOA Gateway interfaces with Adabas in a smooth, seamless way, implementing almost all features of both the Mainframe and OpenSystems version of Adabas:
Sequential / direct access with various positioning options
Transactionality
LOB (large objects) access
The following is a sample SOA Gateway 'WebService' definition for an Adabas file exposed as a 'Web Service'
Before a SOA Gateway WebService can be used, the mapping between the physical layout (the Adabas FDT) and the SOA Gateway (XML) representation must be in place. This mapping is called the SOA Gateway 'DataView'. In addition to the manual approach described in detail in the Data Views section, there are a number of semi-automated methods aiding in the generation of SOA Gateway DataViews for Adabas resources
A new DataView can be generated from an Adabas file using the 'WebService Discovery wizard', which will not only generate the DataView (XRD), but also a XSD, plus the SOA Gateway Resource definition itself.
Use the 'WebService creation Wizard' to generate the WebService(s)
Important:
As Adabas only knows about the 2-character "internal field
names", you will have to edit the DataView and assign "friendly names" to all
fields. Import the DataView(s), open it with the XRD editor, edit the field
name(s), save the file, and re-export it to the server.
DataView(s) for SOA Gateway Adabas resources can be generated/imported from SYSOBJH extracts.
Use the 'WebService creation Wizard' to generate the WebService(s)
