User guide

Creating view models
36 Data Integration with Sybase Avaki Studio
thought of as single-use database operations. You can run an ad-hoc query using
either the CLI or the JDBC driver. For information about using the CLI to run an
ad-hoc query, see the Sybase Avaki EII Command Reference. For information about
using a JDBC driver to run an ad-hoc query, see the Sybase Avaki EII API Guide.
• Allow database identity mappings: Check this box if database identity mappings
are allowed on this database connector. A database identity mapping is a spe-
cial-purpose user alias. It allows operations performed by some Avaki user on a
particular database connector to be executed in the name of an alternate user/pass-
word combination. For details about configuring database identity mappings, see
the Sybase Avaki EII Administration Guide.
• JDBC fetch size: This parameter can be used to fine-tune performance of database
operations. When an application uses the JDBC driver to execute a database opera-
tion, it typically processes the rows that are returned one after another, but the
driver applies a buffering optimization by fetching rows in batches; the fetch size is
the number of rows to be fetched in such a batch. In most circumstances, the
driver’s default fetch size will be optimal, so you’ll want to keep the Default set-
ting. But if you decide that database operations executed through this database con-
nector should generally use a nondefault fetch size, enter the relevant number of
rows in the Custom field. Note: you can also set the fetch size for individual data-
base operations. See the Sybase Avaki EII Provisioning and Advanced Data Inte-
gration Guide for details.
• Properties: Optional. Specify any connection properties that are required for your
database. For information about database-specific properties, see your database
documentation.
• Connection pooling: Specify whether to enable Avaki connection pooling. When
connection pooling is enabled, database connections can be reused, which typically
improves performance for JDBC applications. By default, Avaki connection pooling
will keep up to 15 connections open to a back-end database. If your driver has
built-in connection pooling, it may not be necessary to use Avaki connection pool-
ing. Select one of the following options:
— Use Avaki connection pooling with the default pool size (15).
— Use Avaki connection pooling with a custom pool size: Enable connection pool-
ing and specify the desired connection pool size.
— Don’t use Avaki connection pooling.
• XA driver (optional): Specify an XA driver class if you plan to use this database
connector to support distributed transactions. This class must reside in the JAR file