Tuning JDE for ORACLE.

JDE113

Member
Hi all.
My company is using JD EnterpriseOne 8.12 oracle database 10R1. I was install and configuration JD Edwards EnterpriseOne 8.96 HTML Web Server for Microsoft Windows-Based Systems and Oracle Application Server.
JDE application performance very slow.

Oracle database had been tuned and performance very good.
I was change some value of parameters in JAS.ini and JDBJ.ini file but i don't know these are appropriate.

Here is content of that files:
1. JAS.INI FILE:

<font class="small">Code:</font><hr /><pre> # Please refer to the JAS Installation Guide for detailed information on
# this file.
# WORKING CONFIGURATION FILE =D:\OraHome_1\j2ee\JasOC4J\applications\jasapp\webclient\WEB-INF\classes\jas.ini
#

[SECURITY]
DataSource=System - 812
NumServers=2
SecurityServer=AS01
SecurityServer1=AS02
UseLogonCookie=TRUE
CookieLifeTime=72000
SSOEnabled=FALSE
SSOUserIDOnly=FALSE
# set password only if SSOUserIDOnly is set to TRUE
Password=
#Version Security level for task explorer - 0 is default, set to 1 for strict version security
StrictVersionSecurity=0
OracleSSO=FALSE

[OWWEB]
PathCodes=('PD812')
MO QUEUE=webclient/moqueue
ProxyPoolSize=50
F0005Prefix=DR
F0004Prefix=DT
#ProxyHost=
#ProxyPort=
MAXUser=100
FtpPort=21
FtpUsr=anonymous
FtpPwd=anonymous
UseMOWinNTShare=FALSE
PrintImmediate=TRUE
KeepUBE=TRUE
UBEQueue=QBATCH
SystemDateFormat=DME
SystemDateSeparator=.
VirtualClientTimeOut=3600000
InYourFaceError=TRUE
ShowSubmitJobs=TRUE
AutoPopulate=ON
AutoPopulateBufferSize=50

# The HelpPath key determines where JAS looks for help files.
# Syntax: "http://[machine]/[path]/".
# Note, if you specify "/jde/owhelp/", this machine is assumed.
HelpPath=/jde/owhelp/
PPCSetDefaultFocus=FALSE

# auto resume interval for fetch update dialogs, in milliseconds
TimeWaitBeforeAutoResume=1000
# Global Page size for grids.
# This setting overrides the application level page size when the application level page size is smaller # than this setting.
# Valid values are from 0 to 100. When this value is greater than 100, the Global Page size will be set # to 100.
# The default value is 0, which will never override application level page size.
#GlobalPageSize=100
GlobalPageSize=12

# the default section size for "go to end" functionalilty
# if there are more than 60 visible columns on the grid, the system will reduce this section size by 50%.
#SectionSize=200
SectionSize=72

#This setting changes web client hotkey behavior on Internet Explorer only. When it's turned on, the right alt key
#will not invoke web client hotkey functions. In some foreign countries people may need to use right alt key to enter
# special characters. In that case this setting should be set to TRUE.
DisableRightAltKey=FALSE

# Max file size for upload. Default 50 Mb
MaxFileUploadSize=50

#Turn on/off Item Help Show BSVW Info feature.
ShowBSVWInfo=FALSE

#Turn on/off auto populate feature
AutoPopulate=ON

#The MAX number of values the autopopulate buffer holds
AutoPopulateBufferSize=50


[CACHE]
# These intervals are in milliseconds. For example, 60000ms = 1 minute
#UserSession=3600000
#UserProfile=1200000
#CacheCheck=60000
#Menu=3600000
UserSession=28800000
UserProfile=28800000
ViewTable=28800000
ResultSet=2880000
Connection=28800000
Security=28800000
UDCInfo=28800000
CacheCheck=60000
Menu=28800000

