Configuration

Overview of Configuration

BizTalk Server can be configured with either Basic Configuration settings or Custom Configuration settings.

• Basic Configuration : This configuration will take care of setting up all the required settings with the help of BizTalk server but this is not the way usually the BizTalk Server configured in production environment, because, this configuration mode will not allow to use remote SQL Server. To learn pros and cons about this configuration, have a look at this link.
• Custom Configuration (Recommended): This configuration mode provides a high-level analysis on the configuration state of the features that have been installed on the local machines (BizTalk Server). This way of configuration allows you to configure/unconfigure features, configure security settings and import/export configurations. To learn more about Custom Configuration, have a look at this link.

Let's see how to configure BizTalk Server 2010 using Custom Configuration mode.

Note: You may come across with few questions about BizTalk Databases, Roles, Host & Host Instances and it's uses. Just follow the configuration. I will explain later in my post about these.

Configuration

This section will explain you to how to configure BizTalk Server 2010 as a standalone server by following the steps in this section. Let see how you can configure a standalone server. Run BizTalk Server Configuration application with administrator rights (Run as Administrator) by choosing Start -> All Programs -> Microsoft BizTalk Server 2010 -> BizTalk Server Configuration. You need to right-click on BizTalk Server Configuration and then select Run as Administrator option to run under administration rights otherwise you cannot configure BizTalk server.

Note: You can even configure a BizTalk Server as a part of an existing BizTalk Server as a group. 

Specifying BizTalk Core Database and User Credential: In the "Microsoft BizTalk Server Configuration - Start" - dialog box,

• Select the configuration type as “Custom configuration”
• Specify the “Database server name” where BizTalk’s core databases need to be created.
• Specify an administrator credential to “Service credential” option. Note: this credential should be the administrator in BizTalk Server box and SQL Database (/w System Admin permission)
• And click on “Configure” button to proceed. 

       Note: Configuration dialog box will show a warning message when specify user credential to confirm that the given Service Credential has the administrative privileges. Click “Yes” to proceed

Import/Export Configuration: (We are not going to use this option now.) If you already have a BizTalk configuration file (.xml), you can import that file using option "Import Configuration".

