Objective: In this article we are going to learn how to start and stop Admin server and overview of Boot identity file in Weblogic Server Administration and  Monitoring.

Core Weblogic Server Administration and Monitoring:

• Starting servers with start script.

• Boot Identity File (boot.properties)

• WLS Administration console overview

• Enterprise Manager Fusion Middleware console

• Comparison of Fusion Middleware console and the Weblogic server Admin control.

• Weblogic Scripting tool.

Starting and stopping Admin servers:

1. Start/Stop Admin Server:

• Admin server can be started by running a default script or custom script created by us.

• To start a Admin server with a weblogic server-included startup script:

1. Open a command prompt on the machine on which you created the domain.

2. Change the directory to DOMAIN_HOME

3. Run below command:

bin\startweblogic.sh (on windows supported only if cygwin or MKS are installed)

bin/startweblogic.cmd (only on windows)

The startweblogic script sets the environment variable by invoking:

DOMAIN_HOME\bin\setDomainEnv.cmd  (setDomainEnv.sh on UNIX)

Also, Invokes java weblogic.server command, which starts the JVM that starts the weblogic server instance.

When the server successfully completes startup process, it shows following command:

<Notice><WeblogicServer><BEA-000360><Server started in RUNNING mode>

This script does not use Node manager to start or manage the server, instead it invokes the Java command to invoke the weblogic.server class which is the main class for weblogic server instance.

• To use a weblogic script to start a weblogic managed server:

1. Start the Domain’s Admin server

2. In a command prompt on the computer that hosts the Managed Server, change to the directory that contains the startManagedWebLogic script:

i. DOMAIN_NAME\bin\startManagedWebLogic.cmd (Windows)

 ii. DOMAIN_NAME/bin/startManagedWeblogic.sh(LINUX)

3.  Run below command:

i. startManagedWebLogic.cmd managed_server_name admin_url (Windows)

ii. startManagedWebLogic.sh managed_server_name admin_url (UNIX).

4.  For each Managed Server that you want to start, open a separate command shell and follow steps 4 and 5. If you are starting Managed Servers on another machine, log in to that machine (remotely or locally) and then follow steps 2 and 3.

Overview of Boot Identity File:

• A boot identity file – boot.properties, contains the user credentials for starting and stopping an instance of WebLogic Server

• An administration server or managed server can refer to this file for user credentials instead of prompting at the command line to provide them.

• Because the credentials are encrypted, using a boot identity file is more secure than storing plain text credentials in a startup or shutdown script.

• There can be a different boot identity file for each server in a domain.

• If you choose Development Mode when creating a domain by using the Configuration Wizard, a boot identity file is automatically created for the administration server.

• If you use Node Manager to start managed servers rather than running start scripts manually, you do not need to create boot identity files for them. Node Manager creates its own boot identity files and stores them under each server's directory in the data / nodemanager subdirectory.

Creating Boot Identity file

Steps to create a boot file.

1. Stop the Admin Server if it is already running with stopWeblogic.sh script.

2. ./stopWeblogic.sh script will prompt for credentials. Enter the Domain administrator credentials.

3. Here, before adding boot.properties file, the scripts are prompting for Credentials.

4. Once we create boot.properties file, start and stop scripts will automatically take credentials and don’t prompt for those. This meets security requirements.

5. In a terminal window, navigate to DOMAIN_HOME.

6. cd to /servers/Adminserver subdirectory.

7. If security folder is not present create one: mkdir security

8. cd security/

9. Create boot.properties file

10. vi boot.properties

username=weblogic

password=Welcome1

:wq

11. Now start the Weblogic Server by running ./startWeblogic.sh script.

12. This time credentials will be automatically taken by the script.

13. Check if those credentials are safe?

14. open boot.properties once the Admin server is up and running.

15. cat boot.properties

password={AES}TV0p745h78YHN89g35HYT567vLbNHY\=

username={AES} HN89g350p745h35HYT567vLbNTV0p7\=

Varun Kapila

Add comment