Hi,

We have an orchestration deployed as a web service. Our environment has 2
hosts for high availability, which share the same Biztalk database, again
clustered for high availability.

The issue we are having is that we have to deploy the web service on both
the hosts. We build and deploy the orchestration on host 1, and publish it a
s
a Web service.

When we get to the second host, we can build the orchestration, and deploy
it as a web service. But we are not able to deploy the orchestration as it i
s
already deployed to the Biztalk database. To be able to deploy it from this
host, we need to undeploy the already installed instance. I have manually
copied the orchestration dll and dependencies to the GAC. But the web servic
e
suspends the orchestration on the second node which was configured, even
though the first node works fine.

What am I doing wrong here? What is the correct way to deploy the
orchestration and publish the web service in the second node?

Thanks,
Adarsh

[ Post a follow-up to this message ]

There was a help update around 8/10.
This page describes what you are asking about :


ms-help://BTS_2004/Deploying/htm/ebiz_depl_assemblies_izlg.htm

In Visual Studio .NET 2003, you can install BizTalk assemblies in the GAC at
the same time as you deploy them.

To install an assembly in the GAC using Visual Studio .NET

Copy the BizTalk assembly to your local computer into a folder such as C:\My
BizTalk Assemblies.
Open the Visual Studio .NET 2003 command prompt. See Using the BTSdeploy
Command Line Tool.
In the \ProgramFiles\Microsoft Visual Studio .NET 2003\SDK\v1.1\Bin
directory, type the following command:
<path>gacutil.exe /if "<pathname to the BizTalk assembly .dll>"

Note  gacutil.exe is located in <drive>\ProgramFiles\Microsoft Visual Studio
.NET 2003\SDK\v1.1\Bin



ms-help://BTS_2004/Deploying/htm/ebiz_asdepl_concepts_grbe.htm

When you deploy the assembly metadata, the assembly is registered in a
Configuration database and it can be installed in the GAC. Each of the
available deployment methods - the BizTalk Deployment Wizard, the BTSdeploy
command line tool, or the Visual StudioĀ® .NET 2003 deploy command - places
the assembly metadata into a Configuration database. You can install an
assembly in the GAC as a separate step using the GAC utility - gacutil. You
may need to do this when there are several servers that point to the same
database. For example, assume there is a group of BizTalk servers (A, B, and
C) that share a common Configuration database. To deploy BizTalk Assembly_X
to this group of servers, you would perform the following tasks:

Copy Assembly_X to Server_A, Server_B, and Server_C. Place the assembly in a
folder such as C:\My BizTalk Assemblies on each server.
On Server_A, install Assembly_X into the common Configuration database using
one of the deployment tools.
On Server_B and Server_C, from the Visual Studio .NET 2003 command prompt,
type the command:
<path>gacutil.exe /if "<path to AssemblyX>"


Note  By default, the gacutil.exe is located in
<drive>\ProgramFiles\Microsoft Visual Studio .NET 2003\SDK\v1.1\Bin.

Additionally, you must run gacutil.exe on Server_A if you have not already
installed in the GAC during deployment

Also: ms-help://BTS_2004/SDK/htm/ebiz_sdk_utils_btsinstaller_bvkn.htm

Neal Walters
http://Biztalk-Training.com  FREE Demos and Biztalk Videos

[ Post a follow-up to this message ]