SOA Suite 11.1.1.3 - doesn't create managed server

Question

Trying to install SOA Suite 11.1.1.3 from the docs at http://download.oracle.com/docs/cd/E15523_01/install.1111/e14318/qisoa.htm
Get right up until section "6.1 Configuring Custom Port Numbers for Oracle BAM" (without any errors in logs etc) and notice that the MW_HOME/user_projects/domains/domain_name/servers/ directory only has one entry - AdminServer - i.e. doesn't contain soa_server1 or bam_server1.
Odd, so anyway, carry on without it, startWeblogic.sh runs fine, contents of startManagedWebLogic_readme.txt are as follows:
To start managed servers, use either startManagedWebLogic.cmd
or startManagedWebLogic.sh, as appropriate for your environment.
Usage instructions:
For ease of reference, you defined the following managed
servers in your domain:
bam_server1
soa_server1
All good.
So I run startWeblogic.sh soa_server1. This actually creates the MW_HOME/user_projects/domains/domain_name/servers/soa_server1 directory - which seems good - but then it fails with the following:
####<05-Jun-2010 10:48:09 o'clock BST> <Info> <Security> <ts-laptop-u> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1275731289804> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server soa_server1 for security realm myrealm.>
####<05-Jun-2010 10:48:09 o'clock BST> <Notice> <Security> <ts-laptop-u> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1275731289805> <BEA-090082> <Security initializing using security realm myrealm.>
####<05-Jun-2010 10:48:10 o'clock BST> <Critical> <Security> <ts-laptop-u> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1275731290018> <BEA-090403> <Authentication for user weblogic denied>
####<05-Jun-2010 10:48:10 o'clock BST> <Critical> <WebLogicServer> <ts-laptop-u> <soa_server1> <Main Thread> <<WLS Kernel>> <> <> <1275731290020> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:965)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:244)
at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
at com.bea.common.security.internal.service.JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
at $Proxy16.login(Unknown Source)
Presumably, because there isn't a boot.properties file.
Even fixing that it gives me:
Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid;
I assume this is all down to the managed server not being created at config time.
Any ideas as to why this would be?
Thanks

Answer 1

Thanks for the reply Anuj,
1. Let me make one point clear, I don't need to create a Web Logic domain if I create a SOA DOMAIN.? right?
2. In setDomainEnv.sh BEA_JAVA_HOME has the JRMC (supported for SOA) PATH, as I selected jrmc while creating SOA DOMAIN.
3.I checked commEnv.sh file ( MW_HOME/wlserver_10.3/common/bin/commEnv.sh) and I copied some of the code,there is JAVA_HOME , so I will change to supported JRockit(jrmc).
# Reset JAVA_HOME, JAVA_VENDOR and PRODUCTION_MODE unless JAVA_HOME
# and JAVA_VENDOR are pre-defined.
if [ -z "${JAVA_HOME}" -o -z "${JAVA_VENDOR}" ]; then
# Set up JAVA HOME
*JAVA_HOME="/home/oracle/jrockit-R27.5.0-jdk1.6.0_03"*
# Set up JAVA VENDOR, possible values are
#Oracle, HP, IBM, Sun ...
JAVA_VENDOR=Oracle
# PRODUCTION_MODE, default to the development mode
PRODUCTION_MODE=""
fi
I don't see any other files where I have to change JAVA_HOME . I will look up in Web Logic forums too.
Thanks again
Arvind
Edited by: Arvind on Jul 21, 2010 7:30 AM
Edited by: Arvind on Jul 21, 2010 8:51 AM