Posts Tagged ‘BizTalk’

This next posts will focus on optimizing some BizTalk Server 2013 R2 configurations. The following recommendations can be used to increase BizTalk Server performance or just to make the platform more resilient to failures. The optimizations listed in this topic are applied after BizTalk Server has been installed and configured.

Configure host and Host instances

One of the task that we need to do in all our new BizTalk environment over and over again is creating and configuring the Host, Host Instances and of course the adapter handlers.

BizTalk Server provides great flexibility for addressing high availability, because you can strategically dedicate logical hosts to run specific areas of functionality such as receiving messages, sending messages or processing orchestrations.
By default the BizTalk configuration will create two BizTalk Host and Host Instances:

  • BizTalkServerApplication: This is the default Host and Host Instance created during configuration that will do all the work on the BizTalk Server, i.e. is the default send and receive handler for all installed adapters (other than HTTP, WCF (BasicHttp, CustomIsolated, WebHttp and WSHttp) and SOAP Receive Handlers), and is also used for processing orchestration and tracking.

BizTalk-Server-2013-R2-BizTalkServerApplication-Host

  • BizTalkServerIsolatedHost: The logical container for HTTP, WCF (BasicHttp, CustomIsolated, WebHttp and WSHttp) and SOAP Receive Handlers.

BizTalk-Server-2013-R2-BizTalkServerIsolatedHost-Host

Although a single BizTalk Host can contain items that receive, send, and process messages, it is considered a best practice to create different hosts for each function to create security boundaries and for easier management and scalability. In particular, we recommend that you use different hosts for processing and for receive/send operations, and that you separate trusted and non-trusted items.

As the official documentation specify, in addition to the high availability aspects of the host instance configuration, you should separate sending, receiving, processing, and tracking functionality into multiple hosts. This provides flexibility when configuring the workload in your BizTalk group and is the primary means of distributing processing across a BizTalk group.

This also allows you to stop one host without affecting other hosts. For example, you may want to stop sending messages to let them queue up in the MessageBox database, while still allowing the inbound receiving of messages to occur.

Separating host instances by functionality also provides some of the following benefits:

  • Each host instance has its own set of resources such as memory, handles, and threads in the .NET thread pool.
  • Multiple BizTalk Hosts will also reduce contention on the MessageBox database host queue tables since each host is assigned its own work queue tables in the MessageBox database.
  • Throttling is implemented in BizTalk Server at the host level. This allows you to set different throttling characteristics for each host.
  • Security is implemented at the host level; each host runs under a discrete Windows identity.

However this also may bring some potential drawbacks if too many host instances are created because each host instance is a Windows service (BTSNTSvc.exe or BTSNTSvc64.exe), which generates additional load against the MessageBox database and consumes computer resources (such as CPU, memory, threads), so you need to be careful.

The following figure will provide you with a general overview of the relationship between servers, hosts and host instances, however is not intended to be the best practices. This architecture will depend from many factors and will change from client to client:

BizTalk-Server-2013-R2-Host-and-Host-Instances

Normally we read that we need to create at least 4 host instances:

  • Sending
  • Receiving
  • Processing
  • And tracking

but that’s not absolutely true because, at least since BizTalk Server is supported in 64 bits, we typically use 64-bits versions and in this case we also need to create at least one Host Instance that will run on 32-bits because FTP adapter, SQL adapter, POP3 adapter and MIME Decoder on 64-bit host instances is not supported by the product (http://technet.microsoft.com/en-us/library/aa560166.aspx)

We can define that one of the best practices for hosts and host instances is the following:

  • BizTalkServerTrackingHost: A BizTalk Host that hosts tracking is responsible for moving the DTA and BAM tracking data from the MessageBox database to the BizTalk Tracking (DTA) and BAM Primary Import databases.
  • BizTalkServerReceiveHost: This host will be responsible for processing messages after they are picked up in a receive location.
  • BizTalkServerReceive32Host: has the same goal as the previous however this must have the “32-bits only” option select so that we can run the 23-bits adapters.
  • BizTalkServerSendHost: This host will be responsible for processing messages before they are sent out to the send port.
  • BizTalkServerSend32Host: has the same goal as the previous however this must have the “32-bits only” option select so that we can run the 32-bits adapters.
  • BizTalkServerApplication: This host will be responsible for process messages based on the instructions in orchestrations that need to run in 32-bits.
  • BizTalkServerApplication64Host:This host will be responsible for process messages based on the instructions in all or most common orchestrations.

Note: You can create other Application Host if you want to separate process base in some application logic.

You can read more about this topic in more details in my previous post: PowerShell to Configure BizTalk Server Host and Host Instances according to some of the Best Practices or in TechNet Wiki: BizTalk Server Best Practices: Create and Configure BizTalk Server Host and Host Instances.

You can find a simple script to configure Host, Host Instance and Adapter Handlers described earlier in this post optimized for BizTalk Server 2013 R2 (and also 2013) in TechNet Gallery:

Power Mode

The different performance states are dynamically managed by Windows in conjunction with hardware and platform firmware to respond to varying workload requirements. The 3 default power plans exposed by Windows provide varying tradeoffs of performance vs. power consumption. For example, if the High Performance power plan is selected, Windows places the system in the highest performance state and disables the dynamic scaling of performance in response to varying workload levels. Therefore, special care should be taken before setting the power plan to High Performance as this can increase power consumption unnecessarily when the system is underutilized.

In some cases you may experience degraded overall performance on a machine when running with the default (Balanced) power plan. The issue may occur irrespective of platform and may be exhibited on both native and virtual environments. The degraded performance may increase the average response time for some tasks and cause performance issues with CPU-intensive applications

To change a power plan:

  • Press the “Windows key” to switch to the Start screen and type “Power Options” and click in “Power Options” option from the Search menu.

Windows-Server-2012-R2-Power-Options-Menu

  • From the power plan page, choose the High Performance option

Windows-Server-2012-R2-Power-Options-High-Performance

  • Close the Power Option window.

 

Consider setting the ‘text in row’ table option to boost BizTalk Server Performance

SQL Server provides a table option called text in row to declare that the contents of the fields of type text, ntext, or image data whose dimensions are smaller than those of a data page (8Kb) must be stored in a data row. By setting this option on BizTalkMsgBoxDb tables (Parts table, Spool table and DynamicStateInfo Tables), you can increase message throughput when working with small messages which have a small context and orchestrations that have a small persistence size. This makes reading and writing the in-row strings about as fast as reading or writing limited size varchar, nvarchar, or varbinary strings. Similarly, when the values are stored off-row, the Database Engine incurs an additional page read or write.

How to exploit the Text in Row table option in BizTalk Server

The following section explains how and when applying the text in row table option to boost BizTalk performance.

  • Parts Table: When the message size is smaller than the dimensions of a data page that are of 8kb, applying the text in row table option on the Parts table can lead to BizTalk Server performance improvement.
  • Spool Table: When the average size of the message context is less than 8 kb, enabling the text in row table option on the Spool table helps you reduce the number of accesses when reading messages from the MessageBox along with their context. To apply this option to the Spool table, you must eliminate unnecessary context properties and distinguished fields to reduce the size of the message context lower than 8 Kb.
  • DynamicStateInfo Tables: These tables, one for each host, contain a field of type image called imgData that contains binary-serialized orchestration state when they encounter a persistence point during their execution. When the internal state of orchestrations within a host HostA is so small that its size once serialized is less than 8 kb, the text in row technique can successfully be applied to the DynamicStateInfo_HostA table. Therefore we recommend that you keep the internal state of orchestrations as small as possible. This technique can significantly reduce the time that is spent by the XLANG Engine to serialize, persist, de-serialize and restore the internal state of an orchestration in case of persistence point.

See more about this topic in the following resources:

You can use the following settings sample that in your environment:

  • EXEC sp_tableoption N’Spool’, ‘text in row’, ‘6000’
  • EXEC sp_tableoption N’Parts’, ‘text in row’, ‘6000’
Related links

This next posts will focus on optimizing some BizTalk Server 2013 R2 configurations. The following recommendations can be used to increase BizTalk Server performance or just to make the platform more resilient to failures. The optimizations listed in this topic are applied after BizTalk Server has been installed and configured.

Install SSO Configuration Application MMC Snap-In

BizTalk Server leverages the Enterprise Single Sign-On (SSO) capabilities for securely storing critical information such as secure configuration properties (for example, the proxy user ID, and proxy password) for the BizTalk adapters. Therefore, BizTalk Server requires SSO to work properly. BizTalk Server automatically installs SSO on every computer where you install the BizTalk Server runtime.

But it also can keep your own application configuration data in SSO database, let say the usual configurations that we normally keep in a configuration file (“app.config”)). One of the great and useful tool that we normally use for archiving this is a custom tool original created by Richard Seroter, the: SSO Config Data Store Tool.

