Send Many Validated with airSlate SignNow

Send many validated

hi I'm Dan to me and in this webcast we're going to discuss how you can use out-of-the-box pipeline components to enable schema validation in biztalk server 2010 the important thing to note first is that biztalk does not perform schema validation by default if an XML received pipeline is used biztalk does perform a high-level inspection of the message to determine the message type making sure that there is a corresponding scheme with deploy to the configuration database however this type is only defined by the target namespace and the root node name provided the message is well-formed XML the actual structure of the internal content may be completely invalid and bistec will still persist a message to the message box now that we know that we need to explicitly enable schema validation here are two ways to accomplish this within a receive pipeline the first is to use the editor box XML receive pipeline and simply set a couple of instance properties within the pipeline configuration on the received location because this method does not require any custom code it can be applied after an application has already been deployed the second method involves creating and deploying a custom pipeline that includes an XML validator component within the validation stage this component is part of the biztalk toolbox and doesn't require any actual coding however you do need to add a custom pipeline to host a component as none of the out of the box pipelines included let's look at the first method to get started assuming you have the receive location configured to use an XML receive pipeline you need to go into the instance properties by clicking the ellipsis button next to the pipeline drop-down list and then to change to properties the first property to set is the document spec names property by default this will be blank but to enable schema validation you will need to provide a list of every schema that defines a legitimate message through this location note that once you enter a schema here or other message types that attempt to enter vidas location will be rejected even if the schema is deployed to the database the schemas must be entered using the fully qualified name of the dotnet class representing the schema it can be quite tricky to get this right so we'll look at that in more detail on the next slide the only other property you must set is to change the validate document flag from its default setting of false to true note that if you set this flag without setting the document spec names property then you will get a runtime error stating that validation can only be performed when document schemas are provided getting the fully qualified name specification correct is a bit tricky and if you get it wrong then you'll just get runtime errors with every message submitted a sample fully qualified name is shown here as you can see it is made up of the.net name of the schema followed by the name of the assembly a comma separates these two items if you need to specify multiple schemas use a pipe character to delimit them the spaces around the pipe character are optional the easiest way to get the fully qualified name is to open the scheme of properties by double-clicking the item in the schemas list under the application the general page lists both the dotnet name and the assembly name for the schema just concatenate these two fields with a delimiting comma to get the fully qualified name the advantage of using this method is that there is no custom development required since it is achieved simply by configuring added a box components in the biztalk admin console this means that an administrator can add this validation to a receive board after the application has been fully developed and deployed without requiring any new development cycle the changes are effective immediately you don't even need to restart the host instances a potential disadvantage of this approach is that it can be tricky to get the fully qualified name is correct and you won't know this until run time when validation just doesn't work as expected it also tends to obscure the functionality a bit because unless you look into the instance properties you won't see the schema validation is enabled finally there is a situation where specifying multiple schemas that share the same target namespace can lead to runtime ambiguity issues that discussion is beyond the scope of this module but the following blog post describes details about this error and how to resolve it here we have a simple biztalk project in visual studio 2010 as you can see it contains schemas defining a simple request and response a map between the two and a very simple orchestration that simply execute the map and returns the response I've already deployed this application and published it using the WCF publishing wizard so let's give it a test first we'll look at the received location configuration so that you can see that i'm using the default xml receive pipeline and i haven't changed any of the standard properties on that here we have a valid request message for a service i'm going to submit it using soap you I we expect to get a successful response which we do now I'm going to make the message invalid simply by commenting out a mandatory field and i'll resubmit the message again notice we still get a successful response the reason is because I didn't change the root node name or the target namespace which is all that biztalk needed to recognize the message type it didn't do any further validation beyond that now we'll go back into our biz talk receive location and turn on schema validation by going into the properties here I'll have to set the document spec name for the schema that I want validated I happen to have that my clipboard so I'll paste it in there I'll also need to set the validate document property to true now by saving those changes they're effective immediately we don't have to restart any services now we'll go back to soap you I and resubmit are invalid message and this time we get a soap fault I'm going to look at the raw view because the text wraps and it's a little bit easier to see the reason for the error which is a schema validation error so biztalk is now validating the message all the way through the alternative method for validating scheme is is to use the XML validator pipeline component which is installed into the visual studio tool box with the developer edition of biztalk in order to host this component we need to create a custom receive pipeline but this is a lot easier than it sounds using the graphical pipeline designer tool in visual studio it is merely a matter of dragging and dropping an item or two from the toolbox on to the appropriate stage container and in many cases we don't even have to set any properties on the component the advantages of using this method include the fact that we don't have to mess around with tricky document specifications and fully qualified names the pipeline designer gives us a nice GUI tool to select scheme is if we really need to specify them it also makes the validation feature more apparent in the configuration especially if we named our custom pipeline appropriately and finally this method provides a workaround to that ambiguity issue we mentioned earlier about multiple schemas sharing the same target namespace on the downside it does require a bit of development effort so an administrator can't just decide to add this feature later on without a new release and deployment however I would advise developers to always include a custom pipeline for validation anyway even if they're not sure it's required because then the administrator is always free to choose which pipeline to be used for any given receive location back in our biz talk project in visual studio I'm now going to add a new custom receive pipeline to host my xml validator component so we're going to add new item we're going to get a new receive pipeline give it a meaningful name and you'll see right away the pipeline designer surface opens up so all I need to do is going to my tool box and drag an XML validator component onto the validate stage I'm also going to drag an XML disassembler component onto the disassembled stage this is necessary in order to parse the XML and set properties on the message context such as the biztalk message type and any other properties mark for promotion in the schema now that's really all the custom development I have to do for this demo provided I don't need any further constraints the XML disassembler will check the message and ensure that we have a schema deployed that matches the message type of the request if we want to restrict the incoming message types to a subset of all of the scheme is currently deployed that we can go to the document schemas property click the ellipsis here and simply choose the scheme of this that we want to limit this pipeline from accepting we don't need to do that here so I'll cancel that for now on the XML validator component itself we really don't need to set any properties because by default it will validate the message against any matching schema if finds deploy to the database now all I need to do is build the project and redeploy going back into the biztalk admin console we'll just refresh the group so it picks up the new configuration and then we'll go back into the receive location and now I can select my custom pipeline and if we go into the properties will see that we've got our XML disassembler component and our XML validator component and if I wish I can override the settings on the document spec names for both of these components and that would be particular to this instance but we don't need to do that here now we'll go back to soap you I and resubmit are invalid message and we should expect to see the same soulful with the same validation error which we do in this webcast we have shown that deep level schema validation at the receive port is not a default functionality in biztalk server we have to explicitly take steps to enable it we also saw that there are two ways to implement this validation using editor box components the first way is by configuring instance properties and the XML receive pipeline in the port which doesn't require any custom development effort and secondly by creating a custom pipeline to host an XML validation component I hope you have found this webcast useful and informative please also take some time to visit our user groups web portal where you'll find plenty of other links and resources if you decide the join and membership is free you'll not only have access to more areas at a portal including downloads of presentations code samples and participation in the discussion thread but you'll also receive event notifications and newsletters from Bristol I promise you won't be spammed and you can always unsubscribe if you change your mind again I'm Dan to me and I want to thank you for listening to this webcast if you have any comments or questions please feel free to use the YouTube comments stream