My Oracle Support Banner

How to set Additional Java VM arguments for a BPM Engine Running in IBM WebSphere Application Server (Doc ID 840422.1)

Last updated on MARCH 12, 2019

Applies to:

Oracle Business Process Management Suite - Version 5.5.10 to 5.7.3
Information in this document applies to any platform.
***Checked for relevance on 10-Jan-2012***


There are several additional Java VM arguments that might be needed to tune the BPM Engine, to enable particular fixes, or to enable additional debugging. The way to add these arguments is different between the Standalone and the J2EE Engine. This document addresses how to add additional arguments (or system properties) in a IBM WebSphere Application Server (WAS).

Here are a few examples of these arguments (the related issue for each one is shown between brackets):
-Dfuego.ebjengine.todoqueue.maxitems.nonlater=1000   [Unpublished <Bug 7730870>]
-Dfuego.ebjengine.todoqueue.maxitems.later=100   [Unpublished <Bug 7730870>]
-Dfuego.server.amountInstancesToCommit=250   [Unpublished <Bug 7731819>, Discontinued in 10.3.2. See <Note 983023.1> for more details]   [Unpublished <Bug 7729408>]
-Dfuego.fdi.polling.debug=true   [Unpublished <Bug 8472778>]
-Dfuego.fdi.hybrid.ldap.debug=true   [Unpublished <Bug 8351448>]
-Dfuego.fdi.hybrid.ldap.debug=detail   [Unpublished <Bug 8248055>]
-Dfuego.ldap.polling.fullscan.iterations=10   [Unpublished <Bug 9621017>]   [Unpublished <Bug 7726911>]


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.