Integrating to the max...BizTalk Style

For my project I needed to expose an Endpoint, which accepts an HTTP Post with Xml as input/output. As I like to start small I’ve tried to start with a small test project. In this project, I wanted to learn how to expose an endpoint, how to set everything up and what options are there. This, because there are a lot of resources on all sort of specific issues, but the ones I faced were scattered in several blogposts. So for my project I developed a WCF Service, which was created using a WCF Webrole so that I can also publish it in Azure. ·          Create a new WCF Webrole o    Create a new Cloud service o    Create a new web role o    Which should result in a similar structure ·          Configure the endpoint to use WCF-WebHTTP and allow a help page At this point, you have a WCF Service, which is not yet exposed a WCF-WebHTTP endpoint. We can do this by: o  ...

This time we will follow up on the Service Virtualization concept I mentioned in my previous post. Service redesign Apply security Monitoring Service redesign Why? A webservice might not have been developed by your team, a changes in the web service should not break your existing implementation, it might not meet certain standards, resulting for example as shown in the figure below, in a ‘large’ wsdl which contains a lot of methods, of which you only need one. Consider the port in BizTalk generated based on a web service, it is generated with every method defined in the webservice, if one of the methods changes, it will lead to a broken solution, although we only needed to implement a single method.      http://abdulrafaysbiztalk.wordpress.com/ We can change this by defining a Virtual Service layer around the webservice, for this, we will use the public Geoipservice which (unfortunately) only exposes 2 methods (but I think the example provides a good ...

When you have the BizTalk Adapter pack installed, it will update the (machine) config, with some endpoints for certain line of business adapters… After starting a WCF service, the testclient will start; you might get an error for each MEX endpoint registered for the LOB adapter as shown in the figure below; Even though MEX is not enabled in the web.config of the particular project; it’s problably documented somewhere, but i could not found a fix, so hereby the workaround, the manual of the LOB adapters already states which config file to edit; And comment the adapters you don’t need;   The annoying thing is however, that with this setting, generating schemas using the ‘Add generated items’ wizard will not work as expected and you can’t see the tables/procedures in you database. So remember to enable IMEX if you need to create schemas for the SQL adapter!   HTH, Sander               Start the svc editor