I am trying to use the WSE Adpater to consume a web service from within a
Biztalk Orchestration.

I have managed to do this successfully agasint the UsernameSigning Sample
that comes with the WSE 2.0 distribution.

However I am now trying to access the actual target service and the
following problem is arising:

When working through the WSE Adaptor wizard I access a secure web service
endopint requiring a client certificate, this works fine. The service suppor
t
two operations both of which I select. I then select the associated policy
file via its URL and receive the following error message

"The policy file is not valid. Verify that the URL or file location referes
to a valid policy file"

Key points to note:

The wsdl file was access via
https://myservice.com/service.wsdl
(i.e. the wsdl is not accessible in the usual way  as service.asmx?wsdl)

The wsdl specifies that the location of the service is
https://myservice.com/service.asmx

The policy file contains the following

<?xml version="1.0" encoding="utf-8"?>
<policyDocument xmlns="http://schemas.microsoft.com/wse/2003/06/Policy">
<mappings>
<defaultEndpoint>
<defaultOperation>
<request policy="#MessageAge-Policy"/>
<response policy=""/>
<fault policy=""/>
</defaultOperation>
</defaultEndpoint>
</mappings>
<policies
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurit
y-utility-1.0.xsd"
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing"
xmlns:wse="http://schemas.microsoft.com/wse/2003/06/Policy"
xmlns:wsp="http://schemas.xmlsoap.org/ws/2002/12/policy"
xmlns:wssp="http://schemas.xmlsoap.org/ws/2002/12/secext"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecuri
ty-secext-1.0.xsd">
<wsp:Policy wsu:Id="MessageAge-Policy"
xmlns:wsp="http://schemas.xmlsoap.org/ws/2002/12/policy"
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing"
xmlns:wssp="http://schemas.xmlsoap.org/ws/2002/12/secext">
<wssp:MessageAge wsp:Usage="wsp:Required" Age="300"/>
</wsp:Policy>
</policies>
</policyDocument>

I am thinking that the problem must be something to do with a check
performed along the lines of the service location in the wsdl must match an
endpoint defined in the policy. So I manaually amended the policy file to
explicity have the same url for the endpint as the service location and
loaded this from the file system, however this resulted in the same error.

Any help would be greatly appreciated.

Thanks

Glen

[ Post a follow-up to this message ]