Hot answers tagged biztalk
When I have done this sort of thing before - database shared across applications, I find it best to have a single "engine" management service that handles the database - and all apps interface with that. This allows for single place for database code changes - new tables etc - and also managing access, turning on/off application access, security, downtime ...
When a flood of messages is received from a particular X (say X1), Y should try and combine the messages (removed duplicates, etc.) without any loss of information and then send the messages at pace that Z would be able to handle. All this while messages from other Xs would be processed (by Y) and be sent to Z.
It depends on what you want to prove with your tests. If you want to prove that the transform works, you can use one or more input messages, apply the transformation, and use validation on the output message. More specific validations can be done with XPath checks on specific fields. These kind of tests can be used to validate upto 80% of the working of ...
I'm not an expert on BizTalk, but I made some unit tests for XSLT. I found several ways to do it. Creating some XML that represent the usual data. Developing a reverse tool (from XSLT output to significant XML data) and then testing XSLT over a big amount of XML (e.g. monthly invoicing, integration messaging, etc.). If you can obtain the significant part ...
Only top voted, non community-wiki answers of a minimum length are eligible