Boot Identity Files

   A boot identity file is a text file that contains user credentials for starting and stopping an instance of WebLogic Server. An Administration Server can refer to this file for user credentials instead of prompting you to provide them. Because the credentials are encrypted, using a boot identity file is much more secure than storing unencrypted credentials in a startup or shutdown script. If there is no boot identity file when starting a server, the server instance prompts you to enter a username and password.

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.

Step1:   

       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.

Step2: 

       Place the following two lines in a text file: 

              username=Admin username

              password= Admin password

Step3:   

         Save the file as boot.properties and locate it in the security directory of the server’s root directory, the server automatically uses this file during its subsequent startup cycles.

              If there is no security directory then you create one and place this file in the

security directory.

BEA_HOME\user_projects\domains\SampleDomain\servers\ AdminServer\security 

Creating a boot Identity file for managed server:

               If a Managed Server uses the same root directory as the Administration Server, it can use the same boot properties file as the Administration Server. If you use a Node Manager to start a Managed Server, you do not need to create a boot identity file.

Step1:   

       Start the domain’s Administration Server to make sure that the required security files are in the security directory of the Administration Server’s domain and root directories. If the files are not present, the Administration Server generates them.   

Step2:   

        Place the following two lines in a text file: 

              username=Admin_username

              password= Admin_password

Step3:   

        Save the file as boot.properties and locate it in the security directory of the server’s root directory, the server automatically uses this file during its subsequent startup cycles.

              If there is no security directory then you create one and place this file in the

security directory.

BEA_HOME\user_projects\domains\SampleDomain\servers\ Managed1\security