I installed the Logic Apps mapper/schema editor SDK on a BizTalk 2016 VM.
After I loaded a BizTalk project to make some changes, I discovered that the BizTalk Project Template was overwritten.
I thought this was a bug and reported it.
SaaS connectors that will grow in numbers in the near future and connectors to Azure Services. Connectors that provide connectivity to anything, anywhere, which is basically the key driver for integration. Hence the centralizing Logic Apps and BizTalk Server at the heart of Microsoft’s Enterprise Integration Platform.
We have arrived in the digital age, where applications and data is everywhere. With all types of devices, we are connected 24/7 and surrounded by data we consume. And enterprises need to be connected and have access to data in- and outside their data center or cloud. Therefore, integration plays an essential role that it always had.
Microsoft technology has evolved over the years and matured into the tools we can use in this digital age to build integrations that fulfill current business needs. BizTalk Server, and Logic App each serve the need for enterprise requirements for integration and can work together nicely. And this Microsoft’s vision for integration i.e. the unified integration experience.
BizTalk Server can provide deep integration with divers line of business systems like SAP and Oracle and act as a gateway to the cloud. Logic Apps can make enterprises more agile to quickly deploy small integration solutions with minimal overhead and lead time. Both collaborate well with API Management and the Azure Service Bus, two other key Azure Services, forming Microsoft Integration Platform. A platform designed and built for the digital age!
Cheers,
Steef-Jan
The new kid on the block in Microsoft’s integration portfolio is Logic Apps. And for those who do not know what a Logic App is; it’s a hosted piece of integration logic in Microsoft Azure. To be more precise the hosting is done in Azure in a similar way as a Web App and the logic are built by creating a trigger followed by a series of actions similar to a workflow. And you can simply create and
We are happy to announce that BizTalk Server 2016 is available on the MSDN Subscriber download site. We currently have the following versions available:
The BizTalk Server 2016 Developer edition will be coming soon.
We also have the BizTalk Server 2016 Enterprise edition available in Azure through the classic portal (this will be coming to the new portal soon).
Host Integration Server 2016 is also part of BizTalk Server and available for MSDN download too. For more info on HIS 2016 check out the team blog here.
We are constantly looking for feedback to improve the product. If you want to participate and work even more with the product group feel free to sign up for Azure Advisors and join our group. If your company already is a part of the Azure Advisors use this link to join.
For those of you that missed our announcements here and here, BizTalk Server 2016 has been released to manufacturing (RTM) today! What does this mean? Well, we now go through the process of making the media available across all channels which takes a little time to complete. But we know you can’t wait for all…
Blog Post by: BizTalk Team
After Microsoft announced today that BizTalk Server 2016 just reach RTM, however is not yet public available for download – that is the 10th major release of BizTalk Server – bringing several new capabilities like: Support for the latest platform versions: Windows Server 2016, SQL Server 2016, Office 2016 and Visual Studio 2015 SQL Server […]
Blog Post by: Sandro Pereira
Take a moment and think about the best manager that you’ve had. I’ll wait. Now, think about the worst manager you’ve had. What characteristics separate the two? It’s said that people don’t leave companies, they leave managers. Sure, that happens…. Read More ›
Blog Post by: Richard Seroter
After I loaded a BizTalk project to make some changes, I discovered that the BizTalk Project Template was overwritten.
I thought this was a bug and reported it.
I was sending a message from the Logic App to BizTalk.
I used the JSON Schema wizard and used the default setting. Root
, for the Root element.
There was a failure executing the receive pipeline: "CRMDemo.ReceivePipeline1, CRMDemo, Version=1.0.0.0, Culture=neutral, PublicKeyToken=17c282d81ae800e3" Source: "XML validator" Receive Port: "CRMReceivePort" URI: "/GetCRMAccount/Service1.svc" Reason: The XML Validator failed to validate. Details: The element 'Root' in namespace 'http://CRMDemo.JSONSchema1' has invalid child element 'id'. List of possible elements expected: 'body'..
I looked at the message body from suspended message
{"id":"94bf6bf8-4a96-e611-80ea-c4346bdc7221","name":"Silly Goose two","phone":"748-852-1256"}
There wasn’t a body
node. 💡
I then checked the source from the Logic App
{ "Send_message": { "inputs": { "body": { "id": "@{triggerBody()?['accountid']}", "name": "@{triggerBody()?['name']}", "phone": "@{triggerBody()?['telephone1']}" }, "host": { "api": { "runtimeUrl": "https://logic-apis-northcentralus.azure-apim.net/apim/biztalk" }, "connection": { "name": "@parameters('$connections')['biztalk_1']['connectionId']" } }, "method": "post", "path": "/Send", "queries": { "receiveLocationAddress": "http://40.86.103.129/GetCRMAccount/Service1.svc" } }, "runAfter": {}, "type": "ApiConnection" } }
My BizTalk Schema is shown below.
<?xml version="1.0" encoding="utf-16"?> <xs:schema xmlns:b="http://schemas.microsoft.com/BizTalk/2003" attributeFormDefault="unqualified" elementFormDefault="unqualified" targetNamespace="http://CRMDemo.JSONSchema1" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:element name="Root"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="id" type="xs:string" /> <xs:element minOccurs="0" name="name" type="xs:string" /> <xs:element minOccurs="0" name="phone" type="xs:string" /> </xs:sequence> </xs:complexType> </xs:element> </xs:schema>
Finally it came to me. 😳
I needed use the body
node as the name of the Root element in my schema. That solved the problem.
The BizTalk Documenter has been compiled and refactored for .Net 4.6 and BizTalk 2016 Tap release.
This will only work for BizTalk 2016.
RSS feed for comments on this post. TrackBack URI
xon Olympus, een snelgroeiend ICT-dienstenbedrijf uit Utrecht dat zich specialiseert in de integratie van systemen en applicaties op het Microsoft-platform, fuseert met zijn Belgische branchegenoot Codit. Het fusiebedrijf gaat verder onder de naam Codit.
Blog Post by: AxonOlympus