Archive for August, 2008
|Configuration Interface||Command-Line and BizTalk Configuration Wizard||SharePoint Central Administration website|
|Encryption Key Management||Possible only via Command-Line||Possible only via website function "Manage Encryption Key"|
|Encryption Key Backup||Command-Line File Based, Can backup to any file location||Website Based, Can backup only to a removable drive|
|SSO MMC Capability?||Exists as an MMC, can be loaded remotely with appropriate BizTalk install||MMC does not exist, cannot be configured remotely.|
|Requires RDP access for SSO configuration?||No||Yes|
|Group Setup for SSO||SSO Administrators, SSO Affiliate Administrators, SSO Service Account||SSO Administrators, SSO Administrator Account, SSO Service Account|
|Requires SSO Service Account to be process identity for configuration?||No||Yes|
|SSO delegation options||Credential based on port configuration||Credential variability options – Group and Individual options.|
|Runs as Windows Service?||Yes||Yes|
|Required on all servers in Farm?||No||Yes|
|Operates out of an SSO database?||Yes||Yes|
|Command-line options for SSO?||Yes||Partial|
|Automatic Credential Update?||Yes||No|
The above table shows there are a considerable number of differences in the SSO configuration and functionality options of SSO across the two products. Perhaps in the future the two SSO products can provide a combination of the features in the chart above because both offer valuable options and would make an excellent combination together. A more consolidated SSO experience would also be helpful from a product administration perspective.
I recently wrote a blog post about avoiding some of the pitfalls of installing BizTalk Server 2006 R2 onto Windows Server 2008. One of the gaps in my post was that I did not mention all of the roles and features that I used when configuring Windows Server 2008 prior to installing BizTalk. Since there is really very little documentation out there on MSDN for BizTalk installs onto Windows Server 2008, I wanted to help clear up the documentation gaps so that others could get this latest version of the Windows Server running for their BizTalk environment.
For this BizTalk project, I was primarily using FILE, MSMQ, and the WebSphere MQ (MQSC) adapters in case you are wondering. Here is a photo of the roles and features that I configured in order to get BizTalk to run successfully:
On Windows Server 2008 the initial page that loads is called the Server Manager and includes an excellent overview of the configuration of the server. The screenshot I provided above came from the Server Manager’s section for Windows Server 2008 configured roles and features. This list of roles and features does not cover all BizTalk features so you may be required to add other roles or features for BizTalk adapters other than the ones I used.