Create a boot identity file

A boot identity file contains the user credentials for starting and stopping an instance of WebLogic Server. An administration server or managed server can refer to this file for user credentials instead of prompting at the command line to provide them. Because the credentials are encrypted, using a boot identity file is more secure than storing plain text credentials in a startup or shutdown script. There can be a different boot identity file for each server in a domain.

For the Production Mode domain, you can create the boot identity file manually, as explained below.

Check that the following directory is present in the domain directory:
$WL_HOME/user_projects/domains/<domain_name>/servers/AdminServer

Note: If the directory is not present, the server has not yet been started after WebLogic 12c server installation. Start the AdminServer using the ./startWebLogic.sh command from the $WL_HOME/user_projects/domains/<domain_name>/bin directory.
If the AdminServer was started with the start script in a Terminal window, click Ctrl + C in that window to stop the server.
Navigate to the domain directory $WL_HOME/user_projects/domains/<domain_name>/servers/AdminServer directory, for example:
/u01/app/oracle/product/weblogic12c/Middleware/user_projects/domains/empirica/servers/AdminServer
Create a subdirectory called security.
Navigate to the security directory and execute the following command:
$ cat - > boot.properties

username=weblogic

password=<domain_password>
To save the file and exit the editor, press Ctrl+D.
From the $WL_HOME/user_projects/domains/<domain_name>/bin directory, restart the server using the ./startWebLogic.sh command.
When messages that say RUNNING appear, press Ctrl+C.
From the $WL_HOME/user_projects/domains/<domain_name>/servers/AdminServer/security directory, execute cat boot.properties to verify that:
- The user name and password have been encrypted by the server.
- A comment has been added with the timestamp when encryption occurred.