[SERVER COMPONENTS]
#
# Do not modify this section
#
com.jdedwards.runtime.virtual.MAFComponentLoader
com.jdedwards.jas.UserManager
com.jdedwards.jas.JDBCProxy
com.jdedwards.jas.JDEORB
com.jdedwards.jas.DDValidation
com.jdedwards.jas.security.SecurityBroker
com.jdedwards.jas.UDCJDBC
com.jdedwards.jas.JDEUDCText
com.jdedwards.jas.JDEUpdates
com.jdedwards.jas.JDEQueries
com.jdedwards.jas.JDEOWDirect
com.jdedwards.jas.ServerQuery
com.jdedwards.jas.JDESignon
com.jdedwards.jas.PerfMonInit

[JDENET]
# Enterprise Server JDENET port
serviceNameConnect=6014

# JAS Server JDENET Listening port
serviceNameListen=6013

# Maximum number of dedicated kernel types
maxKernelRanges=1

# Time out value for requests sent to the Enterprise Server
enterpriseServerTimeout=90000

# JDENET socket connection pool size
#maxPoolSize=50
maxPoolSize=100

# Directory for JDENET temporary file
tempFileDir=c:\var\temp

# Clustered logical datasource retry interval
ClusterRetryInterval=60000

# Dedicated Kernel Definitions
[JDENET_KERNEL_DEF1]
krnlName=XAPI Kernel
processClassName=com.jdedwards.runtime.virtual.xapi.PublishedMessageProcessor
startMessageRange=15001
endMessageRange=15250
maxNumberOfThread=3


[SERVER]
# Enterprise Server and port providing Glossary Text information
glossaryTextServer=AS02:6014

# Encoding scheme
# 1252- English and Western European
# 932- Japanese
# 950- Traditional Chinese
# 936- Simplified Chinese
# 949- Korean
codePage=1251
#per application team, set the default setting to true. This will impact the
#performace negatively, change it back to false if jargon is not needed
enableJargon=TRUE
jargonCacheTimeout=360000

[LOGS]
# JDBC Trace (in stdout)

rtdebugTrace=FALSE
rtlog=D:\OraHome_1\j2ee\JasOC4J\log\rt.log
rtdebug=D:\OraHome_1\j2ee\JasOC4J\log\rtdebug.log


rtlogType=All
#or =BSFN|TableIO|SYSFUNC|MISC|ER|EVENT|THREAD (any combination).


# The STDERR and STDOUT keys must point to the same directory that was supplied for the
# STDERR and STDOUT fields when defining the WebSphere Application Server.
# This is usually the INTERNET directory under B7333.
#
#stderr=~ORACLEHOME~/j2ee/~OC4JNAME~/log/stderr.txt
#stdout=~ORACLEHOME~/j2ee/~OC4JNAME~/log/stdout.txt
stderr=D:\OraHome_1\j2ee\JasOC4J\log\stderr.txt
stdout=D:\OraHome_1\j2ee\JasOC4J\log\stdout.txt

[TRANSACTIONS]
# Configuration settings to customize transaction processing within JAS.

# ReapInterval : Interval in minutes of how often the TransactionReaper
# should check for abandoned transactions.
# Valid values: Integer from 1 to n
# Default: 5 minutes
# MaxAge : Maximum age in minutes of a transaction. Transactions
# older than this will be rolled back by the
# TransactionReaper.
# Valid values: Integer from 1 to n
# Default: 10 minutes
#

ReapInterval=5
MaxAge=10

[ERPINTERACTIVITY]
#interactivity level. valid values are: LOW, MEDIUM, and HIGH
InteractivityLevel=HIGH
# whether multiple browsers fetch is enabled
MultipleBrowserEnabled=FALSE
# the maximum number of open browsers for each user
MaxOpenBrowsers=10
# the number of records fetched for each database fetch before getting a system warning
DBFetchLimitBeforeWarning=2000

[TASKEXPLORER]
Version=2

