BizTalk JSON Schema Wizard: Error in JSON Instance File.XMLNodeConverter can only convert JSON that begins with an object

BizTalk JSON Schema Wizard: Error in JSON Instance File.XMLNodeConverter can only convert JSON that begins with an object

This week while trying to use the BizTalk Server 2016 JSON Schema Wizard to generate an XML schema from a specific JSON file to be sent to a Logic App I got the following error:

Error in JSON Instance File.XMLNodeConverter can only convert JSON that begins with an object. Path ‘’, line 1, position 1.

The JSON file had the following format:

[
  {
    "IntID": 208,
    "ItemLogID": 14255826,
    "Step": "IN",
    "BusinessUnit": "TST",
  },
  {
    "IntID": 209,
    "ItemLogID": 14257419,
    "Step": "IN",
    "BusinessUnit": "TST",
  }
]

Basically, I’m trying to send a list of “objects” that in my case are Locks, to be processed.

Cause

The cause of this “problem” is that a JSON array of objects, it may not make sense in a BizTalk Server XML world as Morten la Cour very well written in this forum. At that sentence, I will add: “at it his being done today”. Because with a few improvements could be smarter and support this type of messages.

Why? The BizTalk
JSON Schema Wizard is a simple and “stupid” converter, it will ask only for you
to provide a root node and a namespace that it will add to the XML Schema and
the XML JSON representation because it will require that information to be able
to uniquely identify this type of message.

But it will not understand what is a “not identified” object array because it needs to give it a Record name in the XML equivalent.

So, that means
that it will not support JSON arrays?

No, it will support JSON arrays if you provide a field name to that array, i.e., instead of having:

[
…
]

You should have:

{
   "field name": [
   …
   ]
}

Solution

If you don’t have the control over that JSON message,
you may need to create a custom pipeline component to add or remove this field
name that will identify the array in the XML equivalent message.

If you have control over the structure of the JSON
message the simple way is to modify the structure of the message to include a
field name to identify the array. Lucky it was my case, so I modify the
original structure descrived above to be:

  {
    "locks": [
    {
      "IntID": 208,
      "ItemLogID": 14255826,
      "Step": "IN",
      "BusinessUnit": "TST",
    },
    {
      "IntID": 209,
      "ItemLogID": 14257419,
      "Step": "IN",
      "BusinessUnit": "TST",
    }
  ]
}

Now, if I try to run the BizTalk JSON Schema Wizard
against this message it will be able to create the JSON Schema.

The post BizTalk JSON Schema Wizard: Error in JSON Instance File.XMLNodeConverter can only convert JSON that begins with an object appeared first on SANDRO PEREIRA BIZTALK BLOG.

BizTalk Port Multiplier Tool

BizTalk Port Multiplier Tool

You may all remember Richard Seroter BizTalk SendPort Duplicator tool and how he descrived that frequently during development, and even in production, we have a need to create new BizTalk ports that are virtually identical to an existing one where we just need to change some small configurations like:

  • Address/URI;
  • Send Port Filter criteria;
  • Different pipelines or pipeline components configuration;
  • And so on.

And by default, the only options we have are:

  • Export the application binding files, manually clean the file and change the values; And then import the Binding file again;
  • Or manually recreate the entire port again;

Both options are time-consuming and need a lot of manually work.

And Richard Seroter was, and still is, an amazing lifesaving tool that allows you to duplicate send ports easily, so why a new tool?

“BizTalk Port Multiplier Tool” it has all Richard tool functionalities but is more than a Send Port Duplicator, and that is the reason I decided to create a new tool.

“BizTalk Port Multiplier Tool” is a simple tool that aims to simplify port “cloning” process by allowing you to easily “clone or duplicate” any existing port: Receive Port or Send Port.

  • Send Ports are easy, you only need to give a different name to the port, and you can clone it;

Devscope BizTalk Port Multiplier tool Send Ports

  • Receive Ports are tricky because they may contain several Receive Locations and the URI needs to be unique;

Devscope BizTalk Port Multiplier tool

This tool will extend default BizTalk Server capabilities transforming the tedious and sometimes complicate port creation based on an existing one a little simple and easy allowing you to:

  • Create a new Receive Port based on an existing one;
    • It will also export the binding file from that new Receive Port;
  • Create a new Send Port based on an existing one;
    • It will also export the binding file from that new Send Port;
  • Generate different binding files for each environment

