BEA-387026 encountered after upgrading to OSB 11g (11.1.1.7)

Problem:

When you have an OWSM policy attached to an OSB 11g proxy service, this typically works fine. But after upgrading to OSB 11g PS6 (11.1.1.7), you may experience the following error in the logs:

<Jun 19, 2014 6:34:21 PM EDT> <Error> <OSB Security> <BEA-387026> <An internal web service security error occurred [error-code: InternalError, message-id: 5630667683963361529-6593aaf0.146aae8a55c.-4741, proxy: SalesOrder/ProxyService/SalesOrder, target: null, operation: null]--- Error message:nulljava.lang.NoSuchMethodError: com/bea/wli/sb/security/wss/WssInboundContext.setRequestMessage(Ljavax/xml/soap/SOAPMessage;Ljava/lang/Class;Ljavax/xml/soap/MessageFactory;)V        at com.bea.wli.sb.security.wss.wsm.WsmInboundHandler.processRequest(WsmInboundHandler.java:181)        at com.bea.wli.sb.security.wss.WssHandlerImpl.doInboundRequest(WssHandlerImpl.java:228)        at com.bea.wli.sb.context.BindingLayerImpl.addRequest(BindingLayerImpl.java:291)

Solution:

1. Log in to the WebLogic Server Administration Console

2. Untarget "OWSM Policy Support in OSB Initializer Aplication" from the osb_cluster and AdminServer

3. Shutdown osb_server1, osb_server2, and AdminServer

4. Run these commands on the first node of your cluster (modify directories accordingly):

cd /u01/app/oracle/middleware/user_projects/domains/osb_domain/servers/osb_server1/tmp 

rm -rf * 

cd /u01/app/oracle/middleware/user_projects/domains/osb_domain/servers/osb_server1/cache 

rm -rf *

5. Run these commands on the second node of your cluster (modify directories accordingly):

cd /u01/app/oracle/middleware/user_projects/domains/osb_domain/servers/osb_server2/tmp 

rm -rf * 

cd /u01/app/oracle/middleware/user_projects/domains/osb_domain/servers/osb_server2/cache 

rm -rf *

6. Startup Admin_Server, osb_server1, osb_server2

7. Target "OWSM Policy Support in OSB Initializer Aplication" from osb_cluster and AdminServer

8. Shutdown osb_server1, osb_server2, and AdminServer

9. Run these commands again on the first node of your cluster (modify directories accordingly):

cd /u01/app/oracle/middleware/user_projects/domains/osb_domain/servers/osb_server1/tmp 

rm -rf * 

cd /u01/app/oracle/middleware/user_projects/domains/osb_domain/servers/osb_server1/cache 

rm -rf *

10. Run these commands again on the second node of your cluster (modify directories accordingly):

cd /u01/app/oracle/middleware/user_projects/domains/osb_domain/servers/osb_server2/tmp 

rm -rf * 

cd /u01/app/oracle/middleware/user_projects/domains/osb_domain/servers/osb_server2/cache 

rm -rf *

11. Startup Admin_Server, osb_server1, osb_server2


Applicable Versions:

• Oracle Service Bus (OSB) 11g (11.1.1.7)

References:

• http://blog.whitehorses.nl/2013/12/27/owsm-java-lang-nosuchmethoderror-when-using-wss_username_token_service_policy/?utm_source=tuicool

Unable to retrieve composite detail in EM Fusion Middleware Control

Problem:

When logging in to the Oracle Enterprise Manager 11g Fusion Middleware Control console to view the details of the SOA composite, you might receive the following error when you click on the composite:

Unable to retrieve composite detail.
The composite X is not available. This could happen because either the composite has been undeployed or soa-infra has not yet loaded this composite.

The soa_server1.out log file will show this error:

<Jun 19, 2014 12:00:23 PM EDT> <Error> <Default> <J2EE JMX-46336> <MBean operation access denied.
  MBean: oracle.soa.config:name=soa-infra,j2eeType=CompositeLifecycleConfig,Application=soa-infra
  Operation: getDefaultComposite(java.lang.String)
  Detail: Access denied. Required roles: Admin, Operator, Monitor, executing subject: principals=[]
java.lang.SecurityException: Access denied. Required roles: Admin, Operator, Monitor, executing subject: principals=[]
        at oracle.as.jmx.framework.wls.spi.security.WLSMBeanSecurityHelper.isInWlsGlobalSecurityRoles(WLSMBeanSecurityHelper.java:245)

Resolution:

Even though the stack trace above claims otherwise, in Oracle SOA Suite 11g (11.1.1.7), you must grant the user 'Administrators' role to the user. Could be a bug.

Applicable Versions:

• Oracle SOA Suite 11g (11.1.1.7.0)