Oracle® Retail Service Backbone Retail Integration Console Guide 14.0 E49444-01 |
|
Previous |
Next |
All of the RSB and RIB integration flows are displayed in two different tables. The menu on the left side helps to filter the flow entries by App Name, Message Family Name, or Type of flow.
This table shows the following columns:
Flow ID: This is a unique ID assigned to each integration flow.
Consumer Application: The application that consumes the service.
Consumer: The qualified name of the consumer service.
Decorator: The name of the decorator service.
Provider: The qualified name of the provider service.
Provider Application: The name of the application that provides the service.
Family Name: The name of the message family of the service.
This table shows the following columns:
Flow ID: This is a unique ID assigned to each integration flow.
Publisher Application: The application that publishes the message to a topic.
Publisher: The qualified name of the publisher topic.
Subscriber: The qualified name of the subscriber topic.
Subscriber Application: The application that subscribes to the topic.
When a row in the table (RSB or RIB) is selected, a panel appears below the table and gets populated with detailed information of the selected flow.
When an RSB flow is selected, four additional tabs are displayed.
This panel displays the diagram of request flow from consumer, decorator service and provider in sequence.
This table shows three graphs of collected metric information.
This graph displays the number of success and failure counts for decorator and Edge App Service.
This tab has 3 additional sub-tabs that display the Decorator Service SLA alerts, Edge App SLA Alerts and Decorator Service Business alerts.
These are generated when the decorator service violates the service level agreement or a predefined condition.
This tab displays a table of the following columns:
Component: The components that are secured in the flow.
Edge Application Service: The retail application in RIB. For example, RMS.
Proxy Service and Business Service: RSB components in OSB.
Consumer: The retail application that is either internal or external.
Name: The names of the components used in the flow.
Policy Type: This is the name of the web service policy configuration. Possible values are:
PolicyUnsecured
PolicyA
PolicyB
Note: The security policies certified by Oracle Retail are:
|
Policy Name: The policy security configuration used to secure the component.
For Policy A, the Policy Name is Wssp1.2-2007-Https-UsernameToken-Plain.xml
.
For Policy B, the Policy Name is Wssp1.2-2007-Wss1.1-UsernameToken-Plain-EncryptedKey-Basic128
, Wssp1.2-2007-EncryptBody and Wssp1.2-2007-SignBody
.
Is Certified?: Displays whether the security policy is supported.
When a RIB flow is selected, the following additional panel is displayed.
This panel contains the Flow Diagram, its details and the Family, Message, and Payload information table.
Flow Diagram displays the diagram of request flow from publisher, topic (or TAFR) and subscriber in sequence.
Publisher is responsible for creating the messages.
Topic is where the publisher publishes its messages to.
TAFR is a RIB component that could transform, filter and route the message.
Subscriber receives the message.
Message Family: Contains information specific to a related set of operations on a business entity or related business entities. For example, Orders message family contains information about purchase order events.
Message Type: A message family may contain multiple message types. Each message type encapsulates the information specific to a business entity within one or more business events. For example, the order message family is published for events such as Delete PO, Create PO.
Payload Information: the Retail Business Object (RBO) type for the Message Type.
Application API Information: Each PL/SQL based application uses a Message Family Manager specific API for publishing all messages within a specific message family. API is an interface to stored procedure package and wrapper to the staging table and additional business logic surrounding the message publication.