Preparing WebLogic for AquaLogic Interaction
This topic describes how to configure WebLogic Server for
use with the ALI portal application.
WebLogic Basic Authentication must be disabled for the ALI
portal application on WebLogic Server. To do this, in the WebLogic config.xml for the ALI portal, set <enforce-valid-basic-auth-credentials> to false.
- Disable WebLogic Basic Authentication for the ALI portal
application.
To do this, in the WebLogic config.xml for
the ALI portal, set <enforce-valid-basic-auth-credentials> to false.
<security-configuration>
...
<enforce-valid-basic-auth-credentials>
false
</enforce-valid-basic-auth-credentials>
</security-configuration>
- On AIX, HP-UX, and Solaris, verify that your WebLogic domain
is configured to use a valid 64–bit Java SDK.
- On AIX, HP-UX, and Solaris, add -d64 to
your domain's JAVA_OPTIONS.
To do this, edit the setDomainEnv.sh script
for your domain. Find where JAVA_OPTIONS is set,
near the end of the file, and add the -d64 flag.
For example:
#JAVA_OPTIONS="${JAVA_OPTIONS}"
JAVA_OPTIONS="-d64 ${JAVA_OPTIONS}"
export JAVA_OPTIONS
- Increase the JVM's MaxPermSize.
A MaxPermSize of 256m is recommended.
If MaxPermSize is set too low, you will see java.lang.OutOfMemoryError: PermGen space when attempting
to start the portal.
To increase MaxPermSize, edit
the setDomainEnv.sh script for your domain. Find
where MaxPermSize is being set for your JAVA_VENDOR, and set it to 256m.
For example: if [ "${JAVA_VENDOR}" = "HP" ] ; then
#MEM_ARGS="${MEM_ARGS} -XX:MaxPermSize=128m"
MEM_ARGS="${MEM_ARGS} -XX:MaxPermSize=256m"
export MEM_ARGS
fi
