This OBE tutorial describes and shows you how to enable auto login using the boot identity file.
Approximately 1/2 hour
This OBE tutorial covers the following topics:
|
Overview | |
|
Scenario | |
|
Verifying the Prerequisites | |
|
Stopping and Starting a Managed Server | |
|
Configuring the boot.properties File | |
|
Summary | |
|
Related Information | |
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.
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.
Before you start the tasks, make sure that your system environment meets the following requirements:
Software Requirements
The system should have Oracle WebLogic Server 10.3 installed.
Setup Requirements
You should have completed the following OBEs:
To start and stop a Managed Server, perform the following steps:
|
1. |
In the Oracle WebLogic Server Console, under the Domain Structure section, click Server. Then click dizzy1.
|
|
2. |
Notice that the "Settings for dizzy1" section appears. Click the Control tab and click the Start/Stop tab.
|
| 3. |
Select the dizzy1 check box and select Shutdown > Force Shutdown Now.
|
| 4. |
In the Server Life Cycle Assistant section, click Yes.
|
| 5. |
Notice the message A request has been sent to immediately shut down the selected servers. Click the Refresh icon to view the updated status.
|
| 6. |
Browse to /u01/app/oracle/product/Middleware/user_projects/domains/dizzyworld/bin and enter the following command to start dizzy1:
|
| 7. |
Notice that you are prompted here for the username and password. Enter admin and welcome1, respectively. dizzy1 is started.
|
| 8. |
You've now seen the normal start for a managed server. Press and hold Ctrl + C to stop the running server.
|
To configure the boot.properties file, perform the following steps:
|
1. |
Browse to /u01/app/oracle/product/Middleware/user_projects/domains/dizzyworld/servers/dizzy1/security
and edit the boot.properties
file.
Note: You need to create the security folder and the boot.properties file incase the parent folder is empty.
|
|
2. |
Modify the file with the following values and save it.
|
| 3. |
Browse to /u01/app/oracle/product/Middleware/user_projects/domains/dizzyworld/bin and enter the following command to start dizzy1:
|
| 4. |
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.
|
In this lesson, you learned how to:
|
Verify the prerequisites | |
|
Start and stop a Managed Server | |
|
Configure the boot.properties file | |
Place the cursor over this icon
to hide all screenshots.