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

Logic Apps and EDI (III)

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

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

In this post I go to explain how to modify our Agreement, to allow receive from CompanyA, messages of type INVOICE_99B_D.

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.

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.

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.

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.

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

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.