[PIM Sync]
# Synchronization super user information.
# This user information is used as a proxy user to create sessions to EnterpriseOne for all the users
# synchronizing CONTACTS, APPOINTMENTS, and TASKS.
# This user must have full access to the CONTACTS, APPOINTMENTS, and TASKS database.
# MUST BE CHANGED to match installation
user=JDE
password=jde123
environment=DV812
role=*ALL
#
# Session pool size
# A session represents a connection (i.e. signon) to EnterpriseOne.
# All the session in the pool will be created using the synchronization super user information.
# It is recommended to set this number to match the number of CallObject kernels on
# the EnterpriseOne Enterprise Server.
#
poolSize=20
#
# Synchronization business function names, update this after APP. Devlelopment finalized
# DO NOT CHANGE
contactBSFN=PIMSynchronize
appointmentBSFN=PIMSynchronize
taskBSFN=PIMSynchronize
#
# trace request/response XML to JASDEBUG, true is on, false is off
showXML=false
#
# trace request/response XML to stdout, true is on, false is off
verbose=false

[EVENTS]
#
# The InitialContextFactory and JNDI provider URL for the event server's JNDI service.
#
initialContextFactory=com.ibm.websphere.naming.WsnInitialContextFactory
jndiProviderURL=corbaloc:iiop:localhost:2809

#Specify the Mail Merge Location on Web Server, it should be under the webclient dir.
[MAIL MERGE AND DOC GEN]
MailMergeLocation=D:/OraHome_1/j2ee/JasOC4J/applications/jasapp/webclient/MailMerge


#Specify the necessary settings from the readme file created by the installation
#of the Transaction Server Component - Performance Monitor

[PERFMON]

#
# URL of Performance Monitor. Used by instrumented code to register with
# Performance Monitor.
#
monitorUrl=none

#
# PerfMon Pool size
#
ClientPerfCacheSize=100

#
# Identifier for source of performance data.
#
hostPort=

#
# Transaction will be timed out by Monitor server if end transaction is not
# received this number of milliseconds after the start transaction.
#
transactionTimeout=60000

#
# Not currently being used.
#
sampler=60
</pre><hr />

2. JDBD.INI FILE:

<font class="small">Code:</font><hr /><pre>
#=======================================================================
# jdbj.ini - JDBj configuration
#
# This file contains configuration information for JDBj, which provides
# general database access capabilities on behalf of J.D. Edwards Java
# solutions.
# WORKING CONFIGURATION FILE = D:\OraHome_1\j2ee\JasOC4J\applications\jasapp\webclient\WEB-INF\classes\jdbj.ini
# IMPORTANT: All keys in this file are case sensitive.
#=======================================================================

#=======================================================================
# ERP specific information
#
# These sections apply only when accessing ERP data. These sections are
# ignored for standalone database access.
#=======================================================================

#-----------------------------------------------------------------------
# Bootstrap session
#
# The user, password, role information is optional. It is used by the
# the JDBJ Unit tests and JDBExplorer only if these parameters are not
# specified on the command line. The environment is required field otherwise
# JAS cannot signon to the HTML client.
#
# NOTES: * This information in this section corresponds to the information
# specified in the [DB SYSTEM SETTINGS] section of this installation's
# JDE.INI file.
#-----------------------------------------------------------------------

[JDBj-BOOTSTRAP SESSION]
user=JDE
password=jde123
environment=PY812
role=*ALL