Why do I need to “clone” a Receive Port?

Sometimes you also need to create a receive port with similar configurations of an existing one, also changing only few configurations or simple the URI and instead of manually recreating you can have 90% of the process done automatically.

Sometimes is practical, sometimes or in some scenarios it may not work but in most of the cases it will. So it is basically a best-effort operation and not an exact clone because they may have several Receive Locations and the Address/URI needs to be unique. So, you then need to go to each receive location and reconfigure them.

Download

Credits also to my team member at DevScope, Pedro Almeida that collaborated in the development of this tool.

You can download BizTalk Port Multiplier Tool from:
BizTalk Port Multiplier ToolBizTalk Port Multiplier Tool
GitHub

Or from:
BizTalk Port Multiplier ToolBizTalk Port Multiplier Tool
Microsoft | Code Gallery

The post BizTalk Port Multiplier Tool appeared first on SANDRO PEREIRA BIZTALK BLOG.

BizTalk Bindings Exporter Tool

BizTalk Bindings Exporter Tool

Following my commitment with the attendees at Integrate 2019 London and US that shared with me the same headaches and concerns, and following my series of posts about “BizTalk Bindings Exportation” published on BizTalk360 blog. I’m happy to announce the birth of a new BizTalk Server tool: BizTalk Bindings Exporter Tool.

BizTalk Binding Exporter Tool” is a simple tool which will suppress the absence of advanced binding file generation capabilities in the BizTalk Server Administration Console allowing you to generate and export a binding file from BizTalk Applications in an intuitive and easy way.

Exporting a BizTalk Server Application binding is, at first sight, a simple and quick task that can be done using the BizTalk Server Administration Console:

  • Click Start, click All Programs, click Microsoft BizTalk Server 20xx, and then click BizTalk Server Administration
  • In the console tree, expand BizTalk Server Administration, expand the BizTalk Group, and then expand Applications
  • Right-click the application whose bindings you want to export, point to Export, and then click Bindings…
  • On the Export Bindings page, in Export to file, type the absolute path of the .xml file to which to export the bindings
  • Ensure that Export all bindings from the current application option is selected, and then click OK

But even in simple tasks, we may encounter challenges that require us to perform some monotonous and boring manual operations that consume some of our precious time and are always subject to failures. Because out-of-the-box BizTalk Administration Console doesn’t allow you to:

  • Export a Binding file of a specif Receive Port or list of Receive Ports;
  • Export a Binding file of a specif Send Port or list of Send Ports;
  • Export a Binding file of a specif Assembly or list of Assemblies;

And these are just a few scenarios. You can only fully Export the binding files of an entire application which will lead you sometimes an extensive and fallible manual work to clean the binding files.

Normally the binding exportation starts in development, but we also will need to generate the same bindings for other environments like production and for that we normally need to open the binding file and replace/fix the differences for each different environment… which is normally a tedious operation. What we need to replace is mainly:

  • the URI’s: it should be fixed, but it is not mandatory. If you know what you are doing, you can fix them directly on the environment after you import the Binding.
  • the host instances: not mandatory, if you have the same host and host instances names across all your different environments (as best practices will tell you to do).
  • the NT Group Name associated in the Services (Orchestrations): according to securities best practices you shouldn’t use the same BizTalk Groups in different environments, so in this case, if you follow this best practices, you need to change these parameters in your binding file.

Normally, everyone changes the URI’s but neglecting the other parameters may be causing problems during the Binding import.

Once again, this tool will extend default BizTalk Server capabilities transforming the tedious and sometimes complicate binding generation a little simple and easy.

DevScope BizTalk Bindings Exporter Tool

You just need to specify the connection string to the BizTalk Management database (BizTalkMgmtDb)

DevScope BizTalk Bindings Exporter Tool

And this tool allows you to generate and export binding files with the following capabilities:

  • Export binding(s) file(s) for an entire Application or a list of Applications;
  • Export binding(s) file(s) from a specify Assembly or list of Assemblies;
  • Export binding(s) file(s) from a Receive Port or list of Receive Ports;
  • Export binding(s) file(s) from a Send Port or list of Send Ports;
  • Or Generate different binding files for each environment if you create an Excel File with the mapping for each environment ;

