Child pages
  • Application Server
Skip to end of metadata
Go to start of metadata


  • Ensure that the app server and version being used complies with Oracle's supported environments matrix. Only use the versions explicitly called out in the support matrix. Do not deviate at all from the point versions specified. ATG is very sensitive to app server version
  • Verify that session replication (clustering) is enabled. All session-scoped components in ATG should be serializable per product documentation
  • Ensure that the session timeout has been set and is appropriate
  • Find out where logs are being written to (ATG and the app server each write out their own logs). Make sure there is a good log rotation strategy in place and that very old logs are automatically purged
  • Verify that whitespace is being stripped from JSP pages
  • Consider pre-compiling JSPs for better performance
  • Be sure to enable log file compression
  • Be sure to enable log file rotation/purging

WebLogic App Server

  • Ensure that the number of connections to the database will not exceed the database's capacity and that there are enough connections
  • Put all of your managed servers in two or three clusters (for code deployment purposes)
  • Make sure you use multicast
  • If there are fewer than four managed servers per cluster, use unicast
  • Be sure to enable whitespace stripping. Instructions may be found here, specifically "compress-html-template" attribute
  • Increase the JTA Timeout value to 21600 sec (6 hours, due to BCC deployments) or higher
  • Check the Set XA Transaction Timeout for each of created DataSources for all but the ATGPUB DataSource
  • Set the XA Transaction Timeout value for each of created DataSources to 600 sec for all but the ATGPUB DataSource
  • Increase the Accept Backlog setting by 25% in the Configuration > Tuning tab until the CONNECTION_REFUSED errors disappear or are significantly reduced in the WebLogic plug-in logging on the Apache servers.
  • Increase the Login Timeout on Configuration > Tuning tab for each of created Servers from 5000 to 10000
  • Increase the Complete Message Timeout on Protocols > General tab for each of created Servers to 300
  • Increase the Duration on Protocols > HTTP tab for each of created Servers to 200
  • Uncheck the Enable Keepalives option on Protocols > HTTP tab for each of created Servers
  • Reduce the session timeout from the default of 30 minutes to a lower value of 15 - 20 minutes in the web application's web.xml (unless a higher timeout is a client requirement)
  • If using the WebLogic HTTP Plug-in, make sure that the "WebLogic Plug-In Enabled" setting is checked in the advanced section of the Configuration > General section of the WebLogic cluster or in each singleton WebLogic server
  • Consider using GridLink data sources. Note: this feature may have licensing implications. Please contact your local Oracle sales rep to confirm your are entitled to use it
  • Never have underscores (_) in the host name of the machine running WebLogic. It will throw an odd LDAP-related error
  • Make sure that only one JDBC driver appears in the CLASSPATH listing. Failure to do so may result in sealing violations or intermittent issues with columns in Commerce databases. This includes the default ojdbc6.jar files (11.2.0.x drivers) in the WebLogic modules directory.
  • Have the "Test Connections on Reserve" checked for each datasource. (Datasource > Connection Pool tab > Advanced section at the bottom)
  • All but the Publishing datasource should have the Set XA Transaction Timeout checked (Datasource > Transaction tab) and set the XA Transaction Timeout to 600 seconds.
  • No labels