Modified 02-MAY-2011 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Changes
Cause
Solution
Applies to:
Hyperion Financial Close Management - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
Symptoms
After bringing up all the Hyperion Services and setting the schedule to 'open' within FCM, none of the assigned Tasks will start. Error thrown in the soa_server*-diagnostic.log, see below.
Changes
The Keystore Step was either missed or skipped. See 'Configuring the Keystore for Oracle Web Services Manager' in the EPM Install guide http://download.oracle.com/docs/cd/E17236_01/epm.1112/epm_install_11121.pdf .
Cause
The issue is caused by the following setup: The keystore was not configured correctly. The following error identifies the issue:
[2011-04-17T03:55:02.416-04:00] [soa_server1] [ERROR] [] [oracle.soa.bpel.engine.ws] [tid: orabpel.invoke.pool-4.thread-15] [userId: fcmdemo] [ecid: 0000IxWGuip5yWc5Tjl3ic1DeGqd0001DQ,0:1:100004215] [APP: soa-infra] [composite_name: FCCNotificationComposite] [component_name: SendNotification] [component_instance_id: 2079] got FabricInvocationException[[
java.security.UnrecoverableKeyException: Password verification failed
at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:769)
at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:38)
at java.security.KeyStore.load(KeyStore.java:1185)
at oracle.wsm.security.jps.WsmLegacyKeyStore.
at oracle.wsm.security.jps.WsmKeyStoreFactory.getKeyStore(WsmKeyStoreFactory.java:60)
at oracle.wsm.security.policy.scenario.executor.SecurityScenarioExecutor.updateWsmKeyStore(SecurityScenarioExecutor.java:1216)
at oracle.wsm.security.policy.scenario.executor.SecurityScenarioExecutor.initialize(SecurityScenarioExecutor.java:455)
at oracle.wsm.security.policy.scenario.executor.SecurityScenarioExecutor.init(SecurityScenarioExecutor.java:305)
at oracle.wsm.security.policy.scenario.executor.Wss11SamlWithCertsScenarioExecutor.init(Wss11SamlWithCertsScenarioExecutor.java:72)
at oracle.wsm.policyengine.impl.runtime.WSPolicyRuntimeExecutor.populateAssertionExecutors(WSPolicyRuntimeExecutor.java:256)
at oracle.wsm.policyengine.impl.runtime.WSPolicyRuntimeExecutor.populateAssertionExecutors(WSPolicyRuntimeExecutor.java:279)
at oracle.wsm.policyengine.impl.runtime.WSPolicyRuntimeExecutor.init(WSPolicyRuntimeExecutor.java:162)
at oracle.wsm.policyengine.impl.PolicyExecutionEngine.getPolicyExecutor(PolicyExecutionEngine.java:137)
at oracle.wsm.policyengine.impl.PolicyExecutionEngine.execute(PolicyExecutionEngine.java:101)
at oracle.wsm.agent.WSMAgent.processCommon(WSMAgent.java:937)
at oracle.wsm.agent.WSMAgent.processRequest(WSMAgent.java:454)
at oracle.fabric.common.BindingSecurityInterceptor.processRequest(BindingSecurityInterceptor.java:94)
at oracle.integration.platform.common.InterceptorChainImpl$1.run(InterceptorChainImpl.java:187)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.integration.platform.common.InterceptorChainImpl.processRequestAsSubject(InterceptorChainImpl.java:185)
at oracle.integration.platform.common.InterceptorChainImpl.processRequest(InterceptorChainImpl.java:102)
at oracle.integration.platform.common.mgmt.InterceptorChainManager.processRequest(InterceptorChainManager.java:235)
at oracle.j2ee.ws.client.mgmt.runtime.SuperClientInterceptorPipeline.handleRequest(SuperClientInterceptorPipeline.java:96)
at oracle.j2ee.ws.client.jaxws.DispatchImpl.handleRequest(DispatchImpl.java:615)
at oracle.j2ee.ws.client.jaxws.DispatchImpl.handleRequest(DispatchImpl.java:593)
at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:789)
at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:235)
at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:106)
at oracle.integration.platform.blocks.soap.AbstractWebServiceBindingComponent.dispatchRequest(AbstractWebServiceBindingComponent.java:517)
at oracle.integration.platform.blocks.soap.WebServiceExternalBindingComponent.processOutboundMessage(WebServiceExternalBindingComponent.java:207)
at oracle.integration.platform.blocks.soap.WebServiceExternalBindingComponent.sendSOAPMessage(WebServiceExternalBindingComponent.java:826)
at oracle.integration.platform.blocks.soap.WebServiceExternalBindingComponent.request(WebServiceExternalBindingComponent.java:603)
at oracle.integration.platform.blocks.mesh.SynchronousMessageHandler.doRequest(SynchronousMessageHandler.java:139)
at oracle.integration.platform.blocks.mesh.MessageRouter.request(MessageRouter.java:179)
at oracle.integration.platform.blocks.mesh.MeshImpl$2.run(MeshImpl.java:178)
at javax.security.auth.Subject.doAs(Subject.java:396)
at oracle.integration.platform.blocks.mesh.MeshImpl.doRequestAsSubject(MeshImpl.java:176)
at oracle.integration.platform.blocks.mesh.MeshImpl.request(MeshImpl.java:152)
at sun.reflect.GeneratedMethodAccessor885.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy295.request(Unknown Source)
Solution
1) Navigate to /Oracle/Middleware/user_projects/$DOMAIN_HOME/config/fmwconfig
2) Delete or rename the default-keystore.jks file
3) Rerun the command:
keytool -genkeypair -keyalg RSA -alias orakey -keypass welcome1 -keystore defaultkeystore.jks -storepass welcome1 -validity 3600
4) Reboot SOA.
Please change the alias/password as needed to fit your environment. Keep in mind if you have already gone through the steps in Enterprise Manager for setting the Keystore Management, your ID and Password must match what you entered into the key file. If it doesn't you will continue to get failed password error messages. See 'Assign the Keystore to the EPM System WebLogic domain' in the EPM Install guide for more details.
No comments:
Post a Comment