By JuergenKress on Jul 24, 2013
We can tune default Application Module settings for Application Module pools, connection pools & data sources as per our requirements. It is mostly depends on use or access of an Application Module.
As a performance optimization, when an instance of an AM is returned to the pool in "managed state" mode, the pool keeps track that the AM is referenced by that particular session. The AM instance is still in the pool and available for use, but it would prefer to be used by the same session that was using it last time because maintaining this so-called "session affinity" improves performance.
So, at any one moment in time, the instances of application modules in the pool are logically partitioned into three groups, reflecting their state:
· Unconditionally available for use
· Available for use, but referenced for session affinity reuse by an active user session XYZ
· Unavailable, inasmuch as it's currently in use (at that very moment!) by some thread in the web container.
values that you supply through the Configuration Manager are saved in
an XML file named bc4j.xcfg. All of the configurations for all of the
application modules in a single Java package are saved in the same file.
For example, if you have a EmployeeReviewModule and a BonusAssignment
application module which both live in the com.yourcompany.hr package,
then the configuration information for both of these modules will be
saved in the bc4j.xcfg file in the ./com/yourcompany/hr/common directory
in your project's source path. When your project is compiled, this
bc4j.xcfg file gets copied to the same directory in your project's out
path, so that the ADF framework can find it at runtime.
Note that child elements of the <AppModuleConfig> tag appear with tag names matching their property values. It's also important to understand that if a property is currently set to its runtime default value, then the Configuration Manager does not write the entry to the bc4j.xcfg file.
User can manually manage Application Pool & Connection Pool using
Application Pool Parameters
1. Pool Behavior Parameters
1. Failover Transaction State Upon Managed Release (jbo.dofailover)
2. Row-Level Locking Behavior Upon Release (jbo.locking.mode)
3. Disconnect Application Module Upon Release (jbo.doconnectionpooling)
4. Enable Application Module Pooling (jbo.ampool.doampooling)
5. Support Dynamic JDBC Credentials (jbo.ampool.dynamicjdbccredentials)
6. Reset Non-Transactional State Upon Unmanaged Release (jbo.ampool.resetnontransactionalstate)) Read the article here.
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.