Method 1: boot.properties
(Recommended)
Edit a
boot.properties file in the domains directory. Format is:
username=weblogic
password=mybasicknowledge
boot.properties
file can be placed following directory depend on which managed server you are
using
./servers/bam_server1/security/boot.properties
./servers/soa_server1/security/boot.properties
./servers/AdminServer/security/boot.properties
If the
directories or files don’t exist you can create them.
After the
first bootup the password will become encrypted.
Note:
If you want
to keep boot.properties in separate location then edit setDomainEnv.sh, which
is located in /bin and add following parameter to JAVA_PROPERTIES
-Dweblogic.system.BootIdentityFile=${DOMAIN_HOME}/security/boot.properties
Line looks
like
JAVA_PROPERTIES="-Dplatform.home=${WL_HOME}
-Dwls.home=${WLS_HOME} -Dweblogic.home=${WLS_HOME}
-Dweblogic.system.BootIdentityFile=${DOMAIN_HOME}/security/boot.properties
Method 2:
In the
startManagedWeblogic.sh you will see the following lines:
# Set WLS_USER equal to your system username
and WLS_PW equal
# to your system password for no username and
password prompt
# during server startup. Both are required to bypass the startup
# prompt.
WLS_USER=""
export WLS_USER
WLS_PW=""
export WLS_PW
