This post is related to OAM Managed server issue from our Oracle Access Manager Training (next batch starts on 29th Nov, 2015 – Register now for early bird discount, limited time only) where apart from Architecture, Installation, Configuration, Integration we also cover High Availability & Disaster Recovery.
As OAM is deployed on Weblogic Server, We cover WebLogic Concepts like Domain, Admin & Managed Server and Clusters.
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 issues like above or wish to discuss challenges you are hitting in Oracle Access Manager Implementation, register for our Oracle Access Manager Training (next batch starts on 29th Nov, 2015 – Register now for early bird discount, limited time only).
We are so confident on quality and value of our training that We provide 100% Money back guarantee so in unlikely case of you being not happy after 2 sessions, just drop us a mail before third session and We’ll refund FULL money (or ask us from our happy trainees in our private Facebook Group).
Did you subscribe to our YouTube Channel (375 already subscribed) ?
The post Starting OAM Managed Server from Weblogic Console, Check This ? appeared first on Oracle Trainings for Apps & Fusion DBA.