In a meeting a few weeks ago the question of how to support the MOS protocol with BizTalk came up. The MOS protocol, used in the media industry, has two flavours – Versions 3.x are implemented as ’proper’ web services Versions 2.x are implemented as ’xml over TCP’ As the former is a no-brainer for BizTalk, I wanted to look at what it would take to support the later- The protocol (as
Search this Site:
Recent Posts
- Logic App Consumption deployment: The secret of KeyVault parameter cannot be retrieved. Http status code: ‘Forbidden’. Error message: ‘Access denied to first party service
- BizTalk Server Visual Studio project: attempted re-targeting of the project has been canceled.
- BizTalk Oracle Adapter error: The assembly required for type mapping not found.
- PowerShell script to identify all SQL V1 actions and triggers inside Logic Apps Consumption
- Friday (funny) Fact: There is no size limit for the Logic App parameter name