WLS 8.1 SP4
Windows XP SP2

My client is moving from JRun to WebLogic.  I'm part of the support
team for this move.  They currently have desktop images scripted and
installed automatically, including WebLogic Server, onto development
environments.

The issue I'm having is when you try and start a managed server, it
balks with the following exception:

weblogic.nodemanager.NodeManagerException: [CommandInvoker: Failed to
send command: 'online to server 'HAHA' to NodeManager at host:
'localhost:5555' with exception [Security:090504]Certificate chain
received from localhost - 127.0.0.1 failed hostname verification check.
Certificate contained LOL8675309 but check expected localhost. Please
ensure that the NodeManager is active on the target machine]
at
weblogic.nodemanager.client.CommandInvoker.execute(CommandInvoker.java:154)

at
weblogic.nodemanager.client.CommandInvoker.invoke(CommandInvoker.java:91)

at
weblogic.nodemanager.client.NodeManagerClient.executeCommand(NodeManagerClie
nt.java:161)

at
weblogic.nodemanager.client.NodeManagerExecuteRequest.execute(NodeManagerRun
time.java:1641)

at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
No Exception Messages

The image of course was built on LOL8675309 and it seems that the
Demo.crt and DemoIdentity.jks hold this reference.  I have tried
building my own but just get beyond this with broken certificate chain
errors that further confound the problem.

Desired Solution.  I have turned the net and this site upside down
looking for an easy way to do this.  I have created my own certs and
Identity file, added it to the jdk cacerts, specifed this for the
application in question as well as in the node manager properties file.
This of course results in the Admin which starts and runs without
issue fighting with Node Manager when it tries to start the Managed
server.  Is there some resource that outlines the replacement of the
default Demo cert files with new ones.  I am limited in experience in
this but I find doc in this regard plenty telling what to do but not
how to do it.

Ideal Solution.  I would like to change the scripted install to not
reference LOL8675309 at all.  I thought that there was a silent install
option to specify this during install but it doesn't seem to exist
anymore?  Is there some way to do this with a silent install or
otherwise.  Changing our scripting of the install would be a cleaner
workaround from having to provide developers with new certs and support
configuring WLS to use them.

Any help or suggestions appreciated.

[ Post a follow-up to this message ]