Starting the Administration Server

To start the Administration Server, follow the ensuing steps:

1. Log in as the wls user on the first machine prod01 and navigate to the folder:
[wls@prod01]$ cd $DOMAIN_HOME/bin

2. Start the Administration Server:

[wls@prod01]$ ./startWebLogic.sh

3. The server will initiate the startup process and ask for the WebLogic Administrator
username and password:
Enter username to boot WebLogic server: wlsadmin
Enter password to boot WebLogic server:

4. Type wlsadmin as the username and the value you previously specified during domain
creation.
5. WebLogic Administration Server will start.
The Administration Server is now running and waiting for connections in the host and
port that are specified during domain creation at
URL: http://prod01.domain.local:7001/console.
Log output:
<Started the WebLogic Server Administration Server "PROD_AdminServer" for
domain "PROD_DOMAIN" running in production mode.>
Note:
The system administrator should also create a boot.properties file to avoid entering the
boot username and password in every WebLogic Server startup.

Creating the boot.properties file

Specify a boot.properties file so the Administration Server doesn't ask for the username
and password at startup.
1. Go to the Administration Server root folder:
[wls@prod01]$ cd $DOMAIN_HOME/servers/PROD_AdminServer

2. Create and enter a new directory:

[wls@prod01]$ mkdir security
[wls@prod01]$ cd security

3. Create a new file called boot.properties with wlsadmin as the username and the value
you specified:
[wls@prod01]$ echo -ne "username=wlsadmin\npassword=" > boot.properties
[wls@prod01]$ cat boot.properties
username=wlsadmin
password=********

4. The next time you start WebLogic Administration Server, it will use the credentials
from the boot.properties file. The file will also be encrypted:
[wls@prod01]$ cat boot.properties
password={AES}If68A2GSiO6Fa8w4j0giDJGR0FATHnfPsoZvpmF/Ipc\=
username={AES}UYyIQYkN6z5o8PsS/IccG3VgZv6LP1zj+Ro1JBDb2ZE\=

Starting the Administration Server in the background

You usually start the Administration Server as a background process in Linux.
1. Go to the WebLogic domain's bin directory:
[wls@prod01]$ cd $DOMAIN_HOME/bin

2. Start the Administration Server in the background:

[wls@prod01]$ nohup ./startWebLogic.sh &
[1] <PID>

The value is the process ID of the Administration Server.

The standard output (stdout) and standard error (stderr) of the process will be appended to
a file called $DOMAIN_HOME/bin/nohup.out.