Issue in starting oam server through Weblogic Console

ISSUE:

Unable to start oam_server through Weblogic Console after starting node manager for first time.

ERROR OBSERVED:

Logs @ $DOMAIN_HOME/servers/oam_server1/logs/oam_server1.out

<<
<Oct 23, 2015 8:44:20 AM > <Error> <Socket> <BEA-000438> <Unable to load performance pack. Using Java I/O instead. Please ensure that a native performance library is in: '/usr/jdk/instances/jdk1.6.0/jre/lib/sparcv9/server:/usr/jdk/instances/jdk1.6.0/jre/lib/sparcv9:/usr/jdk/instances/jdk1.6.0/jre/../lib/sparcv9:/u02/oracle/middlewareoam/patch_wls1036/profiles/default/native:/u02/oracle/middlewareoam/patch_ocp371/profiles/default/native:/u02/oracle/middlewareoam/wlserver_10.3/server/native/solaris/sparc64:/u02/oracle/middlewareoam/wlserver_10.3/server/native/solaris/sparc64/oci920_8:/usr/jdk/packages/lib/sparcv9:/lib/64:/usr/lib/64'>
<Oct 23, 2015 8:44:27 AM > <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified..
weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:341)
at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1789)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:443)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:841)
Truncated. see log file for complete stacktrace
Caused By: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
Truncated. see log file for complete stacktrace
Caused By: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:42)
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
Truncated. see log file for complete stacktrace
>
<Oct 23, 2015 8:44:27 AM > <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Oct 23, 2015 8:44:27 AM > <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:917)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)>
<Oct 23, 2015 8:44:27 AM > <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Oct 23, 2015 8:44:27 AM > <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Oct 23, 2015 8:44:27 AM > <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

REASON:

setNMProps.sh was not executed which sets properties that are added to the NodeManager.

SOLUTION:

Step 1) Stop the NodeManager Process

Step 2) Execute setNMProps.cmd located under (oam_home\oracle_common\common\bin)

$MW_HOME/oracle_common/common/bin

$. ./setNMProps.sh

Step 3) Start the NodeManager process from below location:

$WL_HOME/server/bin

$nohup ./startNodeManager.sh &

Step 4) Now start the oam_server1 through Weblogic Console

After running the script setNMProps.sh and restarting  the NodeManager in the middleware home, the managed server starts up fine. There are properties that need to be added to the NodeManager in the environment before starting oam_server for first time.