Configuring Single Sign-On (SSO): BizTalk Server leverages the Enterprise Single Sign-On (SSO capabiliities for securely storing critical information such as secure configuration properties for the BizTalk adapters. BizTalk Server automatically installs SSO on every computer where you install the BizTalk server runtime. You must install at least one SSO Server (it can be a local computer where BizTalk installed) If you have a custom installation of the BizTalk Administration Console and/or BizTalk Explorer. In our training, we are doing BizTalk Server custom installation. So you need to configure SSO. Click on this link to know more about "Installing Enterprise SSO in a BizTalk Server Environment".
Note: SSO Server may be a local computer where you have installed the BizTalk Server runtime or it can be a separate and/or standalone server.

• Click on "Enterprise SSO" node on the left-hand side options.

• Tick the check-box "Enable Enterprise Single Sign-On on this computer" to configure this server with SSO settings (on the local box) 

• Create a new SSO System: Select this option if this is the first SSO server you are configuring in SSO system. Otherwise you can select “Join an existing SSO system” if you want to connect to an existing SSO system in the BizTalk Server environment.
• Database Source Name: This will be database source for SSO and the DB icon show that it is valid to create a database in the name “SSODB”. Otherwise it will show an error icon like  with error description.
• Server Name: this will show the SQL Server instance name which has specified in the first step
• Database name: This step will create a database SSODB in the given SQL Server.
• Windows Service: Specify a user account which should be a part of SSO Administrator group.
• Windows Accounts: Specify the group names for SSO Administrator(s) and SSO Affiliate Administrator(s).
• Click on “Enterprise SSO Secret Backup” node on left-side selection. Use this setup page to save the master secret to an encrypted backup file in the event that disaster recovery if needed.

• Secret backup password: Type the password for the backup file. Use one easy to remember password.
• Confirm password: Retype the same password to confirm.
• Password reminder: Type a reminder for the password you enter.
• Backup file location: Provide a file name and file path (default file & location) to the secret backup file. By default it is stored at “<drive>:\Program Files\Common Files\Enterprise Single Singe-On\”

             Consideration:

- When configuring the SSO Windows accounts using local accounts, you must specify the account name without the computer name

- When using a local SQL Server named instance as data store, you must use LocalMachineName\InstanceName instead of LocalMachineName\InstanceName, PortNumber.

Configuring BizTalk Server Group: In this section, the configuration creates BizTalk core databases. Though we are configuring standalone BizTalk server, still it is consider as a group. Later we can add a new server with this server.

• Select “Enable the BizTalk Server Group on this computer” to configure this server as a BizTalk Group. Note: You can configure currently configuring BizTalk server as a part of existing group also.
• Select “Create a new BizTalk Group” to create the BizTalk Server group that you will use to administer all the BizTalk Server databases (or) select “Join an Existing BizTalk Group” to join a BizTalk group that already exists.
• Analysis Database for Tracking Aggregations: There will be an option to create an analysis database for tracking aggregations if you have installed MS SQL Server Analysis Services in the server where you configure to create BizTalk core databases.
• Data Store: The data stores list provides an editable view of the BizTalk Server Management, MessageBox, and Tracking databases. Type the name of the server and database that you will use for each one. In this case, you just leave as-is.
• BizTalk Administrative Roles: Specify the BizTalk Administrators and Operators windows group.

Considerations: When using a local SQL Server named instance as data store, you must use LocalMachineName\InstanceName instead of LocalMachineName\InstanceName, PortNumber.

Configuring BizTalk Server Runtime: This step will create runtime environment. To create BT Server Runtime Host and Host Instances. BizTalk Server Runtime is the core engine of BizTalk Server, providing message routing capabilities.

• Select “Register the BizTalk Server runtime components” to enable host creation on this computer.
• Select “Create In-Process Host and Instance” to create a Host application on this computer.
• Host name: Type the name of the BizTalk Host. By default this is BizTalkServerApplication. (Leave as-is in this configuration)
• Trusted: Select this if you want to pass the credentials (SSID and/or Party ID) of the sender when submitting messages to the MessageBox database. This is equivalent to creating a trust relationship between the servers. In this configuration don’t select it.
• Select “Create Isolated Host and Instance” to create an Isolated Host application on this computer.
• Isolated host name: Type the name of the BizTalk Host. By default this is BizTalkServerIsolatedHost. (Leave as-is in this configuration)
• Trusted: Select this if you want to pass the credentials (SSID and/or Party ID) of the sender when submitting messages to the MessageBox database. This is equivalent to creating a trust relationship between the servers.
• Windows Server: Specify the service account for BizTalk Host Instance & Isolated Host Instance accounts. 
• Windows Group: Specify the windows group for Host Users & Isolated Host users.

Note: Restart the Enterprises SSO service must be necessary

Considerations: The first host you create in a group must be an In-Process host and host instance. In a multi-server environment in which you have two or more computers configured with BizTalk Server runtime and belonging to the same group, you cannot have the same service account used for both a trusted and untrusted host application

Business Rules Engine: This Business Rules Engine configuration will provide a tool called Business Rules Composer to integrate Business Rules into Orchestrations (process in the BizTalk called Orchestration).

• Select “Enable the Business Rules Engine on this computer” to configure this server with business rule engine.
• Data stores: specify the database name for Rules Engine Database.
• Windows Service: Specify a user account to run the rule engine update service.

Considerations: Microsoft recommends that you configure a BizTalk Server group before you configure BRE. If you configure the BRE before configuring a BizTalk Server group, the BizTalk Server configuration does not add group-related administrative roles to the Rule Engine database.

Apply Configuration: So far you have just specified the details to configure. This will be applied to the server only when you say "Apply Configuration". To finalize the configuration, click on "Apply Configuration"

Verify the configuration before click on "Next" on the above shown dialog box.

Click on the “Finish” button to complete the configuration of SSO, Group, Runtime, and BRE

Note: You can apply the configuration one by one rather applying all settings together at the end.

You should see the final window after configuring all setup on BizTalk Server as given below.

Prev: Installation