We now of OCCAS up and running. Hooray!
Unfortunately, it is not going to run well. We need to do a lot of performance tuning to make it really hum.
Maximum Message Size
Upgrade the maximum number of bytes allowed in messages that are received over all supported protocols...
For each server, navigate to "Protocols" >> "General" and double the "Maximum Message Size".
Java Arguments
When using Node Manager (which everyone should), you can alter the Java Arguments by navigating to...
Server >> Server Start
Here are some recommendations:
| Topic | Example Settings | Description |
|---|---|---|
| Memory | -Xms4g -Xmx4g | Always set the minimum (Xms) and maximum (Xmx) to the same value. Use as much memory as you can! |
Disable Start Script
In WebLogic 12.1.1 (and higher), the nodemanager has been modified to use the "startWebLogic.sh" script to launch WebLogic. I prefer the old technique because it allows creating custom startup parameters for each server. Let's disable the "start script". (In the nodemanager.properties file)
weblogic.StartScriptEnabled=false
Nice! But, with great power comes great responsibility!
Without the "start script", we're going to have to provide all the necessary info.