|
|
|
|
|
|
|
|
|
|
|
BizTalk 2009 : The BizTalk Management Database |
Unlike the Messagebox, the Management Database is not used to store messages and is not considered to be "working storage." The Management Database is where most configuration and system-level information is stored and accessed from within BizTalk. |
|
BizTalk 2009 : Handling Failed Messages and Errors |
To keep the Messagebox as empty as possible, the tracking subsystem will move completed messages to the Tracking Database on a periodic basis. This is accomplished by a BizTalk host that has been tagged as a "tracking" host by specifying an option in the Host Properties page. |
|
|
|
|
Microsoft Dynamics GP 2010 : Creating an ODBC data source |
Every computer that needs to run the Dynamics GP application will need to have an ODBC (Open Database Connectivity) data source pointing to the SQL Server. This is true for all servers and workstations, including the server where SQL Server is installed. |
|
|
|
|
|
|
|
Extending Microsoft Dynamics CRM 4.0 : IFrames |
IFrames are “inline frames or windowless inline floating frames” and provide an easy mechanism for integrating data, because they can exist free form or easily pass data through them to the underlying source. |
|
|
|
|
BizTalk 2009 : Understanding the Message Bus |
The Message Bus is the backbone of the BizTalk Server product. The bus contains unique parts, each of which are explained later in the subsection "Messaging Components." The most obvious of these is the Messagebox, which is explained first. |
|
|
BizTalk Server 2006 Operations : Disaster Recovery |
A disaster recovery plan must include steps to bring the backup site online as well as steps to deal with potential data loss as a result of the major system disruption. BizTalk Server 2006-based solutions require a comprehensive disaster recovery plan that covers both the BizTalk servers and the BizTalk Group running in SQL Server. |
|