10.02.2013 Views

Progress Sonic ESB Configuration and Management Guide

Progress Sonic ESB Configuration and Management Guide

Progress Sonic ESB Configuration and Management Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Table 8. DB2 Connection Properties (continued)<br />

Property Description<br />

StripNewlines<br />

OPTIONAL<br />

UseCurrentSchema<br />

OPTIONAL<br />

<strong>Progress</strong> <strong>Sonic</strong> <strong>ESB</strong> <strong>Configuration</strong> <strong>and</strong> <strong>Management</strong> <strong>Guide</strong> 8.5 160<br />

DB2<br />

{true | false}<br />

Specifies whether new-line characters in a database operation are sent to<br />

the DB2 server:<br />

● true — The DB2 driver removes all new-line characters from<br />

database operations.<br />

● false — If you know that the database operations used in your<br />

application do not contain new-line characters, setting StripNewLines<br />

to false eliminates parsing by the DB2 server <strong>and</strong> improves<br />

performance.<br />

The default is true.<br />

{true | false}<br />

Specifies whether results are restricted to the tables in the current schema<br />

if a DatabaseMetaData.getTables call is called without specifying a<br />

schema or if the schema is specified as the wildcard character %.<br />

Restricting results to the tables in the current schema improves the<br />

performance of calls for getTables methods that do not specify a schema.<br />

This property determines behavior as follows:<br />

● true — Results that are returned from the getTables method are<br />

restricted to tables in the current schema.<br />

● false — Results of the getTables method are not restricted.<br />

The default is false.<br />

User The case-sensitive user name used to connect to the DB2 database.<br />

WithHoldCursors<br />

OPTIONAL<br />

{true | false}<br />

Determines whether the cursor stays open on commit—either DB2 closes<br />

all open cursors (Delete cursors) after a commit or leaves them open<br />

(Preserve cursors):<br />

● true — The cursor behavior is Preserve.<br />

● false — The cursor behavior is Delete. Rolling back a transaction<br />

closes all cursors regardless of how this property is specified.<br />

The default is true.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!