...
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Requirements
Functional
# | Interface | Requirement | Additional Information |
---|---|---|---|
Error Handling
# | Error Scenario | Expected behavior |
---|---|---|
Capabilities
# | Parameter | Expectation | Notes |
---|---|---|---|
1 | Response Time 1 Batch request | ||
2 | Batch-size | ||
3 | Response payload size | ||
4 | Supported # DMI PLugins | ||
5 | Test Environment | ||
6 | Concurrent request | ||
7 | Request Frequency |
Out-of-scope
Assumptions
# | Issue | Notes | Decisions |
---|---|---|---|
1 |
...
- The NCMP will create a new thread which will wait 30 seconds.
- The NCMP will add an entry to a hazelcast Map<String,Set<String>> with the clientID and subscriptionName combined as a key and the DMI Plugin names which the subscription has been forwarded to
- Every time a DMI responds to NCMP, NCMP persists the response. The Map entry is for the subscription is then checked
- if the subscription entry still exists in the Map, the NCMP removes the DMI Plugin name from the Set of the relevant Map entry.
- if the Set is now empty, NCMP removes the Map entry and compiles & send a full outcome response
- if the subscription entry does not exists in the Map, the NCMP compiles & sends a partial outcome response
- if the subscription entry still exists in the Map, the NCMP removes the DMI Plugin name from the Set of the relevant Map entry.
- If the Wait thread completes the 30s countdown,
- if the map entry for the subscription exists in the map the thread removes the map entry from the Map. It then sends a partial outcome response
- if the map entry for the subscription does not exist in the map, the thread does nothing
Cloud
...
Event Subscription Event
Insert excerpt CPS Events Structure CPS Events Structure
...