Cài và cấu hình BizTalk 2010 – Cấu hình Application Event Log (Phần 13)

This is an important step and it should be configured or validate before BizTalk Server Setup (part 8 ) because:

  • BizTalk Server setup keeps a record of events in the Application Event Log. Depending on the BizTalk Server features installed, the amount of space required in the log may exceed its limit. If the application event log runs out of space during BizTalk Server setup, the installation will fail.
  • Also in production you always want a rolling list of the latest events (information, warnings or failures) and you don’t want that your Application Event Log becomes massive in size.

However, I purposely left this point to the end because by default the Application Event Log is already correctly configured:

  • Maximum log size (Kb): 20489 – that is 20 MB, which gives us a comfortable historic of events
  • And the option “Overwrite events as needed (oldest events first)” is select, with this option we prevent that the log to exceed its limits, avoiding installation failures:
    • Typical error: Inner exception: The event log file is full


To change settings in the Application Event Log

  • Click Start, click Control Panel and then double-click Administrative Tools.
  • Click Event Viewer.
  • In the Event Viewer, expand Windows Logs.
  • Right-click Application and then click Properties. This opens the Log Properties dialog box.
    • To see how much available space your log has, compare the Log Size field with the Maximum log size field.
    • To provide more space in the event log, enter a higher number in the Maximum log size field.
    • To enable overwriting of old events when the log becomes full, select Overwrite events as needed.
    • To clear the log events, click Clear log.
  • Click OK, to close the Event Viewer
Samples of BizTalk events in the Application Event Log



The following BizTalk host instance has initialized successfully.
BizTalk host name: BizTalkServerApplication
Windows service name: BTSSvc$BizTalkServerApplication


A message sent to adapter “SMTP” on send port ” EmailNotificationPort” with URI “mailto:myemai@email.pt” is suspended.

Error details: There was a failure executing the send pipeline: “Microsoft.BizTalk.DefaultPipelines.XMLTransmit, Microsoft.BizTalk.DefaultPipelines, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35” Source: “XML assembler” Send Port: ” EmailNotificationPort” URI: “mailto: myemai@email.pt” Reason: Name cannot begin with the ‘<’ character, hexadecimal value 0x3C. Line 2, position 1.

A request-response for the “SOAP” adapter at receive location “/WebServiceasmx” has timed out before a response could be delivered.


The cube “MyView” was not processed. Please run the cube DTS to process the cube.

The adapter failed to transmit message going to send port “DynamicSendPort” with URL “http://Service.asmx&#8221;. It will be retransmitted after the retry interval specified for this Send Port. Details:”Server was unable to process request. —> Object reference not set to an instance of an object.”.

Sưu tầm: Cài và cấu hình BizTalk 2010 – Cấu hình BizTalk Server SQL Jobs (Phần 11)

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

If you want these functionalities you must configure and enabled them.


How to configure Backup BizTalk Server (BizTalkMgmtDb)

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.


Step 1 – Set Compression Option

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:

view source


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:

view source


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

For more information see Tiago Almeida article: BizTalk Server 2010 Backup Compression

Step 2 – BackupFull

The original script is:

view source


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


  • Frequency (@Frequency): The default is d (daily). This is the recommended setting. Other values include h (hourly), w (weekly), m (monthly), or y (yearly).
  • Name (@MarkName): The default is BTS. The name is used as part of the backup file name.
  • Location of backup files (@BackupPath): 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:

view source


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:

view source


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


  • @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
    • view source


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

Change the script to:

view source


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

Step 4 – Clear Backup History

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

view source


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


  • @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
    • view source


      exec [dbo].[sp_DeleteBackupHistory] @DaysToKeep=14 , @UseLocalTime =1

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


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:

  • 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:

view source


CREATE PROCEDURE [dbo].[sp_DeleteBackupHistoryAndFiles] @DaysToKeep smallint = null




set nocount on

IF @DaysToKeep IS NULL OR @DaysToKeep <= 1


