Oracle® Retail Service Backbone Integration Console User Guide Release 19.0.000 F22955-02 |
|
![]() Previous |
![]() Next |
This chapter provides an overview of the Retail Integration Console (RIC) product.
Most tools, such as administration consoles similar to the WebLogic Administration Console or the Oracle Service Bus (OSB) Console, are designed to get the product up and running and for general configuration and administration purposes of a single domain. They are not intended as a solution to monitor and manage the entire integration infrastructure (that is, Databases, Hosts, Message Queues, Service Buses, and so on) at once. They routinely don't provide any historical metrics or real 24/7 diagnostics.
Infrastructure administrators do not want to be in a situation where a problem occurred an hour ago and they no longer have any information on it because they only have real-time data; both real-time and historical monitoring and diagnostics capabilities are required.
Administrators routinely have to be able to answer the usual question that comes up when everything was running fine one day and fails to perform on the next, which is, ”what has changed?” Administrators need historical information to refer to at all tiers of the infrastructure including the hosts as well as visibility across the stack including both monitoring and configuration data to answer that question.
In production environments, it becomes extremely difficult to reproduce such issues as the load, network, application environment, and overall intermittent behavior of all of the tiers and how it affects the business. Correlating events, both systemic and business errors and coming to a quick conclusion is key to ensure optimal service levels in a production environment for end-users. That means a full stack 24/7 real-time and historical monitoring solution that can also provide meaningful diagnostics across the entire application system stack.
The Retail Integration Console is designed to provide historical and real-time configurations and metrics 24/7 across all tiers and for the Oracle Retail integration infrastructure components, and to provide these in the business context of the Oracle Retail applications.
The Oracle Retail Integration Console (RIC) participates in the Oracle product set console domain. RIC has been designed to integrate with other Oracle product consoles from a look-and-feel perspective.
RIC is the user interface application designed to provide a unified view of the RTG Integration products within the business context of the Oracle Retail applications.
RIC is architected to understand and leverage the Retail Technology Group (RTG) infrastructure configuration for the OSB and Retail Integration Bus (RIB) products and presents all data in user friendly way in terms of retail and business entities and flows.
For this release RIC is used only for monitoring (in other words, read-only operation).
Accessibility involves making your application usable for differently-abled persons, such as low vision or blindness, deafness, or other physical limitations. This means creating applications that can be used without a mouse (keyboard only), used with a screen reader for blind or low-vision users, and used without reliance on sound, color, or animation and timing.
RIC provides the ability to support the above accessibility in the applications.
Users should be able to navigate to all parts and functions of the application using the Tab and arrow keys, without using any keyboard shortcuts. In addition to that, keyboard shortcuts provide additional ways to access a function quickly.
Keyboard shortcuts provide an alternative to pointing devices for navigating the page. There are five types of keyboard shortcuts that can be used in ADF Faces applications:
Tab traversal, using Tab and Shift+Tab keys: Moves the focus through UI elements on a screen.
Accelerator keys (hot keys): Bypasses menu and page navigation, and performs an action directly. For example, Ctrl+C for Copy.
Access keys: Moves the focus to a specific UI element. For example, Alt+F for the File menu.
Default cursor/focus placement: Puts the initial focus on a component so that keyboard users can start interacting with the page without excessive navigation.
Enter key: Triggers an action when the cursor is in certain fields, or when the focus is on a link or button.