Starting WebLogic managed servers without providing username and password manually – SOA Suite 11g tip
After installing the Oracle SOA suite 11g, you will notice that you have to enter username and password for each managed server during startup and shutdown. This in contrary to the administration server where you don't need to enter username and password at startup. I was wondering if there was an easy way of skipping this manual step for the managed servers as well.
And yes, there is an easy and elegant way to prevent entering credentials every startup and shutdown. Just follow these steps:
1 Create a boot.properties file.
Create a plain text file called
boot.properties with the following content:
2 Place the boot.properties file in the security directory.
Save or copy this file in the
security directory under the managed server root directory. This directory was not created at installation time, so I had to create it myself. The server root directory is located at
3 Start the managed server.
The server will read the credentials from the
boot.properties file and in case of plain text username and password the server encrypt the username and password. Notice the following lines in the output:
<Sep 23, 2009 10:51:25 PM CEST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Sep 23, 2009 10:51:25 PM CEST> <Notice> <Security> <BEA-090083> <Storing boot identity in the file: D:\Middleware\user_projects\domains\base_domain\servers\bam_server1\security\boot.properties>
boot.properties file is still plain text with the username and password values encrypted. Do no copy the encrypted version between managed servers. Even when the credentials are the same, the resulting file is different.
For more information and alternatieve solutions see Creating Boot Identity Files for Managed Servers.
- OWB 10g R2 â€“ Changing the repositories password disables the Control Center
- Create a WebApplication secured with custom JAAS Database LoginModule & Deploy on JDeveloper 10.1.3 Embedded OC4J 10.1.3.1, Stand Alone OC4J and OPMN Managed OC4J (10g AS)
- Deploying and running ADF 11g applications on WebLogic 11g
- Logging in JDeveloper 11g / WebLogic Server
- Starting with EJB 3.0 Persistence in Eclipse 3.1 using the GlassFish Reference Implementation
- new Puppet 3 Weblogic provisioning module
- The AMIS Summary of Oracle OpenWorld 2013 is available for download – 60-page white paper
- WebLogic & FMW Provisioning update
- The road ahead for WebLogic 12c
- OOW13: summarizing one week and 2000 sessions in 3 hours and a bit – the yearly AMIS OOW Review session – 10th October
- OOW13 and JavaOne 13: Notes from a Conference – Part Two
- OOW13: Cloud roadmap & announcements – from zero to H/A WebLogic Cluster plus Database RAC in 30 minutes
- Het Oracle OpenWorld Preview Evenement (5 september 2013) – 15 sprekers & sessies
- ADF 12c: Using WebSockets to implement client to client push (in a scalable manner)
- JDeveloper 12c & ADF 12c: Launch of the next generation