| Gexit 2005-10-24, 10:32 am |
| Hi all,
I am trying to implement a file dispatcher using BTS.
The solution includes two nested orchestration.
The 1st Orchestration (Main) includes a receive --> external program
(*) --> Start Orchestration --> receive --> send shapes.
The first/last receive/send shapes are bound to a request/response port
and published as a public web service.
When a client submits a request, the Main orchestration activates an
external program (*) to search for the requested file, Assuming the
file exists a copy will be created at a predefined directory.
The Main orchestration activates a 2nd orchestration (Sub) using a
start shape followed by a self correlated receives port(**).
The Sub orchestration requires the following parameters:
1- MainSelfCorrelatedPort (**)
The self correlated port enables the Sub Orchestration to send a reply
back to the Main orchestration via a direct bound send port.
2- MainCorrelationSet
The main correlation set configures the sub receive shape to follow the
main correlation since it is unable to initialize a correlation set
being inactive.
3- MainIncomingMessagePart
Data .
The Sub orchestration includes a receive (file adapter)--> constructed
message (with assign)-->send shapes .
The Sub orchestration designed to collect the xml file created by the
external program (*) and to construct a new message upon the data
retrieved from the xml file.
The new message will be send back to the Main orchestration using a
send shape configured to direct bound the self correlated port(**).
The solution as I described above works fine only for the first
execution, meaning - I have to restart the server application host
instance in order to perform a second execution.
The HAT shows an error - "Could not find a matching subscription for
the message..." on the sub XMLreceive pipeline instance, the message
status is "Terminated" .
I examined the subscriptions list at the "Subscription viewer" and the
messageBox-subscriptions table, It seems that as opposed for the first
execution, at the second execution the receive has no subscription at
all ?!
w h y ? what can be done ...?
THNX :-)
|