I have two web services both hosted on my BizTalk server, both generated
using the BizTalk Web Services Publishing Wizard. On my development server,
the two web services are each hosted in a virtual application under the
server's default web site. On my production server, I have a separate IP
address and web site dedicated to each web service. I haven't been able to
find any way to generate an msi file for my application that will deploy the
web services anywhere other than under the default web site. So I end up
deploying them under the default web site on the production server and then
moving them to where I really want them to be. Is there an easier, better
way?

Thanks,
Zoe

[ Post a follow-up to this message ]

Hi Zoe,

It's possible to do this, but you have to setup your own setup project
for the webservice (that outputs a separate MSI) and then define
custom actions to do what you want.

HTH,

Dick Dijkstra

On Nov 7, 9:50 pm, "Zoe Hart" <zoe.h...@nospam.competitive.com> wrote:
> I have two web services both hosted on my BizTalk server, both generated
> using the BizTalk Web Services Publishing Wizard. On my development server
,
> the two web services are each hosted in a virtual application under the
> server's default web site. On my production server, I have a separate IP
> address and web site dedicated to each web service. I haven't been able to
> find any way to generate an msi file for my application that will deploy t
he
> web services anywhere other than under the default web site. So I end up
> deploying them under the default web site on the production server and the
n
> moving them to where I really want them to be. Is there an easier, better
> way?
>
> Thanks,
> Zoe

[ Post a follow-up to this message ]

another option would be to write a script and include it in your msi.
BizTalk supports running scripts before or after install or import.  Your
script could move the application to the other server after install and do
any other configuration you needed.

Using Pre- and Post-processing Scripts to Customize Application Deployment
http://msdn2.microsoft.com/en-us/library/aa559904.aspx

Matt

"Zoe Hart" <zoe.hart@nospam.competitive.com> wrote in message
news:uaKvX$XIIHA.4272@TK2MSFTNGP05.phx.gbl...
>I have two web services both hosted on my BizTalk server, both generated
>using the BizTalk Web Services Publishing Wizard. On my development server,
>the two web services are each hosted in a virtual application under the
>server's default web site. On my production server, I have a separate IP
>address and web site dedicated to each web service. I haven't been able to
>find any way to generate an msi file for my application that will deploy
>the web services anywhere other than under the default web site. So I end
>up deploying them under the default web site on the production server and
>then moving them to where I really want them to be. Is there an easier,
>better way?
>
> Thanks,
> Zoe
>

[ Post a follow-up to this message ]

I like the script option in that the tasks I need to do - move the files
from A to B - are pretty straightforward and easily scripted.
Thanks,
Zoe

"Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message
news:187B6BB9-7943-4CE9-A322-27424128828F@microsoft.com...
> another option would be to write a script and include it in your msi.
> BizTalk supports running scripts before or after install or import.  Your
> script could move the application to the other server after install and do
> any other configuration you needed.
>
> Using Pre- and Post-processing Scripts to Customize Application Deployment
> http://msdn2.microsoft.com/en-us/library/aa559904.aspx
>
> Matt
>
> "Zoe Hart" <zoe.hart@nospam.competitive.com> wrote in message
> news:uaKvX$XIIHA.4272@TK2MSFTNGP05.phx.gbl... 
>

[ Post a follow-up to this message ]

On Thu, 8 Nov 2007 14:07:25 -0500, "Zoe Hart"
<zoe.hart@nospam.competitive.com> wrote:

>I like the script option in that the tasks I need to do - move the files
>from A to B - are pretty straightforward and easily scripted.
Take a look here:
http://msdn2.microsoft.com/en-us/library/aa577889.aspx

You can add the virtual directories to your application manually, and
in there specify a different port for the destination virtual
directory. Then you only need your normal MSI.

I use it.

--
eliasen, representing himself and not the company he works for.

Private blog: http://blog.eliasen.dk

Private email: jan@eliasen.dk

[ Post a follow-up to this message ]

I like that even better. I'll try it.
Thanks,
Zoe

"Jan Eliasen" <eliasen@nospam.nospam> wrote in message
 news:hqo8j3lht6ucmmltr0akg0rlapseimdp3h@
4ax.com...
> On Thu, 8 Nov 2007 14:07:25 -0500, "Zoe Hart"
> <zoe.hart@nospam.competitive.com> wrote:
> 
> Take a look here:
> http://msdn2.microsoft.com/en-us/library/aa577889.aspx
>
> You can add the virtual directories to your application manually, and
> in there specify a different port for the destination virtual
> directory. Then you only need your normal MSI.
>
> I use it.
>
> --
> eliasen, representing himself and not the company he works for.
>
> Private blog: http://blog.eliasen.dk
>
> Private email: jan@eliasen.dk

[ Post a follow-up to this message ]

On Fri, 9 Nov 2007 14:12:20 -0500, "Zoe Hart"
<zoe.hart@nospam.competitive.com> wrote:

>I like that even better.
So do I :-)

--
eliasen, representing himself and not the company he works for.

Private blog: http://blog.eliasen.dk

Private email: jan@eliasen.dk

[ Post a follow-up to this message ]