General Connection Document Considerations

This section lists general considerations for using a connection document.

Rollback

The "Rollback upon error" option, specified on a connection document, will not be effective when a transaction within an activity must be closed to complete the next step of the operation. For example, a Direct Transfer activity, with "Overwrite existing data" enabled", cannot restore the truncated data if the transfer portion fails.

View Specification

When specifying view names on a connection document, only list views that will actually be used by all activities that use the connection document. Specifying a view name that is not needed by the calling activity may cause that activity to fail.

Connection Pooling

For optimum performance of a connector, underlying connections to the external systems can be pooled. This pooling occurs in the connector API and is automatic with subsequent connections. LotusScript® provides a simple programmatic interface to connection pooling.

The LCSession class exposes a property called "ConnectionPooling." Setting this property to True enables connection pooling. For more information, see the "Connection Pooling" section in the Connector LotusScript® Extensions Guide.

Connecting to Supported Data Source

In order to connect to a supported data source, you must have the required connectivity software for that data source installed on your server. Verify that all of your database software is installed and current with all available maintenance releases and fix packs before attempting to create connection documents.