Re: BizTalk 2004 Orchestration.
From: Scott Colestock (scolestock_at_nospam_usa.net)
Date: 03/21/05
- Next message: Shyam: "Re: NO Enterprise Single Sign-on service!"
- Previous message: kr_jck: "Re: To BizTalk Team: Why need the Promoted Properties? Distinguished Properties?"
- In reply to: Jeremy.Deats_at_gmail.com: "BizTalk 2004 Orchestration."
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 21 Mar 2005 16:06:53 -0600
If you do an installation similar to the one described here:
http://www.traceofthought.net/PermaLink,guid,8f9e9730-bbdf-4b78-8b0a-3aa7b1927e21.aspx
(but you also the SDK options)
you can have Visual Studio set up to deploy to a remote BizTalk server.
However, you might want to consider having the workflow admins you speak of
develop locally, and prepare packaged installations to run on your
production server.
Scott Colestock
www.traceofthought.net
<Jeremy.Deats@gmail.com> wrote in message
news:1111423806.817001.70690@z14g2000cwz.googlegroups.com...
> Can the BizTalk 2004 Orchestration desinger (VS.NET 2003 plug-in)
> operate on a clients desktop that does not have BizTalk 2004 Server
> installed? From the install steps I've seen this tool exist only on the
> the server.
>
> In our environment we various power users we plan to assign as Workflow
> administrators and this individuals will need to modify and create new
> Orcestrations.
>
> -Jeremy
>
- Next message: Shyam: "Re: NO Enterprise Single Sign-on service!"
- Previous message: kr_jck: "Re: To BizTalk Team: Why need the Promoted Properties? Distinguished Properties?"
- In reply to: Jeremy.Deats_at_gmail.com: "BizTalk 2004 Orchestration."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|