biztalk

We have a DMZ with an IIS Web Server, and BizTalk 2009 on a LAN. I'd like to know what is the best way to deploy a BizTalk Web Service so that it is publicly accessible on the Internet, but inline with security best practices. Should we deploy the BizTalk-generated Web Service to the IIS box? Should we host the Web Service on the BizTalk box and expose BizTalk to the world (for specific ports and specific external IP's only)? Should we use IIS as a reverse proxy and host the Web Service on BizTalk? Any guidance much appreciated. I would seriously think about separating the web service from the

BizTalk sees thumbprint for an internal SFTP test as ssh-rsa 2048 33:88:f0:ff:63:78:a9:2b:3f:09:cb:05:81:db:59:86 WinSCP shows: ssh-ed25519 256 ff:2e:5e:33:7a:15:de:69:18:cf:82:ae:f0:4e:7b:d2 (when I click "Session", then "Server/Protocol Information") Is it possible to convert one to the other? Is it possible to get the ssh-rsa thumbprint from WinSCP, PuTTY or some other tool? WinSCP uses Ed25519 host key. It's a different key, than the RSA host key used by BizTalk. You cannot convert one to another. Also you cannot force WinSCP to use RSA hostkey. WinSCP will always use Ed25519 hostkey as

I'm reading all over the net that you your separate your "external schemas" from your "internal schemas" and never expose the "internal schemas" to any external actor. If my solution only acts as a messagebus to create a loose coupling between 2 existing systems, will I really need any internal schemas? System A makes a Request(Message with SchemaA) to Biztalk Biztalk Maps SchemaA to SchemaB Biztalk forwards request of type SchemaB to SystemB SystemB returns ResponseB Biztalk maps ResponeB to ResponeA Biztalk routes the result back to System A I can't see the pro's of having an internal schema

I need a easy and trusted way to compare GAC (Global Assembly Cache) from two servers, during BizTalk migration. I also want to move the GAC from QA to Production if it doesn't exist in the destination server. These are both BizTalk servers and have tons of assemblies GAC'd. I saw some tools online but the link to one was broken (winmerge) and others did not seem really authentic. Thanks for your help. schellack Whenever I need to find something in the GAC, I always just run Gacutil.exe /l > c:/gac.txt from a Visual Studio (or, if that's not available, Windows SDK) command prompt, and then

We have a client that is going to use the AlwaysOn Availability feature of SQL Server 2012. They want to have the BizTalk WCF-SQL port connect to the read-only replica. The documentation on the subject say that the connection has to be made to the SQL Server 2012 Availability Group Listener, and the connection has to be able to set the “ApplicationIntent” parameter. This tells the SQL Listener that the connection is a read-only intent connection, and that it should be redirected to a readable secondary replica. Without that working the connection will be made to the primary database which is

In BizTalk 2006 R2, is there some way to regenerate the reference to a WCF service that has been created using the "Add Generated Items / Consume WCF Service" option? I tried just re-running the wizard, but it creates new ODX, BindingInfo, etc. files, and breaks the solution, so that's not the way :-( Searched the web, but not found any references to how to update the references, just plenty on creating from scratch I agree with Marvin, delete the old files and generate new ones. If you keep the old ones before you regenerate you will of course have other names on the newly created, like

We are using BizTalk Server to send messages via MSMQ. The receiving system requires that each message have the extension property set to a guid (as a byte array). MSDN documents the Extension property of the MSMQMessage here and (in .NET) here . It is simple to set the extension property in .NET: const string messageContent = "Message content goes here"; var encodedMessageContent = new UTF8Encoding().GetBytes(messageContent); // Create the message and set its properties: var message = new System.Messaging.Message(); message.BodyStream = new System.IO.MemoryStream(encodedMessageContent);