Database

The database connector is used to connect to various databases. Supported databases are Oracle, Microsoft SQL Server, IBM DB2 iSeries, IBM DB2, MySql Server, and IFS Applications.

Note for IFS Applications Enabling Run as Flow User will degrade IFS performance. This is an issue within IFS Applications. IFS is aware of the issue and there are currently no plans to fix it.

Note for IBM DB2 A prerequisite for Flow Server to be able to connect to IBM databases is that the IBM Client software has been installed on the Flow Server machine. This software must be obtained from IBM.

Configuration

Setting	Description
Database Type	The type of database
Database server	Address to the database server
Use OpenID Login	Valid for database type: IFS Applications 10. If OpenID Connect is enabled, set to Yes to use OpenID token to authenticate to IFS. Cannot be used in combination with Run as Flow User.
Global User ID	User to login to the database with
Global Password	Password for User
Run as Flow User	NOTE: Has a negative effect on performance: See note on top of the page. Valid for database types: IFS Applications 9 and IFS Applications 10. The Global User needs to have the Impersonate User system privilege The Global User needs to have at least the privileges as the users you are going to impersonate. Replaces user impersonation using the initialization command. If checked, the database queries will be executed as the current flow user id by default. The Flow User ID must match the DIRECTORY_ID of the IFS user you are impersonating. The user id can be overridden in the machine-task using "Run as User", regardless of the "Run as Flow User" setting.
Initialization Command	Optional command to execute immediately after successful login NOTE: For database types IFS9 and IFS10, there are restrictions on fnd_session_api usage. See "Run as Flow User".
Cleanup Command	An optional command to execute on the database after the operation has been completed.
Command Timeout	Command timeout, in seconds, to use when executing a script or a query. If not set, the default value for database type will be used (most likely 30 seconds). Please note that this is the timeout between Flow Server and database. It is possible that the communication between Flow Client and Flow Server will timeout prior to the command timeout. If the client experiences timeout, but the database command does not, the database command will still be executed completely.
Connection Pooling	Valid for database types: Oracle (10.2 or higher), Oracle (older versions), and Microsoft SQL Server. Sets whether connection pooling should be used.
Connection Timeout	Time, in seconds, to wait for a connection to be establishing before raising an error.

Security

The database connector connects directly to the database using different kinds of authentication protocols according to what kind of database it is connected to.