Peter,

> I presume that I'd like to use the new optimized wire protocol. I
> haven't seen a specific discussion about it, though.

The optimized wire protocol is not yet supported in pure Java
implementation of the driver, only when driver uses Firebird client
library (that is done via libjaybird21.so for driver types NATIVE, LOCAL
and EMBEDDED).

> Regarding the XML file, it's the Rhapsody Interface/Integration
> engine (from Orion Health) that requires it. What it does with the
> XML, I don't know. I'm assuming that it parses out the database
> connection and SQL elements and passes them along to any JDBC
> compliant driver. So, probably my question should have omitted any
> reference to XML.

Then just check the existing examples in Rhapsody, it should work.
Please note that Firebird (and Jaybird) supports only IN or OUT
parameters, but not INOUT.

> Is the JDBC driver exposed to any calling
> application by virtue of either the .so being in the linux sbin path,
> or jar file in the java classpath?

Primarily by jar in classpath. The .so is used by the driver to access
the Firebird's client library.

> IOW, if the calling application
> knows how to talk to a JDBC driver, it needs to supply certain
> elements like socket info to connect to the database, SQL statement
> to do something with the database, etc., and also the JDBC driver
> needs to be there waiting for a request.

JDBC driver is on the client side. But in general your comments are correct.

Roman