However since 2009 that Microsoft released a MMC snap-in to tackle this exact issue: SSO Configuration Application MMC Snap-In provides the ability to add and manage applications, add and manage key value pairs in the SSO database, as well as import and export configuration applications so that they can be deployed to different environment.

To install SSO Configuration Application MMC Snap-In you need to:

  • Unzip the SSOConfigurationMMCSnapIn.zip file available in Microsoft page.
  • This file is composed by three zip files, so after unzip the first file you should unzip also the SSOMMCSnapInSetup.zip file.
  • Run as Administrator the setup.exe or SSOMMCSnapInSetup.msi file
  • In the Welcome to the SSO Application Configuration Setup Wizard page, click “Next”

155-BizTalk-Server-2013-R2-SSO-App-Snapin

  • In the Select Installation Folder page:
    • Accept the default installation folder or set another one
    • In the “Install SSO Application for yourself, or for anyone who uses this computer” option, select “Everyone”
    • And click “Next”

156-BizTalk-Server-2013-R2-SSO-App-Snapin

  • In the Enter Company Name page, enter the name of your company and click “Next”

157-BizTalk-Server-2013-R2-SSO-App-Snapin

  • In the Confirm Installation page, click “Next” to install the SSO Application Configuration MMC Snap-In

158-BizTalk-Server-2013-R2-SSO-App-Snapin

  • In the installation Complete page, click “Close”

159-BizTalk-Server-2013-R2-SSO-App-Snapin

However unfortunately this tool will not work properly in BizTalk Server 2013 R2, at least running in Windows Server 2012 R2. At the first sight it seems that everything is working properly but when you try to create a key value pair you will see that nothing happens and no key is created:

160-BizTalk-Server-2013-R2-SSO-App-Snapin

To fix this issue I recompile the SSOMMCSnapIn.dll using the latest version of “Microsoft.EnterpriseSingleSignOn.Interop.dll” available with BizTalk Server 2013 R2 that you can download at Microsoft TechNet Gallery: BizTalk Server 2013 R2: Fix for SSO Configuration Application MMC Snap-In

Update: Notice that this issue it’s also documented here https://support.microsoft.com/kb/2954101 (Known issues in BizTalk Server 2013) and you will find different solutions to solve it.

To solve the issue you just need to overlap the existing SSOMMCSnapIn.dll file, normally present in “C:\Program Files\Common Files\Enterprise Single Sign-On” folder with this version of the file. Now if you try to add a new key value pair everything will work fine.

161-BizTalk-Server-2013-R2-SSO-App-Snapin

Configure BizTalk Jobs History (Microsoft SQL Server Agent job history log)

Have you ever notice that you never have present a log history of the Monitor BizTalk Server job?

170-BizTalk-Server-2013-R2-BizTalk-Jobs-History

The reason why this happens is that BizTalk Server is shipped out with a total of 13 SQL Agent jobs, most of them running each minute, the only exception is the Monitor BizTalk Server job that by default occurs every week on Sunday at 00:00:00.

And to be completely honest there are two problems present:

  • We rarely inspect our environment in the weekend, only in critical situations or customers that have a 25x 7 administration team.
  • By default the Microsoft SQL Server Agent job history log is configure to
    • “Limit size of job history log” with a maximum of 1000 rows
    • And “Maximum job history row per job” with 100 rows

168-BizTalk-Server-2013-R2-BizTalk-Jobs-History

Which means that a few minutes after the Monitor BizTalk Server job run successfully or unsuccessfully, it’s historic is overwritten with the row log historical of the remaining 12 jobs. Therefore never expected to have this historic job on Monday when you arrive to the office.

Because BizTalk Server has 13 Jobs to keep a decent and consistent job history log you should increase the “Limit size of job history log” according to the number of existing jobs in your environment, for example at least 1300 for BizTalk Server environment (100 for each job)

To resize the job history log based on raw size

  • In Object Explorer, connect to an instance of the SQL Server Database Engine, and then expand that instance.
  • Right-click SQL Server Agent, and then click Properties.
  • Select the History page, and then confirm that Limit size of job history logis checked.
  • In the Maximum job history log size box, enter the maximum number of rows the job history log should allow.
  • In the Maximum job history rows per job box, enter the maximum number of job history rows to allow for a job.

169-BizTalk-Server-2013-R2-BizTalk-Jobs-History

To resize the job history log based on time

  • In Object Explorer, connect to an instance of the SQL Server Database Engine, and then expand that instance.
  • Right-click SQL Server Agent, and then click Properties.
  • Select the History page, and then click Automatically remove agent history.
  • Select the appropriate number of Days(s), Week(s), or Month(s).

Force Full Backup BizTalk Server (BizTalkMgmtDb) job

I will not enter in much details in this steep, you can read more about it in my blog at: A different way to Force a Full Backup of the BizTalk Server databases.

The standard way is to use the “BizTalkMgmtDb.dbo.sp_ForceFullBackup” stored procedure. However, and unlike what many people think, this stored procedure does not perform a full backup it only marks internally on BizTalk Server databases that the next time the Backup BizTalk Server job runs it will need to perform a full backup of the data and log files. You really need to be aware of two important things:

  • The Backup BizTalk Server job is the only supported method for backing up the BizTalk Server databases. Use of SQL Server jobs to back up the BizTalk Server databases in a production environment is not supported.
  • You can use the SQL Server methods to backup the BizTalk Server databases only if the SQL Server service is stopped and if all BizTalk Server processes are stopped.

Alternative, to help one of my DBA teams you may create a custom Force Full Backup BizTalk Server job that is composed by two steps:

  • Step 1: Force Full Backup
    • That will call the “BizTalkMgmtDb.dbo.sp_ForceFullBackup” stored procedure
  • Step 2: Backup BizTalk Server
    • That will call the standard Backup BizTalk Server (BizTalkMgmtDb) job

1723-BizTalk-Server-2013-R2-Force-Full-Backup-BizTalk-Server-job

You can download the custom “Force Full Backup BizTalk Server (BizTalkMgmtDb)” Job from Microsoft | TechNet Gallery: Force Full Backup BizTalk Server (BizTalkMgmtDb) Job

Related links

This next posts will focus on optimizing some BizTalk Server 2013 R2 configurations. The following recommendations can be used to increase BizTalk Server performance or just to make the platform more resilient to failures. The optimizations listed in this topic are applied after BizTalk Server has been installed and configured.

Deleting BizTalk backup files

BizTalk Server database databases and their health are very important for a successful BizTalk Server database messaging environment. BizTalk is shipped out with a total of 13 SQL Agent jobs. By default, the following BizTalk jobs aren’t configured and enabled upon installation and the two jobs that needs configuration are the two most important jobs: the “Backup BizTalk Server” and the “DTA Purge and Archive“. This is nothing new and everybody knows!

However what many times we forget is that this two jobs, by default, don’t provide functionalities for deleting backup files that have accumulated over time on our file system and we normally forget to create a “process” or a “job” to accomplish this until is too late. The result of that is… lots of times we just remember when the disks are full and everything stop to work!

You can solve this problem by implementing you custom sp_DeleteBackupHistory or by creating a Maintenance Plan to delete BizTalk Database Backups files.

Implementing a custom sp_DeleteBackupHistory

To implement a custom sp_DeleteBackupHistory you need to:

· Start SQL Server Management Studio, and then connect to the BizTalk Management Database. By default, this database is named BizTalkMgmtDb.

· Click New Query to open a Query Editor window.

· Run the following Transact-SQL script to create the sp_DeleteBackupHistoryAndFiles stored procedure:

