INTERFACE ID |
IB02 - Banners |
|||||||||||||||
SOURCE |
RMS |
|||||||||||||||
DESTINATIONS |
External |
|||||||||||||||
INTEGRATION STYLE |
Asynchronous – Unidirectional |
|||||||||||||||
DESCRIPTION |
RMS publishes messages about banners and channels to the RIB. A banner provides a means of grouping channels, thereby allowing the customer to link all brick and mortar stores, catalogs, and Web stores. The BANNER table holds a banner identifier and name. The CHANNELS table shows all channels and any associated banner identifiers. To take advantage of banners and channels, the customer must run RMS in a multi-channel environment. |
|||||||||||||||
DATA |
|
|||||||||||||||
DEPLOYMENT |
RIB |
|||||||||||||||
INTEGRATION SERVICE LEVELS |
Guaranteed, once-only delivery to destination |
Yes |
||||||||||||||
Scheduled data exchange |
No |
|||||||||||||||
Audit-trail kept for data exchange (state historical duration of audit trail) |
Auditing at message level. |
|||||||||||||||
Alerting required should data exchange fail? |
Yes |
|||||||||||||||
Retry of data exchange necessary? (state number of times before error is logged or failure condition is met) |
Yes. RIB Hospital. |
|||||||||||||||
Data purge on data transmittal? |
Yes |
|||||||||||||||
Security on data exchange required? |
No |
|||||||||||||||
PERFORMANCE SERVICE LEVELS |
If this is a server application, what is the design-time number of concurrent clients that will be serviced? |
|
||||||||||||||
Priority of integration (High, Medium, Low)? |
|
|||||||||||||||
Fail-over required? |
|
|||||||||||||||
Expected response time or batch processing window |
N/A |
|||||||||||||||
Frequency of messaging or batch data exchange |
|