What are the two relationships between Service Solution Component definition for ABCS and the
actual implementation performed In the Service Constructor/JDeveloper?
A.
Service Solution Component of ABCS types have no relation to the eventual implementation in
the Service Constructor/JDeveloper.
B.
Service Solution Component of ABCS types are upstream of the eventual
implementationinService Constructor/JDeveloper.
C.
Service Solution Component provides functional metadata for the ABCS before the actual
implementation in JDeveloper.
D.
Service Solution Component provides the Interface for the ABCS before the actual Implement
in JDeveloper.
Explanation:
A service solution component is a chunk of functionality within the scope of a
business task that is implemented as an AIA service artifact. For example, a service solution
component corresponds to an Application Business Connector Service (ABCS), Enterprise
Business Service(EBS), or Enterprise Business Flow (EBF). A service solution component
conveys the functionality that the AIA service artifact needs to fulfill.
Note #1:Define the service solution components that make up a business task in a Project
Lifecycle Workbench project. Each service solution component that you define should correspond
to a single composite or service that will be built or reused. These composites and services
collectively accomplish the functionality and logic required by their parent business task.
Note #2:Service Constructor guides the developer through four of the six subphases of developing
an ABCS. The four subphases are:
* Define service description and details
Define high-level information about the service solution component and the project and business
task to which it belongs.
* Define the service object (or interface)
Define the type of message that the ABCS will receive and if and how it will reply.
* Define the target service
Define the services that will be invoked by the ABCS, and the message it will pass to those
services.
* Define additional options and generation point
Define options such as error-handling and extension run-time location, as well as the launching
point to generate an Oracle JDeveloper project for continued development.
Once the developer has completed the Service Constructor interview, a complete Oracle
JDeveloper project is produced that the developer will continue to develop, incorporating use
case-specific requirements.
Service Constructor enhances developer productivity by providing a more user-friendly interface to
the Composite Generator (formerly the Artifact Generator) and auto-inspection of services and
project selection from the Project Lifecycle Workbench.
Reference: Oracle Fusion Middleware Concepts and Technologies Guide for Oracle Application
Integration Architecture Foundation Pack:Working with Project Lifecycle Workbench Service Solution Components