CREATE PROCEDURE [dbo].[sp_DeleteBackupHistoryAndFiles] @DaysToKeep smallint = null
AS
BEGIN
   set nocount on
   IF @DaysToKeep IS NULL OR @DaysToKeep <= 1
      RETURN
   /* Only delete full sets
   If a set spans a day in such a way that some items fall into the deleted group and the other does not, do not delete the set */
   DECLARE DeleteBackupFiles CURSOR
   FOR SELECT 'del "' + [BackupFileLocation] + '\' + [BackupFileName] + '"' FROM [adm_BackupHistory]
   WHERE  datediff(dd, [BackupDateTime], getdate()) >= @DaysToKeep
   AND [BackupSetId] NOT IN (SELECT [BackupSetId] FROM [dbo].[adm_BackupHistory] [h2] WHERE [h2].[BackupSetId] = [BackupSetId] AND datediff(dd, [h2].[BackupDateTime], getdate()) < @DaysToKeep)
   DECLARE @cmd varchar(400)
   OPEN DeleteBackupFiles
   FETCH NEXT FROM DeleteBackupFiles INTO @cmd
   WHILE (@@fetch_status <> -1)
   BEGIN
      IF (@@fetch_status <> -2)
      BEGIN
         EXEC master.dbo.xp_cmdshell @cmd, NO_OUTPUT
         delete from [adm_BackupHistory] WHERE CURRENT OF DeleteBackupFiles
         print @cmd
      END
      FETCH NEXT FROM DeleteBackupFiles INTO @cmd
   END
   CLOSE DeleteBackupFiles
   DEALLOCATE DeleteBackupFiles
END
GO

· Change the “Clear Backup History” step of the Backup BizTalk Server job so that it calls the sp_DeleteBackupHistoryAndFiles stored procedure instead of the sp_DeleteBackupHistory stored procedure.

However I personally don’t like this approach for two main reasons:

· I avoid to change the scripts of BizTalk standard jobs

· And I also believe that this approach is very limited and doesn’t allow the flexibility that we all want.

Instead I really prefer to take advantage of all features that SQL gives me and create a maintenance plan with a Cleanup task to remove this files.

Implementing a Maintenance Plan to clean BizTalk Database backup’s files

Maintenance Plans allows DBA’s to have flexibility to create a workflow to execute several tasks required to make sure that database are optimized, regularly backed up, and free of inconsistencies. However almost all of these tasks are warranted by the existing BizTalk jobs and I will not use them. The only thing we need is to create a task to clean BizTalk Database backup’s files from our file system.

The main advantage of this approach is that will allow us more flexibility for further changes and we can also use them to other backup’s that we have.

Note: You should ensure that SQL Server Agent service is running because the maintenance plans depend on the Microsoft SQL Server Agent in order to run on a regular basis.

Important Note: this example is created to run in a developer machine, so if you are implementing this approach in production environments make sure to keep the backups for the time you see that fit your requirements or make sure the backups are save in an external storage before you delete this files from the file system.

To create the maintenance check the following post: How to create a Maintenance Plan to delete BizTalk Database Backups files

Pre-allocate space and define auto-growth settings for BizTalk Server databases

By default BizTalk Server databases are defined with small files size and with the parameter “Autogrowth” set to:

  • Increase by 1 MB for database file
  • And by 10% for log file

So what’s the problem with these settings?

Auto growth setting plays an important role in BizTalk configuration for performance reasons, why?

SQL Server database auto-growth is a blocking operation which hinders BizTalk Server database performance. When SQL Server increases the size of a file, it must first initialize the new space before it can be used. This is a blocking operation that involves filling the new space with empty pages.

Therefore it’s recommended to:

  • Set this value (databases auto-growth) to a fixed value of megabytes instead of to a percentage, so SQL server doesn’t waste is resources expanding the data and log files during heavy processing. This is especially true for the MessageBox and Tracking (DTA) databases:
    • In a high throughput BizTalk Server environment, the MessageBox and Tracking databases can significantly increase. If auto-growth is set to a percentage, then auto-growth will be substantial as well.
    • As a guideline for auto-growth, for large files increment should be no larger than 100 MB, for medium-sized files 10 MB, or for small files 1 MB.
    • This should be done so that, if auto-growth occurs, it does so in a measured fashion. This reduces the likelihood of excessive database growth.
  • Also allocate sufficient space for the BizTalk Server databases in advance to minimize the occurrence of database auto-growth.

To define auto-growth and Pre-allocate space for BizTalk Server databases check the following post: Pre-allocate space and define auto-growth settings for BizTalk Server databases

Configure BizTalk Server Windows Services

By default, the “Startup type” propriety of BizTalk Windows Services, Enterprise Single Sign-On Service, Microsoft UDDI Notification Service and the BAMAlerts service are set as “Automatic”, however some of this Windows Services may not start automatically after a system restart, to avoid this behavior you must configure the “Startup type” to “Automatic (Delayed Start)” option in this services:

  • BAMAlerts
  • Microsoft UDDI Notification Service
  • Rule Engine Update Service

The previous version of BizTalk Server also had this problem for:

  • Enterprise Single Sign-On Service
  • BizTalk Service BizTalk Group : BizTalkServerApplication Service

153-BizTalk-Server-2013-R2-Services-automatic

Despite being configured as “Automatic“, the Recovery properties are configured properly to restart the service after failures.

154-BizTalk-Server-2013-R2-Services

To proper configure the BizTalk Services, “Enterprise Single Sign-On Service”, “BAMAlerts” and “Microsoft UDDI Notification Service” Windows service:

  • Press the “Windows key” to switch to the Start screen, type “Services” and click in “View local services” option rom the Search menu.

153-BizTalk-Server-2013-R2-Services-search-menu

  • In the Services window, on the Services (Local) panel select the service for example “BAMAlerts”, right click and select “Properties” option.

153-BizTalk-Server-2013-R2-Services-BamAlerts

  • On the BAMAlerts Properties (Local Computer) window:
    • On the General tab apply the following configuration.
      • Startup type: “Automatic (Delayed Start)”

153-BizTalk-Server-2013-R2-Services-Bam-Alerts-automatic-delay

    • On the Recovery tab, apply the following configuration:
      • First failure: “Restart the Service”
      • Second failure: “Restart the Service”
      • Subsequent failures: “Restart the Service”
      • Reset fail count after … day: 1
      • Restart service after … minutes: 1

153-BizTalk-Server-2013-R2-Services-Bam-Alerts-recovery

    • Click “OK” to apply the changes and close the window
  • Repeat the steps for the other services.

You could and should apply the same Recovery properties configurations for the SQL Server services:

  • SQL Full-text Filter Daemon Launcher
  • SQL Server
  • SQL Server Agent
  • SQL Server Analysis Services
  • SQL Server Browser
  • SQL Server Integration Services 12.0
  • SQL Server Reporting Services
  • SQL Server VSS Writer

By default they are configure as “Take No Action”

171-BizTalk-Server-2013-R2-SQL-Services

And should be configured as:

  • Startup type: “Automatic”
  • and First, Second and Subsequent failures: “Restart the Service”

172-BizTalk-Server-2013-R2-SQL-Services

Install and configure BizTalk Health Monitor V2

BizTalk Health Monitor is a snap-in, basically it’s the same of BizTalk MsgBoxViewer tool that we used monitor a BizTalk environment by gathering all information of a BizTalk group and detecting any issues, non-critical or critical warnings to detect any potential problems in advance, but in this case is integrated more closely with the BizTalk Administration Console to provide BizTalk administrators a quick and complete dashboard of a BizTalk group which will help them monitor the health of their BizTalk platform.

You can download the standalone version of BHM from Microsoft Download Center here: BizTalk Health Monitor

Prerequisites:

  • BizTalk Server 2010, 2013 or 2013 R2 should be installed and configured.

To install and configure BizTalk Health Monitor V2 check the following post: Installing the new BizTalk Health Monitor snap-in on Biztalk Server 2010 or BizTalk Server 2013

Related links

This post is for the BizTalk Server and other Portuguese Community, will be held on January 22, 2015 between 18:45 – 21:50 the III Encontro da comunidade Porto.Data meeting at the Science and Technology Park of University of Porto (UPTEC) in Oporto.

I will be speaking about: Microsoft Azure BizTalk “…”: What we have now and what’s next

Abstract: Azure BizTalk Services is a simple, powerful, and extensible cloud-based integration service. It provides Business-to-Business (B2B), Enterprise Application Integration (EAI) and Hybrid Connections capabilities for delivering cloud and hybrid integration solutions. In this session we will address the current existing features in Cloud Integration using Microsoft Azure BizTalk Services, what to expect from the next releases and what will be the future of the Enterprise Integration in the cloud and on-premises.

