IFS Applications 9/10

This chapter describes how to setup the IFS Applications 9 and IFS Applications 10 connectors.

The IFS Applications connectors are available as Connector Services as of Flow 6.14.

For documentation about how to connect to IFS Applications using the Database Connector bundled with Flow Server, click here.

Note 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.




Address to the IFS Applications Server

Use OpenID Login (Only applicable to IFS 10)

  • If OpenID Connect is enabled, set it to Yes to use the OpenID token to authenticate to IFS.

  • Cannot be used in combination with Run as Flow User.

Global User ID

User ID to authenticate against the database. To use IFS Applications as the auth provider for Flow, leave Global User ID and Password blank and provide a username for the connector on the Flow User.

Global Password

Password for the Global 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: 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 the database. It is possible that the communication between Flow Client and Flow Server will timeout prior to the command timeout. If the client experiences a timeout, but the database command does not, the database command will still be executed completely.


The IFS Applications connectors should use HTTPS to connect to the IFS Applications server.

Last updated