Using the SOA Gateway to access the Sybase EAServer database Adaptive Server Anywhere.
The EAServer product set from Sybase includes Adaptive Server Anywhere. Adaptive Server Anywhere provides a full-featured SQL database for EAServer applications. It is designed to operate in environments with limited physical and database administration resources. Adaptive Server Anywhere is a transaction-processing relational database management system (RDBMS) with full recovery capabilities, online backup, referential integrity actions, stored procedures, triggers, row-level concurrency control, and a rich SQL language.
Go to here to download the Sybase EAServer Developer Edition which is used in this example.
This HOWTO assumes that the SOA Gateway and the Sybase database are both running on Windows.
For the purpose of this HOWTO, we will be using one of the sample databases provided by Sybase, "Jaguar SVU Sample".
By default, the Sybase installation sets the DSN information required for accessing the sample database:
Check that the login details are correct.
Select the Configure... button having first highlighted the sample database as shown above.
Select the Login tab:
If the User ID and Password is not set set them to dba and sql respectively.
The SOA Gateway must now be configured to access and use this DSN
Start the SOA Gateway Control Center and add a SOA Gateway Server (if necessary). See here for more information.
If you do not have an Sybaser driver, add one now. See here for more information.
Right click on your server, and select Create new WebServices:
From the next dialog choose Sybase_Driver and click
The next dialog prompts you for the the
: In this case it will be Jaguar SVU Sample
: As it has been set at DSN level this is not necessary. Otherwise set as appropriate.
: This will be a pattern match value passed to the SQL Command. The search pattern characters are: an underscore (_), which represents any single character and a percent sign (%), which represents any sequence of zero or more characters.
: This is a hard-limit on the amount of tables the SOA Gateway will attempt to discover.
Advanced Options: Enables changing the generated WebService name. Leave unset.
Example:
Now click
The SOA Gateway will ask the Sybase Server database ( identified by the Jaguar SVU Sample DSN) to display all the tables which match the request. In our case, the number of tables starting with 'a' were returned.
Select table allbooks, and click
The results of the import will be displayed in a dialog
Click to finish the Web Service creation
You have now created a Web Services based on table allbooks from the Sybase database!
Now that the Web Services have been set up, you can access the Web Service Description Language ( WSDL ) by clicking in the WSDL URL link in the Control Centre.
This WSDL is the starting point to accessing the your tables and stored procedures using the SOA Gateway. There are many clients available to consume and use web services, for example soapUI, XMLSpy, and InfoPath.
A tutorial on how to access Adabas data through soapUI is available here. The follow example is based on that tutorial, and shows how to access the allbooks table we have just enabled.
Start soapUI and create a new WSDL project.
Import the allbooks WSDL, E.g. http://localhost:56000/allbooks_DBA?WSDL
Edit the list request
Completely remove the <all:allbooks_DBAGroupHeader> element from the <soap:Header> element
In the <Security> element, add Username and Password for accessing the allbooks table if required. Otherwise, the <Security> element, and indeed the rest of the <Header> element can be removed as shown below.
Add "*" as the content of the <book_id> element ( same as
SELECT * from allbooks; )
E.g
Hit the green arrow, and the results of the request should be displayed
Congratulations! You have now accessed a Sybase table using the SOA Gateway!