III Evento da Comunidade Porto.Data

A comunidade Porto.Data tem como objectivo a partilha de experiências e conhecimento entre os profissionais no Porto.

Na sessão (Microsoft Azure BizTalk “…”- O que temos actualmente, o que aí vem) irei abordar os actuais recursos existentes em Cloud Integration usando Azure BizTalk Services, um serviço de integração baseado na nuvem simples, avançado e extensível que fornece recursos entre empresas (B2B) e integração de aplicativos empresariais (EAI) para proporcionar soluções de integração de nuvem e híbridas. Mas mais importante o que esperar dos próximos lançamentos e qual será o futuro das Integrações Empresariais on-premises e na Cloud (Azure BizTalk MicroServices), um pequeno resumo do que foi apresentado no summit de integração em Redmond pela Microsoft, sendo provavelmente a primeira vez que este tópico será apresentado em Portugal.

O evento irá ocorrer no próximo dia 22 de Janeiro no auditório da UPTEC, pelas 18:45 no Porto. As inscrições são limitadas, não tem custos de inscrição mas é obrigatório que reserve o seu lugar aqui.

Confira a agenda abaixo:

  • 18:45– Abertura e recepção.
  • 19:00 – Community News
  • 19:10 – ” SQL Transparent Data Encryption” – Quilson Antunes (DBA – hmR)
  • 20:10 – Coffee break
  • 20:40 -Microsoft Azure BizTalk “…”: O que temos actualmente, o que ai vem – Sandro Pereira (Microsoft Integration MVP) DevScope
  • 21:40 – Fim do evento
  • 21:45 – Sorteio de prémios
  • 21:50 – Jantar livre

This next posts will focus on installing and configuring BizTalk Server 2013 R2 and additional components

Make sure that you have installed all the latest critical Windows updates from Microsoft and all the prerequisites before you install BizTalk Server 2013 R2.

Configure BizTalk Server SQL Jobs

BizTalk Server databases and their health are very important for a successful BizTalk Server database messaging environment. Although there can be many settings that we can configure, like auto-growth settings for BizTalk Databases (you can learn more here), there are two main things that we must understand and be aware, especially the database administrators:

  • Execution of the BizTalk Server SQL Agent jobs are crucial for managing the BizTalk Server databases and for maintaining optimal performance.
  • The Backup BizTalk Server job is the only supported method to backup the BizTalk Server databases and requires that all of the BizTalk Server databases are configured to use the SQL Server full recovery model.

BizTalk is shipped out with a total of 13 SQL Agent jobs. By default, the following BizTalk jobs aren’t configured and enabled upon installation:

  • Backup BizTalk Server (BizTalkMgmtDb)
  • DTA Purge and Archive (BizTalkDTADb)
  • MessageBox_Message_Cleanup_BizTalkMsgBoxDb

The two jobs that needs configuration are the two most important jobs: the “Backup BizTalk Server” and the “DTA Purge and Archive“. If you want these functionalities you must configure and enabled them.

148-BizTalk-Server-2013-R2-sql-server-agent-jobs

How to configure Backup BizTalk Server (BizTalkMgmtDb)

This is the job provided by Microsoft to do a best practice backup of the BizTalk databases. This job has to be configured for it to be able to run.

This Job consists of four steps:

  • Step 1 – Set Compression Option – Enable or disable compression during backup.
  • Step 2 – BackupFull – Performs full database backups of the BizTalk Server databases.
  • Step 3 – MarkAndBackUpLog – Backs up the BizTalk Server database logs.
  • Step 4 – Clear Backup History – Specifies for how long the backup history is kept.

To configure the Backup BizTalk Server job:

  • Press the “Windows key” to switch to the Start screen, type “SQL Management” or “SQL” and click in “SQL Server Management Studio” option to switch to the Start screen.
  • In Object Explorer panel, connect to the SQL Server instance and expand the server tree.
    • Expand the “SQL Server Agent” node
    • Expand “Jobs” node
  • Double click “Backup BizTalk Server (BizTalkMgmtDb)” to open the job properties window.
  • In the Job Properties – Backup BizTalk Server (BizTalkMgmtDb) dialog box, under “Select a page”, click “Steps”.
  • In the “Job step list”, click in the job you want to edit, and then click “Edit”

149-BizTalk-Server-2013-R2-job-properties-backup-biztalk-server-biztalkmgmtdb

Step 1 – Set Compression Option

Since BizTalk Server 2010, BizTalk Server supports compression for its SQL Server database backups thereby providing some benefits like: less space needed for the backup files, fewer I/O operations for the backup and restore and so on.

This job step calls a stored procedure named sp_SetBackupCompression on the BizTalk management database (BizTalkMgmtDb by default) to set the value on the adm_BackupSettings table.

The original script is:

exec [dbo].[sp_SetBackupCompression] @bCompression = 0 /*0 - Do not use Compression, 1 - Use Compression */

The stored procedure has only one parameter:

  • @bCompression: By default, Set Compression Option is set to 0, which makes backup compression off by default. To change the default, change Set Compression Option to 1.

Change the script to:

exec [dbo].[sp_SetBackupCompression] @bCompression = 1 /*0 - Do not use Compression, 1 - Use Compression */
Step 2 – BackupFull

The BackupFull step is responsible for performing a full backup of the database.

The original script is:

exec [dbo].[sp_BackupAllFull_Schedule] 'd' /* Frequency */, 'BTS' /* Name */, '<destination path>' /* location of backup files */

Where:

  • Frequency: The default is d (daily). This is the recommended setting. Other values include h (hourly), w (weekly), m (monthly), or y (yearly).
  • Name: The default is BTS. The name is used as part of the backup file name.
  • Location of backup files: Replace ‘<destination path>’ with the full path (the path must include the single quotes) to the computer and folder where you want to back up the BizTalk Server databases.

There are also three optional parameters:

  • Force full backup after partial backup failures (@ForceFullBackupAfterPartialSetFailure): The default is 0 when not specified, which means that if a log backup fails, no full backups are done until the next full backup frequency interval is reached.
    • Replace with 1 if you want a full backup to be made whenever a log backup failure occurs.
  • Local time hour for the backup process to run (@BackupHour): The default is NULL when not specified, which means that backup job will not be associated with the time zone of the BizTalk Server computer and will run at midnight UTC time (0000).
    • If you want to backup to run at a particular hour in the time zone of the BizTalk Server computer, specify an integer value from 0 (midnight) to 23 (11 PM) as the local time hour for the BackupHour parameter.
  • Use local time (@UseLocalTime): This is an extra parameter that you can also add that tells the procedure to use local time. The default value is 0.
    • If set to 0, then it uses current UTC time – GETUTCDATE() – 2007-05-04 01:34:11.933
    • If set to 1, then it uses local time – GETDATE() – 2007-05-03 18:34:11.933

Change the script to:

exec [dbo].[sp_BackupAllFull_Schedule] 'd' /* Frequency */, 'BTS' /* Name */, '<your_destination_path>\BizTalk Database\Full' /* location of backup files */
Step 3 – MarkAndBackUpLog

The MarkAndBackupLog step is responsible for marking the logs for backup, and then backing them up.

The original script is:

exec [dbo].[sp_MarkAll] 'BTS' /*  Log mark name */, '<destination path>' /* location of backup files */

Where:

  • @MarkName: Log mark name is part of the naming convention for backup files:
    • <Server Name>_<Database Name>_Log_< Log Mark Name >_<Timestamp>
  • @BackupPath: You must change the destination path this to a valid one. It may be local or a UNC path to another server.

There is also one optional parameter:

  • @UseLocalTime: This is an extra parameter that you can also add that tells the procedure to use local time
    • exec [dbo].[sp_MarkAll] 'BTS' /* Log mark name */,'<destination path>'  /*location of backup files */ , 1
      

Change the script to:

exec [dbo].[sp_MarkAll] 'BTS' /* Log mark name */, '< your_destination_path>\BizTalk Database\Logs' /* location of backup files */
Step 4 – Clear Backup History

The Clear Backup History step is responsible for perform a cleanup of the backup history according for how long a backup should be kept.

