tim lŠbÝŠÇ.²È¨žÉ¢rº,¡û\¢

Is it possible to test the MLLP connection inside an orchestration?
--
Thanks
Tim

eric stott

Why would you want to? What is the purpose?

Eric

tim lŠbÝŠÇ.²È¨žÉ¢rº,¡û\¢

I was constructing a message in an orchestration but I got an error message
that said that "message is not constructed." I found somewhere on the net
that said that the orchesctration is so smart that it recognizes that a
request/response port might be disconnected and that the message would not be
constructed.

So I need to loop around the request/response port to construct the message.
So I need to test if the port is connected.

I guess it would be nice to know when the connection is up or down. When I


will ask, "are you connected?"

--
Thanks
Tim

"Eric Stott" wrote:

tom canter - neudesic

Tim,
I'm not sure that the Orchestration does know at design time... that
the send port (MLLP) will be down at run time.

The error message you are seeing has nothing to do with the Send Port
(MLLP or otherwise).

It actually is telling you that your Orchestration Design right now
results in a path through the code that results in the possibility of a
message later in the orchestration of not having been constructed.

One example is when you are using a Listen shape, in which one branch
attempts to retrieve a correlated message from the message box and the
other branch is a timeout. Later in the orchestration you take the
final message that was constructed and send it. But if the timeout
branch fires, then you don't have the correlated message... and
therefore the message was not constructed.

You could also just be not constructing the message at all. You will
have to inspect your orchestration design and determine why your
orchestration may leave you in the state of using a message while it
hasn't been constructed.

This is a compile time check, not a runtime check... the compiler is
checking your code design and has decided that you are in this state.
No actual test of the MLLP Connection has occured.

Tom
Neudesic