1.0

Table Of Contents
The default behavior executes the procedure only on the query member:
CALL procedureName()
CREATE Statements
Use Create statements to create functions, indexes, procedures, schemas, synonyms, tables, triggers, and views.
CREATE ASYNCEVENTLISTENER
Installs an AsyncEventListener implementation to SQLFire peers in a specied server group.
Syntax
CREATE ASYNCEVENTLISTENER listener-name
(
LISTENERCLASS 'class-name'
INITPARAMS 'init-params'
[ MANUALSTART boolean-constant ]
[ ENABLEBATCHCONFLATION boolean-constant ]
[ BATCHSIZE integer-constant ]
[ BATCHTIMEINTERVAL integer-constant ]
[ ENABLEPERSISTENCE boolean-constant ]
[ DISKSTORENAME store-name]
[ MAXQUEUEMEMORY integer-constant ]
[ ALERTTHRESHOLD integer-constant ]
)
SERVER GROUPS ( server_group_name [, server_group_name ]*)
LISTENERCLASS
The fully-qualied name of the class that implements the AsyncEventListener interface. For
example, "user.application.TestAsyncEventListener". If you are conguring the built-in
DBSynchronizer implementation, specify com.vmware.sqlre.callbacks.DBSynchronizer.
INITPARAMS
Specify initialization parameters to pass to the init() method of the AsyncEventListener
implementation. SQLFire passes the single string of initialization parameters when you execute
the CREATE ASYNCEVENTLISTENER statement. You must include the INITPARAMS
argument, even if it denes no parameters (INITPARAMS '').
The built-in DBSynchronizer requires two comma-separated parameters and has two optional
parameters. The initialization string uses the format: 'db-driver-class,db-url[,user,password]':
db-driver-class species the fully-qualied class name of the JDBC driver to use for
connecting to the external database.
db-url species the connection string to use to connect to the external database.
[,user,password] optionally species the username and password to use for the connection.
Specify the ,user,password parameters to ensure that the password value never appears in
external exception messages.
If instead you include the username and password as part of the db-url (for example by
appending ?user=username&password=password), SQLFire attempts to mask password
values in exception messages by matching common patterns such as password=..., password=..,
or pwd=... However, the actual value may appear in exception messages under certain
circumstances.
For example, to connect to an external Apache derby database, you would specify a
DBSynchronizer INITPARAMS string similar to
'org.apache.derby.jdbc.EmbeddedDriver,jdbc:derby:newDB;create=true;'.
MANUALSTART
vFabric SQLFire User's Guide436
vFabric SQLFire Reference