|
Home > Archive > BizTalk Server General > June 2006 > deploying (upgrading) BizTalk solutions
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
deploying (upgrading) BizTalk solutions
|
|
| Przemo 2005-09-13, 6:00 pm |
| Hi,
I have a very simple messaging solution based on the newest avaliable
version of BTS 2006 and VS.NET 2005. It transforms one xml schema into
another without orchestration.
But when I make some changes to map and schemas and deploy it to a server
(the same computer as development) BizTalk still works on the old project.
It show in managemet console new maps, the new assembly is also in GAC.
I start and stop my Biztalk application and also unelist and enlist the ports.
The only thing which works is to stop and start an instance of BTS which is
hosting my application. But that host can host also some other applications
on a production server and it is not intended to stop it all.
Do you have some suggestions?
przemo
| |
|
| I had similar problems and the only solution was to restart the host
application as you said. Perhaps you could move it out into its own biztalk
application.
"Przemo" wrote:
> Hi,
>
> I have a very simple messaging solution based on the newest avaliable
> version of BTS 2006 and VS.NET 2005. It transforms one xml schema into
> another without orchestration.
> But when I make some changes to map and schemas and deploy it to a server
> (the same computer as development) BizTalk still works on the old project.
> It show in managemet console new maps, the new assembly is also in GAC.
> I start and stop my Biztalk application and also unelist and enlist the ports.
>
> The only thing which works is to stop and start an instance of BTS which is
> hosting my application. But that host can host also some other applications
> on a production server and it is not intended to stop it all.
>
> Do you have some suggestions?
>
> przemo
| |
| Doug Girard [MSFT] 2006-06-06, 7:20 pm |
| Everytime you update a same-named BizTalk assembly, you'll need to restart
all of the host instances which it runs on for the change to take effect.
This is just how the .NET runtime works. It maintains a cache in memory
and runs off of this working copy. You'll need to restart the host
instances for them to pick up the new copy from the GAC.
If you're interested in finding out more about application deployment and
upgrade in BizTalk Server 2006, we've just released a whitepaper on the
subject which should assist. You can download "BizTalk Server 2006:
Understanding Application Deployment and Upgrade" from:
http://download.microsoft.com/downl...89-aca6-2577e71
512f7/UnderstandBTSAppDepl.doc
Hopefully this helps to demystify the requirements of application
deployments and upgrades.
HTH,
Doug Girard [MSFT]
Note: This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
>Thread-Topic: deploying (upgrading) BizTalk solutions
>thread-index: AcW6D4KHI7ltfYpIRM6meXaieI9ofQ==
>X-WBNR-Posting-Host: 130.76.96.17
>From: "=?Utf-8?B?c29saWQ=?=" <solid@discussions.microsoft.com>
>References: <D63207DC-C4C0-4D4A-8577-30ACB0EF22A9@microsoft.com>
>Subject: RE: deploying (upgrading) BizTalk solutions
>Date: Thu, 15 Sep 2005 09:07:02 -0700
>Lines: 23
>Message-ID: <E4732160-BB90-4150-93C0-163A9BD244F6@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.biztalk.general
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.biztalk.general:17559
>X-Tomcat-NG: microsoft.public.biztalk.general
>
>I had similar problems and the only solution was to restart the host
>application as you said. Perhaps you could move it out into its own
biztalk
>application.
>
>"Przemo" wrote:
>
server[vbcol=seagreen]
project.[vbcol=seagreen]
ports.[vbcol=seagreen]
is[vbcol=seagreen]
applications[vbcol=seagreen]
>
| |
|
| Doug,
I have a question on MSI deployment of Biztalk Application in Biztalk 2006.
In Biztalk 2004 when we used the BTSInstaller we can set the "Install" path
in the proprties of the BTSInstaller Project.
But in Biztalk 2006 we use "Biztalk Admin Console" for creating the MSI and
there is no place where we can set the "Target Install Path".
Is there any way to set the "Target Install Path" in Biztalk 2006 so that
th person installing doesnt have to select the path manually for each
installation.
You help on this would be greatly apreciated.
Thanks in advance.
--
Thanks and Regards,
Gan
"Doug Girard [MSFT]" wrote:
> Everytime you update a same-named BizTalk assembly, you'll need to restart
> all of the host instances which it runs on for the change to take effect.
> This is just how the .NET runtime works. It maintains a cache in memory
> and runs off of this working copy. You'll need to restart the host
> instances for them to pick up the new copy from the GAC.
>
> If you're interested in finding out more about application deployment and
> upgrade in BizTalk Server 2006, we've just released a whitepaper on the
> subject which should assist. You can download "BizTalk Server 2006:
> Understanding Application Deployment and Upgrade" from:
> http://download.microsoft.com/downl...89-aca6-2577e71
> 512f7/UnderstandBTSAppDepl.doc
>
> Hopefully this helps to demystify the requirements of application
> deployments and upgrades.
>
> HTH,
> Doug Girard [MSFT]
>
> Note: This posting is provided "AS IS" with no warranties, and confers no
> rights.
> --------------------
> biztalk
> server
> project.
> ports.
> is
> applications
>
>
| |
| Doug Girard [MSFT] 2006-06-08, 7:18 pm |
| I've answered this on your original thread.
Thanks,
Doug Girard [MSFT]
Note: This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
>Thread-Topic: deploying (upgrading) BizTalk solutions
>thread-index: AcaKbc0xMryVuHxhTGWS2+tJa+4A5Q==
>X-WBNR-Posting-Host: 63.76.56.130
>From: =?Utf-8?B?R2Fu?= <Gan@discussions.microsoft.com>
>References: <E4732160-BB90-4150-93C0-163A9BD244F6@microsoft.com>
<j$oGOlaiGHA.5608@TK2MSFTNGXA01.phx.gbl>
>Subject: RE: deploying (upgrading) BizTalk solutions
>Date: Wed, 7 Jun 2006 13:06:02 -0700
>Lines: 99
>Message-ID: <8DBA813F-561B-4C1A-9DC2-34A651680530@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.biztalk.general
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.biztalk.general:38132
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.biztalk.general
>
>Doug,
>
>I have a question on MSI deployment of Biztalk Application in Biztalk 2006.
>In Biztalk 2004 when we used the BTSInstaller we can set the "Install"
path
>in the proprties of the BTSInstaller Project.
>But in Biztalk 2006 we use "Biztalk Admin Console" for creating the MSI
and
>there is no place where we can set the "Target Install Path".
>
>Is there any way to set the "Target Install Path" in Biztalk 2006 so that
>th person installing doesnt have to select the path manually for each
>installation.
>
>You help on this would be greatly apreciated.
>Thanks in advance.
>--
>Thanks and Regards,
>Gan
>
>
>"Doug Girard [MSFT]" wrote:
>
restart[vbcol=seagreen]
effect.[vbcol=seagreen]
and[vbcol=seagreen]
http://download.microsoft.com/downl...89-aca6-2577e71[vbcol=seagreen]
no[vbcol=seagreen]
into[vbcol=seagreen]
GAC.[vbcol=seagreen]
the[vbcol=seagreen]
which[vbcol=seagreen]
>
|
|
|
|
|