Oracle Identity Manager(OIM) start up error

ISSUE:

While starting OIM Server from Weblogic console ,below error was observed.

<<

<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 WSRPIdentityAsserter is not specified..
weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for WSRPIdentityAsserter is not specified.
at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:342)
at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
>>

REASON:

Node Manager was not configured properly to use the required startup script for the managed(OIM) server.

Before start of  OIM Server from console(for first time) setNMProps.sh was not executed.

SOLUTION:

1) Stop the node manager process if it is already running.

2) Edit nodemanager.properties file and edit below parameter:

  StartScriptName=startWebLogic.sh
  StopScriptEnabled=true
  StartScriptEnabled=true

Note: You can execute setNMProps.sh also from below location:

$MW_HOME/oracle_common/common/bin

3) Save the file.

4) Start Node Manager Process and try starting OIM Server from console.

$WL_HOME/server/bin

$nohup ./startNodeManager.sh &

Server starts up without nay issues.