As you probably know, Weblogic has the main parameter file (setDomainEnv.sh), which takes into consideration the various vendors and bit sizes to then make judgement on which memory parameters to use.

Because the 'total memory' used includes not only the Xmx but also the takes into consideration the thread stacks, permGen size and all the library memory allocations. Perm sizes is configured by using the MaxPermSize though I also wanted to apply maximum memory available for each thread.

I also noticed that the managed domain servers are separated within other scripts. For OIM and SOA there's setOIMDomainEnv.sh and within the setSOADomainEnv.sh respectively) though in my opinion, there were too many MEM_ARGS variables passed between all 3 domain environment files (any more than 1 is too much) The parameters used to fine-tune was also distributed from within the file.

I decided to 'clean up' this particular file by removing all the unwanted data and loop conditions. Obviously this does not improve performance to any significant level though it provides a quick and simple alteration if I wish to alter the memory.

I decided to place 3 conditional statements within the setDomainEnv.sh file to centralize the memory allocation and make the conditional memory allocations within the setOIMDomainEnv and the setSOADomainEnv file. Within the main environment script, I included the $SERVER_NAME parameter to allow the environments to be set independently.

After fine-tuning (after attempting to startup the managed servers with the minimal requirements), both OIM and SOA servers needed the exact same parameters as part of the minimal requirements for both servers to start up.

The OIM and SOA servers would initiate the startup with lower heap sizes though the allocated amount was insufficient for the simplistic use of OIM functionalities.

The maximum stack allocation (-Xss) is set to 256k. I did initially set this to 64k though the WLS managed servers wouldn't even begin to startup. PermSizes for both OIM and SOA are set particularly low (32m) though the MaxPermSize is the bigger consideration when allocating memory. This could be lower however using simple functionality within OIM threw a perm Size error.

Below is the code used. You can download the Weblogic Scripts I used to startup of the managed servers of OIM and SOA. Alternatively, You can simply use the snippet of information below along with the server name parameter.

Script below

. ${WL_HOME}/common/bin/commEnv.sh
. ${DOMAIN_HOME}/bin/setSOADomainEnv.sh
. ${DOMAIN_HOME}/bin/setOIMDomainEnv.sh

if [ "${SERVER_NAME}" == "AdminServer" ] ; then
MEM_ARGS="-Xms256m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=256m -Xss256k"
fi
if [ "${SERVER_NAME}" == "oim_server1" ] ; then
echo "This is the OIM Server"
MEM_ARGS="-Xms64m -Xmx1024m -XX:PermSize=32m -XX:MaxPermSize=512m -Xss256k"
fi
if [ "${SERVER_NAME}" == "soa_server1" ] ; then
echo "This is the SOA Server"
MEM_ARGS="-Xms64m -Xmx1024m -XX:PermSize=32m -XX:MaxPermSize=512m -Xss256k"
fi
export MEM_ARGS

About the author