OHS
|
OTD
|
OHS is
primarily an Apache based web server and can do forward and reverse
proxy functionality
|
OTD is
primarily a high performant HTTP and TCP software load balancer, designed for
scalability and high throughput
|
a Web Server is
required to serve static content and also to do proxy capability, then OHS is
a better choice.
|
If full
fledged software load balancer with request throttling, draining, Quality of
Service, is required then OTD is probably a better choice
|
OHS can be used to deploy some static content.
|
OTD does not
expose the ability to serve static contents.
|
OHS is used when high throughputs are not required.
|
Used when looking
for better monitoring / troubleshooting / tuning for high throughput
deployment requirements
|
Used when it is fine to restart the web servers occasionally for
configuration changes.
|
No Downtime required for applications as backend servers can be
added/removed dynamically.
|
|
HTTP responses from the backend servers can be cached. OTD provides a
built-in mechanism for caching .
|
Application Module tuning is a critical setting which will affect the UI performance. Following are the recommended application module settings for OIM and these are already set out-of-box (OOB) in later releases of OIM 11g R2. Ensure that these settings are implemented as recommended in your environment. -Djbo.ampool.doampooling=true -Djbo.ampool.minavailablesize=1 -Djbo.ampool.maxavailablesize=120 -Djbo.recyclethreshold=60 - Djbo.ampool.timetolive=-1 -Djbo.load.components.lazily=true - Djbo.doconnectionpooling=true -Djbo.txn.disconnect_level=1 - Djbo.connectfailover=false -Djbo.max.cursors=5 - Doracle.jdbc.implicitStatementCacheSize=5 - Doracle.jdbc.maxCachedBufferSize=19 open DOMAIN_HOME/bin/setDomainEnv.sh file for the WebLogic Server instance.find these lines: JAVA_OPTIONS="${JAVA_OPTIONS}" export JAVA_OPTIONS and change it to: JAVA_OPTIONS="-Djbo.ampool.doampooling=true -Djbo.ampool.minavailablesize=1 -Djbo.ampool.maxavailablesize=120 -D...
Comments
Post a Comment