The original script clear out the instances in the MarkLog table older than 14 days:

exec [dbo].[sp_DeleteBackupHistory] @DaysToKeep=14

Where:

  • @DaysToKeep: specifies how long the backup history is kept in the Adm_BackupHistory table. Periodically clearing the backup history helps to maintain the Adm_BackupHistory table at an appropriate size.
    • The default value for the DaysToKeep parameter is 14 days.

There is also one optional parameter:

  • @UseLocalTime: This is an extra parameter that you can also add that tells the procedure to use local time
    • exec [dbo].[sp_DeleteBackupHistory] @DaysToKeep=14 , @UseLocalTime =1
      

In this particular case I like to leave the default settings.

Important Note: This job step does not provide functionality for deleting backup files that have accumulated over time. You can solve this problem by implementing you custom sp_DeleteBackupHistory or by creating a Maintenance Plan to delete BizTalk Database Backups files (see more details in BizTalk Server 2013 R2: Installation and Configuration – Optimize the BizTalk Server 2013 R2 environment (Part 17))

After properly configure, to enable the Backup BizTalk Server job:

  • Under “Jobs” in SQL Server Management Studio Object Explorer, Right click in the name of the job “Backup BizTalk Server (BizTalkMgmtDb)” and select “Enable” option.

150--BizTalk-Server-2013-R2-enable-backup-biztalk-server-biztalkmgmtdb

  • In the result screen, click “Close”.

151-BizTalk-Server-2013-R2-enable-backup-biztalk-server-biztalkmgmtdb-result-screen

How to configure DTA Purge and Archive (BizTalkDTADb)

This job automates the archiving of tracked messages and the purging of the BizTalk Tracking database to maintain a healthy system and to keep the tracking data archived for future use.

And it’s configured to call the stored procedure dtasp_BackupAndPurgeTrackingDatabase, which uses the six parameters you must configure in this job:

  • @nLiveHours: Any completed instance older than the (live hours) + (live days) will be deleted along with all associated data. Default is 0 hours.
  • @nLiveDays: Any completed instance older than the (live hours) + (live days) will be deleted along with all associated data. Default interval is 1 day.
  • @nHardDeleteDays: All data (even if incomplete) older than this will be deleted. The time interval specified for HardDeleteDays should be greater than the live window of data. The live window of data is the interval of time for which you want to maintain tracking data in the BizTalk Tracking (BizTalkDTADb) database. Anything older than this interval is eligible to be archived at the next archive and then purged. Default is 30 days.
  • @nvcFolder: Folder in which to put the backup files.
  • @nvcValidatingServer: Server on which validation will be done. NULL value indicates no validation is being done. Default is NULL.
  • @fForceBackup: Default is 0. This is reserved for future use.

To configure the DTA Purge and Archive job:

  • Start by running the “SQL Server Management Studio”, if it is not already open, press the “Windows key” to switch to the Start screen, type “SQL Management” or “SQL” and click in “SQL Server Management Studio” option from the Search menu.
  • In Object Explorer panel, connect to the SQL Server instance and expand the server tree.
    • Expand the “SQL Server Agent” node
    • Expand “Jobs” node
  • Double click “DTA Purge and Archive (BizTalkDTADb)” to open the job properties window.
  • In the Job Properties – DTA Purge and Archive (BizTalkDTADb) dialog box, under “Select a page”, click “Steps”.
  • In the “Job step list”, click Archive and Purge, and then click Edit.

152-BizTalk-Server-2013-R2-job-properties-dta-purge-and-archive-biztalkdtadb

The original script after installing BizTalk looks like this:

exec dtasp_BackupAndPurgeTrackingDatabase
0, --@nLiveHours tinyint, --Any completed instance older than the live hours +live days
1, --@nLiveDays tinyint = 0, --will be deleted along with all associated data
30, --@nHardDeleteDays tinyint = 0, --all data older than this will be deleted.
null, --@nvcFolder nvarchar(1024) = null, --folder for backup files
null, --@nvcValidatingServer sysname = null,
0 --@fForceBackup int = 0 --

This means that:

  • Any completed instance that is older than the live days plus live hours will be deleted, as will any associated data.
  • Any data older than the HardDeleteDays will be deleted.

Normally I use these configurations for production environments:

exec dtasp_BackupAndPurgeTrackingDatabase 0, 10, 20, '<destination path>', null, 0

However in a development machine we don’t need to maintain the archived tracking data, so I just purge it periodically. BizTalk gives you the option to Archive and Purge the tracking data or just simple purge the data without archiving:

  • Change the SQL Statement inside “DTA Purge and Achieve” SQL Job to
declare @dtLastBackup datetime set @dtLastBackup = GetUTCDate() exec dtasp_PurgeTrackingDatabase 1, 0, 7, @dtLastBackup

After properly configure, to enable the Backup BizTalk Server job:

  • Under “Jobs” in SQL Server Management Studio Object Explorer, Right click in the name of the job “DTA Purge and Archive (BizTalkDTADb)” and select “Enable” option.
  • In the result screen, click “Close”.
MessageBox_Message_Cleanup_BizTalkMsgBoxDb

This job removes all messages that are not referenced by any subscribers in the BizTalkMsgBoxDb database tables.

Important Note: This job is also started by the MessageBox_Message_ManageRefCountLog_BizTalkMsgBoxDb job. Therefore, we recommend that you disable this job.

Related links

This next posts will focus on installing and configuring BizTalk Server 2013 R2 and additional components

Make sure that you have installed all the latest critical Windows updates from Microsoft and all the prerequisites before you install BizTalk Server 2013 R2.

Install and Configure the Microsoft BizTalk ESB Toolkit

BizTalk Server includes a powerful publish/subscribe mechanism for messaging applications that works by creating and filling subscriptions, which provides a highly efficient and scalable platform for service-oriented architecture (SOA) applications. The BizTalk ESB Toolkit extends the functionality of BizTalk Server to provide a range of new capabilities focused on building robust, connected, service-oriented applications that incorporate itinerary-based service invocation for lightweight service composition, dynamic resolution of endpoints and maps, Web service and WS-* integration, fault management and reporting, and integration with third-party SOA governance solutions.

The good news is that since BizTalk Server 2013, Microsoft BizTalk ESB Toolkit is integrated with the BizTalk Server setup.

To install the Microsoft BizTalk ESB Toolkit

  • Close any programs you have open. Run the BizTalk Server 2013 R2 installer as Administrator.
  • On the BizTalk Server installation Start page, click “Install Microsoft BizTalk ESB Toolkit”.

133-BizTalk-Server-2013-R2-install-microsoft-biztalk-esb-toolkit

  • On the License Agreement page, select “Yes, I accept the terms of the license agreement” to accept the license agreement and click “Next”

134-BizTalk-Server-2013-R2-BizTalk-ESB-Toolkit-license-agreement

  • On the Component Installation page, select the components you want to install and then click “Next”

135-BizTalk-Server-2013-R2-BizTalk-ESB-Toolkit-component-installation

  • On the Summary page, review installation details and then click “Install”.

136-BizTalk-Server-2013-R2-BizTalk-ESB-Toolkit-summary

  • On the Installation Completed page, click “Finish” to close the installation wizard.

137-BizTalk-Server-2013-R2-BizTalk-ESB-Toolkit-installation-completed

To configure the Microsoft BizTalk ESB Toolkit

  • Press the “Windows key” to switch to the Start screen, type “ESB Configuration tool” or “ESB”, right-click “ESB Configuration tool” option from the Search menu, and then click “Run as Administrator”.
    • Note: You must run the ESB Configuration Tool as an administrator.

138-BizTalk-Server-2013-R2-BizTalk-ESB-Toolkit-esb-configuration-tool

  • In the ESB Configuration Tool page, from the left pane, select “ESB Configuration” and on the right pane:
    • For “Database Server (Defaults)”: specify the database server name where the databases required for BizTalk ESB Toolkit will be created.
    • In the “IIS Web Services (Defaults)” box:
      • Specify the user credentials under which the applications required for BizTalk ESB Toolkit will be created.
      • Also specify the name of the website in IIS under which the applications will be created.
    • The “BizTalk User Groups (Defaults)” box lists the default user groups available for ESB configuration.
      • Leave the default values
      • Important: At this stage, you can click “Apply Configuration” towards the top of the ESB Configuration Tool to configure the Microsoft BizTalk ESB Toolkit with the default settings. However, we will continue to configure the remains steps for a custom configuration.

