Friday, September 01, 2017

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

Wednesday, August 09, 2017

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.

Wednesday, August 02, 2017

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

Monday, July 31, 2017

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.

Thursday, July 27, 2017

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.

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