BizTalk Server General - Managing Orchestrations using WMI

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server General > November 2004 > Managing Orchestrations using WMI





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 Managing Orchestrations using WMI
Fazal

2004-11-12, 5:48 pm

Hi,
I am attempting to create batch files to completely manage orchestrations
in a production environment where Visual studio components or Biztalk
Explorer are not allowed. I liked the setup and cleanup batch files provided
in the samples and modified the same for our purposes.
Each time I use those batch files however, I am ending up with an unbound
orchestration. Here are the steps I am using

1. @BTSDeploy Deploy Assembly=%AssemblyDirectory% INSTALL=TRUE Log=Deploy
2. @BTSDeploy Import Binding=%BindingFileName% Log=Binding
3. @CScript /NoLogo "..\..\Admin\WMI\Enlist
Orchestration\VBScript\EnlistOrch.vbs" %OrchestrationName% %AssemblyName%
where the parameters are set up using SET commands.

Any help would be greatly appreciated.

Thanks,
Fazal

Danny Buysse

2004-11-14, 2:46 am

I think you should check your BindingFile you use if this is correct.
In particular you should check the SendPortRef and ReceivePortRef settings
of your services, they should correspond with entries in the
SendPortCollection and ReceivePortCollection.


"Fazal" wrote:

> Hi,
> I am attempting to create batch files to completely manage orchestrations
> in a production environment where Visual studio components or Biztalk
> Explorer are not allowed. I liked the setup and cleanup batch files provided
> in the samples and modified the same for our purposes.
> Each time I use those batch files however, I am ending up with an unbound
> orchestration. Here are the steps I am using
>
> 1. @BTSDeploy Deploy Assembly=%AssemblyDirectory% INSTALL=TRUE Log=Deploy
> 2. @BTSDeploy Import Binding=%BindingFileName% Log=Binding
> 3. @CScript /NoLogo "..\..\Admin\WMI\Enlist
> Orchestration\VBScript\EnlistOrch.vbs" %OrchestrationName% %AssemblyName%
> where the parameters are set up using SET commands.
>
> Any help would be greatly appreciated.
>
> Thanks,
> Fazal
>

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com