When would you use security in AIA Integration flows?
A.
between any two services
B.
between remote invocations and as required by business
C.
between all remote invocations
D.
only between two Web service invocations
Explanation:
Note: An Integration Flow represents the journey of a message from a business
event-triggering
source, through possible intermediary milestones, to one or more target milestones. At each
milestone, the message is stored in a different state.
An Integration Flow represents the runtime path of a message. It is not a design-time artifact.
AIA recommends a variety of integration styles and patterns to enable the flight of a message in
an Integration Flow. The AIA artifacts that are required for the collaboration between applications
or functions are dependent on the integration style adopted for an Integration Flow.
Note 2: Oracle Application Integration Architecture (AIA) provides support for all security-related
functions
including:
* Identification
* Authentication (verification of identity)
* Authorization (access controls)
* Privacy (encryption)
* Integrity (message signing)
* Non-repudiation
* Logging
The service-oriented architecture (SOA)-based integration approach allows for clear separation
between the interface and the actual business logic. This provides the
Security models:
* Point-to-Point or End-to-End Security
* Transport-Level Security
* Message-Level Security
* Securing ABCSReference: Oracle Application Integration Architecture, Infrastructure Components and Utilities
Guide