/* 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)


IF (@@fetch_status <> -2)


EXEC master.dbo.xp_cmdshell @cmd, NO_OUTPUT

delete from [adm_BackupHistory] WHERE CURRENT OF DeleteBackupFiles

print @cmd


FETCH NEXT FROM DeleteBackupFiles INTO @cmd



CLOSE DeleteBackupFiles

DEALLOCATE DeleteBackupFiles



  • 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.
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.
  • For more information: How to Purge Data from the BizTalk Tracking Database

The original script after installing BizTalk looks like this:

view source


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:

view source


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

For more information: How to Configure the DTA Purge and Archive Job

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

view source


declare @dtLastBackup datetime set @dtLastBackup = GetUTCDate() exec dtasp_PurgeTrackingDatabase 1, 0, 7, @dtLastBackup



Removes all messages that are not referenced by any subscribers in the BizTalkMsgBoxDb database tables.


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

Sưu tầm: Cài và cấu hình BizTalk 2010 – Cài và cấu hình local SMTP dùng cho Reporting Server (Phần 9)

Installing SMTP Server Feature on Windows Server 2008 R2 is an easy process requiring only few steps to complete.

To install SMTP Server Features
  • Open “Server Manager Console”
    • Start → Administrative Tools → Server Manager
  • Under “Features” select “Add Features”


  • In “Select Features” screen, select “SMTP Server” option


    • In “Add role services and features required for SMTP Server?” screen, click “Add Required Role Services”


    • Click “Next”
  • In “Web Server (IIS)” screen, click “Next”
  • In “Role Services” screen, click “Next”.
  • In “Confirm Installation Selections” screen, Review the installation selection, and note that SMTP Server will be installed, and click Install.


  • In “Installation Result” screen, ensure that the installation is fully successfully, and then click Close.


To configure a local SMTP Service for the report server
  • Verify that the service is running in the Services console.


  • Click Start, point to “All Programs”, point to “Microsoft SQL Server 2008 R2”, point to “Configuration Tools”, and then select “Reporting Services Configuration Manager”


  • On the “Reporting Services Configuration Connection” page, ensure that the “Server Name” is you server, in my case “BTS2010LAB01”, and ensure that the “Report Server Instance” name is “MSSQLSERVER”, and then click “Connect”.


  • Select “E-mail Settings” tab on the left tree
    • E-mail Settings: Reporting Services includes a report server e-mail delivery extension that allows report subscribers to get reports delivered to an electronic mailbox. The e-mail delivery extension uses a Simple Mail Transport Protocol (SMTP) to deliver the report or notification. You can use the Reporting Services Configuration Manager to specify which SMTP server or gateway on your network to use for e-mail delivery.
      • On the Email Settings page, enter the name of the SMTP server. This value can be an IP address, a UNC name of a computer on your corporate intranet, or a fully qualified domain name.
      • In Sender Address, enter the name an account that has permission to send e-mail from the SMTP server.


      • Then Click “Apply”
  • In the result page, ensure that the configuration is fully successfully, and click “Exit”


To use the Reporting Services Configuration Manager, you must have the following:
  • Local system administrator permissions on the computer that hosts the report server you want to configure. If you are configuring a remote computer, you must have local system administrator permissions on that computer as well.
  • You must have permission to create databases on the SQL Server Database Engine used to host the report server database.
  • Windows Management Instrumentation (WMI) service must be enabled and running on any report server you are configuring. The Reporting Services Configuration tool uses the report server WMI provider to connect to local and remote report servers. If you are configuring a remote report server, the computer must allow remote WMI access.
  • Before you can connect to and configure a remote report server instance, you must enable remote Windows Management Instrumentation (WMI) calls to pass through Windows Firewall.
You can use the Reporting Services Configuration Manager to perform the following tasks:
  • Configure the Report Server service account. The account is initially configured during setup, but can be modified by using the Reporting Services Configuration Manager if you update the password or want to use a different account.
  • Create and configure URLs. The report server and Report Manager are ASP.NET applications accessed through URLs. The report server URL provides access to the SOAP endpoints of the report server. The Report Manager URL is used to open Report Manager. You can configure a single URL or multiple URLs for each application.
  • Create and configure the report server database. The report server is a stateless server that requires a SQL Server database for internal storage. You can use the Reporting Services Configuration Manager to create and configure a connection to the report server database. You can also select an existing report server database that already contains the content you want to use.
  • Configure a scale-out deployment. Reporting Services supports a deployment topology that allows multiple report server instances use a single, shared report server database. To deploy a report server scale-out deployment, you use the Reporting Services Configuration Manager to connect each report server to the shared report server database.
  • Backup, restore, or replace the symmetric key that is used to encrypt stored connection strings and credentials. You must have a backup of the symmetric key if you change the service account, or move a report server database to another computer.
  • Configure the unattended execution account. This account is used for remote connections during scheduled operations or when user credentials are not available.
  • Configure report server e-mail. Reporting Services includes a report server e-mail delivery extension that uses a Simple Mail Transfer Protocol (SMTP) to deliver reports or report processing notification to an electronic mailbox. You can use the Reporting Services Configuration tool to specify which SMTP server or gateway on your network to use for e-mail delivery.

Sưu tầm: Cài và cấu hình BizTalk 2010 – Cài BizTalk Adapter Pack 2010 và kết nối BizTalk AppFabric (Phần 10)

In sequence of a set of posts about installation and configuration of BizTalk 2010, I leave you here two excellent posts about:

Installing BizTalk Adapter Pack 2010 posted by Steef-Jan Wiggers:

And Microsoft AppFabric Connect in BizTalk 2010 posted by Thiago Almeida:

Installing BizTalk Adapter Pack 2010 on x64

The BizTalk Adapter Pack 2010 provides connectivity to SAP, Oracle E-Business Suite, Siebel and SQL and Oracle Databases. The BizTalk Adapter Pack can be installed in conjunction with, or separately from, BizTalk Server.

The BizTalk Adapter Pack 2010 includes support for new versions of the following line-of-business applications and databases: SAP 7, Oracle EBS 12.1 and SQL Server 2008 R2. The Adapter Pack also provides support for Visual Studio 2010 and .NET Framework 4.

It is included in both the Enterprise and Standard Editions of BizTalk. When you install the adapter pack on x64 environment you have to perform a few steps. These steps were described in earlier versions through installation guides, although for some it was not always clear (i.e. I saw couple of questions on forum about how to install or problems people had). There is documentation to install adapters pack, but now during installation one is guided through the necessary steps.

Adapter Pack BizTalk 2010 Figuur 1

This is a definite improvement towards installing Adapter Pack on for instance x64 environment as shown on the screenshot above. So first step is installing WCF LOB Adapter SDK and by clicking on the first step an installer of SDK is launched.

Adapter Pack BizTalk 2010 Figuur 2

By clicking next and selecting one of installation options the SDK is installed. After installation you will see that first step is completed in the overall process. Second step is installation of the Adapter Pack (x86). By clicking Microsoft BizTalk Adapter Pack needs to be installed an installer is launched again.

Adapter Pack BizTalk 2010 Figuur 3

After installation of this pack the screen is updated again stating second step is completed successfully.

Adapter Pack BizTalk 2010 Figuur 4

You will sometime see windows update screen or screen with question if you want to join the improvement program. Next step is installing the Microsoft BizTalk Adapter Pack(x64). Before installing this pack you have to install x86 first, which is overlooked a lot of times in past by people. Can’t happen having guidance.

Adapter Pack BizTalk 2010 Figuur 5

Having installed the x64 Adapter Pack the final step can be performed.

Adapter Pack BizTalk 2010 Figuur 6

By clicking on Install Microsoft BizTalk Adapters for Enterprise Applications an installer is launched.

Adapter Pack BizTalk 2010 Figuur 7

As this installation has been successfully completed the process of installing the LOB Adapters is complete.

Adapter Pack BizTalk 2010 Figuur 8

I recommend to always choose complete installation of SDK, Adapter Packs and Microsoft BizTalk Adapters for Enterprise Applications.You the have documentation at you disposal. Going through this process you now have full set of adapters ranging from new WCF Adapters to old (non-WCF) Adapters. Next step is adding the appropriate adapters in BizTalk Administration Console.

Adapter Pack BizTalk 2010 Figuur 9

You have to go navigate to Platform Settings –> Adapters and then right click New –> Adapter.

Note: When installing the adapter pack you do not see a new adapter show up under the Adapters folder or in the drop down for Add new Adapter. The adapter pack installs new custom bindings.The BizTalk “adapter” for instance for the Oracle database shows up in BizTalk as the OracleDBBinding. The standard bindings are wsHttpBinding, netTcpBinding, etc. OracleDbBinding and SqlBinding are themselves custom bindings. (Ben Cline explained this on forum few weeks ago).

Adapter Pack BizTalk 2010 Figuur 10

You can also download the interactive or normal poster of BizTalk Adapter 2010. The BizTalk Adapter Pack is included with BizTalk Server 2010 and you can download the BizTalk Server 2010 Evaluation if you want to try it out.

When completing this process you also have installed all the prerequisites for AppFabric Connect. When starting a WCF Workflow Service you will see BizTalk Mapper.

This post goes over a couple of points around the installation of Microsoft AppFabric Connect feature of BizTalk Server 2010 and a note on the licensing requirements.

Installations Details

The installation details of the BizTalk AppFabric Connect feature are described in detail here by Trace Young:


On a development or runtime machine where Windows Server AppFabric is already installed you can start up the BizTalk Server setup and select ‘Install Microsoft AppFabric Connect’:


Once there you can see the required installation steps: you need BizTalk Server, the Microsoft WCF LOB Adapter SDK (this is a pre-requisite for the BizTalk Adapter Pack), and the BizTalk Adapter Pack itself (this is the part that installs the actual AppFabric Connect feature proper):


There are actually two features that compose the Microsoft AppFabric Connect feature: the mapper activity; and the line of business activities. Both [update 30/10/2010] Even though the splash screen mentions the BizTalk runtime is required, only the mapper requires the BizTalk Server runtime to be installed on the machine. The line of business activities are as they were in BizTalk 2009, you only need the WCF LOB SDK and the BizTalk Adapter Pack.

When clicking to install Microsoft BizTalk Server, the only parts needed for the [update 30/10/2010] mapper part of the AppFabric Connect feature on a development environment are the following:


Note that you only need the Developer Tools and SDK on a development environment, but the Server Runtime is needed on all environments [update 30/10/2010] for the mapper feature. This is because the mapper depends on certain core DLLs from BizTalk Server but the LOB activities don’t.

Next is the WCF LOB adapter SDK. On a development environment you need both Runtime and Tools (if you want just the mapper then just Runtime is enough). On non-development environments (UAT, Production, etc) you can install only the runtime option.


If you made it this far and all you wanted was the mapper in your workflow then you have it already. If you want the LOB feature then the last step is to install the adapters you are interested in from the BizTalk Adapter Pack. For example, if I’m only interested in the WCF-SQL and the WCF-Oracle adapters I choose them from the custom installation:


With this you can start a new .NET 4 WCF Workflow Service project or add a new workflow to an existing project. You should now be able to use ‘Add Adapter Service Reference’ from your workflow project to get the LOB activities, and of course you will find the mapper activity in your workflow’s toolbox:



[update 30/10/2010] Microsoft’s approach to this at the moment is that you need a BizTalk Server Standard or Enterprise license to use the Windows AppFabric Connect feature (even if you only need the LOB adapters and did not install the BizTalk runtime).

Sưu tầm: Cài và cấu hình BizTalk 2010 – Cài và cấu hình BizTalk Server (Phần 8)

BizTalk 2010 Installation and Configuration, the last chapter!!!

In this section you’ll install BizTalk Server, confirm that the installation succeeded, and then configure BizTalk Server.

When you installed SQL Server, setup granted your account Database Administrator rights. Since these rights are also required for installing BizTalk Server, you must do one of the following:

  • Use the same account you used when you installed SQL Server.
  • Make sure the account you’re using now also has Database Administrator rights.
To install BizTalk Server 2010
  1. Close any programs you have open.
  2. Insert the BizTalk Server 2010 installation disk into the DVD-ROM drive.
  3. On the Start screen, click Install Microsoft BizTalk Server 2010.
  4. On the Customer Information screen, type your user name and organization, enter your product key, and then click Next.
  5. On the License Agreement screen, click Yes, I accept the terms of the license agreement, and then click Next.
  6. Use the Customer Experience Improvement Program page of the BizTalk Server 2010 Installation Wizard to enable feature usage reporting functionality for BizTalk Server.
  7. On the Component Installation screen, review the available components and select the ones you want to install.
  8. Accept the default installation location or click Browse to move to the location where you want to install BizTalk Server 2010, and then click Next.
  9. If your computer is missing a prerequisite component such as ADOMD.NET, Setup can install the redistributable prerequisites. You can either:
    1. Select Automatically install the redistributable prerequisites from the web
    2. OR Select Automatically install the redistributable prerequisites from a CAB file if you have downloaded the CAB file. If you select this, you can then browse to the location of the CAB file and select it.
  10. On the Summary screen, verify that the components that you select to install are correct.
  11. To enable auto-logon after a system reboot, click Set and provide your logon information. Auto-logon is enabled only for reboots during setup, and is disabled when setup is complete.
  12. Click Install to start the installation process.
  13. On the Microsoft Update Setup page, click Use the Microsoft Update when I check for updates (recommended).
  14. On the Installation Completed screen, clear the Launch BizTalk Server Configuration check box, and then click Finish.
Verify Your Installation

You can check to see whether your installation was successful by using either Programs and Features or the Registry.

To verify installation using Programs and Features

  1. Click Start, click Control Panel (View by: Large/Small icons), and double-click Programs and Features.
  2. When the list is fully populated, look for BizTalk Server 2010. If it appears in the list, setup succeeded.

To verify installation using the Registry

  1. Open a command prompt.
  2. Type regedit and then press Enter.
  3. When the Registry opens, browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\3.0
  4. If files exist in the 3.0 folder, setup succeeded.
  5. Close the Registry, and then close the command prompt.
Configure BizTalk Server

Use the following procedure to complete a basic configuration of BizTalk Server. For information on customizing your configuration, see Custom Configuration in the BizTalk Server Help.

To configure BizTalk Server 2010 using Basic Configuration

  1. Click Start, click All Programs, click Microsoft BizTalk Server 2010, right-click BizTalk Server Configuration, and then click Run as Administrator.
  2. In the Database field, enter the name of the local computer.
  3. In the Service Credential field, type the User name and Password for the account that the BizTalk services will run under.
  4. Click Configure.
  5. Note: You may receive a warning if you enter a user name with administrative credentials on this computer. Click OK to continue.
  6. On the Summary screen, review the configuration about to be performed, and then click Next.
    Don’t worry about SharePoint Adapter, we deal with this later!
  7. On the Completion screen, click Finish.

Note: Once again don´t worry about SharePoint Adapter, we deal with this later.

Setting up BizTalk – SharePoint Adapter

We now have the ability to configure the “SharePoint Adapter”. For that you must:

  1. Run BizTalk Server Configuration
  2. On the Configuration Screen, select the option “SharePoint Adapter” and use the drop down list to select the WSS Site where you would like the adapter to be installed, in this case “SharePoint – 90”.
  3. Assuming everything is aligned correctly, you should now be able to click the “Apply Configuration” button.
  4. On the Summary screen, click “Next”
  5. On the Completion screen, click Finish.

We now have BizTalk Server 2010 FULLY Installed and Configured!!!


Sưu tầm: Cài và cấu hình BizTalk 2010 – Disable the Shared Memory Protocol (Phần 7)

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 the SQL Server Client Network Utility.

To disable Shared Memory protocol for SQL Server
  1. Click Start, point to All Programs, point to Microsoft SQL Server 2008 R2, click Configuration Tools, and then click SQL Server Configuration Manager.
  2. In SQL Server Configuration Manager, expand SQL Server Network Configuration, and then click Protocols for MSSQLSERVER.
  3. Right-click Shared Memory, and then click Disable.
  4. Click SQL Server Services, right-click SQL Server (MSSQLSERVER), and then click Stop. After the service has stopped, right-click SQL Server (MSSQLSERVER) again, and then click Start.
  5. Close SQL Server Configuration Manager.

Sưu tầm: Cài và cấu hình BizTalk 2010 – Cài và cấu hình SharePoint Foundation 2010 (Phần 6.1)

Previously I explained in detail how to Install and Configure Windows SharePoint Services using Windows SharePoint Services 3.0 with SP2, to remember, BizTalk Server 2010 supports these two versions of WSS:

  • SharePoint Foundation 2010
  • Windows SharePoint Services 3.0 with SP2

However, if you wish to use SharePoint Foundation 2010, I suggest reading Steef-Jan Wiggers post:

where is explained in detail all the steps required to install and configure SharePoint Foundation 2010 and SharePoint Services Web Service Adapter for BizTalk Server 2010

Installing Windows SharePoint Services Web Service Adapter BizTalk Server 2010/SharePoint Foundation 2010

I think a lot of you have read the excellent series ShareTalk Integration (SharePoint/BizTalk) by Kent Weare. Focus was on BizTalk 2009 and Microsoft Office SharePoint Server (MOSS) 2007. Now with BizTalk 2010 you are able to configure SharePoint adapter to Windows SharePoint Services like previous 2009 version.BizTalk Server 2010 supports two versions of WSS:

  • SharePoint Foundation 2010
  • Windows SharePoint Services 3.0 with SP2

Latter is explained in detail by Sandro Pereira, BizTalk 2010 Installation and Configuration – Install and Configure Windows SharePoint Services. In this post I like to share how to configure BizTalk SharePoint Adapter with SharePoint Foundation 2010.

Installing and configuring Windows SharePoint Services consists of the following procedures:

  • Install Windows SharePoint Services
  • Configure Windows SharePoint Services
  • Extend the Default Web Site as a virtual server

Install Windows SharePoint Foundation 2010

First step of installation is to install prerequisites. In my situation I am installing SharePoint Foundation on virtual machine (Windows Server 2008R2 x64, 4 core’s 4 Gb memory) following the installation manual for BizTalk Server 2010 called: Installing BizTalk Server 2010 on Windows Server 2008 R2 and 2008 (see BizTalk Server 2010 documentation).


When installing software prerequisites you just have to click Next a few times (it is pretty straight forward).





After this it installing SharePoint Foundation itself.


This involves also a couple of steps, where you have to make some choices.


Installation depends on if you want to do a standalone or server farm.


A Stand-alone installation configures a single computer with all the necessary files and settings to create a fully functioning SharePoint implementation, including Web server, application server, and database. SQL Server Express 2008 is installed and configured to provide data storage capability. SQL Server Express is based on the Microsoft SQL Server architecture, but it has the following limitations:

  • lack of enterprise features support;
  • limited to one CPU;
  • one gigabyte (GB) memory limit for the buffer pool;
  • databases have a 4 GB maximum size;
  • SQL Server Express will not support a server farm configuration or a multi-processor computer.

In addition to the SQL Server Express limitations, the inherit SharePoint Foundation Standalone configuration limitation is that you cannot add servers to create a SharePoint farm. If you need to add another SharePoint 2010 Web Front End later than you won’t be able to. If you anticipate the need to scale up to a larger or more robust installation, choose the Server Farm option.

SharePoint Foundation 2010 Server Farm will install all components. You can add additional servers to form a SharePoint farm, including load balanced SharePoint 2010 Web Front End servers. The Complete option installs a Web server and configures the computer to provide application server functionality. The SharePoint Foundation 2010 Complete install option does not provide database functionality. If you continue with this option and your server does not belong to a domain, for instance just a workgroup you will see error if you proceed with steps below.






For development purposes, proof-of-concepts or demo it is better to choose Standalone. If you opted for this then the SharePoint 2010 Products Configuration Wizard will immediately begin the ten step configuration process.



After you have let the wizard run through, you should automatically be directed to a default SharePoint Foundation 2010 site that looks a lot like the screen below.


Install Windows SharePoint Services Adapter

As soon as this has been done you can proceed with next steps installation manual. It then comes down to installing BizTalk. When you select components you will see that you can install Windows SharePoint Services Adapter.