Error When Sending Service Request Through OWSM Gateway

Question

We are trying to test using OWSM Gateways and Server Agents to sign and then verify messages being passed to a web service on a server. We have been able to get this to work with a simple HelloWorld type service without any problems. We then followed the exact same steps to do this with an actual service and it is not working.
We run the test from the "Test Page" inside the ccore GUI. We first test the connection directly to the service and receive a message about it missing the WS Security header. This is somewhat expected. Then, we send through the gateway which is set up to sign the message and pass along the header and receive the same error message:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header/><env:Body><env:Fault xmlns="http://schemas.oblix.com/ws/2003/08/Faults"><faultcode xmlns="">:GenericFault</faultcode><faultstring xmlns="">WS-Security process failure:FAULT CODE: InvalidSecurity FAULT MESSAGE: Missing WS Security header in the SOAP message</faultstring><faultactor xmlns=""></faultactor></env:Fault></env:Body></env:Envelope>
We have checked the OWSM logs and can see that both times the server agent receives the request. The gateway logs, however, do not show any requests or responses even though the message should have gone through it. We do see these messages in the logs when testing our HelloWorld service with the same sign/verify settings. A review of the gateway.log file shows the following message displayed each time we submit a test to the malfunctioning service:
2007-10-18 10:30:22,263 INFO [AJPRequestHandler-HTTPThreadGroup-54] gateway.WSDLRegistry - Exception occured in updateWSDL
We have until tomorrow to get this issue resolved before development presses to move forward without OWSM security and we cannot have that. Your immediate assistance is required. Thank you.

Answer 1

Some additional research has been done here and it seems that web services created with SOAP 1.1 (such as the HelloWorld service) work just fine. The problem is with services created with SOAP 1.2. Are there separate configurations or changes that need to be made for SOAP 1.2 services?