Connect to your on-premises SAP system from Azure Logic Apps (III)

In this post, we will invoke directly to a RFC on our on-premises SAP from our Logic App. This post continues the series of SAP Connector for Azure Logic Apps.

Connect to your on-premises SAP system from Azure Logic Apps (II)

In this post, we will see how to connect from an Azure Logic App to SAP and get the schemas of the different operations from SAP System. This post continues the series of SAP Connector for Azure Logic Apps.

Connect to your on-premises SAP system from Azure Logic Apps (I)

In this blog post, I will share how we can expose and consume SAP functionality with Logic Apps, with the SAP ERP Central Component (ECC) connector.

Playing with Persistence Points in Biztalk Orchestrations

Today I want to share how BizTalk uses the persistence points and what to expect when an orchestration is suspended and we resume it.

Logic Apps and EDI (VII). Problems developing a PRO solution

This post is about the problems that I found developing a real solution for a customer.

BizTalk Maps - Using Recursive XSLT template to simulate FOR clause

Recently, I was resolving an MSDN forum question that needs to split an input String to String destination nodes with maximum 80 length.

The problem was, how to generate N destination nodes with only one input node splitting the string in fixed length strings.

How to deploy with RM template the Azure Functions Connection Strings

This post explain how to deploy connection strings for our Azure Functions with an Azure Resource Manager template.

"ORA-12154: TNS:could not resolve the connect identifier specified" from Visual Studio or BizTalk

Few days ago, testing my BizTalk solution on my local environment, I get all the time the same error: "ORA-12154: TNS:could not resolve the connect identifier specified"

Copy any message to a single node on destination message

This example is to copy any input message, the whole XML into a single node on a destination typed message.

BizTalk 2013 R2 Orphaned BizTalk DTA service instances are not removed

In one of our BizTalk 2013 R2 environments, after running Message Box Viewer, a warning was reported: "DTA Orphaned Instances (Incompleted Instances in DTA but not in Msgbox). 2 (Large number can impact DTA Size and so perfs) - one possible cause is described in KB 978796 - Contact Microsoft CSS for more info !"

Logic Apps and EDI (VI)

Continuing with my series about Logic Apps and EDI, today I will start a "sub-series" about how to use PowerShell and the API Rest, to deploy EDI artifacts to our Enterprise Integration Account.

Large Data Growth In Biztalk360 Database

Recently in one of our BizTalk360 deployments, the database grow fast, even that we have configured the Purging (Settings > BizTalk360 Health > Data Purging).

BizTalk360 don't send e-mail notifications

Recently we configured a BizTalk360 and in our environment, alerts/notification aren’t being sent.

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.

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 ...

Considerations when you deploy BizTalk360

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

Logic Apps and EDI (V)

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

• Logic Apps and EDI (I)
• Logic Apps and EDI (II)
• Logic Apps and EDI (III)
• Logic Apps and EDI (IV)

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

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:

• Logic Apps and EDI (I)
• Logic Apps and EDI (II)
• Logic Apps and EDI (III)

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