Place
the cursor over this icon to load and view all the screenshots for this tutorial.
(Caution: Because this action loads all screenshots simultaneously, response
time may be slow depending on your Internet connection.)
Note: Alternatively, you can place the cursor
over each individual icon in the following steps to load and view only the screenshot
associated with that step.
The screenshots will not reflect the specific environment
you use. They are provided to give you an idea of where to locate specific
functionality in Oracle WebLogic Server.
Overview
A boot identity file 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 more secure
than storing unencrypted credentials in a startup or shutdown script. If there
is no boot identity file when you start a server, the server instance prompts
you to enter a username and password. The boot identity file can be different
for each server instance in the domain.
The Dizzyworld system architects want to make the environment
more secure by using auto login to the WebLogic server instance. To implement
this, the boot identity file is used.
Note that the boot.properties file is identified and you are not prompted
for a username and password. The server is in the running mode.
Navigate back to the /u01/app/oracle/product/Middleware/user_projects/domains/dizzyworld/servers/dizzy1/security
location and view the boot.properties
file. You notice that the content of this file is now encrypted.
Bookmark
Place
the cursor over this icon to load and view all the screenshots for this tutorial.
(Caution: Because this action loads all screenshots simultaneously, response
time may be slow depending on your Internet connection.)
