BizTalk Server 2010 AppFabric Connect for Services

December 10, 2010

Using the recently released BizTalk Server 2010 AppFabric Connect for Services you can extend BizTalk Orchestrations and LOB applications into the cloud.

This post from the BizTalk Server team offers some situations where this feature may be useful.

This new feature pack can be downloaded here: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=f7735a19-cdb3-4f52-8e7b-c58f04c5c86a


Registering script maps with .svc file extension’s on IIS7

November 13, 2010

By default there is no script map for files with the .svc file extension on a default IIS 7.0 installation,. To register the script map use the following command:

C:\Windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe -r -y 

Configuring BAM with BizTalk Server 2010

October 29, 2010

In general when building a new BizTalk Server environment it is best to follow the installation guides provided by Microsoft with each release of its product but from time to time even following the instructions will result in errors.

When building my BizTalk 2010 environment I encountered such an error when trying to configure BAM, Hopefully reading this post will save you some valuable time.

As specified by the installation guide, if you plan to configure BAM alerts you will need to install SQL Notification Services. This feature of SQL Server stopped shipping after the release of SQL Server 2005.

To get this feature working you will need to disregard the instructions as outlined in the BizTalk 2010 installation guide and follow these alternative instructions:

Before installing SQL Server 2008 R2 install the following:

  • SQL Server 2005 Notification Services (from the a copy of the SQL 2005 installation iso)
  • SQL Server 2005 SP2.
  • SQL Server 2005 SP3.

Connect to SAP gateway failed

November 14, 2009

I received an error (in the windows event log) the other day when trying to configure a BizTalk receive location using the WCF LOB SAP adapter. The error looked like this:


The Messaging Engine failed to add a receive location "" with URL "" to the adapter "WCF-Custom".
Reason: "Microsoft.Adapters.SAP.RFCException: Details: ErrorCode=RFC_OK. ErrorGroup=RFC_ERROR_COMMUNICATION. SapErrorMessage=Connect to SAP gateway failed
Connect_PM TPNAME=, GWHOST=, GWSERV=

One solution (as suggested by MSDN) is to install the SAP client.

This solution works, but what is it about the SAP client install that is required by the WCF LOB SAP adapter? Why should you have to install the SAP client on a production server?

It turns out the SAP client modifies the following file: c:\windows\system32\drivers\etc\services, by making entries to resolving the SAP gateway host’s name (as used in BizTalk WCF SAP receive location’s URI) to the gateways address.

Once you manually modify this file to contain these entries the WCF SAP BizTalk receive location will work without having to install the SAP client.


How to save password for WCF Adapter in BizTalk binding file

October 28, 2009

A great tip on how to include passwords when saving binding files. Not recommended for security reasons, however useful when you need to pre-configure many send/receive ports.

Check out the details -> here.


Configuring the MQSeries MQSC adapter

September 7, 2009

I recently had a requirement to receive and send data to an IBM WebSphere MQ server using Microsoft BizTalk Server 2006 R2.

There are two ways of achieving this:

  • Using the MQS adapter.
  • Using the MQSC adapter (client based).

In this case I was required to use the MQSC adapter as we were trying to connect to a non windows hosted MQ Series server. This post outlines what required to get communication happening (from the BizTalk Server side.)

Microsoft Host Integration Server

Microsoft Host Integration Server (HIS) is a gateway application providing connectivity between between Microsoft Windows networks and IBM mainframe and AS/400 systems. Support is also provided for advanced integration with Windows networks and software, such as linking Microsoft Message Queuing applications to IBM WebSphere MQ, binding Microsoft DTC transactions with CICS, and cross-protocol access to DB2 databases on IBM platforms.

The MQSC Adapter is not available as part of a standard BizTalk Server 2006 R2 install. This adapter is included as part of Microsoft Host Integration Server 2006 (HIS).

MQSC Client For WebSphere MQ

The MQSC Client for WebSphere MQ allows the use of MQSC commands either directly connected to a queue manager, or via a client connection to the queue manager. It also provides a number of formatting options for the display of the results to the commands.

The MQSC Client for WebSphere MQ is required as a pre-requisite when using the Microsoft Host Integration Server MQSC adapter.

1. Downloading pre-requsities

  • Download Host Integration Server 2006 (This can be located within MSDN subscriber dowloads).
  • Download MQSC Client for WebSphere MQ. (This can be located from the IBM website Here. For our installation purpose, I downloaded and used version “6.0.2.4 Clients”.

2. Installation

Installation of the MQSC Client for WebSphere MQ is simple. When installing choose the default setup suggestions.

When installing the Host Integration Server 2006, the only component required to be installed is the WebSphere MQ (Client Based) BizTalk adapter for host systems.

HostSystemsAdapters

This adapter connects BizTalk Server 2006 to remote MQSeries Queue Managers, using the WebSphere MQ Base Client (non-transactional) or WebSphere MQ Transactional Extended Client APIs.

3. Configuration

To configure your MQSC adapter receive/send ports you must supply the following information:

  • Chanel name
  • Connection name
  • Queue
  • Queue Manager

This configuration can be entered in the send/receive adapter configuration screen:

MQSC adapter receive location configuration

MQSC adapter receive location configuration

MQSC send port configuration

MQSC send port configuration

Troubleshooting

When originally configuring the MQSC I experienced the following error:

The adapter “MQSC” raised an error message. Details “The specified module could
not be found. (Exception from HRESULT: 0x8007007E) A dependency could not be
found. Refer to product documentation for information on MQSC Adapter software
prerequisites.”.For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

http://www-01.ibm.com/support/docview.wss?rs=171&context=SSFKSJ&dc=D400&dc=D410&dc=D420&dc=D430&q1=client&uid=swg24009961&loc=en%5FUS&cs=utf-8&lang=en&S%5FTACT=105AGX10&S%5FCMP=LP

This error is experienced when you are running an incompatible version of the MQSC Client for WebSphere MQ. Ensure you have installed a version of the MQSC client with a fix pack of 6.0.1.1 or higher.