官术网_书友最值得收藏!

首頁 >

Oracle WebLogic Server 12c Advanced Administration Cookbook

Starting the Administration Server

Administration Server is a WebLogic Server instance specific to administering a WebLogic domain through the Administration Console application at the /console URI.

It's a common task to deploy runtime applications to the Administration Server in development environments, but you should avoid doing it in production. Leave the Administration Server only to the administrative tasks of the console.

Getting ready

Since there is only one Administration Server per WebLogic domain, you have to start the Administration Server only in prod01.

How to do it...

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 <password> value you previously specified during domain creation.
  5. WebLogic Administration Server will start.

How it works...

The Administration Server is now running and waiting for connections in the host and port that are specified during domain creation at http://prod01.domain.local:7001/console.

<Started the WebLogic Server Administration Server "PROD_AdminServer" for domain "PROD_DOMAIN" running in production mode.>

There's more...

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 <password> value you specified: 
    [wls@prod01]$ echo -ne "username=wlsadmin\npassword=<password>" > boot.properties

[wls@prod01]$ cat boot.properties
username=wlsadmin
password=<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 <PID> 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.

Accessing the Administration Console

The Administration Console application is running in the Administration Server. To access it, follow the ensuing steps:

  1. Open your web browser and navigate to http://prod01.domain.local:7001/console:
  2. Type the wlsadmin username and the password that was specified earlier.

See also

  • Starting the Node Manager
  • Starting/Stopping the WebLogic Managed Server
主站蜘蛛池模板： 正定县| 徐汇区| 武汉市| 云和县| 磐石市| 手机| 陆良县| 义马市| 股票| 沅陵县| 万荣县| 元阳县| 宁陵县| 文安县| 上思县| 玉山县| 育儿| 武城县| 穆棱市| 沾益县| 海原县| 辛集市| 钟祥市| 秦皇岛市| 方山县| 临邑县| 博白县| 行唐县| 新昌县| 雅安市| 广汉市| 隆回县| 修水县| 上林县| 泽普县| 四子王旗| 阿巴嘎旗| 沾化县| 沂南县| 奉贤区| 广灵县|