When we install weblogic domain configuration wizard ask for username and password for administration purpose and mode of installation whether it "DEVELOPMENT MODE" OR "PRODUCTION MODE".
if we select "DEVELOPMENT MODE" in configuration wizard then it will create boot.properties file which contain username and password of weblogic user in encrypted format.
if we select "PRODUCTION MODE" in configuration wizard then it will not create boot.properties file and while starting weblogic server it will ask for username and password,once we supplied it the server gets started.
if you have installed weblogic domain in "PRODUCTION MODE",WE CANNOT START/RUN WEBLOGIC/ADMIN SERVER IN THE BACKGROUND,IF YOU TRY TO START
IT IN THE BACKGROUND IT WILL NOT ASK FOR "USERNAME" AND "PASSWORD" AND IT WILL GET FAIL.
++++++++++++++++++++++++++++++++++++++++
CREATING/ENABLING boot.properties file
++++++++++++++++++++++++++++++++++++++
boot.properties
++++++++++++++
$DOMAIN_HOME/server/AdminServer/security/boot.properties
[fusion@wlsadmin servers]$ pwd
/u02/Middleware_console/user_projects/domains/base_domain/servers
[fusion@wlsadmin servers]$ ls -ltrh
total 12K
drwxr----- 6 fusion dba 4.0K Feb 28 19:55 AdminServer
drwxr----- 3 fusion dba 4.0K Feb 28 21:06 domain_bak
drwxr----- 6 fusion dba 4.0K Feb 28 21:50 WLS_SOA1
[fusion@wlsadmin AdminServer]$ mkdir security
[fusion@wlsadmin servers]$cd /u02/Middleware_console/user_projects/domains/base_domain/servers/AdminServer/security
/u02/Middleware_console/user_projects/domains/base_domain/servers/AdminServer/security
[fusion@wlsadmin security]$ vi boot.properties
[fusion@wlsadmin security]$ head boot.properties
username=weblogic
password=weblogic123
[fusion@wlsadmin security]$
STOP SERVER AND START/RUN IN THE BACKGROUND.
++++++++++++
STOPPING THE SERVER
++++++++++++++++++++
[fusion@wlsadmin bin]$ ./stopWebLogic.sh
Stopping Weblogic Server...
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Connecting to t3://wlsadmin.user.com:9001 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'base_domain'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
Shutting down the server AdminServer with force=false while connected to AdminServer ...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:
Exiting WebLogic Scripting Tool.
Done
Stopping Derby Server...
[fusion@wlsadmin bin]$
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
STARTING IN THE BACKGROUND WITHOUT PROVIDING THE PASSWORD
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[fusion@wlsadmin bin]$ nohup ./startWebLogic.sh &
[1] 9391
[fusion@wlsadmin bin]$ nohup: appending output to `nohup.out'
[fusion@wlsadmin bin]$ jobs
[1]+ Running nohup ./startWebLogic.sh &
[fusion@wlsadmin bin]$ tail -f nohup.out
<Feb 28, 2014 11:33:29 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 28, 2014 11:33:29 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 28, 2014 11:33:29 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 28, 2014 11:33:29 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 28, 2014 11:33:29 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G2,OU=(c) 2007 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
<Feb 28, 2014 11:33:29 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 127.0.0.1:9001 for protocols iiop, t3, ldap, snmp, http.>
<Feb 28, 2014 11:33:29 PM IST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on 127.0.0.1:9002 for protocols iiops, t3s, ldaps, https.>
<Feb 28, 2014 11:33:29 PM IST> <Notice> <WebLogicServer> <BEA-000329> <Started WebLogic Admin Server "AdminServer" for domain "base_domain" running in Production Mode>
<Feb 28, 2014 11:33:29 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Feb 28, 2014 11:33:29 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
NOTE:
++++++++
AS I MENTIONED BEFORE boot.properties file contain "USERNAME" AND "PASSWORD" IN ENCRYPTED FORMAT.
[fusion@wlsadmin bin]$ head /u02/Middleware_console/user_projects/domains/base_domain/servers/AdminServer/security/boot.properties
#Fri Feb 28 23:33:23 IST 2014
password={AES}dKYRc73dRVs7wopkUtr4gXMiiZGtWUu7O+Y8tRq+wqc\=
username={AES}DwvTgtGEBc44tzo9wF5H++RTHiEn2QJ8O34IRlDOdbU\=
[fusion@wlsadmin bin]$
[fusion@wlsadmin bin]$ date
Fri Feb 28 23:36:00 IST 2014
[fusion@wlsadmin bin]$
if we select "DEVELOPMENT MODE" in configuration wizard then it will create boot.properties file which contain username and password of weblogic user in encrypted format.
if we select "PRODUCTION MODE" in configuration wizard then it will not create boot.properties file and while starting weblogic server it will ask for username and password,once we supplied it the server gets started.
if you have installed weblogic domain in "PRODUCTION MODE",WE CANNOT START/RUN WEBLOGIC/ADMIN SERVER IN THE BACKGROUND,IF YOU TRY TO START
IT IN THE BACKGROUND IT WILL NOT ASK FOR "USERNAME" AND "PASSWORD" AND IT WILL GET FAIL.
++++++++++++++++++++++++++++++++++++++++
CREATING/ENABLING boot.properties file
++++++++++++++++++++++++++++++++++++++
boot.properties
++++++++++++++
$DOMAIN_HOME/server/AdminServer/security/boot.properties
[fusion@wlsadmin servers]$ pwd
/u02/Middleware_console/user_projects/domains/base_domain/servers
[fusion@wlsadmin servers]$ ls -ltrh
total 12K
drwxr----- 6 fusion dba 4.0K Feb 28 19:55 AdminServer
drwxr----- 3 fusion dba 4.0K Feb 28 21:06 domain_bak
drwxr----- 6 fusion dba 4.0K Feb 28 21:50 WLS_SOA1
[fusion@wlsadmin AdminServer]$ mkdir security
[fusion@wlsadmin servers]$cd /u02/Middleware_console/user_projects/domains/base_domain/servers/AdminServer/security
/u02/Middleware_console/user_projects/domains/base_domain/servers/AdminServer/security
[fusion@wlsadmin security]$ vi boot.properties
[fusion@wlsadmin security]$ head boot.properties
username=weblogic
password=weblogic123
[fusion@wlsadmin security]$
STOP SERVER AND START/RUN IN THE BACKGROUND.
++++++++++++
STOPPING THE SERVER
++++++++++++++++++++
[fusion@wlsadmin bin]$ ./stopWebLogic.sh
Stopping Weblogic Server...
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Connecting to t3://wlsadmin.user.com:9001 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'base_domain'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
Shutting down the server AdminServer with force=false while connected to AdminServer ...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server:
Exiting WebLogic Scripting Tool.
Done
Stopping Derby Server...
[fusion@wlsadmin bin]$
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
STARTING IN THE BACKGROUND WITHOUT PROVIDING THE PASSWORD
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[fusion@wlsadmin bin]$ nohup ./startWebLogic.sh &
[1] 9391
[fusion@wlsadmin bin]$ nohup: appending output to `nohup.out'
[fusion@wlsadmin bin]$ jobs
[1]+ Running nohup ./startWebLogic.sh &
[fusion@wlsadmin bin]$ tail -f nohup.out
<Feb 28, 2014 11:33:29 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 28, 2014 11:33:29 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 28, 2014 11:33:29 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 28, 2014 11:33:29 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 28, 2014 11:33:29 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G2,OU=(c) 2007 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.10045.4.3.3.>
<Feb 28, 2014 11:33:29 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 127.0.0.1:9001 for protocols iiop, t3, ldap, snmp, http.>
<Feb 28, 2014 11:33:29 PM IST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on 127.0.0.1:9002 for protocols iiops, t3s, ldaps, https.>
<Feb 28, 2014 11:33:29 PM IST> <Notice> <WebLogicServer> <BEA-000329> <Started WebLogic Admin Server "AdminServer" for domain "base_domain" running in Production Mode>
<Feb 28, 2014 11:33:29 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Feb 28, 2014 11:33:29 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
NOTE:
++++++++
AS I MENTIONED BEFORE boot.properties file contain "USERNAME" AND "PASSWORD" IN ENCRYPTED FORMAT.
[fusion@wlsadmin bin]$ head /u02/Middleware_console/user_projects/domains/base_domain/servers/AdminServer/security/boot.properties
#Fri Feb 28 23:33:23 IST 2014
password={AES}dKYRc73dRVs7wopkUtr4gXMiiZGtWUu7O+Y8tRq+wqc\=
username={AES}DwvTgtGEBc44tzo9wF5H++RTHiEn2QJ8O34IRlDOdbU\=
[fusion@wlsadmin bin]$
[fusion@wlsadmin bin]$ date
Fri Feb 28 23:36:00 IST 2014
[fusion@wlsadmin bin]$
No comments:
Post a Comment