Boot.properties not working in SOA 11g environment (Enterprise Linux)

Question

I need to get this working because I want an unattended start-up of the Managed (SOA) server.
Here's the problem...
The Administration server script ($MW_HOME/user_projects/domains/base_domain/startWebLogic.sh) runs perfectly. I am not prompted for a username or password.
The installation gives me two (different) scripts of the same name - startManagedWebLogic.sh
One of these scripts is in $MW_HOME/wlserver_10.2/common/bin. I've ignored this one. The 2nd one (the one I'm using) is in $MW_HOME/user_projects/domains/base_domain/bin
The proper (single) location of the boot.properties file is unclear to me. I have placed two copies of the identical file (two files - not a link) in $MW_HOME/user_projects/domains and $MW_HOME/user_projects/domains/base_domain
Each file looks like this:-
# Generated by Configuration Wizard....
username=weblogic
password=welcome1
If I run startManagedWebLogic.sh from a terminal, I am prompted for username and password.
I enter the username (weblogic) and password (welcome1) and the SOA server starts.
In the unattended mode, the invocation is (effectively) this:-
nohup startManagedWebLogic.sh soa_server1 >mwl.log 2>&1 &
In this case an exception is thrown (weblogic.security.SecurityInitializationException)
It seems quite clear to me that the boot.properties file is being ignored either because there is some configuration value that indicates that it should not be used or, more likely, it's in the wrong place!

Answer 1

During start up of the managed server, it looks out for the boot.properties within the server root directory by default. Hence you should put your boot.properties file in the Managed Server root directory.
That may be in your case : $MW_HOME/user_projects/domains/base_domain/servers/ManagedServerName/ Directory.
Or else you can specify the location of the boot.properties files using the following parameter:
-Dweblogic.system.BootIdentityFile=filename
where filename is the fully qualified pathname of a valid boot identity file.
To specify this argument in the startManagedWebLogic.sh script, add -Dweblogic.system.BootIdentityFile as a value of the JAVA_OPTIONS variable. For example:
set JAVA_OPTIONS=-Dweblogic.system.BootIdentityFile=C:\BEA\user_domains\mydomain\boot.properties
Thanks,
Sandeep