Versions Compared

Key

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

...


Error Scenario

Expected behavior

Sign-off

1Non responding DMIs (configurable timeout)An error message listing the 'pending' CM Handle IDs. statusMessage/statusCode to be agreed. 
2Non Existing or non-valid CM Handle IdsAn error message listing the 'rejected' CM Handle IDs.
3DMI Plugin without CM Event subscription supportAn error message listing the 'rejected' CM Handle IDs 
4Late Response (after timeout defined in #1) from DMIA list of outcomes (complete status on how many cmhandles are pending/rejected/accepted) from client subscription is returned in response. 

statusMessage/statusCode to be agreed. 

 

5Create for existing subscription idThe whole subscription will be rejected. statusMessage/statusCode to be agreed. 

 

6Delete for non-existing subscription idThe whole delete subscription will be rejected. statusMessage/statusCode to be agreed. 

 

7Error upon error

An error scenario on a second subscription for the same cm-handle/xpath as a previous subscription which did not complete successfully (yet)

to be discussed, see Error Upon Error Combinations

...



...

Characteristics


Parameter

Expectation

Notes

Sign-off

1Frequency of LCM Subscription EventsNo high volume of such events is expected
For testing purpose 1 LCM event per minute would suffice.

kieran mccarthy confirmed

 

2Number of SubscriptionsMax: 200

kieran mccarthy confirmed

3CM Handles per Subscription

Avg: 200

Max: 500 (document only)

kieran mccarthy to confirm
Note: consider limit and future 'simple' ALL (wildcard) option when above that limit

4Xpaths per Cm HandleAvg: 10

5Status update processing time(Order of 30) seconds (NCMP side)

...