#-----------------------------------------------------------------------
# Bootstrap physical data source
#
# This defines the data source where the OCM and some other system
# tables reside. JDBj uses this at bootstrap time and later to look up
# OCM entries on demand. If it is not valid, then no ERP database
# access is possible.
#
# Here is a description of each field in this section:
#
# ---------------- --------------------------------------- -----------
# Field Description Applies to
# ---------------- --------------------------------------- -----------
# name The data source name. This is not that All
# important for bootstrap connections,
# but it does show up in error messages
# and the log.
# ---------------- --------------------------------------- -----------
# databaseType The database type. One of the All
# following:
#
# I = AS/400
# O = Oracle
# S = SQL Server
# W = UDB
# M = MSDE
# ---------------- --------------------------------------- -----------
# server The server (i.e. the host), or AS/400,
# "localhost". SQL Server
# MSDE
# ---------------- --------------------------------------- -----------
# database The database. Oracle,UDB
# ---------------- --------------------------------------- -----------
# serverPort The server port. SQL Server
# ---------------- --------------------------------------- -----------
# physicalDatabase The physical database (used as library AS/400,
# qualifier for AS/400). SQL Server,
# MSDE
# ---------------- --------------------------------------- -----------
# owner The owner. Oracle,
# SQL Server,
# UDB,
# MSDE
# ---------------- --------------------------------------- -----------
# lob Supports lobs. Oracle,
#
# AS/400
# ---------------- --------------------------------------- -----------
# unicode Performs unicode conversion. SQL Server
# MSDE
# ---------------- --------------------------------------- -----------
# databaseInstance The instance name of server. (JDELocal) MSDE
# ---------------- --------------------------------------- -----------
# translateOn AS400 translate on (default is FASLE) AS400
# ---------------- --------------------------------------- -----------
#-----------------------------------------------------------------------
#
# NOTES: * This information in this section should match the
# corresponding information specified in the
# [DB SYSTEM SETTINGS] section of this installation's JDE.INI
# file.
#-----------------------------------------------------------------------

[JDBj-BOOTSTRAP DATA SOURCE]
name=System - 812
databaseType=O
server=oraclus
serverPort=1521
database=oraclus
physicalDatabase=
owner=SY812
lob=true
unicode=true
databaseInstance=
translateOn=

#-----------------------------------------------------------------------
# Bootstrap spec data source (Optional)
#
# This defines the data source where the serialized spec tables reside.
# JDBj uses this at bootstrap time and after to look up serialized spec
# objects on demand. JDBj first looks for the name specified in this
# section in the Data Source Master table (F98611). If it finds a data
# source there, it uses it to read the serialized spec tables. If it
# does not find the data source in the Data Source Master table, then
# it initializes a new data source based on the rest of the fields in
# this section.
#
# If this section is not specified, then JDBj uses the OCM to find the
# serialized spec tables. If it is not valid, then no ERP database
# access is possible.
#
# See the description for "Bootstrap physical data source" above for
# information about which fields must be filled in for a given database
# platform.
#-----------------------------------------------------------------------

# [JDBj-SPEC DATA SOURCE]
# name=
# databaseType=
# server=
# serverPort=
# database=
# physicalDatabase=
# owner=
# lob=false
# unicode=true
# user=
# password=
# databaseInstance=
# translateOn=

#=======================================================================
# END - ERP specific information
#
# The rest of the sections apply when accessing ERP and standalone data.
#=======================================================================

#-----------------------------------------------------------------------
# JDBC drivers
#
# This defines JDBC drivers and JDBC specific settings.
#-----------------------------------------------------------------------

[JDBj-JDBC DRIVERS]
ORACLE=oracle.jdbc.driver.OracleDriver
#AS400=com.ibm.as400.access.AS400JDBCDriver
SQLSERVER=com.microsoft.jdbc.sqlserver.SQLServerDriver
#UDB=COM.ibm.db2.jdbc.app.DB2Driver

[JDBj-ORACLE]
tns=tnsnames.ora

[JDBj-LOGS]
jdbcTrace=false

[JDBj-SERVER]
dbcsConversionTolerant=true

#-----------------------------------------------------------------------
# Connection pool settings
#-----------------------------------------------------------------------

[JDBj-CONNECTION POOL]

; The minimum number of connections to a data source. When closing old connections,
; the value set by this parameter will remain in the pool regardless of use.
;
; Valid values: 0 or greater
; Default value: 5

minConnection=5

