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.