An update to BAM SSIS pre-requisites

I got a call today from a client who was doing his initial install of BizTalk 2009 and had a similar issue as described in my post Do I need to install SSIS on my BizTalk server to configure and use BAM? NO!  The difference was that he was using SQL Server 2008 and the…

0

Perms, perms, perms (or deploying BAM activities with cubes when Analysis Services runs as a different service account)

This will be the first of a two part blog post about real-world adventures in BAM deployment.  As time has proven over and over, permissions and environment variables tend to trip even the most careful planners up when deploying artifacts to non-development environments.   I have developed a BAM solution for a customer which has been…

0

The right tool for the right job

Here’s a little gem I discovered today.  I am running down a permissions issue with BAM and SQL Server Analysis Services.  On my local dev box, I wanted to fully emulate the permissions from my full-blown dev environment, so in my Services MMC, I changed the Analysis Services log on account from LocalSystem to the…

0

Do I need to install SSIS on my BizTalk server to configure and use BAM? NO!

The various supporting components required to support BizTalk are very well understood – we need Enterprise Single Sign On, SQL Server Database Services, SQL Server Integration Services if we’re running BAM Tools (plus Analysis Services if we’re enabling BAM Aggregations), SQL Server Notification Services if we are using BAM Alerts, IIS to support the BAM Portal,…

1

Setting up SSIS on a SQL Server which does not have a default SQL instance

This one caught me a few weeks ago setting up the infrastructure to support my BAM solution in a new environment.  Although the environment was already setup for BizTalk, it had never been configured for BAM.  I needed to install the SQL Workstation Components on the BizTalk servers, as well as SQL Server Integration Services…

2