; The maximum number of connections to a data source for all users. Additional
; database connection requests beyond this value will be queued for the next available
; connection.
;
; Valid values: 1 or greater (must be equal to or greater than "minConnection")
; Default value: 50

#maxConnection=50
maxConnection=100

; The number of connections to initialize upon pool creation.
;
; Valid values: a value equal to or greater than "minConnection" AND equal to or
; less than "maxConnection"
; Default value: 5

#initialConnection=5
initialConnection=10

; The increment of connections the system will create when a request for a connection
; cannot be satisfied with the current allocation as long as the maxConnection value
; has not been reached.
;
; Valid values: The rule of thumb is (poolGrowth >= maxConnection/10)
; Default value: 5

poolGrowth=5

; Amount of time in milliseconds that a connection remains idle before it is flagged
; to be cleaned up. Keeping this value high may or may not add to performance. Reducing
; the value may reduce memory consumption.
;
; Valid values: 0 or greater
; Default value: 1800000 (30 minutes)

;connectionTimeout=1800000

connectionTimeout=600000

; Amount of time in milliseconds that the pool cleaner is set to clean data sources
; that have a validation string. When cleaning occurs, any connections which have been
; flagged as idle will be cleaned up. The amount of time between a connection
; becoming idle and being cleaned up can be as long as the connectionTimeout value plus
; the cleanPoolInterval value.
;
; Valid values: 0 or greater
; Default value: 600000 (10 minutes)

cleanPoolInterval=600000

; The maximum number of JDBC prepared statements cached on each JDBC connection.
;
; Valid values: 0 or greater
; Default value: 50

maxSize=50

; The number of JDBC statements purged from a JDBC connection if the maxSize limit is
; reached. The statements purged will be the statements in the cache which have not
; been used for the longest amount of time.
;
; Valid values: The rule of thumb is (cachePurgeSize >= maxSize/10 + 2)
; Default value: 5

cachePurgeSize=5

#-----------------------------------------------------------------------
# JDBj Runtime properties
#
# These are all optional. They correspond to system runtime properties
# applicable to JDBj logical connections.
#
# NOTES: * In each case, the values listed are the defaults. The
# template default entries are commented out. Make sure
# and remove the pound sign (#) when changing these values.
#-----------------------------------------------------------------------

[JDBj-RUNTIME PROPERTIES]

; AS400 Database ASP property. Use this setting if you are running your iSeries
; server with multiple user databases or IASP (Independent Auxiliary Storage Pool)
; and have your EnterpriseOne tables located on the IASP. The IASP name can be found
; by using the command WRKRDBDIRE. This entry is not needed if you only have *LOCAL
; configured on your system in the WRKRDBDIRE Remote Location name.
;
; Valid values: Any valid string

# AS400DatabaseASP=null

; AS400 package name property. Overrides the default sql package
; name on the AS400 with the specified name.
;
; Valid values: Any valid string

# as400Package=JDBj

; AS400 package library name property. Overrides the default sql package
; library name on the AS400 with the specified name.
;
; Valid values: Any valid string

# as400PackageLibrary=JDBj-Library

; AS400 extended dynamic property. Overrides the default extended dynamic
; setting with the specified setting. If specified to a false, AS400 database
; will not use packages. This will have a negative impact on performance.
;
; Valid values: true, false

# as400ExtendedDynamic=true

; Data cache entry size threshold property. Sets the maximum
; size (in rows) for a single entry in the data cache. If a
; potential entry exceeds this threshold, then it will not be
; cached. -1 indicates that all eligible entries should be
; cached.
;
; Valid values: -1 or greater

# dataCacheEntrySizeThreshold=500

; Data cache entry threshold property. Sets the maximum size (in
; entries) for the data cache. If the data cache exceeds this
; size, then the least recently used entries are removed to
; make room for the new entry. -1 indicates that there is no
; maximum.
;
; Valid values: -1 or greater

# dataCacheEntryThreshold=100