Credits also to my team member at DevScope, Pedro Almeida that collaborated in the development of this tool.

You can download BizTalk Bindings Exporter Tool from:
BizTalk Bindings Exporter ToolBizTalk Bindings Exporter Tool
GitHub

Or from:
BizTalk Bindings Exporter ToolBizTalk Bindings Exporter Tool
Microsoft | Code Gallery

The post BizTalk Bindings Exporter Tool appeared first on SANDRO PEREIRA BIZTALK BLOG.

How to Expose Microsoft Flow thru Azure API Management

How to Expose Microsoft Flow thru Azure API Management

Recently on Serveless360, a community blog that I contribute, I explain how you able to expose an Azure Logic App as an API using Azure API Management (APIM) you can see more details about it here: How to Expose and protect Logic App using Azure API Management (Part 1) – Exposing the Logic App. Today’s question is: Can we do the same with Microsoft Flow? Can we expose a Microsoft Flow that exposes an HTTP endpoint as an API on APIM?

And the short answer is… yes yes! It not as easier as Logic Apps because you don’t have a direct and seamless way to do it, but it can manually be done. And the goal of this blog post is explained to you how to accomplish that.

What is Azure API Management?

Is not the goal of this blog post but for you to be contextualized, if you are not familiar with APIM, in a simple way, Azure API Management is a fully managed service that enables customers to publish, secure, transform, maintain, and monitor APIs.

And it will allow you in a matter of a few clicks in the Azure Portal, most of the times, for you to create an API façade that acts as a “front door” through which external and internal applications can access data or business logic implemented by your custom-built backend services, running on Azure, for example, Logic Apps, App Services, or other many services or running on-premises in your organization. The APIM then will be able to handle all the tasks involved in mediating API calls, like request authentication and authorization, rate limit and quota enforcement, request and response transformation, logging and tracing, and/or API version management.

Azure API Management definition

APIM is made up of the following components:

  • The API gateway is the endpoint that:
    • Accepts API calls and routes them to your backends.
    • Verifies API keys, JWT tokens, certificates, and other credentials.
    • Enforces usage quotas and rate limits.
    • Transforms your API on the fly without code modifications.
    • Caches backend responses were set up.
    • Logs call metadata for analytics purposes.
  • The Azure portal (old Publisher Portal) is the administrative interface where you set up your API program. Use it to:
    • Define or import API schema.
    • Package APIs into products.
    • Set up policies like quotas or transformations on the APIs.
    • Get insights from analytics.
    • Manage users.
  • The Developer portal serves as the main web presence for developers, where they can:
    • Read API documentation.
    • Try out an API via the interactive console.
    • Create an account and subscribe to get API keys.
    • Access analytics on their usage.

Note: in this blog post, I will not explain how you create an API Management resource on Azure.

Exposing a Microsoft Flow on Azure API Management

Triggered using an HTTP based trigger

The important thing, it needs to be triggered using an HTTP based trigger like the Request trigger.

Like Logic Apps, you can only expose a Microsoft Flow that is triggered using an HTTP based trigger like the Request trigger. Basically, that exposes an HTTP endpoint, on your APIM.

Exposing Microsoft Flow on Azure API Management

I told earlier that exposing a Microsoft Flow, it is not as easier as Logic Apps because you don’t have a direct and seamless way to do it.

The Microsoft APIM team has done a very good job and they created an intuitive and quite easy experience that quickly allows developers or administrators to add new APIs to APIM based on an Azure Logic Apps, if you try to add a new API you will get a “wizard” that you can actually choose to import a Logic App, and it will do everything for you:

Azure API Management Add Logic App

So, for us to replicate the “Add Logic App” wizard and accomplish the goal of exposing a Flow on APIM we need to:

  • First, we need to access to our Flow by accessing the Flow portal: https://flow.microsoft.com/ and sign in with your account
  • In flow.microsoft.com, select My flows in the top navigation bar, and from the list of Flows, choose the flow you want to expose on APIM and select the Edit button.

Microsoft Flow Edit a Flow

  • On the Flow Designer (or editor) click on top of the HTTP trigger to expand it and copy the HTTP POST URL property

Microsoft Flow Edit a Flow HTTP Trigger HTTP POST URL

