What should you do?

You are integrating BizTalk Server 2010 with a secure Microsoft Windows Communication Foundation (WCF) service that does not have metadata exchange (MEX) enabled. The web service provider distributes an XML schema with a root node named SecretData without a namespace for the data provided by the web service. You generate a BizTalk schema based on the XML schema. You finish developing the application and deploy it for integration testing. When testing the service, you trace the messages received from the service. You see that the response message is within a single element named SecureResponse. SOAP elements wrap the response message and the SecureResponse element. You need to specify the inbound message body properties to ensure that the message can be received. What should you do?

You are integrating BizTalk Server 2010 with a secure Microsoft Windows Communication Foundation (WCF) service that does not have metadata exchange (MEX) enabled. The web service provider distributes an XML schema with a root node named SecretData without a namespace for the data provided by the web service. You generate a BizTalk schema based on the XML schema. You finish developing the application and deploy it for integration testing. When testing the service, you trace the messages received from the service. You see that the response message is within a single element named SecureResponse. SOAP elements wrap the response message and the SecureResponse element. You need to specify the inbound message body properties to ensure that the message can be received. What should you do?

A.
Choose the Envelope option. Add the soapProcessing endpoint behavior with the property processMessages=True.

B.
Choose the Path option. For the body path expression, specify /*[local-name()=’SecureResponse’]/*[local-name()=’SecretData’].

C.
Choose the Path option. For the body path expression, specify /*[local-name()=’SecretData’]. Add the soapProcessing endpoint behavior with the property processMessages=True.

D.
Choose the Body option. Add the useRequestHeadersForMetadataAddress service behavior.



Leave a Reply 0

Your email address will not be published. Required fields are marked *