Microsoft has recently come up with a Development VM in the Gallery in Azure. It has everything needed for development – BizTalk Server, SQL Server and Visual Studio pre-packaged. You just have to select and click. Azure takes care of the rest and creates the VM within 15 minutes. Here is how it can be done:
The following is from Microsoft. I am adding this here for quick reference.
The BizTalk ESB Toolkit includes the following resolvers: STATIC, UDDI, UDDI3, XPATH, BRE, BRI, ITINERARY, ITINERARY-STATIC and LDAP.
A resolver’s connection string always consists of a moniker (such as BRE) followed by “:\\” and the connection or processing details. The moniker matches the definition of the associated resolver in the configuration file. The properties associated with each connection string are unique, and not all properties are required. The schema for each of the resolvers can be found in the ESB.Resolvers.Schemas project.
TransportLocation=/*[local-name()=’OrderDoc’ and namespace-uri()=’http://globalbank.esb.dynamicresolution.com/northamericanservices/’]/*[local-name()=’ID’ and namespace-uri()=’http://globalbank.esb.dynamicresolution.com/northamericanservices/’];
Action=;
EndPointConfig=;
JaxRpcResponse=;
MessageExchangePattern=;
TargetNamespace=/*[local-name()=’OrderDoc’ and namespace-uri()=’http://globalbank.esb.dynamicresolution.com/northamericanservices/’]/*[local-name()=’customerName’ and namespace-uri()=’http://globalbank.esb.dynamicresolution.com/northamericanservices/’];
The newest version of Virtual PC seems to have several interesting features. See the Microsoft Comparison here.
To install this version, the Processor needs to have Hardware Virtualization capabilities. Not all processors have this capability. The list of processors with Hardware Virtualization is available here.
If you are about to buy a new Notebook or PC to run virtual machines, it may be a good idea to consider this before making a decision.
I had to go through several Blogs and spend several hours trying to configure my BizTalk project to use Client Certificate Mapping, SSL, and WsHttp Adapter.
These are the steps that were needed to make this combination work:
1. Enable Anonymous Access in IIS for the Web Site
2. Setup Certificate Mapping in IIS
3.Enable “Require SSL”
4. Edit the Web.Config file and make sure that the System.ServiceModel looks like this:
<system.serviceModel>
<bindings>
<wsHttpBinding>
<binding name=”CertificateWithTransport”>
<security mode=”Transport”>
<transport clientCredentialType=”Certificate” />
</security>
</binding>
</wsHttpBinding>
</bindings>
<behaviors>
<serviceBehaviors>
<behavior name=”ServiceBehaviorConfiguration”>
<serviceDebug httpHelpPageEnabled=”false” httpsHelpPageEnabled=”true” includeExceptionDetailInFaults=”true” />
<serviceMetadata httpGetEnabled=”false” httpsGetEnabled=”true” />
</behavior>
</serviceBehaviors>
</behaviors>
<services>
<!– Note: the service name must match the configuration name for the service implementation. –>
<service name=”Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkServiceInstance” behaviorConfiguration=”ServiceBehaviorConfiguration”>
<!–<endpoint name=”HttpMexEndpoint” address=”mex” binding=”mexHttpBinding” bindingConfiguration=”” contract=”IMetadataExchange” />–>
<!–<endpoint name=”HttpsMexEndpoint” address=”mex” binding=”mexHttpsBinding” bindingConfiguration=”” contract=”IMetadataExchange” />–>
<endpoint name=”HttpsMexEndpoint” address=”mex” binding=”wsHttpBinding” bindingConfiguration=”CertificateWithTransport” contract=”IMetadataExchange” />
</service>
</services>
</system.serviceModel>
5. In the BizTalk Adapter Settings, make sure that you select “Transport” and “Certificate”.
Today I found that in BizTalk, there is a maximum limit for the number of characters that can be sent in an XML element. The limit is 50,000,000 chars.