|
Home > Archive > BizTalk Server Orchestration > November 2004 > OnStart event on the orchestration ?
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 |
OnStart event on the orchestration ?
|
|
|
| Hello,
I would like to know if it is possible to catch
an "OnStart" event when the orchestration is launched ?
.... and to add some c# code .
(something similar than the ApplicationOnStart in the
global.asax)
I would like to initialize a static variable to use with
orchestrations.
Thanks,
arno
| |
| Nabeel Prior 2004-11-19, 2:46 am |
| Would it not suffice to add an expression editor as the first step in your
orchestration after receiving the message, and use this to set a variable
that will be used in the other stages of the orchestration?
--
Kind Regards,
Nabeel Prior
Web: http://www.brainjar.co.za
Blog: http://www.brainjar.co.za/blog.aspx
"arno" <anonymous@discussions.microsoft.com> wrote in message
news:80ec01c4ce13$0013e1e0$a301280a@phx.gbl...
> Hello,
>
> I would like to know if it is possible to catch
> an "OnStart" event when the orchestration is launched ?
>
> ... and to add some c# code .
>
> (something similar than the ApplicationOnStart in the
> global.asax)
>
> I would like to initialize a static variable to use with
> orchestrations.
>
> Thanks,
> arno
| |
| Hugo Rodger-Brown 2004-11-19, 7:46 am |
| Arno - you'd have to call the C# component from an expression shape as the
first shape in the orchestration. If the C# component was designed as a
singleton, then the first orchestration instance to call it would set
initialise the component, and all subsequent orchestration instances would
reference this object.
However, even if you created a singleton C# object that was called by each
orchestration, this would only be shared across orchestrations running on
the same machine - limiting the core scale-out design of BizTalk.
What is the exact scenario - there are config files or business rules
scenarios that might work?
Hugo
http://hugo.rodger-brown.com
| |
|
| Hi hugo,
Thanks for your answer.
So, i test my component using 2 orchestrations.
My singleton class seems to be created only one time which
is a good new ;-)
So, It means that i can share data value :
- between different calls for the same orchestration
- between different orchestrations.
Every orchestrations reside in the process (and in same
appdomain ???) , it explains why it works.
I don't have any business rules in my component, it's only
a data access component to a specific database ...
I've got a config file but I will read it in a specific
directory if the assembly is executed from the GAC.
Thanks,
arno
>-----Original Message-----
>Arno - you'd have to call the C# component from an
expression shape as the
>first shape in the orchestration. If the C# component was
designed as a
>singleton, then the first orchestration instance to call
it would set
>initialise the component, and all subsequent
orchestration instances would
>reference this object.
>
>However, even if you created a singleton C# object that
was called by each
>orchestration, this would only be shared across
orchestrations running on
>the same machine - limiting the core scale-out design of
BizTalk.
>
>What is the exact scenario - there are config files or
business rules
>scenarios that might work?
>
>Hugo
>http://hugo.rodger-brown.com
>
>
>.
>
|
|
|
|
|