Configuring BizTalk Messaging Services
Microsoft® BizTalk™ Server 2002 provides two methods for configuring BizTalk Messaging Services to manage the exchange of documents between trading partners and applications within your business. You can either use BizTalk Messaging Manager, which is a graphical user interface (UI), or directly access the BizTalk Messaging Configuration object model.
Using BizTalk Messaging Manager or the BizTalk Messaging Configuration object model, you can create messaging ports and channels to manage the exchange of data. You also can create document definitions, envelopes, and organizations, which you use to create messaging ports and channels; and distribution lists, which are groups of messaging ports.
To use BizTalk Messaging Manager, you must:
- Belong to a user account in the BizTalk Server Administrators group, which is created when BizTalk Server 2002 is installed. Additional users can be added to this group as necessary. For more information about adding a user account, see Add users to the BizTalk Server Administrators group.
- Have full database access to the BizTalk Messaging Management database (InterchangeBTM), which means you are able to log in and have been granted the db_owner database role. For more information, see "How to grant a Windows user or group access to a database" in the Microsoft SQL Server online documentation.
Should you use BizTalk Messaging Manager or the BizTalk Messaging Configuration object model API?
BizTalk Messaging Manager enables you to access the BizTalk Messaging Configuration object model through a graphical user interface. Whether or not you use that interface depends on the amount and type of information available to you in your database. The BizTalk Messaging Configuration object model application programming interface (API) enables you to automate all or part of the configuration process, rather than entering the data for each individual entity into BizTalk Messaging Manager. In general, the more business partners you have, the more it benefits you to use the API to configure your messaging service.
For example, suppose a large manufacturing company (a "hub" in the hub-spoke paradigm) uses 1,000 suppliers and maintains a database with information about each supplier. During the "create organizations" step, it would be relatively quick and easy to write code that:
- Extracts information from the database.
- Uses the BizTalk Messaging Configuration object model to programmatically create these 1,000 organizations in the BizTalk Messaging Management database.
In contrast, it could take considerably longer to create all 1,000 objects one-by-one using BizTalk Messaging Manager. (Imagine running the same wizard 1,000 times.) And that is to create only the organizations, not the document definitions, channels, or messaging ports.
However, a small supply company (a "spoke") that maintains relationships with just a few trading partners would likely use BizTalk Messaging Manager to configure its entire messaging system rather than taking time to write specialized code.
For more information about accessing the BizTalk Messaging Configuration object model directly through the API, see Introducing Messaging Services.
The following topic is covered in this section:
Did you find this information useful? Please send your suggestions and comments about the documentation to BizTalk Server Documentation Feedback@microsoft.com