Using BizTalk Messaging Manager
Microsoft® BizTalk™ Messaging Manager is a graphical user interface (UI) with which you can manage the exchange of documents by configuring BizTalk Messaging Services. BizTalk Messaging Services can also be configured programmatically using the BizTalk Configuration object model API. For more information, see Introducing Messaging Services.
- You should use BizTalk Messaging Manager to configure BizTalk Messaging Services prior to processing documents. Accessing and modifying objects that might be in use while Microsoft BizTalk Server 2002 is processing documents can produce unexpected results.
Documents can be exchanged between trading partners and applications within your business. BizTalk Messaging Manager is available both locally from the computer on which BizTalk Server 2002 is installed and remotely as a client application. This enables system administrators to retain security and central control of the server, while enabling remote users to access BizTalk Messaging Manager.
BizTalk Server 2002 Help provides information about how to create and manage the following BizTalk Messaging Manager objects:
BizTalk Server 2002 Help also provides information about how to use distribution lists.
BizTalk Messaging Manager objects
The following illustration shows the relationships between the objects that you can create by using BizTalk Messaging Manager.
The following summary provides a brief overview of the objects that you can create by using BizTalk Messaging Manager. This summary also further explains the relationship between the objects. For more detailed information about each object, click the link at the end of each description to go to the Help topic for that object.
Channels are the primary objects in BizTalk Messaging Manager. The purpose of all other BizTalk Messaging Manager objects is to either create channels or support the operation of channels. Channels identify the source of documents, which can be an organization, an application within your business, or an XLANG schedule. Channels also identify inbound and outbound documents by using document definitions. For more information, see Understanding Channels.
Messaging ports identify a destination for the documents that are processed by a channel. The destination can be an organization, an application within your business, or an XLANG schedule. A messaging port specifies a destination address to which the documents are sent, how they are transported to that address, and if and how they are secured and enveloped. For more information, see Understanding Messaging Ports.
Organizations represent other trading partners with which you exchange documents. A special organization type, called the home organization, represents your business. You can create applications for the home organization that represent the internal applications that your business uses. Organizations and applications serve as the source for a channel or the destination for a messaging port. For more information, see Understanding Organizations.
A document definition represents a specific type of document that is processed by BizTalk Server 2002. A document definition provides a pointer to a specification. Specifications define the document structure, type, and version. Channels specify an inbound and an outbound document definition to indicate which documents the server processes. A document definition can be used in any number of channels. For more information, see Understanding Document Definitions.
Envelopes provide BizTalk Server 2002 with the information that the server needs to either open inbound or create outbound interchanges. Envelopes can be selected from within a messaging port to direct the server in creating outbound interchanges. Envelopes, which are independent of a messaging port, can be used by BizTalk Server 2002 to open inbound interchanges. For more information, see Understanding Envelopes.
Distribution lists are groups of messaging ports with which you can send the same document to a group of different trading partner organizations or internal applications. You must create at least one channel for a distribution list, just as you do for an individual messaging port. For more information, see Understanding Distribution Lists.
- The objects that you can create by using BizTalk Messaging Manager can also be created programmatically by using the BizTalk Messaging Configuration object model. For more information, see Understanding Messaging Services.
- The objects that you can create by using BizTalk Messaging Manager also use objects that you can create by using other BizTalk Messaging Services user interfaces. Channels use maps, which you can create by using BizTalk Mapper. Document definitions use document specifications, and envelopes use envelope specifications. You can create specifications by using BizTalk Editor.
The following topics are covered in this section:
- For comprehensive information about BizTalk Messaging Manager, see About BizTalk Messaging Manager.
- For quick reference about why you perform specific tasks, see Why Perform BizTalk Messaging Manager Tasks.
- For detailed procedures on how to accomplish tasks, see How to Perform BizTalk Messaging Manager Tasks.
Did you find this information useful? Please send your suggestions and comments about the documentation to BizTalk Server Documentation Feedback@microsoft.com