139-BizTalk-Server-2013-R2-BizTalk-ESB-Toolkit-esb-configuration-tool-wizard

  • From the left pane, expand “Exception Management” and do the following:
    • Click in the “Database” option and on the right pane:
      • Select “Enable Exception Management Database” check box to configure an exception management database.
      • In “Database server name”: specify the database server name where you want to create this database (specify the same database server name that you specify in the ESB Configuration panel under Database Server (Default) option)
      • In “Database name”: leave the default name “EsbExceptionDb”.
      • Leave the default groups

140-BizTalk-Server-2013-R2-BizTalk-ESB-Toolkit-esb-exception-management-database

    • Click on the “Exception Web Services” option from the left pane and on the right pane:
      • Select “Enable Exception Services” check box to configure these services.
      • In “User Account” and “user Account Password”: specify the user account and password under which this services will run.
      • In “BizTalk Isolated Group” – Leave the default value “BizTalk isolated Host Users”
      • In “Website Name”: specify the website where you want to run these services.

141-BizTalk-Server-2013-R2-BizTalk-ESB-Toolkit-esb-exception-management-exception-web-services

  • From the left pane, expand “ESB Core Components”, and do the following:
    • Click the “Itinerary Database” option and on the right pane:
      • Select the “Itinerary Database” check box to configure an itinerary database.
      • In “Database server name”: specify the database server name where you want to create this database (specify the same database server name that you specify in the ESB Configuration panel under Database Server (Default) option)
      • In “Database name”: leave the default name “EsbItineraryDb”.
      • Leave the default groups

142-BizTalk-Server-2013-R2-BizTalk-ESB-Toolkit-esb-esb-core-components-itineray-database

    • Click on the “Core Web Services” option from the left pane and on the right pane:
      • Select the “Enable Core Services” check box to configure these services.
      • In “User Account” and “user Account Password”: specify the user account and password under which this services will run.
      • In “BizTalk Isolated Host Group” – Leave the default value “BizTalk isolated Host Users”
      • In “Website Name”: specify the website where you want to run these services.

143-BizTalk-Server-2013-R2-BizTalk-ESB-Toolkit-esb-esb-core-components-core-web-services

  • From the left pane, click “Configuration” to specify the SSO configuration.
    • If you are installing and configuring the Microsoft BizTalk ESB Toolkit in a single server environment, you should select “File Configuration Source”, which is the default selection. However, if you are setting up a multiple-machine deployment, you must select the “SSO Configuration Source”, and then provide the following values.
      • SSO Server: Name of the SSO server.
      • Configuration file: Click the ellipsis button (…), and then browse to the Esb.config file, which is included in the Microsoft BizTalk ESB Toolkit
      • Application Name: Type a name for the SSO application. For example, ESB Toolkit.
      • Contact Information: Type the appropriate contact information in the following format: someone@example.com.
      • Administrator Group Name: Click the ellipsis button (…), and then browse to the appropriate name
      • User Group Name: Click the ellipsis button (…), and then browse to the appropriate name
    • Select “File Configuration Source”

144-BizTalk-Server-2013-R2-BizTalk-ESB-Toolkit-esb-configuration

  • From the left pane, click “ESB BizTalk Applications” option, from the right pane, do the following:
    • Select the “Enable ESB Core Components in BizTalk Server” check box to create the application in the BizTalk Server Administration console.
      • Select the “Use Default Binding” to bind this application to the default host.
      • Optional you can select the “Do not use Default Binding” if you do not want to bind the application to the default host. In such a case, you must explicitly bind the application to a host, once the application is created.
    • Select the “Enable ESB JMS/WMQ Components in BizTalk Server” check box to create the application in the BizTalk Server Administration console.
      • Select the “Use Default Binding” to bind this application to the default host.
      • Optional you select the “Do not use Default Binding” if you do not want to bind the application to the default host. In such a case, you must explicitly bind the application to a host, once the application is created.

145-BizTalk-Server-2013-R2-BizTalk-ESB-Toolkit

  • Click “Apply Configuration” on the top of the ESB Configuration Tool to configure the Microsoft BizTalk ESB Toolkit.
Verify Your Installation

Open IIS and notice that the applications required for Microsoft BizTalk ESB Toolkit are now created under the website you specified.

146-BizTalk-Server-2013-R2-BizTalk-ESB-Toolkit-esb-iis

Open BizTalk Server Administration console and notice that the ESB applications are now installed and present in our console.

147-BizTalk-Server-2013-R2-BizTalk-ESB-Toolkit-esb-esb-biztalk-applications

Install Critical Windows Updates and BizTalk Server Cumulative Update

Once again, after you finish installing all the components, I check and install all Windows update if available and install the latest BizTalk Cumulative Update package and if necessary restart the server (note that this step is not necessary).

However I will like to mention that until this date there isn’t any Cumulative Update for BizTalk Server 2013 R2.

Related links

This next posts will focus on installing and configuring BizTalk Server 2013 R2 and additional components

Make sure that you have installed all the latest critical Windows updates from Microsoft and all the prerequisites before you install BizTalk Server 2013 R2.

Install and Configure Microsoft UDDI Services

UDDI Services provides Universal Description, Discovery, and Integration (UDDI) capabilities for sharing information about Web services within an organization’s intranet, between business partners on an extranet, or on the Internet. UDDI Services can help improve the productivity of developers and information technology (IT) professionals with more reliable and manageable applications. With UDDI Services you can prevent duplication of effort by promoting reuse of existing development work.

In a stand-alone installation, all default and optional components are installed on a single server. An instance of SQL Server must be installed before installing UDDI Services. When installing UDDI Services, the local instance of SQL Server is used to host the UDDI Services Database. UDDI Services Web Application and Notification Service are then configured to use the local UDDI Services Database.

To install Microsoft UDDI Services:

  • Close all applications before running setup. Run the BizTalk Server 2013 R2 installer as Administrator.
  • On the Start page, click “Install Microsoft UDDI Services”

120-BizTalk-Server-2013-R2-Microsoft-UDDI-Services

  • On the License Agreement page, select “Yes, I accept the terms in the license agreement” to accept the license agreement and click “Next”

121-BizTalk-Server-2013-R2-Microsoft-UDDI-Services-license-agreement

  • On the Component Installation page:
    • In “Available Components”: select and click from the available components you want to install
    • In “Install To”: specify a location to install UDDI Services components
    • And then click “Next” to continue

122-BizTalk-Server-2013-R2-Microsoft-UDDI-Services-component-installation

  • On the Summary page, review installation details and then click “Install”.

123-BizTalk-Server-2013-R2-Microsoft-UDDI-Services-summary

  • On the Installation Completed page, select “Launch Microsoft UDDI Services Configuration” option and then click “Finish” to start the UDDI Services configuration.

124-BizTalk-Server-2013-R2-Microsoft-UDDI-Services-installation-completed

  • On the Microsoft UDDI Services Configuration page, apply the following configurations and then click “Configure” to continue:
    • Select “Basic configuration” option
    • In the “Database server name” field under “Database” properties, enter the name of the local computer that will hosts the UDDI database.
    • In the “Service credential” properties, type the User name and Password for the account that the UDDI services will run under

125-BizTalk-Server-2013-R2-Microsoft-UDDI-Services-configuration-wizard

    • Note: You may receive a warning if you enter a user name with administrative credentials on this computer. Click “Yes” to continue.

126-BizTalk-Server-2013-R2-Microsoft-UDDI-Services-configuration-warning

  • On the Summary page, review configuration information, and then click “Next”
    • You may receive an warning on the UDDI Services Notification Service, don’t worry, we’ll deal with that later

127-BizTalk-Server-2013-R2-Microsoft-UDDI-Services-summary

  • On the Completed page, review configuration information:
    • If UDDI Services Notification Service is failed, which is the case
      • Select “Launch Custom Configuration” option
    • And then click “Finish”

