| CranCran77 2006-02-06, 5:53 pm |
|
I have implemented the resequencer pattern recently in an orchestration
to transmit IDOCs to a remote SAP system. In my orchestration, I have
my send port logic constructed as follows:
-- Transmit Scope Begins --
Send Port SAP
Delay (1s)
Send Port Oracle DB Update
Send Port FILE - Save IDOC
-- Begin Exception --
Suspend Orchestration w/message
-- End Exception --
-- End Transmit Scope --
The sent port has delivery notification set to "transmitted" so my
orchestration performs by simply waiting for delivery of the IDOC
before proceeding to the next step. Now, I also have my resequencer
orchestration setup to write the document to a directory upon
successful delivery.
We tested a simple case with 3 documents earlier today and I noticed
that the 1st and 3rd documents were received okay by SAP but the 2nd
document never showed delivered in their system, nor errored or
anything. We could nto find any remote connection issues and in the
HAT tool, all 3 transfers should successful transmission on first try.
One thing I noticed was transmission 1 happened at 05:08:39 pm,
transmission 2 at 05:08:49pm, and the last at 05:08:50pm. Could it
have been due to only a 1 second delay in the send port scope logic?
Would increasing the delay really make a different or is it only
masking a potential problem??
Please help, I have to deploy this project this weekend to production
and want to make sure my code changes are solid.
Kind regards,
Chris
|