WebLogic server domains are controlled by administrative users. The username and password of such user is given at the time of domain creation. In order to start WebLogic server, we must provide correct administrative username and password.
In this post, I will walk you through the different ways in which you can provide administrative user credentials to start the server. Depending on the mode of the server (Development/Production) and environment security, we can provide the credentials using three distinct ways. They are as follows:
When you start the WebLogic server for the first time after its creation, you are asked to enter the username and password to boot the WebLogic server. The username you enter is displayed on the command line but not the password.
In case of Admin servers, once you provide the username and password and the server is started, the credentials are stored in a file named boot.properties in encrypted format. The location of the file is <DOMAIN_HOME>/servers/AdminServer/security/boot.properties. Following is an example of the contents of boot.properties.
This file is generally not created by default for managed servers. In order to specify the credentials for the managed servers, you are required to create this file manually and specify the credentials in plain text. Once the managed server is started, WebLogic encrypts the contents of this file.
Once this file is created, you are no longer prompted to enter the credentials.
We can also specify the administrative username and password using Java Options. WebLogic server is basically a java process and like all java processes WebLogic makes use of various java options for configurations. WebLogic supports use of following java options to specify the credentials:
Note that these parameters are to be provided in plain text. This option is particularly useful when you are going to create custom scripts for starting and stopping the servers. Also you can use it in startWebLogic.sh/startWebLogic.bat or setDomainEnv.sh/setDomainEnv.bat files.
This post is just to give you an idea about various ways of providing administrative user credentials to start WebLogic server. Make sure you protect the files which store the credentials in plain text from unauthorized access.
Ganesh Kamble works as Oracle Fusion Middleware Consultant and is an Oracle Certified Specialist in Access Management. Having started his career in product development at Oracle, Ganesh got excellent exposure to the middleware technologies during his work in integration of Tier-1 banking product Oracle Banking Platform with Oracle Fusion Middleware products. He was honored with Outstanding Contribution award by Oracle.
His key areas of interest are Oracle Identity and Access Management, Oracle Service Oriented Architecture and Java with passion for blogging on various encounters with Oracle products. He publishes blogs regularly on http://k21technologies.com/blog/. He can be reached at firstname.lastname@example.org and http://twitter.com/ganeshk_8