Starting OAM Managed Server from Weblogic Console, Check This ?

 

One of the trainee from our previous batch encountered issue while starting OAM Managed server (oam_server1) from WebLogic Administration Console (/console). When a server is started using Console, a utility called Node Manager is used in the background. Make sure that Node Manager is running and Machine is associated with Managed Server

If you see node manager is fine and still startup fails then check the Managed Server log file located at $DOMAIN_HOME/ servers/ [oam_server1]/ logs and in our case, it was showing below error messages:

Caused By: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]Security Provider 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)
at weblogic.security. service. CSSWLSDelegateImpl. initializeServiceEngine(CSSWLSDelegateImpl.java:299)
at weblogic. security.service. CSSWLSDelegateImpl. initialize(CSSWLSDelegateImpl.java:220)
at weblogic.security. service. CommonSecurityServiceManagerDelegateImpl. InitializeServiceEngine (CommonSecurity ServiceManagerDelegateImpl.java:1789)

Root Cause:

In the nodemanager.properties file (configuration file that is used to start node manager), the value of the flag StartScriptEnabled was set to false (by default) because of which the parameters that are provided in startWeblogic.sh was not provided to JVM and therefore, resulting in the error as specified above.

Fix:

1. Stop Node Manager: Exit from the terminal in which node manager started.

Note: there is no script to stop Node Manager so just kill the process

2. Run setNMProps.sh script located under $MW_HOME/oracle_common/common/bin
./setNMProps.sh (This will enable the StartScriptEnabled flag in nodemanager.properties)

You should get the output as:  “Appending required nodemanager.properties

3. Start Node manager ./startNodeManager located under $WL_HOME/server/bin

./startNodeManager.sh

4. Start Managed Server using Administration Console. It should be RUNNING now.

If you want to learn more in Oracle Access Manager Implementation then register for our free Minicourse by clicking on below image.

OAM FREE Mini Course by Oracle ACE Atul Kumar

Series NavigationOracle Access Manager (OAM 11g) Interview Questions.. Do you know enough about OAM ??? >>

Share This Post with Your Friends over Social Media!

About the Author SeemaYadav

Oracle Consultant at K21 Technologies - Oracle Gold Partner specialising in Design, Implement, and Support.

Leave a Comment:

2 comments
S Khan says July 6, 2017

Perfect ! It worked for me. Thanks Seems.

Reply
Add Your Reply