; Data varification property. Enable or disable the data verification
; between actual data and EnterpriseOne specification for insert and
; update operations.
; The verification is performed on the following types:
; - EVDT_CHAR
; - EVDT_STRING
; - EVDT_NID
; - EVDT_TEXT
; - EVDT_VARSTRING
; - EVDT_VARCHAR
; - EVDT_MATH_NUMERIC
;
; This property will have a negative impact on performance.
;
; Valid values: true or false

# dataVerification=false

; Oracle NCHAR Trimming property. Indicates if the Oracle NCHAR
; Trimming logic is turned or off. True means the returned NCHAR
; data is intact. False means always right trim the returned
; NCHAR data.
;
; Valid values: true or false

# disableOracleNcharTrimming=false

; E1Menu cache purge property. Sets the number of
; milliseconds after which inactive spec cache entries are
; purged. 0 means to never purge spec cache entries.
;
; Valid values: 0 or greater

# E1MenuCachePurge=3600000

; Force single data source property. Indicates whether JDBj
; should force operations involving multiple database objects to
; run against a single data source. If this is true, JDBj will
; only resolve the physical data source for the first database
; object involved in a given operation. Otherwise, JDBj will
; resolve physical data sources for all database objects and
; throw an exception if a single operation spans multiple data
; sources.
;
; Valid values: true, false

# forceSingleDataSource=false

; Result set timeout property. Sets the the number of
; milliseconds for the result set timeout. A result set will
; timeout if it has not had any operations for a period of time.
; -1 means that result sets will not timeout.
;
; Valid values: -1 or greater

# resultSetTimeout=60000

; Retry interval property. Sets the interval (in milliseconds)
; to wait before retrying idempotent database operations. -1
; means not to retry, 0 means retry immediately.
;
; Valid values: -1 or greater

# retryInterval=0

; Retry maximum property. Sets the number of times to retry
; idempotent database operations. -1 means to retry
; indefinitely.
;
; Valid values: -1 or greater

# retryMaximum=5

; OCM cache purge property. Sets the number of
; milliseconds after which inactive OCM cache entries are
; purged. 0 means to never purge OCM cache entries.
;
; Valid values: 0 or greater

# ocmCachePurge=3600000

; Personal Spec Versions property. Indicates if user's personal
; version can be read. This is only enforced during a read and not
; during a spec generation. If it set to a true, the personal version
; will be returned if it exists, otherwise the public version will be
; returned. If the property is set to a false, then the personal
; version will not even be read and we will default to the public
; version
;
; Valid values: true , false

# personalSpecVersions=false

; Service cache purge property. Sets the number of
; milliseconds after which inactive service cache entries are
; purged. 0 means to never purge service cache entries.
;
; Valid values: 0 or greater

# securityCachePurge=3600000


; Service cache purge property. Sets the number of
; milliseconds after which inactive service cache entries are
; purged. 0 means to never purge service cache entries.
;
; Valid values: 0 or greater

serviceCachePurge=28800000

; Spec cache purge property. Sets the number of
; milliseconds after which inactive spec cache entries are
; purged. 0 means to never purge spec cache entries.
;
; Valid values: 0 or greater

specCachePurge=28800000

; Spec consistency check property. Sets the level of spec
; consistency checking. Set this property to a higher level to
; improve exception messages relating to spec inconsistency
; problems. Set this to a lower level when it is not needed
; since it may degrade performance.
;
; Valid values: full, minimal, none

# specConsistencyCheck=minimal

; Spec generate on demand property. Indicates whether JDBj
; should generate specs on demand if it can not find them
; in the persistent cache.
;
; Valid values: true, false

# specGenerateOnDemand=false

; Transaction isolation property. Sets the isolation level to be
; used for transactions.
;
; Valid values: default, none, read uncommitted, read committed,
; repeatable read, serializable

# transactionIsolation=default

; Transaction timeout property. Sets the number of milliseconds
; for the transaction timeout. A transaction will timeout if it
; has not had any operations for a period of time. If this
; timeout is set to a -1 then the transaction timeout feature
; will be disabled. (This currently only happens when JDBj is
; run as part of a JAS transaction.)
;
; Valid values: -1 or greater

