User guide

View models in Avaki Studio
2 Data Integration with Sybase Avaki Studio
Background: Avaki concepts
Before tackling the task of creating a view model, you should be familiar with some
Avaki concepts and terminology. This information can be found in the Sybase Avaki
EII Overture. You’re ready to use Avaki Studio when you know the answers to these
questions:
• What is a database connector?
• What is a database operation?
• What is a data service and what is it good for?
• How do data services interact with database operations and with other data ser-
vices?
• What are data service dependencies and database operation dependencies?
• What is a result set?
What is a view model?
A view model is the abstract, graphical representation of the processing performed by
a particular Avaki data service. The view model represents the flow of data from one
or more input sources through a number of operators to an output result. You create a
view model and deploy the resulting data service(s) using Avaki Studio.
The inputs to a view model can be relational result sets produced by Avaki database
operations or data services; XML results produced by data services; data catalog files
in CSV or XML format; HTTP operations; and web services calls.
A view model is not required to have any inputs; it can generate its own data. Nor is it
required to have any operators—though there would be no point to a view model that
has neither inputs nor operators.
Outputs are also in result set format. Most operators produce a single output (the
exception is the Splitter operator). Every view model includes a Result element, but a
view model need not produce output. View models can produce at most one output
result set.