Versions Compared

Old Version 10

changes.mady.by.user Kolawole Adebisi-Adeolokun

Saved on

compared with

New Version 11

changes.mady.by.user Gerard Nugent

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


Functional Requirement

Error Scenario

Expected Behavior

Sign-off

1

#2

Non Responding DMI during new DataJob Request

NCM shall send asynchronous message containing:

  • Subjobs that have not started with the DMI and the qualifier (after http timeout), no subJobs Ids since they would have to be assigned by south bound system

Client is responsible for retry. 

Wait for implantation proposal 

 Csaba Kocsis , CPS

2

#2

Unmatched Alternate IDs 

Toine Siebelink  : Not discussed yet but  I would suggest similar behavior as legacy bulk interface (async response with failed FDNS) - If an unmatched alternated (1 or more), send a response back to client saying no jobs or 0 subjob

If request contains none-exited alternateid ? - Goes to client


 Csaba Kocsis, all cps 

3

#3

Non Responding DMI during new status update

Error handling just by HTTP timeout (java interface will throw an exception)

 Csaba Kocsis all cps 

4

#4 
General

Not existing Topics

NCMP is NOT responsible for checking or handling messages to non existing (client) topics
Also 'internal' topics are assumed to be set up correctly

 Csaba Kocsis  all cps

5

Misc.

Other Robustness 

  1. NCMP Down
  1. What happens to Sub-jobs that have not started with the DMI and the qualifier (after http timeout)
  2. What happens to if NCMP crashes immediately after responding to the request ?

 Agreed to revisit robustness once basic happy and standard error scenarios (DMI not responding) have been implemented 



High Level Solution

Gliffy Diagram
macroId6bf79daa-23fd-4cbe-b8f3-339d124b4200
displayNameAsync_Job_Flow
nameAsync_Job_Flow
pagePin4

Characteristics for NEW Batch KPI


ParameterExpectationNotesSignoff
1



2



Solution Proposal

Sequence Diagram

...