Creating a Boot Identity File for an Administration Server
If a boot identity file for an Administration Server does not already exist, and if you want to bypass the prompt for username and password, create one as follows:
Start the Administration Server at least once and provide the user credentials on the command line.
During the Administration Server’s initial startup process, it generates security files that must be in place before a server can use a boot identity file.
Place the following two lines in a text file:
The username and password values must match an existing user account in the Authentication provider for the default security realm and must belong to a role that has permission to start and stop a server.
Save the file.
If you save the file as boot.properties and locate it in the server’s root directory, the server automatically uses this file during its subsequent startup cycles.
boot.properties file creation steps using weblogic.Server class :
you can create a boot identity file by including the following options in the Java command:
-Dweblogic.management.username=username -Dweblogic.management.password=password -Dweblogic.system.StoreBootIdentity=true
These options cause the server instance to boot with the supplied user credentials and then store them in a file named boot.properties.
For example, the following command starts an Administration Server named myAdminServer and creates a boot identity file:
java -Dweblogic.management.username=username -Dweblogic.management.password=password -Dweblogic.system.StoreBootIdentity=true -Dweblogic.Name=myAdminServer weblogic.Server
note: Do remember to set domain environment variables(setDomainEnv.sh/bat) before executing above else it will give an error.
Creating a Boot.properties Identity File for a Managed Server:
To create a boot identity file for a Managed Server:
-Start the domain’s Administration Server to make sure that the required security files are in the root directory of the Administration Server. If the files are not present, the Administration Server generates them.
-Copy the SerializedSystemIni.dat file from the Administration Server’s root directory to the Managed Server’s root directory.
-Place the following two lines in a text file:
The username and password values must match an existing user account in the Authentication provider for the default security realm and must belong to a role that has permission to start a server.
– Save the file