Every COM+ application that can run XLANG schedule instances, such as the default XLANG Scheduler, also has a database associated with it. This Orchestration Persistence database is linked using a data source name (DSN). Database authentication should be done through Windows 2000 authentication, not SQL Server authentication. One reason for this is that Windows authentication is regarded as more secure. Going through Windows will also allow you to use Delegate for impersonation levels, since Kerberos v5 has to be used.
As you can see in Figure 8.22, when you choose Windows Authentication, you are able to explicitly grant or deny a user or group access to the database.
Next, you need to administer these SQL Server users for BizTalk Server:
1. Open the BizTalk Server Administration tool (Start | Programs | BizTalk Server 2000 | BizTalk Server Administration).
2. Select Microsoft BizTalk Server 2000, right-click it, and select Properties.
3. Change User name to sa_InterchangeBTM, and the Password to whatever you choose when creating the user.
5. Expand Microsoft BizTalk Server 2000.
6. Select BizTalk Server Group, right-click it, and select Properties.
7. Click the Connection tab.
8. Change the User name and Password for the Tracking database and Shared Queue database.
9. Press OK and restart BizTalk Server.
Was this article helpful?