BTS 2004 VS 2006
BIZTALK SERVER 2006 IMPROVEMENTS
“Applications” In Biztalk 2004
For each solution developed there are a set of inter-related artifacts (schemas, maps, pipelines, orchestrations, receive ports, receive locations, send ports, other...) that need to be managed. In BizTalk Server 2004 the idea of a formal application container did not exist.
The result was a mishmash of BizTalk artifacts that required thorough documentation to or access to the original developer ;) to understand their relation.
In Biztalk 2006
To improve the productivity of the developer and administrator, BizTalk Server 2006 introduces the BizTalk "Application”. In BizTalk 2006, an application is a logical grouping of all the BizTalk design-time artifacts (schemas, maps, pipelines, orchestrations), messaging components (receive ports, receive locations and send ports) and other related items such as policies that comprise an integrated business process. Therefore as the number of complex applications increases they can still be individually managed in a simple and intuitive manner.
Great… Isn’t it???
“BizTalk Administration Console”
In Biztalk 2004
To administrate Biztalk artifacts logon on to that server and open MMC.
To monitor message and services go to HAT.
To import binding files go to Biztalk Deployment wizard
To import policies go to Rules Engine deployment wizard.
In Biztalk 2006:
Every thing mention above will be achieved by going only to BizTalk Administration Console. It will be having ability to create, configure and manage one or more applications across multiple servers. Additionally, the MMC includes the ability to import and export applications for installation across multiple servers or for facilitating moving between staging and production environments.
Yes, you can view HAT as well in MMC.
Although message monitoring is no longer a function of HAT, Biztalk 2006 gives new “hub” pages which give an administrator visibility into messaging active within BizTalk in same MMC.
Also, you can import bindings/policies from same MMC.
“Artifacts Dependencies Hell”
In BizTalk Server 2004
We have to start, stop, enlist, and bind artifacts individually. As dependencies grew it was up to developer to understand all the dependencies between artifacts and to stop these artifacts in order based on their dependencies before deploying or redeploying.
In BizTalk Server 2006
Administration console makes it much, much easier. With a single click on the application, all the artifacts contained within will be started in the correct sequence and the application will instantly be ready to process messages
There is also significant improvement in Packaging Biztalk solution again through single MMC.
For each solution developed there are a set of inter-related artifacts (schemas, maps, pipelines, orchestrations, receive ports, receive locations, send ports, other...) that need to be managed. In BizTalk Server 2004 the idea of a formal application container did not exist.
The result was a mishmash of BizTalk artifacts that required thorough documentation to or access to the original developer ;) to understand their relation.
In Biztalk 2006
To improve the productivity of the developer and administrator, BizTalk Server 2006 introduces the BizTalk "Application”. In BizTalk 2006, an application is a logical grouping of all the BizTalk design-time artifacts (schemas, maps, pipelines, orchestrations), messaging components (receive ports, receive locations and send ports) and other related items such as policies that comprise an integrated business process. Therefore as the number of complex applications increases they can still be individually managed in a simple and intuitive manner.
Great… Isn’t it???
“BizTalk Administration Console”
In Biztalk 2004
To administrate Biztalk artifacts logon on to that server and open MMC.
To monitor message and services go to HAT.
To import binding files go to Biztalk Deployment wizard
To import policies go to Rules Engine deployment wizard.
In Biztalk 2006:
Every thing mention above will be achieved by going only to BizTalk Administration Console. It will be having ability to create, configure and manage one or more applications across multiple servers. Additionally, the MMC includes the ability to import and export applications for installation across multiple servers or for facilitating moving between staging and production environments.
Yes, you can view HAT as well in MMC.
Although message monitoring is no longer a function of HAT, Biztalk 2006 gives new “hub” pages which give an administrator visibility into messaging active within BizTalk in same MMC.
Also, you can import bindings/policies from same MMC.
“Artifacts Dependencies Hell”
In BizTalk Server 2004
We have to start, stop, enlist, and bind artifacts individually. As dependencies grew it was up to developer to understand all the dependencies between artifacts and to stop these artifacts in order based on their dependencies before deploying or redeploying.
In BizTalk Server 2006
Administration console makes it much, much easier. With a single click on the application, all the artifacts contained within will be started in the correct sequence and the application will instantly be ready to process messages
There is also significant improvement in Packaging Biztalk solution again through single MMC.
