Minimal Weblogic memory allocation for OIM 11gR2PS2

I could not locate the absolute memory allocation for the Weblogic managed servers for OIM and SOA. Allocating the maximum allocation pool (-Xmx), heap size, does not allocate the total RAM memory to the Weblogic managed servers. Items outside the realms of the maximum allocations poll, such as thread stacks, perm sizes, and library memory allocations also need to be considered.
August 10, 2014
OIMOIM11gR2PS2SOAWeblogicJAVA

Too many Domain Environment files!

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.

https://technicalconfessions.com/images/postimages/postimages/_306_3_memory arguments in WLS for OIM SOA.png

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

Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.
Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles

Comments

Other Posts

HOW TO provision AD group membership from OpenIDM

OpenIDMICFAD-connector

June 15, 2018
Created by: Daniel Redfern
For what I see, there's not too many supportive documentations out there that will demonstrate how provision AD group membership with the ICF connector using OpenIDM. The use of the special ldapGroups attribute is not explained anywhere in the Integrators guides to to the date of this blog. This quick blog identifies the tasks required to provision AD group membership from OpenIDM to AD using the LDAP ICF connector. However this doesn't really explain what ldapGroups actually does and there's no real worked example of how to go from an Assignment to ldapGroups to an assigned group in AD. I wrote up a wiki article for my own reference: AD group memberships automatically to users This is just my view, others may disagree, but I think the implementation experience could be improved with some more documentation and a more detailed example here.
Read More...

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid

ICFIDMOpenIDMOpenICF

November 8, 2017
Created by: Daniel Redfern
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...

org.forgerock.script.exception.ScriptCompilationException: missing ; before statement

IDMsync.confforgerockopenidm

November 8, 2017
Created by: Daniel Redfern
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statemen

OpenIDMsync.confForgeRock

September 17, 2017
Created by: Daniel Redfern
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

Caused by: org.forgerock.json.resource.BadRequestException: Target does not support attribute groups

OpenIDMForgeRockICFConnector

September 17, 2017
Created by: Daniel Redfern
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid

OpenIDMForgeRockICFConnectorAD

September 17, 2017
Created by: Daniel Redfern
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...

ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_g

OpenIDMIDMGoogleGoogle-AppsICFreconciliation

September 12, 2017
Created by: Daniel Redfern
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...

forgerock-openidm-encryptedjwt-error

OpenIDMIDMForgeRockJWTIAM

August 29, 2017
Created by: Daniel Redfern
Received the JWT error
Read More...

Unexpected character ('¾' (code 190)): expected a valid value

ForgeRock-OpenIDMOpenIDMIDMKeystore

June 25, 2017
Created by: Daniel Redfern
Unexpected character occurred when the IP addresses changes and the virtual instance was migrated into a separate network subnet.
Read More...

OpenDJ Error - Connect Error Result Code: 91 (Connect Error)

OpenDJLDAPldapsearchForgeRock

June 5, 2017
Created by: Daniel Redfern
When trying to connect, I would then receive the following error "Connect Error Result Code: 91 (Connect Error)"
Read More...