User guide

Data Integration with Sybase Avaki Studio 19
The Avaki perspective: A tour
good places to start are the /GeneratedViews, /Shares, and /WSDLs folders. (For more
information on the contents of the default directories in the data catalog, see the Avaki
Overture.)
Once you’ve found the input source you want, you can drag and drop it from the Data
Catalog view to the view model pane. Studio automatically creates a corresponding
Input Source element in the view model.
Creating and managing input sources
You can also use the Data Catalog view to create input sources (both provisioned and
generated SQL views) and to manage input sources. Select an item of interest in the
catalog and right-click for a context menu. You can:
• Provision a SQL view from a database table.
• View database schemas.
• Generate a SQL view from a data service, database operation, or a virtual database
operation.
• Generate schema for a data service, a database operation, or a virtual database oper-
ation. Generating schema generally involves a call on the database and at least a
partial execution of the data service or database operation. Studio extracts the
schema from the returned metadata without iterating over the rows of the result set.
The exception is updates—the schema for a database operation that includes an
update operation can be generated without executing the database operation.
Note that when you create a database operation or deploy a data service from Avaki
Studio, the schema is generated at the time of creation. The generate schema utility
is for database operations and data services created in the web UI or the CLI.
• Execute a data service, a database operation, or a virtual database operation.
• Add users or groups to access control lists (ACLs), remove users or groups from
ACLs, and modify ACLs. For details, see “Modifying ACLs” on page 98.
• Add, remove and modify the attributes of objects in the data catalog. For details,
see “Managing attributes” on page 101.
• View the dependencies for a database operation, a virtual database operation, or a
data service. Dependencies are other database operations or data services that
receive output from the current view model or provide input to it.