Exposing only Service Metadata
Consider a situation where we have a service that has already been exposed. In this case, it is an in-process service that does not rely upon IIS to host the endpoint. An example of this situation may be a NetTCP endpoint hosted by BizTalk. In this case, how can we provide a service contract to a consuming application that it could use in order to conform to the message formats we are expecting? The answer can be found in the BizTalk WCF Service Publishing Wizard!
When we launch the BizTalk WCF Service Publishing Wizard, we have the opportunity to create an endpoint or we have the ability to publish metadata exchange (MEX) endpoint. Utilizing this process will allow us to select an existing Receive Location and then generate a MEX endpoint for that Receive Location. The following screenshot provides an illustration of the screen that we will use to generate this metadata. Once the metadata endpoint has been published, we can provide this endpoint to our consuming...
