Error while starting servers after Oracle IDM 11.1.1.5 installation

Question

I installed Oracle Identity Management Suite 11.1.1.5. I am trying to run ODSM for the first time to create Adapters for LDAP Sync. I tried to start Admin Server and it gives me the following error. Can anyone give me pointers for a workaround? Thanks in advance - Kalyan
<Jun 16, 2011 2:19:37 PM IST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-03026: PDPService and PolicyStore Service instance not found in default context. Reason: null
weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-03026: PDPService and PolicyStore Service instance not found in default context. Reason: null
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1398)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
&nbs p; at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsRuntimeException: JPS-03026: PDPService and PolicyStore Service instance not found in default context. Reason: null
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:185)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:160)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:280)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
Truncated. see log file for complete stacktrace
>
<Jun 16, 2011 2:19:37 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jun 16, 2011 2:19:37 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jun 16, 2011 2:19:37 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

Answer 1

Got solved. Needed to edit weblogic.policy file as mentioned in http://download.oracle.com/docs/cd/E21764_01/install.1111/e12002/oes.htm
19.3.2.2 Editing the weblogic.policy file
To edit the weblogic.policy file, run the following command:
IDM_HOME/common/bin/wlst.sh IDM_HOME/oes/modifygrants.py
Note:
The above command will only work if use the default policy name, weblogic.policy file. If you change the default name for the policy file, then you must open the file in a text editor and add the following lines, as shown in the example:
grant codeBase "file:${idm.opss.oracle.home}/modules/oracle.jps_${jrf.version}/*" {
permission java.security.AllPermission;
grant codeBase "file:${idm.opss.oracle.home}/oes/*" {
permission java.security.AllPermission;
grant codeBase "file:${oes.client.home}/-" {
permission java.security.AllPermission;
};