We will need that URL in order to expose it in APIM.

Now that we have our Flow URL we can go ahead and start configuring our APIM:

  • Access to your APIM on the Azure Portal (old Publisher Portal that is now built-in inside the Azure Portal;
  • And on the left menu, under API Management section, click the API option

Azure API Management Azure Portal

  • By doing that under the All APIs section you will see the list of all APIs that you are already available, and on the main panel you will find several different options to add a new API to your list:
    • From scratch – Blank API;
    • Export based on an OpenAPI, WADL or WSDL specification;
    • Or based on an Azure Service:
      • Logic App
      • API App
      • Or a Function App
  • In our case, we will be creating from the scratch, so go and press Blank API option

Azure API Management Add Blank API

  • And then let’s fill the creation form like this:
    • On the Display name property give your API a name. I will call it “My Flow Demo”
    • On the Name property, you may change the “internal” name. I will suggest leaving like that: “my-flow-demo”
    • On the Web service URL property, paste the HTTP POST URL that we get from the Flow but only until the “triggers” word – Do not place the full
      • https://{name}.azure.com:443/workflows/{GUID}/triggers
      • You can put the full URL, but in this post, we will try to emulate almost all the steps that the APIM Logic App wizard does
    • On the API URL suffix property, give a prefix to your API, for example: flowdemo
    • On the Products property, you can bind this API to a product at this time or leave it blank. I will set mine as “Started”
    • And finally, press Create

Azure API Management Create Add Blank API

  • What we need to do now is create our “manual-invoke” operation, to do that we need to do:
    • Under our “My Flow Demo” API Design section, click + Add operation button

Azure API Management Create Add Blank API Add operation

    • And:
      • On the Display name property give a name to the operation, I will call it “manual-invoke
        • By the way, it doesn’t need to call this name, once again, we will use it just to emulate the API Logic App wizard behavior
      • On the Name property, leave the default value: “manual-invoke”
      • On the URL property:
        • Set the operation to POST
        • And set the URL like “/manual/paths/invoke”
      • On the Description property, you may give a proper description for the operation, in our case, let’s put: Trigger a run of the Flow.
      • Leave the rest of the configurations, we will deal with them later and go ahead and press Save

Azure API Management Create Add Blank API Add operation

  • Now that we have the basic outline of our operation let’s go ahead and configure it properly. To do that we need to:
    • Select the “manual-invoke” operation and then click on the Frontend edit button

Azure API Management Create Add Blank API operation frontend

    • And from the Frontend panel, select the Request option and them + Add representation button

Azure API Management Create Add Blank API operation frontend reques representation

      • Set the Content type as “application/json”
      • Provide a sample request on the Sample property
      • And in the Definition property, select + New definition
        • This will take your provide sample and generate the schema for you
        • Just give a definition a name on the Definition name property: request-manual

Azure API Management Create Add Blank API operation frontend reques representation New definition

          • And then click Create definition button
      • Go ahead and press Save once again
    • Now let’s do the same for the Response. Once again, click on the Frontend edit button
    • And from the Frontend panel, select the Responses option and them + Add response button
    • Because my Flow doesn’t return any message back, instead of selecting the normal 200 OK HTTP Status, I will change that to be a 202 Accepted instead. So, on the response type select from the dropdown the 202 Accepted status and then press Save.
    • Now that we have our Request and Response defined, the only thing we need to configure our policy properly, remember that in the API URL, we didn’t configure the entire URL. To do that we need to:
      • Select the “manual-invoke” operation and then click on the Inbound processing Policies code editor button

Azure API Management Create Add Blank API operation Inbound processing Policies

      • And in the Inbound policy we need to rewrite the URI, here is a sample of the policy you need to implement
 
<policies>
    <inbound>
        <base />
        <set-method id="apim-generated-policy">POST</set-method>
        <rewrite-uri id="apim-generated-policy" template="/manual/paths/invoke/?api-version=2016-06-01&sp=/triggers/manual/run&sv=1.0&sig=7xX3_XxX57XX-xXXXx-xXXXxXXxx5XXxXXxxxxXXXxx" />
        <set-header id="apim-generated-policy" name="Ocp-Apim-Subscription-Key" exists-action="delete" />
    </inbound>
    <backend>
        <base />
    </backend>
    <outbound>
        <base />
    </outbound>
    <on-error>
        <base />
    </on-error>
</policies>
  • And then press Save.

Note: The only thing we didn’t do that the APIM Logic App wizard does is to create a key/value containing the “sig” property of the URL

Now we are all set to test our API.

Testing the Microsoft Flow exposed in Azure API Management

After all the above steps, the next step is for us to test the Logic App expose as an API on APIM before we give access to our developers, teams, or partners. And the easier way to do that is directly on the Azure Portal.

To do that you need to:

  • Under the API top options menu, select Test option, and in this case, there is only one operation, so automatically is selected;
  • On the Request body section, select Raw option and insert a valid and expected request to be sent to your Microsoft Flow;
  • And finally, press Send.
Azure API Management Test invoke Microsoft Flow

And after that, you will see an expected response from the Microsoft Flow.

Azure API Management Test invoke Microsoft Flow result

And we can check that the Flow was executed.

13-azure-api-management-Test-invoke-Microsoft-Flow-execution

It failed because the payload is incorrect but other that everything is ok. We successfully exposed and trigger the Microsoft Flow from Azure API Management.

The post How to Expose Microsoft Flow thru Azure API Management appeared first on SANDRO PEREIRA BIZTALK BLOG.

New Logic App Inline Code icons are now included in Microsoft Integration (Azure and much more) Stencils Pack v4.0.2 for Visio

New Logic App Inline Code icons are now included in Microsoft Integration (Azure and much more) Stencils Pack v4.0.2 for Visio

Due to personal requests from some members of the community, I decided to release another minor version of my stencils pack that will include the following features:

  • New shapes: new shapes were added to existing modules like:
    • Logic App Inline Code (square – original that you can find in Logic App design)
    • Logic App Inline Code JS (square – original that you can find in Logic App design)
    • Logic App Inline Code (Custom shape version 1)
    • Logic App Inline Code (Custom shape version 2)
    • Secure Message Input
    • Secure Message Output

Visio-Microsoft-Integration-Stencils-Pack-v4.0.2-Logic-app-Inline-Code

Microsoft Integration, Azure, Power Platform, Office 365 and much more Stencils Pack it’s a Visio package that contains fully resizable Visio shapes (symbols/icons) that will help you to visually represent On-premise, Cloud or Hybrid Integration and Enterprise architectures scenarios (BizTalk Server, API Management, Logic Apps, Service Bus, Event Hub…), solutions diagrams and features or systems that use Microsoft Azure and related cloud and on-premises technologies in Visio 2016/2013:

  • BizTalk Server
  • Microsoft Azure
    • Integration
      • Integration Service Environments (ISE)
      • Azure App Service (API Apps, Web Apps, Mobile Apps, and Logic Apps)
      • Event Hubs, Event Grid, Service Bus, …
      • API Management
    • IoT, and Docker
    • Machine Learning, Stream Analytics, Data Factory, Data Pipelines
    • and so on
  • Microsoft Power Platform
    • Microsoft Flow
    • PowerApps
    • Power BI
  • PowerShell
  • Infrastructure, IaaS
  • Office 365
  • And many more…
  • … and now non-related Microsoft technologies like:
    • SAP Stencils
Visio: Microsoft Integration and Azure Stencils Pack

You can download Microsoft Integration, Azure, BAPI, Office 365 and much more Stencils Pack for Visio from:
Microsoft Integration Azure Stencils Pack VisioMicrosoft Integration, Azure, Power Platform, Office 365 and much more Stencils Pack for Visio
GitHub

Or from:
Microsoft Integration Azure Stencils Pack VisioMicrosoft Integration and Azure Stencils Pack for Visio 2016/2013 v4.0.2 (22,6 MB)
Microsoft | TechNet Gallery

The post New Logic App Inline Code icons are now included in Microsoft Integration (Azure and much more) Stencils Pack v4.0.2 for Visio appeared first on SANDRO PEREIRA BIZTALK BLOG.

Thanks! Awarded as Microsoft Azure MVP 2019-2020

Thanks! Awarded as Microsoft Azure MVP 2019-2020

On 1st January 2011, I was awarded for the first time Microsoft Most Value Professional (MVP), back them as a BizTalk Server MVP, joining an amazing worldwide group of technicians and community leaders who actively share their high quality and real-world expertise with other users and Microsoft. And since then I was re-award in:

  • 2012, again as BizTalk Server MVP;
  • From 2013 to 2015, I was rebranded as Microsoft Integration MVP;
  • In 2017, Integration become part of Azure category, so I was awarded for the first time as Azure MVP
  • And in the middle of 2017, I was Award in two categories, Azure and Visio MVP;
  • In 2018, I was rewarded Azure MVP

And today, still with all the same pride, honor and enthusiasm than the first time, I’m delighted to share with you that in July 1st I was renewed as a Microsoft Azure MVP (Microsoft Most Valuable Professional) for one more year.

Sandro-Pereira-Azure-MVP-2019

It is with great pride we announce that Sandro Pereira has been awarded as a Microsoft® Most Valuable Professional (MVP) for 7/1/2019 – 7/1/2020. The Microsoft MVP Award is an annual award that recognizes exceptional technology community leaders worldwide who actively share their high quality, real world expertise with users and Microsoft. All of us at Microsoft recognize and appreciate Sandro’s extraordinary contributions and want to take this opportunity to share our appreciation with you.

With just over 3,000 awardees worldwide, Microsoft MVPs represent a highly select group of experts. MVPs share a deep commitment to community and a willingness to help others. They represent the diversity of today’s technical communities. MVPs are present in over 90 countries, in more than 40 languages, and across numerous Microsoft technologies. MVPs share a passion for technology, a willingness to help others, and a commitment to community. These are the qualities that make MVPs exceptional community leaders. MVPs’ efforts enhance people’s lives and contribute to our industry’s success in many ways. By sharing their knowledge and experiences, and providing objective feedback, they help people solve problems and discover new capabilities every day. MVPs are technology’s best and brightest, and we are honored to welcome Sandro as one of them.

This is my 9th straight year on the MVP Program, an amazing journey, and experience that, again, started in 2011, and that gave me the opportunity, and still does, to travel the world for speaking engagement, share the knowledge, and to meet the most amazing and skilled people in our industry.

As usual, I would like to thank all of you! And special to my wife Fernanda and my three kids: Leonor, Laura, and José. And to all members of my beautiful family. THANKS for all the support during these last years! You guys are my inspiration!

And a special thanks to my MVP Lead Cristina Herrero for all the support, to Microsoft Integration Team and Azure Teams, to all my fellow Microsoft Azure (Integration) MVP’s and to DevScope (my company) and all my coworkers (no names here because all of them are amazing professionals)

It’s a big honor to be in the program and I’m looking forward to another great year!

The post Thanks! Awarded as Microsoft Azure MVP 2019-2020 appeared first on SANDRO PEREIRA BIZTALK BLOG.

New Integration Service Environments (ISE) icon is now included in Microsoft Integration (Azure and much more) Stencils Pack v4.0.1 for Visio

New Integration Service Environments (ISE) icon is now included in Microsoft Integration (Azure and much more) Stencils Pack v4.0.1 for Visio

Microsoft Integration, Azure, Power Platform, Office 365 and much more Stencils Pack it’s a Visio package that contains fully resizable Visio shapes (symbols/icons) that will help you to visually represent On-premise, Cloud or Hybrid Integration and Enterprise architectures scenarios (BizTalk Server, API Management, Logic Apps, Service Bus, Event Hub…), solutions diagrams and features or systems that use Microsoft Azure and related cloud and on-premises technologies in Visio 2016/2013:

  • BizTalk Server
  • Microsoft Azure
    • Integration
      • Integration Service Environments (ISE)
      • Azure App Service (API Apps, Web Apps, Mobile Apps, and Logic Apps)
      • Event Hubs, Event Grid, Service Bus, …
      • API Management
    • IoT, and Docker
    • Machine Learning, Stream Analytics, Data Factory, Data Pipelines
    • and so on
  • Microsoft Power Platform
    • Microsoft Flow
    • PowerApps
    • Power BI
  • PowerShell
  • Infrastructure, IaaS
  • Office 365
  • And many more…
  • … and now non-related Microsoft technologies like:
    • SAP Stencils
Visio: Microsoft Integration and Azure Stencils Pack

What’s new in this version?

  • New shapes: new shapes were added to existing modules like:
    • Integration Service Environments (ISE)
    • Logic Apps Custom Connector
    • Relays
Microsoft Integration Service Environments (ISE)

You can download Microsoft Integration, Azure, BAPI, Office 365 and much more Stencils Pack for Visio from:
Microsoft Integration Azure Stencils Pack VisioMicrosoft Integration, Azure, Power Platform, Office 365 and much more Stencils Pack for Visio (18,6 MB)
GitHub

Or from:
Microsoft Integration Azure Stencils Pack VisioMicrosoft Integration and Azure Stencils Pack for Visio 2016/2013 v4.0.1 (18,6 MB)
Microsoft | TechNet Gallery

The post New Integration Service Environments (ISE) icon is now included in Microsoft Integration (Azure and much more) Stencils Pack v4.0.1 for Visio appeared first on SANDRO PEREIRA BIZTALK BLOG.

INTEGRATE 2019 USA – Redmond | June 24-26, 2019 | BizTalk Server Fast & Loud Part II

INTEGRATE 2019 USA – Redmond | June 24-26, 2019 | BizTalk Server Fast & Loud Part II

INTEGRATE (formerly known BizTalk Summit) is the premier, and maybe the biggest integration conference in the world focused on Microsoft Integration and a must go event for anyone who is working in this area. So, if you missed the chance to attend the London event this year, this is your last chance to meet and interact with the Microsoft Product Group, Microsoft Integration MVP’s and a huge list of attendees that are in fact experts from the field in these areas.

Since the first BizTalk Summit event till today, I’m a constant presence as a speaker at these events, and I had the enormous pleasure to present last time this event happened in USA (2017), that was, in fact, the first time I deliver a session in an event in the USA… and the way I was received and cherished by the attendees was so special that I could not miss this opportunity to come back again! So, I’m thrilled to say that I will be present once again in the INTEGRATE USA event delivering the second part of the session: BizTalk Server Fast & Loud!

Also, I’m extremely happy to say that for the second time DevScope (my company) will be sponsoring this amazing event!

I receive so many amazing feedbacks about my BizTalk Server Fast & Loud session two years ago, that this year I decided to create this second part, I was a bit nervous in the beginning because I want to keep the good level on the previous session and avoid what usually happens with the sequels in the movies, as a new part is released the quality goes down… and I think I did a good job, at least based on the feedback in London event. Personally, I love this session more than the previous. But at that time, I decide to do this session I did not know, and/or I had not decided that I would be present in the USA this year. So, this is, in fact, a happy coincidence, because the last time the event happened in USA my talk was the first part of this session :), so it makes more sense. But if you were not there you can see the first part of this session here: BizTalk Server Fast & Loud

