The Configuration Framework enables you to quickly and easily change Microsoft BizTalk Server 2006 configuration at setup. In conjunction with the Microsoft Windows Installer (MSI), the Configuration Framework reads and reports the state of your computer and the configuration tasks requiring action.
When you configure BizTalk Server for the first time using the Configuration Wizard, the Configuration Framework generates an XML file (a configuration snapshot) that you can then modify (that is, change user names, passwords, and so on) and export to other computers. You save your configuration snapshot on the Configuration Summary page, part of the Configuration Wizard. You can use this snapshot to replicate your configuration as part of a scripted installation. This file is located at <BizTalk Installation Path>\ConfigMain.xml.
Note |
|---|
|
Passwords are not stored in the XML file. You must enter one before you use this file.
|
Configuration Framework Command Line Parameters
The following table describes the parameters you can run on the command line within the Configuration Framework.
|
Command Line Parameter
|
Description
|
|---|
|
/U
|
Unconfigures all features.
Note
You can delete BizTalk Server databases after you unconfigure BizTalk Server features. Do not delete BizTalk Server databases before you run this command.
Note
If you want to delete BizTalk Server databases after you unconfigure BizTalk Server features, we recommend that you use the net stop winmgmt command to stop the Windows Management Instrumentation (WMI) service, which may still be running.
|
|
/S
|
Silent configuration.
You must also pass the full path to the configuration XML that contains the features to install and configure. If /s is not passed, the tool runs in User Interface (UI) mode.
|
|
/L
|
-
Sets the full path to the log file (optional).
|
|
/H
|
-
Shows the valid command line parameters.
|
Sample Configuration XML File
The following is a sample configuration XML file with all features installed:
<Configuration>
<Feature Name="MessageQueuing" DisplayName="BizTalk Message Queuing Transport (MSMQT)" Version="1.0" Description="BizTalk native support for Message Queuing (MSMQ), which can work side by side with Windows Message Queuing.">
<MSMQT ID="{56FCE035-775C-4de8-9F68-D91C46C45939}" DisplayName="BizTalk Message Queuing" Description="BizTalk native support for Message Queuing (MSMQ), which can work side by side with Windows Message Queuing.">
<IPAddress />
<Server>ServerName</Server>
<RegisterInDNS>No</RegisterInDNS>
<IntegrateMQWithAD>No</IntegrateMQWithAD>
<Domain />
<MQRouter />
</MSMQT>
</Feature>
<Feature Name="RulesEngine" DisplayName="Business Rules Engine" Version="3.0" Description="BizTalk native support for declarative Business Rules." ConfigByDefault="true">
<SQL ID="{E6C5E071-D6EB-4c31-BFE6-CA16637FBEEB}" DisplayName="Rule Engine Database" Description="SQL Rule Store">
<Server>ServerName</Server>
<Database>BizTalkRuleEngineDb</Database>
<WindowsSecurity>yes</WindowsSecurity>
<UserName />
<Password />
</SQL>
<NTService ID="{6ABAD351-9C7B-423e-9FDE-3A5C52441C00}" DisplayName="Rule Engine Update Service" Description="Notification for the deployment/ undeployment of policies">
<UserName>domain\username</UserName>
<Domain />
<Password>
</Password>
</NTService>
</Feature>
<Feature Name="HwsBaseAssemblies" DisplayName="HWS Runtime" Version="1.0" Description="Components necessary to run Human Workflow Services workflows." />
<Feature Name="HwsWMIProvider" DisplayName="HWS WMI Provider" Version="1.0" Description="Human Workflow Services Administration WMI Provider" />
<Feature Name="MOT" DisplayName="BAM runtime" Version="1.0" Description="Tracking data decoding service used to move tracked data and persist it for query use." />
<Feature Name="BAMTools" DisplayName="Business Activity Monitoring tools" Version="1.0" Description="Tools for the creation and maintenance of the SQL Server and Analysis Server (OLAP) infrastructure for Business Activity Monitoring." ConfigByDefault="true">
<SQL ID="{E1FC3106-8DD4-4f12-9EB6-849DD8BDD605}" DisplayName="BAM Primary Import Database" Description="SQL database used to store the events from the Business Activities and then query for the progress and data of the activity instances. This database is also used for real-time aggregations.">
<Server>ServerName</Server>
<Database>BAMPrimaryImport</Database>
<WindowsSecurity Editable="no">yes</WindowsSecurity>
<UserName />
<Password />
</SQL>
<SQL ID="{1D372BCB-DF59-43b6-A4A9-87082B5727B0}" DisplayName="BAM Archive Database" Description="SQL database used for archiving the Business Activity data which is too old. It is recommended to create the BAM Archive database to minimize the accumulation of Business Activity data in the BAM Primary Import Database.">
<Server>ServerName</Server>
<Database>BAMArchive</Database>
<WindowsSecurity Editable="no">yes</WindowsSecurity>
<UserName />
<Password />
</SQL>
<Question ID="{12A38787-6B24-40ab-8888-5FE8ABA87B26}" Text="Enable A&nalysis Services for BAM aggregations" Answers="Yes,No" Default="Yes">
<Answer Value="Yes" GUID="{902F7E20-D6AE-453f-9D23-935ED7AF94C3}" Selected="Yes">
<SQL ID="{16567D1E-6946-4f4e-BB3F-900DE2648328}" DisplayName="BAM Analysis Database" Description="Analysis Services database that keeps the aggregated historical data for Business Activities" MSOLAPServer="Yes">
<Server>ServerName</Server>
<Database>BAMAnalysis</Database>
<WindowsSecurity Editable="no">yes</WindowsSecurity>
<UserName />
<Password />
</SQL>
<SQL ID="{B973DB76-BA7F-4a2e-A57E-07EEF54B37A8}" DisplayName="BAM Star Schema Database" Description="SQL database used to transform the data collected from the Business Activity Monitoring for OLAP Processing. This database is required when the BAM Analysis database is used.">
<Server>ServerName</Server>
<Database>BAMStarSchema</Database>
<WindowsSecurity Editable="no">yes</WindowsSecurity>
<UserName />
<Password />
</SQL>
</Answer>
<Answer Value="No" GUID="{FC612DFE-1273-4f57-8EE3-95216638A67B}" />
</Question>
<Question ID="{308cc88b-9e51-4103-ae4c-73300e02a7eb}" Text="&Enable SQL Notification Services for BAM alerts" Answers="Yes,No" Default="Yes">
<Answer Value="Yes" GUID="{458e1878-eae6-4e09-8e5c-ba516548ceac}" Selected="Yes">
<Name ID="{8B3212A1-44EA-46bc-A06C-75E289D1F840}" DisplayName="S&QL Server for Alerts Databases:" Description="Notification Services server for BAM Alerting." Hidden="false">
<Value>ServerName</Value>
</Name>
<Name ID="{1DAFDF2D-4377-415a-B1CA-2C5B3729A244}" DisplayName="Prefix for Alerts Database &Names:" Description="Notification Services database root name for BAM Alerting." Hidden="false">
<Value>BAMAlerts</Value>
</Name>
<NTService ID="{c116ba3f-06d0-48cf-b0a1-4b263b07250e}" DisplayName="BAM Notification Services User" Description="Windows account that will have permissions to access the data in the BAM Notification Services databases during Business Activity searches.">
<UserName>username</UserName>
<Domain>domain</Domain>
<Password>
</Password>
</NTService>
<Name ID="{33c8fd0a-c89d-4dd0-8b2b-2ddacc6620e6}" DisplayName="BAM Alerts &SMTP Server:" Description="SMTP server to use for sending out BAM Alerting messages." Hidden="false">
<Value>ServerName</Value>
</Name>
<Name ID="{335b35f5-ffc4-4c7e-8cfc-582ec6bab9e0}" DisplayName="BAM Alerts File &Location:" Description="File system location to use for writing out BAM Alerting messages. If you accept this default location for delivering alerts by file, Configuration will create the file share and grant write permissions to the SQL NS service account and the current logged-on user." Hidden="false">
<Value>\\ServerName\alerts</Value>
</Name>
</Answer>
<Answer Value="No" GUID="{3d95a679-aa37-403f-bf64-194e6aa2d993}" />
</Question>
<Question ID="{FC99D786-2D26-489b-A748-42AE4DD0F6FC}" Text="&Remove the Business Activity Monitoring tools for this Biztalk Group" Answers="Yes,No" Default="No">
<Answer Value="Yes" GUID="{4CF85429-F0DA-4ca3-8068-D125506A3FD9}" />
<Answer Value="No" GUID="{5823E008-032F-4917-9EE5-B0AB4A18325C}" Selected="Yes" />
</Question>
</Feature>
<Feature Name="Engine" DisplayName="Business Activity Services SharePoint pipeline" Version="1.0" Description="The pipeline used by BAS orchestrations to exchange messages with SharePoint Services." />
<Feature Name="WssAdapterWS" DisplayName="Windows SharePoint Services Adapter" Version="1.0" Description="The SharePoint adapter used by Business Activity Services." ConfigByDefault="true">
<Question ID="WSS_ADAPTER_ENABLE_QUESTION" Text="Do you want to enable the Windows SharePoint Services Adapter?" Answers="Yes" Default="Yes">
<Answer Value="Yes" GUID="WSS_ADAPTER_ENABLE_YES" Selected="Yes">
<WebSite ID="WSS_ADAPTER_WEBSITE" DisplayName="Windows &SharePoint Services Adapter Web Site:" Description="The web site on which the Windows SharePoint Services Adapter will be installed.">
<WebSiteName>Default Web Site</WebSiteName>
</WebSite>
<NTCredential ID="WSS_ADAPTER_GROUP" DisplayName="BizTalk SharePoint Adapter Enabled Hosts" Description="The Windows group which has permissions to call the Windows SharePoint Services Adapter web services.">
<NTAccount ScopeType="105" UpLevelFlags="672" DownLevelFlags="2147516422">ServerName\SharePoint Enabled Hosts</NTAccount>
</NTCredential>
</Answer>
</Question>
</Feature>
<InstalledFeature>Documentation</InstalledFeature>
<InstalledFeature>SDK</InstalledFeature>
<InstalledFeature>Migration</InstalledFeature>
<InstalledFeature>EDI</InstalledFeature>
<InstalledFeature>BizTalk</InstalledFeature>
<InstalledFeature>WMI</InstalledFeature>
<InstalledFeature>Runtime</InstalledFeature>
<InstalledFeature>Engine</InstalledFeature>
<InstalledFeature>MOT</InstalledFeature>
<InstalledFeature>HwsBaseAssemblies</InstalledFeature>
<InstalledFeature>MessageQueuing</InstalledFeature>
<InstalledFeature>MSMQ</InstalledFeature>
<InstalledFeature>HwsRuntime</InstalledFeature>
<InstalledFeature>InfoWorkerApps</InstalledFeature>
<InstalledFeature>BusActSvcs</InstalledFeature>
<InstalledFeature>BusActSvcsTPM</InstalledFeature>
<InstalledFeature>BAMPortal</InstalledFeature>
<InstalledFeature>HwsWebService</InstalledFeature>
<InstalledFeature>AdminAndMonitoring</InstalledFeature>
<InstalledFeature>AdminTools</InstalledFeature>
<InstalledFeature>MonitoringAndTracking</InstalledFeature>
<InstalledFeature>BizTalkAdminSnapIn</InstalledFeature>
<InstalledFeature>HealthActivityClient</InstalledFeature>
<InstalledFeature>BAMTools</InstalledFeature>
<InstalledFeature>HwsWMIProvider</InstalledFeature>
<InstalledFeature>Development</InstalledFeature>
<InstalledFeature>VSTools</InstalledFeature>
<InstalledFeature>BizTalkExtensions</InstalledFeature>
<InstalledFeature>BizTalkExplorer</InstalledFeature>
<InstalledFeature>Designer</InstalledFeature>
<InstalledFeature>OrchestrationDesigner</InstalledFeature>
<InstalledFeature>PipelineDesigner</InstalledFeature>
<InstalledFeature>XMLTools</InstalledFeature>
<InstalledFeature>AdapterImportWizard</InstalledFeature>
<InstalledFeature>HwsDesigner</InstalledFeature>
<InstalledFeature>BasSchemaExtension</InstalledFeature>
<InstalledFeature>DeploymentWizard</InstalledFeature>
<InstalledFeature>TrackingProfileEditor</InstalledFeature>
<InstalledFeature>AdditionalApps</InstalledFeature>
<InstalledFeature>SSOAdmin</InstalledFeature>
<InstalledFeature>SSOServer</InstalledFeature>
<InstalledFeature>RulesEngine</InstalledFeature>
<InstalledFeature>WssAdapterWS</InstalledFeature>
<InstalledFeature>OLAPNS</InstalledFeature>
<InstalledFeature>FBAMCLIENT</InstalledFeature>
<InstalledFeature>BAMEVENTAPI</InstalledFeature>
</Configuration>
Concepts
Feature Dependency Matrix
Other Resources
Custom Configuration