Filed under: Biztalk 2004, Debugging, Problems | Tags: BizTalk, Biztalk Server 2004, Deploy, Gacutil, Re-Deploy, Schema
We recently found a blog post by Jon Flanders that has been very helpful in determing when to re-gac some libraries and when to re-deploy the whole solution… This chart shows all the possibilities in a very clear way. (more…)
Filed under: Biztalk 2004, Debugging | Tags: BizTalk, Biztalk Server 2004, BTSNTSVS.exe, Debugging, Pipeline, Pipeline Component
When you have a pipeline components created and you like to test the working of it, create a new Biztalk Server Project for testing purposes. Copy the pipeline components libraries to the next directory: “C:\Program Files\Microsoft BizTalk Server 2004\Pipeline Components”. Create a new pipeline and add the created pipeline components to the toolbar of Visual Studio. Insert the pipeline component in the pipeline and save your test project.
So there are several ways to test your pipeline components and you have to decide for you own what suits you the best. I’m now going to describe two ways of debugging a pipeline component. One possibility is installing a ‘dummy’ orchestrations bound to this pipeline component and push some messages through, and the second possibility is to use the pipeline.exe tool. (more…)
Filed under: Biztalk 2004, Covast EDI Accelerator | Tags: Accelerator, BizTalk, Biztalk Server 2004, Covast, document definitions, EDI, repository
You can have a server with Biztalk Server 2004 installed and Covast EDI Accelerator, but without Microsoft Visual Studio installed. When you want to install a new EDI message in Covast you have to generate the schema with Visual Studio, because this causes a process to run (xml2db.exe). This process installs the document definitions into the repository of Covast.
What if you don’t have Visual Studio installed?
How to install a schema without Visual Studio?
This is what I’m going to explain… (more…)
