Which two statements are true about the harvesting step to leverage AIA 11g R1 lifecycle
capability?
A.
It is necessary to leverage the lifecycle capabilities, such as functional decomposing.
B.
It is necessary to sanity check your implementation.
C.
It is necessary to leverage the lifecycle capabilities, such as auto-generate Bill of-Material.
D.
It is necessary to leverage the lifecycle capabilities, such as facilitating the generation of the
Deployment Plan.
Explanation:
Once you have unit-tested, source-controlled, and completed your composite
implementation, you can harvest these design-time composites into the Project Lifecycle
Workspace and, optionally, Oracle Enterprise Repository.
When you choose to harvest into the Project Lifecycle Workbench, annotations in composite XML
files are published to Project Lifecycle Workbench. These annotations published to Project
Lifecycle Workbench are instrumental in facilitating downstream automation, such as bill of
material (BOM) generation(C)and deployment plan generation(D). Annotations and harvesting are
required to enable this downstream automation.
If downstream automation is not a requirement for you, you may or may not annotate and harvest.
When you reach a point in the lifecycle flow at which the result of annotations and harvesting are
used, such as BOM and deployment plan generation, you can manually complete the BOM via the
Project Lifecycle Workbench UI or manually write your own ANT script to generate a deployment
plan.
Reference: Oracle Fusion Middleware Concepts and Technologies Guide for Oracle Application
Integration Architecture Foundation Pack:
Harvesting Design-Time Composites into Project Lifecycle Workbench and Oracle Enterprise
Repository