128-BizTalk-Server-2013-R2-Microsoft-UDDI-Services-completed

  • On the Microsoft BizTalk Server Configuration (UDDI) page, from the left pane, select “UDDI Services Notification Service” option and configure the following settings:
    • Select “Enable UDDI Services Notification Service” option
    • Under “Windows Service”, set the service account under which the UDDI Notification Service runs.
    • Under “SMTP”, type the SMTP server for sending e-mail notifications.
    • Under “E-mail address”, type the address of the e-mail account used for sending e-mail notifications.
    • Under “SMTP Authentication”, specify the type of authentication used when authenticating with the SMTP server.
    • When finish, click “Apply Configuration”

129-BizTalk-Server-2013-R2-Microsoft-UDDI-Services-enable-uddi-services-notification-service

  • On the Summary page, review configuration information, and then click “Next”

130-BizTalk-Server-2013-R2-Microsoft-UDDI-Services-notification-service-summary

  • On the Completed page, review configuration information and then click “Finish”

131-BizTalk-Server-2013-R2-Microsoft-UDDI-Services-notification-service-completed

Verify Your Installation

To verify that Microsoft UDDI Services is installed correctly:

  • Open Internet Explorer and type http://localhost/uddi, and then hit Enter
    • If UDDI Services is installed correctly, you will see the Welcome to Microsoft UDDI Services page.

132-BizTalk-Server-2013-R2-Microsoft-UDDI-Services-browser

Related links

This next posts will focus on installing and configuring BizTalk Server 2013 R2 and additional components

Make sure that you have installed all the latest critical Windows updates from Microsoft and all the prerequisites before you install BizTalk Server 2013 R2.

BizTalk Adapter Pack

BizTalk Adapter Pack along with BizTalk AppFabric Connect, RFID features, UDDI services and ESB Toolkit are not automatically installed with the default installation process, instead you have to additional install this features.

The Microsoft BizTalk Adapter Pack contains adapters that enable enterprise applications and databases to interface with each other by implementing a common adapter framework. Similar to programming to Web services, adapters enable clients to program to different enterprise applications. Technically, adapters are a binding to Windows Communication Framework (WCF). The BizTalk Adapter Pack consists of the following adapters:

  • Microsoft BizTalk Adapter for Oracle Database (Oracle Database adapter).
  • Microsoft BizTalk Adapter for Oracle E-Business Suite (Oracle E-Business adapter).
  • Microsoft BizTalk Adapter for mySAP Business Suite (SAP adapter). This also includes the .NET Framework Data Provider for mySAP Business Suite (Data Provider for SAP).
  • Microsoft BizTalk Adapter for Siebel eBusiness Applications (Siebel adapter). This also includes the .NET Framework Data Provider for Siebel eBusiness Applications (Data Provider for Siebel).
  • Microsoft BizTalk Adapter for SQL Server (SQL adapter).
Microsoft BizTalk Adapter Pack and Microsoft BizTalk Adapter Pack (x64)

We are preparing a x64 environment machine so why do I need to install both x86 and x64 Microsoft BizTalk Adapter Pack and not only x64 pack?

On any computer where you want to perform design-time tasks using either Visual Studio or BizTalk MMC, you must install the 32-bit adapter because:

  • BizTalk Server Administration console runs as a 32-bit Microsoft Management Console (MMC) application.
  • Visual Studio is also a 32-bit application (and there isn’t any 64-bit version of Visual Studio)

However for BizTalk run time perspective:

  • If you want to run the adapters under a 32-bit BizTalk process (Host Instance): you need to install Microsoft BizTalk Adapter Pack.
  • If you want to run the adapters under a 64-bit BizTalk process (Host Instance): you need to install Microsoft BizTalk Adapter Pack (x64).

So you always have to install Microsoft BizTalk Adapter Pack, or in other cases, you always need to install the 32-bit adapter if you want to perform any operation at design-time, especially, configuring the adapters in the administrative console.

Steps to install BizTalk Adapter Pack

To install BizTalk Adapter Pack:

  • Close any programs you have open. Run the BizTalk Server 2013 R2 installer as Administrator.
  • On the Start page, click “Install Microsoft BizTalk Adapters”

81-BizTalk-Server-2013-R2-install-microsoft-biztalk-adapters-pack

  • In the next Start page, the first step is to install WCF LOB Adapter SDK, select the “Step 1. Install Microsoft WCF LOB Adapter SDK”. An installer of SDK is launched.
    • The WCF LOB Adapter SDK is a collection of a run-time engine and tools that help adapter developers create service-oriented interfaces to existing LOB systems by using WCF. The goal of the SDK is to facilitate uniform development of reusable, metadata-oriented, WCF-based adapters that enable enterprise applications, databases, and messaging platforms to integrate with each other.~

82-BizTalk-Server-2013-R2-Adapter-pack-step-1-install-microsoft-wcf-lob-adapter-sdk

    • On the Welcome to the Windows Communication Foundation LOB adapter SDK Setup Wizard page, click “Next”

83-BizTalk-Server-2013-R2-Adapter-pack-welcome-windows-communication-foundation-lob-adapter-sdk-setup-wizard

    • On the End-User License Agreement page, select “I accept the terms in the License Agreement” to accept the license agreement and click “Next”

84-BizTalk-Server-2013-R2-Adapter-pack-end-user-license-agreement-screen

    • In the Choose Setup Type page, select the installation type “Complete”:
      • Typical: will install the common run time and tools,
      • Custom: will allow you to select the features that you want to install and the installation location.
      • Complete: will install all the features.

85-BizTalk-Server-2013-R2-Adapter-pack-choose-setup-type

    • On the Ready to install WCF LOB adapter SDK page, click “Install”

86-BizTalk-Server-2013-R2-Adapter-pack-ready-install-wcf-lob-adapter-sdk-screen

    • On the Completed the Windows Communication Foundation LOB Adapter SDK Setup Wizard page, click “Finish”

87-BizTalk-Server-2013-R2-Adapter-pack-completed

  • Back to the Start page, the second step is installation of the Adapter Pack (x86), select the “Step 2. Install Microsoft BizTalk Adapter Pack”. An installer of SDK is launched.

88-BizTalk-Server-2013-R2-Adapter-pack-step-2-install-microsoft-biztalk-adapter-pack

    • On the Welcome to the Microsoft BizTalk Adapter Pack Setup Wizard page, click “Next”

89-BizTalk-Server-2013-R2-Adapter-pack-welcome-microsoft-biztalk-adapter-pack-setup-wizard

    • On the End-User License Agreement page, select “I accept the terms in the License Agreement” to accept the license agreement and click “Next”

90-BizTalk-Server-2013-R2-Adapter-pack-end-user-license-agreement

    • In the Choose Setup Type page, select the installation type “Complete”:
      • Typical: will install the common run time and tools,
      • Custom: will allow you to select the features that you want to install and the installation location.
      • Complete: will install all the features.

91-BizTalk-Server-2013-R2-Adapter-pack-choose-setup-type

    • On the Ready to install Microsoft BizTalk Adapter Pack page, click “Install”

92-BizTalk-Server-2013-R2-Adapter-pack-ready-install-microsoft-biztalk-adapter-pack

    • On the Customer Experience Improvement Program page, select if you want to join the customer experience improvement program or not and click “OK”

93-BizTalk-Server-2013-R2-Adapter-pack-customer-experience-improvement-program

    • On the Completed the Microsoft BizTalk Adapter Pack Setup Wizard page, click “Finish”

94-BizTalk-Server-2013-R2-Adapter-pack-completed-microsoft-biztalk-adapter-pack-setup-wizard

  • Back to the Start page, the next step is installing the Microsoft BizTalk Adapter Pack (x64) – note that before you install this pack you have to install x86 first – select the “Step 3. Install Microsoft BizTalk Adapter Pack(x64)”. An installer of SDK is launched.

95-BizTalk-Server-2013-R2-Adapter-pack-step-3-install-microsoft-biztalk-adapter-packx64

    • On the Welcome to the Microsoft BizTalk Adapter Pack(x64) Setup Wizard page, click “Next”

96-BizTalk-Server-2013-R2-Adapter-pack-welcome-microsoft-biztalk-adapter-packx64-setup-wizard

    • On the End-User License Agreement page, select “I accept the terms in the License Agreement” to accept the license agreement and click “Next”

97-BizTalk-Server-2013-R2-Adapter-pack-end-user-license-agreement-screen

    • In the Choose Setup Type page, select the installation type “Complete”:
      • Typical: will install the common run time and tools,
      • Custom: will allow you to select the features that you want to install and the installation location.
      • Complete: will install all the features.

