IFS Connect Properties

This page is a reference list of IFS Connect–related properties: each name and a short explanation of what it does. The list is not complete—more properties may exist in your release, and this page can be updated over time. For every name available on your site, use IFS Connect → JSF properties → IFS Properties (or your administrator's export / documentation).

Note: Changes can affect live integrations—use an IFS administrator or partner where unsure. For yes/no flags, use true or false unless your administrator advises otherwise.

ifs.* — Connectors, Readers, Senders, Timeouts

"Typical default if unset" is what the code uses when the property is missing; always check what is configured in your environment.

Property	Type	Typical default if unset	What it does	If you change it
ifs.includeMetadataToEmailReaderAttachments	true/false	false	When email is read and has attachments, adds a short line before each attachment with sender, recipient, and file name.	true slightly increases payload size.
ifs.persistSynchronousMessages	true/false	false	Whether certain synchronous outbound ("wait for answer") messages are stored like normal messages.	true usually increases database activity and storage.
ifs.includeBodyInRestDelete	true/false	false	For REST DELETE, whether to send a message body (many APIs need no body).	true only if the remote API expects a body; otherwise calls may fail.
ifs.extractEnvelopAfterTransform	true/false	false	After XSL transform on a response, run envelope extraction again when the result is still wrapped.	true only when your integration still returns a wrapped envelope after transform.
ifs.fileReaderPickByDateCreated	true/false	false	For file readers: order by creation time instead of last modified.	Changes which file is picked first; not a speed setting.
ifs.enableApplicationMessageStat	true/false	false	Extra timing-style diagnostics for application messages.	true helps troubleshooting; under load can add memory use.
ifs.httpClientConnectTimeout	seconds	500	Wait when opening an HTTP connection (IFS Connect HTTP client).	Higher waits longer before failing; lower may fail on slow networks.
ifs.httpClientReadTimeout	seconds	500	Wait for data after the connection is open.	Higher tolerates slow responses; lower fails faster.
ifs.sftpClientTimeout	seconds	30	Establish SFTP session timeout.	Higher waits longer to connect; lower fails faster on bad networks.
ifs.sftpClientSocketTimeout	seconds	300	SFTP socket read/write timeout.	Higher keeps idle reads longer; lower may cut off slow transfers.
ifs.ftpClientTimeout	seconds	500	FTP/FTPS operation timeout.	Same pattern as other network timeouts.
ifs.ftpSupportedTlsVersion	text	default	FTPS TLS version for older servers (e.g. 1.2 for TLS 1.2); default is normal behavior.	Set only when FTPS requires a fixed TLS level with an older server.
ifs.includeClientCredentials	text	both	OAuth: send client id/secret both, header only, or body only (both / header / body).	Wrong value → token request fails (error names this property).
ifs.wsdlxsDouble	true/false	false	XSD generation: use double instead of float for decimal numeric fields.	true may affect schema compatibility with strict partners.

Dynamic Timeouts — ifs.workTimeout.*

Pattern	Type	Typical default	What it does	If you change it
ifs.workTimeout.Handler:Operation	seconds	0 (then other timeouts apply)	Work timeout for internal operation senders; use your real Handler:Operation from configuration (one property per pair).	Higher waits longer; lower fails faster.
ifs.workTimeout. + PL/SQL method	seconds	0 (then other timeouts apply)	Work timeout for PL/SQL senders; suffix is the method identifier your integration uses.	Balances wait vs cut-off for PL/SQL calls.

More ifs.* — Often Used Together with Connect

Property	Typical default if unset	What it does	If you change it
ifs.defaultFetchSize	10	Database rows fetched per round-trip in some reads.	Higher uses more memory per round-trip.
ifs.maxFetchSize	30	Upper cap on fetch size.	Higher allows larger fetches (more memory).
ifs.compressionLevel	BEST	Response compression (BEST, SPEED, DEFAULT, NONE).	Affects CPU vs size of responses on paths that compress.
ifs.connectUser	service account	Service user for IFS Connect internal calls.	Must match what security expects; wrong value breaks internal calls.
ifs.jdbcDriverClass	(driver class)	JDBC driver class for the database.	Must match your database; typically set by administration, not trial-and-error.

Note: On many cloud deployments, database connection and owner values are secrets, not editable here—ask your administrator.

fnd.* — IFS Connect Tuning

These names start with fnd. but are read the same way as ifs.* for IFS Connect (for example via IFS Properties or your server PROPERTIES setup).

Property	Type	Typical default if unset	What it does	If you change it
fnd.connectReaderQueueMaxReadAttempts	number	3	How many times to retry loading a queued reader message from the database if it is not found yet.	More retries + waits → longer before a real problem shows; fewer → faster failure if rows are late.
fnd.connectReaderQueueReadAttemptWaitTime	seconds	3	Pause between those retries (seconds).	Higher waits longer between attempts; lower may miss rows that appear a moment later.
fnd.soapServiceGatewayPort	text	(none)	SOAP service gateway port used when building certain URLs.	Wrong port → SOAP calls to the gateway fail or go to the wrong place.
fnd.restrictedQueueChunk	number	10000	Batch size when processing the restricted queue.	Larger → more work per pass, more memory and longer units of work; not a substitute for fixing slow logic.
fnd.restrictedQueueStopCheck	number	1	How often to re-check stop conditions during restricted queue work.	Changes how often processing checks whether to stop; affects responsiveness vs overhead.
fnd.restrictedQueueMaxProcessTime	seconds	300 (5 min)	After this time on a restricted queue, the framework may resend the JMS message so work continues in a new step (default 300 s).	The Connect reader bean uses a 360 s transaction limit (about 300 + 60 s buffer). Increasing this without your IFS / platform administrator also increasing that transaction limit can cause transaction timeouts or rollbacks instead of a clean handover.
fnd.restrictedQueueCheckDelay	seconds	30	Delay before a message is checked again (JMS delivery delay).	Higher → slower leak checks; lower → more frequent checks.
fnd.transformerSpoolDir	path	(none)	Directory for transformer spool files.	Must be a valid, writable path for your server.
fnd.timerDelayOnError.min	ms	5000	Minimum backoff after timer errors (milliseconds).	Lower → retries sooner (can hammer a failing dependency).
fnd.timerDelayOnError.max	ms	60000	Maximum backoff for timers (milliseconds).	Caps how long timers wait between attempts after errors.
fnd.timerDelayOnError.stop	ms	3600000	Upper stop delay used for reader-style backoff (milliseconds).	Higher → much longer waits before some retries on readers.
fnd.timerDelayOnError.minimize	ms	600000	Minimize delay cap for readers after errors (milliseconds).	Caps reader-related backoff in the minimize path.
fnd.timerDelayOnError.pctIncrease	percent	50	Percent increase when stretching delay between retries after errors.	Higher → backoffs grow faster after repeated errors.
fnd.{instance}.failonce	true/false	false	Replace {instance} with your Connect instance name (example: fnd.MY_READER.failonce). Only one failure attempt before giving up when the address has not been retried yet.	true changes retry behavior—get partner / admin review before use.
fnd.{instance}.msgPropName	text	(none)	Replace {instance} with your Connect instance name (example: fnd.MY_JMS.msgPropName). JMS message property name for that instance.	Must match how your JMS routing expects properties on the message.