http://download.microsoft.com/download/a/d/a/d/aad035e6-e03b-4bea-ad9a-fa1ff8d10ca0/BTS06R2_OpReadiness.docx”rel=“nofollow noreferer”>Biztalk 业务指南:

Deploy shared artifacts in a separate application - If artifacts are going to be shared by two or more applications, deploy the shared artifacts into a separate application. For example, if two applications share a schema, place the schema in a separate application. We recommend this because only one artifact in a BizTalk group can have a single locally unique identifier (LUID). A LUID consists of the artifact name and optionally other attributes. If you include an artifact in one application, and then create a reference to it from another application, the referring application may not function correctly when you stop the application containing the artifact. This best practice applies to all artifact types except for files, such as Readme files and scripts, which are added to the application as a File type of artifact. This is because more than one file artifact with the same name can be deployed in a BizTalk group. Therefore, you can use a file having the same name in two or more applications. In this case, stopping one application will not impact the other application. For more information about adding file artifacts, see "How to Add a File to an Application" in BizTalk Server 2006 R2 Help at http://go.microsoft.com/fwlink/?LinkId=106818.

共用的图象在重新分享时实际上会带来变化,这是一个重大事件。 如果你增加图象或修改现有地图,就没有必要重建旧地图。 您可能不得不回收依赖的东道方,以使他们重新了解病情。 否则就应该是95%的 has。

我们把我们共同的方案和功能单独应用。

我不敢理解你的问题,如果我不在场的话,我就非常正确。

你们应该组织自己的计划,可以独立地部署到所有需要它的申请。 然后,在开发过程中,其他项目可以参考。 在部署后,如果对图象进行修改;只需要更新服务器上的图象组群;将保留从申请中提及的图象。

希望这一帮助。