Monday, July 03, 2017

Tracing SAP Adapter

When we have problems with the SAP Adapter, is easy to turn on tracing.

We need only add in our connection URI the RfcSdkTrace parameter and set to true.

Adding this parameter, the adapter traces will be sent to system32 folder, with a minimum trace level.

If you need to send the traces to other directory, you have to add RFC_TRACE_DIR environment variable and set the value of the desired output folder.

Also, if you need traces more detailed, you have to add RFC_TRACE environment variable and set it to 1 or 2. By default and if we don't add this variable, the value is 0 that means tracing level is bare minimum. The 2 value is the more detailed tracing level.

For more information, check this documentation.

Wednesday, June 14, 2017

Getting your BizTalk environment software versions with SQL and PowerShell

Here is simple PowerShell ans SQL scripts, to get the software version easily of your BizTalk software environment:

New Blog about BizTalk "Roving Integrators"

I am working with my friend Mariano Robles on a new Blog called "Roving Integrators", about integration technologies.

There are now few articles, but some of them are very interesting, for example the series about BizTalk Server Logic Apps adapter (first article, second article) or the article about the new BizTalk Management REST APIs included in the last feature update.

We will include more interesting articles ...


Wednesday, May 24, 2017

Considerations when you deploy BizTalk360

When you go to deploy a BizTalk360 solution, you should take into account these requirements or steps.


Wednesday, May 17, 2017

Logic Apps and EDI (V)

This post continues the Logic Apps and EDI series of post, that I began weeks ago:

In this post I go to explain how monitor and tracking B2B scenarios using OMS.

Monday, May 08, 2017

Creating your first Logic App Connector

In this post I will explain, how to implement a simple Connector and use it on a Logic App.

Logic Apps and EDI (IV)

This post continues the Logic Apps and EDI series of post, that I began weeks ago:

In this post I go to explain how get the "Good" and the "Bad" decoded messages from EDIFACT Decode Component.

Thursday, April 27, 2017

Logic Apps and EDI (III)

This post continues the Logic Apps and EDI series of post, that I began last week:
In this post I go to explain how to modify our Agreement, to allow receive from CompanyA, messages of type INVOICE_99B_D.

Tuesday, April 25, 2017

Logic Apps and EDI (II)

This post continues the Logic Apps and EDI series of post, that I began last week.

In this post I want to explain, how to manage errors when Resolve EDIFACT Agreement doesn't found the agreement or any other error.

Monday, April 24, 2017

Global Azure and Integration Bootcamps 2017

Last month I was speaking about Logic Apps on the last two great events.

First was on Saturday 25th March at Madrid, Global Integration Bootcamp, where I talked about Serverless, Logic Apps and Enterprise Integration Pack and the similarities between BizTalk and the PaaS (API Management, Service Bus, Azure Functions and Logic Apps). You can see my slides here.

Friday, April 21, 2017

Logic Apps and EDI (I)

When I began to write this post, my first intention was demonstrate how to migrate a BizTalk EDI Application to Logic Apps with Enterprise Integration Pack, but then I thought to begin with a simple scenario.

I took a sample EDI application in BizTalk from other post (see https://abhijitmahato.wordpress.com/category/biztalk-edi/) and try to implement the same with Logic Apps and Enterprise Integration Pack.

Sunday, April 16, 2017

Versioning Logic Apps feature

Now in Logic Apps, you can see a list of all the versions of your Logic App. Before, Logic Apps supported storing only the previous versions of a Logic App every time you save it, but now you can see all the versions.

This is a great feature to quick rollback a production Logic App to a previous version, if there are any problems when you deploy your last version.

Wednesday, April 12, 2017

Tracked properties on Logic Apps and queries on Log Search or OMS

In our Logic App, we can add tracked properties onto different actions to track our custom data in diagnostics data.

Why we need to track properties? Because it can be very useful to search diagnostics data by custom values (e.g. The order's customer identifier).

Friday, April 07, 2017

Automated Testing Logic Apps with SpecFlow (I)

I start this series of post, talking about how to test our Logic Apps with SpecFlow for Visual Studio 2015. This week I have attended the event "Automated Testing with Logic Apps and Specflow" by Michael Stephenson and I will put in practice some of the ideas that Michael Stephenson talked in that event.

Thursday, April 06, 2017

Deploy or Re-GAC

If we want to update a BizTalk application, sometimes we can only Re-GACing our DLLs instead of redeploy. Obviously, in production environments is recommended to redeploy, but in development environments we can save time just ReGACing.

Wednesday, April 05, 2017

Deconstructing my GIB2017 Demo

Last Saturday, I participated as speaker at Global Integration Bootcamp 2017 at Madrid. You can find the slides of the event at Kabel's Blog.

Monday, March 06, 2017

Global Integration Bootcamp next March 25th 2017


Global Integration Bootcamp will be next March 25th, the first Integration Bootcamp with Microsoft technology held in Spain.

The event will be at Madrid. More info at http://www.kabel.es/globalintegrationbootcamp2017

"EDIFACT Fallback Settings" on Enterprise Integration Pack for Logic Apps

In the new Enterprise Integration Pack for Logic Apps, creating new EDI scenarios, they do not support "EDIFACT Fallback Settings" as there was in BizTalk. This functionality allows when BizTalk has not determined the agreement, apply a default agreement. I have added this suggestion to feedback.azure.com: EDIFACT Fallback Settings suggestion