transactionTimeout=120000

; Trigger auto fetch property. Indicates whether JDBj should
; automatically fetch rows to be changed in order to pass them
; to ERP triggers. This is needed for certain triggers to
; work properly.
;
; Valid values: none, single, all

# triggerAutoFetch=none

; Updatable result set timeout property. Sets the the number of
; milliseconds for the updatable result set timeout. An
; updatable result set will timeout if it has not had any
; operations for a period of time. -1 indicates that updatable
; result sets should have the same value as RESULT_SET_TIMEOUT.
;
; Valid values: -1 or greater

# updatableResultSetTimeout=-1

; Usage execution threshold property. Sets the expected maximum
; time (in milliseconds) for a single database operation to
; execute. If a single database operation takes longer than this
; threshold, then the statement and time will be logged as part
; of usage tracking.
;
; Valid values: 0 or greater

# usageExecutionThreshold=20000

; Usage fetch size threshold property. Sets the expected maximum
; fetch size (in rows) for a single fetch to return. If a single
; fetch returns more than than this threshold, then the actual
; fetch size will be logged as part of usage tracking. -1
; indicates that any fetch size is valid.
;
; Valid values: -1 or greater

# usageFetchSizeThreshold=500

; Usage result set open threshold property. Sets the expected
; maximum time (in milliseconds) for a result set to remain
; open. If a result set is left open longer than this threshold,
; then the result set and time will be logged as part of usage
; tracking. This does not automatically close the result set. A
; usage result set open threshold value of -1 indicates that no
; such usage tracking will occur.
;
; Valid values: -1 or greater

# usageResultSetOpenThreshold=60000

; Usage tracking property. Enables or disables usage tracking.
; This provides additional tracking and logging to use during
; testing. Usage tracking does incur a performance penalty so it
; should be disabled for production code.
;
; Valid values: true, false

# usageTracking=false

; Usage tracking output property. Specifies the destination of
; usage tracking output.
;
; Valid values: log, exception

# usageTrackingOutput=log

; Usage transaction active threshold property. Sets the expected
; maximum time (in milliseconds) for a transaction to remain
; active. If a transaction is left active longer than this
; threshold, then the transaction and time will be logged as
; part of usage tracking. This does not automatically rollback
; the transaction. A usage transaction active threshold value of
; -1 indicates that no such usage tracking will occur.
;
; Valid values: -1 or greater

# usageTransactionActiveThreshold=120000

; Maximum number of parallel application generators.
; Controls how many serialized JAVA application
; objects can be generated at one time.
; For a low-power server, use a lower value.
; For a high-power server, use a higher value.
;
; valid values: 1 or greater

# ParallelAppGens=10

#=======================================================================
# END OF FILE
#=======================================================================

</pre><hr />

Please help me to adjust parameters in two files above.
 

wainwrr

Well Known Member
You need to define your terms more clearly here. What's slow? What does "slow" mean? Under what circumstances?

The reason that there are so many things you could change is that they all matter. And their relationships matter and are complex. You can change settings and something will happen but you might not be able to see it because some other setting masks it. Even if you see a change in performance after a change of setting you can't draw a direct causal, scalable relationship because of the inherent complexity of n-tier systems.

In short, my friend, you need help from someone with experience who can take the time to delve in depth; and that means in all probability a paid consultant who will hopefully explain and teach along the way.

You may get some suggestions and they may help but you still will be no closer to tuning anything; you'll just have made things better under one set of circumstances.

Understanding is the key.
 

sunmi

Member
Hello All,

I have problem with configuring the bweb client for my Standalone E9.00 Demo Does any one here know what am doing wrong I am using the Oracle DATABASE. I installed this perfectly on Windoiw 7

I will appreciate any help I can get thanks

Regardss
Sunmi
 
Top