About my session

Session Name: BizTalk Server Fast & Loud Part II: Optimizing BizTalk

BizTalk Server Fast & Loud Part II: Optimizing BizTalk

Session Overview: Following the success of one of Sandro’s previous presentations at Integrate, Sandro decided to go deep on this hardcore BizTalk topic: Optimizing your BizTalk Server. This session will allow you to gain a better view on how to optimize BizTalk Server for better performance in all phases: your teams proactivity, your code, your environment, and your goals. Once again, this is a very extensive and complex topic and there is no magic formula you can apply to solve all your problems. This presentation will aim to guide you through some of the most important steps, operations, tasks and best practices that you need to do or be aware of, in order to boost the performance of your BizTalk Server projects and that you can adjust or follow according to your needs.

BizTalk Server Fast & Loud Part II: Optimizing BizTalk - Corticeira Amorim

The event will take place between June 24-26, 2019 at Microsoft Campus, Redmond, WA and you are still on time to register for the conference here.

The post INTEGRATE 2019 USA – Redmond | June 24-26, 2019 | BizTalk Server Fast & Loud Part II appeared first on SANDRO PEREIRA BIZTALK BLOG.

BizTalk Server 2020… is coming at the end of CY 2019

BizTalk Server 2020… is coming at the end of CY 2019

