While starting managed servers asks for password of localhost

Question

We have a clustered environment and we are using Virtual IPs for the Managed servers. The managed servers in the forst node is not starting.
The problem I have narrowed down is that there are startup.properties file for the managed servers.
It has argument like -Dtangosol.coherence.localhost\=xgsoapd5v1.ea.com (for SOA1)
While SOA1 it is asking for password for the above host and the managed server is not starting.
Now SOA2 has the similar argument -Dtangosol.coherence.localhost\=xgsoapd5v2.ea.com (for SOA2), but it is not asking for any password and so the SOA2 managed server is sta! rting.
Similarly the while starting BAM1 it is asking for a password , but for BAM2 it is not asking for password and it is starting.
I could not yet figure out why it is behaving differently in the first node.
This is a copy of production with a chnage in the network. That means only the IP addresses are changed. xgsoapd5v1.ea.com and xgsoapd5v2.ea.com are the hostnames
It works perfectly in production environment.

Answer 1

Hi
Under your domain root folder say in the main machine where you have the AdminServer, you should have a folder structure something like this:
../user_projects/domains/yourBPMDomain1/servers. Under the servers folder you can see list of each server. On the main machine you will see one AdminServer folder. Under this there should be a sub-folder named security with one file named boot.properties. This boot.properties file will have encrypted username and password for the weblogic domain.
If this security/boot.properties exist under the each server folder, then when you start the managed server, it will NOT prompt for the username/password. If it DO NOT exist, it will ask for the credentials.
Solution is go to each Machine where you the ManagedServers (SOA Server or BAM Server does not matter). Go to each server and under that create a folder named security and create a file named boot.properties and in this file enter plain text username and password something like this and save the file. Now restart all those servers.
username=domainadminusername
password=doaminadminpassword
When you start the servers, server should start taking the above information. AND server will automatically ENCRYPT the above plain text data into hash codes.
In a nut shell, go to each Server folder across all the remote machines and under that particular managed server create a folder security with one file boot.properties.
Exmaple locations:
On Machine1 - user_projects/domains/bpmDomain1/servers/soa_server1/security/boot.properties
On Machine2 - user_projects/domains/bpmDomain1/servers/bam_server1/security/boot.properties
You DO NEED the admin username and password in plain text for one time to put in boot.properties. Later on it will get encrypted, so there is no threat for any security loop holes.
Thanks
Ravi Jegga