Popular White Paper On This Topic

oh..okay thanks fr your reply. I have used a service
wm.ip.cm:waitStepInit as a first step and actually invoking this
step. But the process modelor is not getting triggered. The
document is getting recognised in the TN and all, there is no
problem in the same.

If TN and PRT are both run on the same machine then
you could start Process by subscribing to TN document
or by publishing some document from TN processing rule
to start a Process Model.

If TN and PRT run on separate systems you have to
iether publish some document, EDI or mapped document
through broker to start process, or you could invoke a
webservice from processing rule to start PRT process.

1. While creating your process model, you can subscribe to a TN Document
Type as a starting step. In this case, when that document comes to TN
and is recognized, the process model kicks off.
2. You can have a processing rule, which will invoke a service, that in
turn will publish a document containing that EDI Data (and other
parameters, if you want) which will trigger the process model.

i'm already invoking the step using a subscription to TN Document
type. But still the process is not getting triggered. I'm
actually invoking the wm.ip.cm:waitStepInit as the first step
with the input as subscription to TN document type. The problem
i'm facing now is that document is getting recognized but the
model is not getting triggered.can you help me??