BizTalk tools available on GitHub

 

In some of the articles I wrote, I published part of the tools I and my team use in the integration projects developed with BizTalk Server.

These tools are available on CodePlex, but as many of you know, next December 15, CodePlex will be shut down, so we decided to make our work available on GitHub.

 

BizTalk Deployment Utility (BizTalkDiff)

BizTalk Deployment Utility is a simple tool allows you to compare two systems based on BizTalk Server and align environments by copying specific ports from a source system to a target system.

With this application you can check the existance of applications, receive ports, receive locations, send ports and send port groups, and decide to create specific objects on the target system. It is a kind of BizTalk Diff.

 

 

You can now find this tool at https://github.com/pellitteris/BizTalkDiff.

 

BizTalk Password Manager

This little tool allows you to set BizTalk send ports and receive locations passwords. You can use it to create automated scripts during deployment operations.

It is just an example that currently manages the adapter FILE, FTP, SFTP, POP3 and WCF *. Of course you can access the source code in order to manage other kind of adapters.

 

You can now find this tool at https://github.com/pellitteris/BizTalkPassword.

 

BizTalk Configuration Reports

BizTalk Configuration Reporting allows you to view and document the current configuration of BizTalk Server in terms of receive ports, send ports and orchestrations.

This tool consists of a database to be placed in the same database instance of BizTalkMgmtDb and a some reports to be installed in an instance of Microsoft SQL Server Reporting Services (SSRS).

The reports, being based on SSRS, display data in real time and allow export in different formats such as Microsoft Word, PDF, Microsoft Excel, TIFF, etc.

This allow to have documentation always up to date.

 

 

You can now find this tool at https://github.com/pellitteris/BizTalkConfigReports.

 

Advertisements

BizTalk Deployment Utility (BizTalk Diff) is growing

Thanks to my team that helps me face increasingly difficult missions in my work, the BizTalk Diff grows by inserting new features. In particular, I want to thank Matteo Chieli who did much of the work.

You can find the updated version of the tool at https://github.com/pellitteris/BizTalkDiff/ address.

In Particular, it is now possible to apply some changes in block to the configuration:


You can set the following settings:

Change send port host and transport options (Retry Count, Retry Interval and Enable Routing for failed messages)


Change receive location host


Change orchestration host


Change WCF based send port timeouts


Change WCF based receive location timeouts


Integrate SQL Server with Power BI

One of the most common scenarios for those who use Microsoft technologies and intend to publish its data into Power BI typically use SQL Server as a data source.

Power BI provides several ways to access SQL Server information, among them there are some that need simple configurations and others that require developments. Below we summarize the different possibilities that you have available:

Power BI has a wide range of connector to access to several types of data sources, these include a connector for Azure SQL Database and one for Azure SQL Data Warehouse.

To access to a SQL Server, whether it be an instance of Azure IaaS or On-Premises instance you can use Power BI Gateways. There is a Power BI Enterprise Gateway for enterprise deployments and a Power BI Personal Gateway for personal use. You can download it directly from Power BI portal and install in a server near your SQL Server.

For additional information about Power BI Gateways refer to https://powerbi.microsoft.com/en-us/gateway/.

Both these features support direct query option, that is SQL Server is queried when the user accesses the report or dashboard. Typically you prefer to schedule the frequency of the update. You can schedule updates every few minutes.

If you want to get a dashboard that receives continuous updates getting the effect of a live dashboard you need to perform simple developments.

To update a Power BI dataset you can use different Microsoft Azure functionality:

Windows Azure Event Hubs + Windows Azure Stream Analytics

Power BI REST API

Both techniques need configuration on Microsoft Azure side and a Windows service that resides in the same network of your SQL Server that is responsible for reading the information and send them to the Cloud.

This approach allows you to make updates with a frequency close to the second.

Use Windows Azure Event Hubs and Microsoft Azure Stream Analytics is simpler and the Power BI dataset is created automatically, but with this technique, you can only insert new information.

The Power BI APIs are a bit more complex but allow several types of operations. For example it is possible to empty the dataset before inserting new information.

However, you must manually create the data set.

You can download a Windows service sample at the address http://db2powerbi.codeplex.com/. This simple solution it able to use both techniques. It is enough to apply a configuration to the QueryConfig.json file and write a query file. The project includes a console (DbToP Svc.Power Bi.UI.exe) that allows you to create the dataset and retrieve its id (required in the configuration file).

