on 05-09-2017 1:00 PM
We require a DTP to execute in serial extraction a API function module initiated by Process Integration in order to catch and return messages to en external (SharePoint) initiator.
Solution to my problem was to query MAX( REQUID ) MAX( TIMESTAMP ) from RSBMONMESS_DTP for the specific DTP ID in field rsbmonmess-MSGV2, then use the message logs to find the specific messages needed for the latest of the parallel processes to determine the completeness of DSO loads. I gave up on forcing serial DTP execution and worked around the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To further explain the issue, the DTP will only allow saving in Serial extraction-parallel processing, which permits splitting the process to multiple asynchronous jobs. This makes it very difficult to catch messages and pass them externally in a PI controlled "synchronous mode'. We need to force the DTP to process in single serial mode in batch processing, but the minimum number of processes allowed is 2, and parallel processing seems to be mandatory for background execution. How can we achieve serial processing in the background in order to control the result messaging appropriately?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.