98-BizTalk-Server-2013-R2-Adapter-pack-choose-setup-type

    • On the Ready to install Microsoft BizTalk Adapter Pack(x64) page, click “Install”

99-BizTalk-Server-2013-R2-Adapter-pack-ready-install-microsoft-biztalk-adapter-packx64

    • On the Customer Experience Improvement Program page, select if you want to join the customer experience improvement program or not and click “OK”

100-BizTalk-Server-2013-R2-Adapter-pack-customer-experience-improvement-program

    • On the Completed the Microsoft BizTalk Adapter Pack(x64) Setup Wizard page, click “Finish”

101-BizTalk-Server-2013-R2-Adapter-pack-completed-microsoft-biztalk-adapter-packx64-setup-wizard

  • Back to the Start page, the final step is installing the Microsoft BizTalk Adapters for Enterprise Applications, select the “Step 4. Install Microsoft BizTalk Adapters for Enterprise Applications”. An installer of SDK is launched.

102-BizTalk-Server-2013-R2-Adapter-pack-step-4-install-microsoft-biztalk-adapters-for-enterprise-applications

    • On the Welcome to the Microsoft BizTalk Adapters for Enterprise Applications Setup Wizard page, click “Next”

103-BizTalk-Server-2013-R2-Adapter-pack-welcome-microsoft-biztalk-adapters-for-enterprise-applications-setup-wizard

    • On the End-User License Agreement page, select “I accept the terms in the License Agreement” to accept the license agreement and click “Next”

104-BizTalk-Server-2013-R2-Adapter-pack-end-user-license-agreement

    • In the Customer Information page, type your User Name and Organization and click “Next” to continue.

105-BizTalk-Server-2013-R2-Adapter-pack-customer-information

    • In the Choose Setup Type page, select the installation type “Complete”:
      • Custom: will allow you to select the features that you want to install and the installation location.
      • Complete: will install all the features.

106-BizTalk-Server-2013-R2-Adapter-pack-choose-setup-type

    • On the Choose Destination Location page, choose the folder location that to want to install this features and click “Next”

107-BizTalk-Server-2013-R2-Adapter-pack-choose-destination-location

    • On the Ready to install page, click “Install”

108-BizTalk-Server-2013-R2-Adapter-pack-ready-install

    • On the Completed the Microsoft BizTalk Adapters for Enterprise Applications Setup Wizard page, click “Finish”

109-BizTalk-Server-2013-R2-Adapter-pack-completed-microsoft-biztalk-adapters-for-enterprise-applications

  • Close the Start page, click “Exit”.

110-BizTalk-Server-2013-R2-Adapter-pack-success

Add adapters to BizTalk Administration Console

As it happens with all adapters that we installed on our BizTalk Servers environment, before we can begin to use them we need to register or add the adapters. So in the next step it will be describing how can we add the enterprise adapters, or any other custom adapter, on the BizTalk Administration Console. To accomplish that we need to:

  • Open BizTalk Administration Console by pressing the “Windows key” to switch to the Start screen, type “BizTalk Server Administration” or “BizTalk”, click “BizTalk Server Administration” option from the Search menu
  • In the console left tree, expand “BizTalk Server Administration –> BizTalk Group –> Platform Settings” and then “Adapters”
  • Right-click on “Adapters” and add a new adapter by selecting the option “New –> Adapter”

111-BizTalk-Server-2013-R2-Register-New-Adapter

  • In the “Adapter Properties” window
    • In the Name box, type a descriptive name for this adapter.
      • WC-SQL
    • In the Adapter combo box, select the adapter from the drop-down that you want to add.
      • WCF-SQL
    • In the Description box, type a description for the adapter (this is optional).
      • The WCF SQL Adapter provides access to SQL Database table, views, stored procedures and functions. Polling is also provided, allowing applications to periodically look for data in databases.
    • Click “OK” to complete the process of adding the adapter.

112-BizTalk-Server-2013-R2-Register-New-Adapter

  • Repeat steps to add the other adapters.

112-BizTalk-Server-2013-R2-Register-New-Adapter-2

Note: This configurations requires that you restart the host instance associated with the adapters.

Related links

This next posts will focus on installing and configuring BizTalk Server 2013 R2 and additional components

Make sure that you have installed all the latest critical Windows updates from Microsoft and all the prerequisites before you install BizTalk Server 2013 R2.

Validate Mail account used by BizTalk to send BAM Alerts

After you configure with success BizTalk Server 2013 R2 BAM Alerts, the configurator will create a new Database Mail Account called “BAM_Alerts_Account” that will be used by BizTalk to send BAM Alerts.

To Validate Mail account used by BizTalk to send BAM Alerts:

  • Press the “Windows key” to switch to the Start screen, type “SQL Management” or “SQL” and click in “SQL Server Management Studio” option from the Search menu.
  • In Object Explorer panel, connect to the SQL Server instance you want to configure Database Mail on, and expand the server tree.
  • Expand the “Management” node and double click “Database Mail” to open the Database Mail Configuration Wizard.
  • On the Welcome to Database Mail Configuration Wizard page, click “Next” to continue
  • On the Select Configuration Task page, select “Manage Database Mail accounts and profiles” option and click “Next”

77-BizTalk-Server-2013-R2-Test-BAM-Alerts-Account -manage-profiles-and-accounts-page

  • On the Manage Profiles and Accounts page, select “View, change or delete an existent account” option, and click “Next”

78-BizTalk-Server-2013-R2-Test-BAM-Alerts-Account -manage-profiles-and-accounts-page

  • On the Manage Existent Account page, select “BAM_Alerts_Account” option under “Account name” and validate the configuration. After that click “Next” to make any change or “Cancel” to exit.

79-BizTalk-Server-2013-R2-Test-BAM-Alerts-Account -manage-existent-account-page

  • On the Complete the Wizard page, click “Finish”.

80-BizTalk-Server-2013-R2-Test-BAM-Alerts-Account -manage-existent-account-page

Finally you should test sending an email with this Database Mail Account, to do that:

  • Right-click on Database Mail and select “Send Test E-Mail…”

81-BizTalk-Server-2013-R2-Test-BAM-Alerts-Account-send-test-e-mail

  • On the Send Test E-mail from windows, specify a “To:” email and click “Send Test E-Mail”

81-BizTalk-Server-2013-R2-Test-BAM-Alerts-Account-send-test-e-mail-details

If all goes well you should receive the email in a few seconds. If you have received the email, you have been able to configure Database Mail successfully.

Related links

This next posts will focus on installing and configuring BizTalk Server 2013 R2 and additional components

Make sure that you have installed all the latest critical Windows updates from Microsoft and all the prerequisites before you install BizTalk Server 2013 R2.

Configure SQL Server Network Configuration protocols

Under certain stress conditions (such as clients accessing SQL Server from the same computer), the SQL Server Shared Memory protocol may lower BizTalk Server performance. You can resolve this problem by disabling the use of the Shared Memory network protocol in SQL Server Network Configuration. Also, to facilitate transactions between SQL Server and BizTalk Server, you must enable TCP/IP and Named Pipes in SQL Server.

To configure the protocols for SQL Server:

  • Press the “Windows key” to switch to the Start screen, type “SQL Server Configuration Manager” and click in “SQL Server Configuration Manager” option from the Search menu.

74-BizTalk-Server-2013-R2-sql-server-2014-configuration-manager

  • In SQL Server Configuration Manager windows, from the left-hand pane expand “SQL Server Network Configuration” option and then click “Protocols for MSSQLSERVER”
    • Verify that both “TCP/IP” and “Named Pipes” are enabled;
      • If not, right-click in the protocol, and then click “Enable”
      • Repeat to enable the other protocol if necessary.
    • Verify that “Shared Memory” id Disable.
    • If not, right-click Shared Memory, and then click “Disable”

75-BizTalk-Server-2013-R2-SQL-Server-2014-configuration-manager-protocols-for-mssqlserver

  • In the left-hand pane, click “SQL Server Services”, right-click “SQL Server (MSSQLSERVER)”, and then click “Restart”. Or click “Stop” and when the service has stopped, right-click “SQL Server (MSSQLSERVER)” again, and then click “Start”.

76-BizTalk-Server-2013-R2-SQL-Server-2014-configuration-manager-sql-server-services-restart

  • Close SQL Server Configuration Manager.
Related links