MSDN Magazine - August 2008 - (Page 64)

modify sits in one file, which is located in the App_Code subdirectory of the virtual directory to which the Web service was published. The name of the file will depend on the name of the entity being published, but will always end with asmx.cs. Opening this file will show the class and Web method declarations, which provide a public interface to calling entities and enable these requests to be pushed directly to the BizTalk MessageBox. To see what this generated code looks like, export an orchestra- The most complex post routing through the firewall is that involving Web services. tion with a two-way SOAP port using the Web Services Publishing Wizard. Once the wizard has completed, open the asmx.cs file in the App_Code directory and look at the code. The name of the Web method will be based on the name of the operation as defined on the port in the orchestration. Within this Web method is code that takes the incoming post and transforms it to a format that can be posted to the MessageBox. Once the Web service pushes it to the MessageBox, it then waits for a response that corresponds to the outbound response on the orchestration’s two-way port and posts this back to the calling entity. This code, once copied and placed on the new IIS server in the public network, must be modified so that it forwards the incoming post to the Web service on the BizTalk Server. The modification to the original proxy Web service code can be accomplished using the code shown in Figure 8. The code overwrites the Web method in the original Web service and, instead of posting to the MessageBox, loads some configurable fields from the web.config file and posts the incoming request to the Web service on the BizTalk IIS server. The routing to the BizTalk engine is still handled by the original proxy Web service. Because both Web services have the identical Web interface, either one can be called using the same client code. During development, therefore, you can work with the original Web service code as published by the wizard to validate that everything is working as expected. The proxy-to-the-proxy can be created during the final stages of testing and deployment without affecting any client code. The final step involved in working with the proxy-to-the-proxy Web service is to modify the web.config file on the public IIS server so that the configurable fields are available. The fields needed by the new Web service are shown here: These settings provide for the authentication values and the redirection URL. The actual list of configurable fields (and whether these are actually stored in the web.config file or elsewhere) is up to the developer, and is shown here for illustration purposes only. The most complex post routing through the firewall is that involving Web services. HTTP posts (and AS2) can be handled in a similar fashion but do Figure 8 Proxy-to-the-Proxy Web Service not require copying and modifying generpublic BTSRedirect.SyncTransResponse Operation_SyncTrans( ated code from BizTalk. In the case of HTTP [System.Xml.Serialization.XmlElementAttribute( Namespace="http://GuardianProStar.BizTalk.Schemas.SyncTrans.SyncTransRequest", posts, these can be routed with fairly simple ElementName="SyncTransRequest")] BTSRedirect.SyncTransRequest part) redirect patterns depending on the nature of { BTSRedirect.SyncTransRequest objSyncTransReq = part; the post. Many organizations can get mired BTSRedirect.SyncTransResponse objSyncTransRes = new BTSRedirect.SyncTransResponse(); in determining the right approach to routing BTSRedirect.GuardianProStar_BizTalk_Orchestrations_SyncTrans_SyncTransactions_Port_SyncTrans objWebServiceMethodCall = new traffic to and from their BizTalk servers, and BTSRedirect.GuardianProStar_BizTalk_Orchestrations_SyncTrans_SyncTransactions_Port_SyncTrans(); it is important to understand that these types // authentication/credentials of conversations should never get overly comstring strWSUser = System.Configuration.ConfigurationManager.AppSettings["WSUser"]; plex, as there are plenty of simple solutions to string strWSPassword = System.Configuration.ConfigurationManager.AppSettings["WSPassword"]; string strWSDomain = System.Configuration.ConfigurationManager.AppSettings["WSDomain"]; this common problem. string strWSAuthenticationType = System.Configuration.ConfigurationManager.AppSettings["WSAuthenticationType"]; objWebServiceMethodCall.Url = System.Configuration.ConfigurationManager.AppSettings["RedirectURL"]; System.Net.CredentialCache cache = new System.Net.CredentialCache(); cache.Add(new System.Uri(objWebServiceMethodCall.Url), strWSAuthenticationType, new System.Net.NetworkCredential(strWSUser, strWSPassword, strWSDomain)); objWebServiceMethodCall.Credentials = cache; // set the response equal to the return value of the call to the web service objSyncTransRes = objWebServiceMethodCall.Operation_SyncTrans(objSyncTransReq); return objSyncTransRes; } Handling Failed Documents EDI implementations are schema intensive. Every document that passes in or out of BizTalk is validated against a corresponding schema. If the document passes validation, it will be routed to the BizTalk engine and will be processed by the EDI components. If the document does not pass validation, however, it will fail and will, by default, remain unprocessed in BizTalk, flagged as invalid. By enabling erBizTalk EDI 64 msdn magazine

Table of Contents Feed for the Digital Edition of MSDN Magazine - August 2008

MSDN Magazine - August 2008 Toolbox CLR Inside Out Basic Instincts Cutting Edge Patterns in Practice Data 2.0 - Expose And Consume Data In A Web Services World Biztalk EDI - Build A Robust EDI Solution With BizTalk Server Silverlight - Create Animations With XAML And Expression Blend Write On! - Create Web Apps You Can Draw On With Silverlight 2 Wicked Code - Craft Custom Controls For Silverlight 2 Team System Foundations Windows With C++ Concurrent Affairs Going Places { End Bracket }

MSDN Magazine - August 2008

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.