Below is an example of Query Config.json file.

As I said, before starting the service you need to apply some Microsoft Azure side configurations.

You can follow the article https://azure.microsoft.com/en-us/documentation/articles/stream-analytics-power-bi-dashboard/ to configure Windows Azure Event Hubs and a Stream Analytics Job.

You have to follow the article https://powerbi.microsoft.com/en-us/documentation/powerbi-developer-register-a-client-app/ before use Power BI REST API.

Integration Dojo – SAP NetWeaver Installation

Nino Crudele's Blog

These are me personal notes about SAP and what I think is important and essential to know about it.

SAP NetWeaver installation, below in case I need to install a new SAP environment for personal integration tests and study purpose, I will keep track and update it.

To find the package installation the best and easy way is using the interactive list here and had a look for SAP NetWeaver AS ABAP 7.03 SP04 64-bit Trial but you can find all SAP versions you need here.
To download the package and software you need to create  a SAP account before.

Click on Trial and complete the form in order to receive the Trial version, you will receive the email and you will have 48 hours time to download it.

image

I installed the SAP NetWeaver in a Windows 2012 Server and i used a SQL Server 2012 and it works perfectly you…

View original post 749 more words

BizTalk Mapper Extensions UtilityPack for BizTalk Server 2013 Updated to v1.8.0.0

Sandro Pereira BizTalk Blog

Exciting news… Version 1.8.0.0 ofBizTalk Mapper Extensions UtilityPackfor BizTalk Server 2013 is now available!

But before talking about the change-log of this version there is another subject that I want to talk first… This project as two new members that was responsible for all the new functionalities available in this version:

  • Martijn Schiedon, Integration architect at ValueBlue (http://www.valueblue.nl) and a Dutch BizTalk community member.
  • And Salvatore Pellitteri. He is Developer Team Manager in Microsys Srl. He works on integration application projects using BizTalk Server and on business intelligence projects using SQL Server platform. He works with BizTalk Server since the first version and has worked in many big integration project with several Italian enterprise organizations using many technologies like SAP, Oracle, SQL Server, AS400, J.D. Edwards and HL7. Salvatore has his own blog https://pellitterisbiztalkblog.wordpress.com/ on which he shares his experiences.

Here’s the change-log for…

View original post 718 more words

BizTalk Server 2013 on Windows 2012 can’t access third-party NAS via UNC path

If you have a BizTalk Server 2013 installed on Windows Server 2012 and configure receive or send ports that access to third-party NAS via UNC paths, you may receive the error code 0x80004005.

In this scenario, only one Windows process at a time is able to access to the remote share, the other processes will fail.

Therefore, the problem exists if multiple receive or send ports are configured on different BizTalk hosts.

In addition, if you enable the ports, trying to access the remote share from Windows Explorer you will get the following error:

 

clip_image001

 

The problem is not related to BizTalk layer, but to Windows Server 2012-based or Windows 8-based computer that fail to connect to a third-party file server that supports the SMBv2 file protocol. In fact, you can reproduce the problem following the step below:

 

·         Log on with a first user to Windows Server 2012;

·         Log on with a second user to the same machine;

·         Both users should try to map a network drive specifying the same remote folder;

·         The second user should get the error.

 

At this moment, to allow the ports configured on multiple BizTalk hosts to works fine, you have to disable SMBv2 and SMBv3 protocol forcing the communications on SMBv1.

To do that execute the following commands:

 

 

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi

sc.exe config mrxsmb20 start= disabled

 

 

Additional information on how to enable and disable Server Message Block (SMB) version 2 (SMBv2) and SMB version 3 (SMBv3) on the SMB client and server components, can be found at this address http://support.microsoft.com/kb/2696547.

 

Remember that SMBv1 must be configured in order to works correctly with BizTalk server environments.

By default with SMBv1 are allowed just 50 client connections and 265 server connections. Typically these value are not compatible with integration scenarios.

So you have to modify the following registry settings in order to grow the number of concurrent sessions.

 

Registry Key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

 

Parameter:

MaxCmds (DWORD)

Possible values: 1-65535

Default Value: 50

Example Value: 16384

 

Registry Key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

 

Parameter:

MaxMpxCt (DWORD)

Possible values: 1-65535

Example Value: 4096

 

Parameter:

MaxWorkItems (DWORD)

Possible values: 1-65535

Example Value: 16384 (Should be at least MaxMpxCt * 4)