After once again many speculations and controversy caused in INTEGRATE 2018 London event about the vNext release of BizTalk Server, promptly denied two weeks after the event with a formal announcement from the Microsoft Integration team, finally some excellent news for the Microsoft Integration community and all the clients out there that still consider MSFT Integration Stack the best in the market. Paul Larson announced in his session at INTEGRATE 2019 London event the release of BizTalk Server 2020 to be scheduled for the end of this year.

BizTalk Server 2020

Of course, one of the main reasons for this new version is about Platform Alignment. This new version will support:

  • SQL Server 2019 and SQL Server 2017 (still not sure if SQL Server 2016 will be also supported)
  • Windows Server 2019 and I’m almost sure that Windows Server 2016 will still be supported
  • .NET Framework 4.8
  • Visual Studio 2019
  • And Azure IaaS VMs

What can we expect… more in BizTalk Server 2020 release?

One of the greatest things for customers that are running BizTalk Server Standard Edition is that BizTalk Server 2020 already comes built-in with all BizTalk Server 2016 Feature Pack Features, that means that all these features are now part of the product in all versions:

  • A new set of cloud adapters:
    • Logic Apps adapter: that will allow you to easily connect and easily extend part of your integration with Azure Logic Apps, making it easier to implement robust hybrid solutions;
    • Service Bus adapter: that will allow you to send and receive messages with Azure Service Bus;
    • Event Hubs adapter: that will allow you to send and receive messages with Azure Event Hubs;
    • Office 365 Mail adapter: that will allow you to send and receive messages using Office 365 e-mail;
    • Office 365 Schedule adapter: that will allow you to set and update appointments using Office 365 schedules;
    • Office 365 Contact adapter: that will allow you to define people and groups using Office 365 contacts;
    • Blob Storage adapter: that will allow you to read and write binary files in Azure Blob Storage;
  • API Management connectivity: the availability to publish an Orchestration endpoint directly on Azure API Management;
  • Deployments with VSTS: Application Life cycle Management feature will help you to perform automatic deployments in an improved and easy way using Visual Studio Team System (VSTS);
  • Security features:
    • Transport Layer Security 1.2: TLS 1.2 is now fully supported in BizTalk Server. This includes all the adapters and accelerators. You can also disable SSL, TLS 1.0, and TLS 1.1 in BizTalk Server;
    • SQL Server Encrypted Data: You will be able to read and write to SQL Server always encrypted columns using BizTalk Server WCF-SQL adapter. The ColumnEncryptionSetting binding property is used to enable or disable the functionality to get decrypted/encrypted column values from an Always Encrypted database;
  • BizTalk Database Backup to Blob Storage: the availability to backup BizTalk Server databases, using the default backup job directly to an Azure Blob Storage;
  • Advanced Scheduling: the availability to set up recurrence on BizTalk Server receive locations with greater precision using times zones, months, weeks, and days;
  • Application Insights: the availability to send BizTalk Server tracking data to Application Insights for extensible analytics, to understand performance and usage of BizTalk Server;
  • Power BI operational data feed in BizTalk Server: Analyze and report BizTalk Server tracking data template, for use with Power Bi visualizations and dashboards;
  • Tracking data to Azure: the availability to send BizTalk tracking data to Azure Application Insights or Event Hubs
  • BizTalk Server Rest Management API’s: you will able to manage BizTalk Server environments using standard RESTful Web Services APIs. You will have now available REST-based API for pretty much for any management activities like retrieving Applications, Hosts, Send Ports, Receive Ports, Receive Locations, Orchestrations, Schemas, Maps, EDI specific things like Agreements, Batches, Parties, Policies, and so on.

But you may expect some small improvements like:

  • Administration (read-only): New set of privileged to access to the BizTalk Server Administration Console by allowing you to restrict unprivileged administrators to viewing existing configurations
  • Enterprise Single Sign-On 2020
  • and others not publicly available yet… let’s wait.

Along BizTalk Server 2020, we will also have a new version of Host Integration Server (HIS) with the same platform alignment that BizTalk Server but also with:

  • IBM platform alignment:
    • IBM z/OS 2.3
    • IBM I V7R3
    • IBM MQ 9
    • IBM CICS 5.4
    • IBM IMS V15
    • IBM BD2 V12
  • Enterprise Single Sign-On 2020
  • Software Development Kit

With this release, Microsoft continues to deliver a mature, reliable and stable integration server that honors the trust of the thousands of customers who run their mission-critical business processes on BizTalk Server.

The post BizTalk Server 2020… is coming at the end of CY 2019 appeared first on SANDRO PEREIRA BIZTALK BLOG.