Working with Project Lifecycle Workbench Bills of Material 4-3
generation based on the BOM until you are certain that you no longer need to alter the functional decomposition and project definition.
Likewise, the composites for the PIP should have been implemented and, ideally, harvested into the Project Lifecycle Workbench before approaching BOM generation.
For more information about using the Service Constructor to generate these composites, see
Chapter 19, Working with Service Constructor. For more information about harvesting composites into the Project Lifecycle
Workbench, see Section 3.2, Harvesting Design-Time Composites into Project
Lifecycle Workbench and Oracle Enterprise Repository.
Actors Only users assigned the AIALifecycleInstallDeveloper role can generate and modify a
BOM for a PIP project. This user should be a developer who is responsible for producing the deployment plan for all executables in the project for which the BOM is
being generated. This developer will therefore also have a solid overall picture of the project.
To generate a BOM for an AIA Lifecycle project: 1.
Access the AIA Home Page. Click Go in the Project Lifecycle Workbench area. Select the Project tab.
2. Click the Generate Bill Of Material link.
This option is available only if your user has the AIALifecycleInstallationDeveloper role assigned and the BOM has not already
been generated.
a.
If the BOM has already been generated and you have been assigned the AIALifecycleInstallationDeveloper role, you will see the Edit Bill of Material
link. Click it to view and edit and generated BOM.
For more information about editing BOMs, see Section 4.3, How to Edit a Bill
of Material for an AIA Lifecycle Project.
b.
If the BOM has already been generated and you have not been assigned the AIALifecycleInstallationDeveloper role, you will see the View Bill Of
Material link. Click it to view the BOM on the Bill Of Material page.
For more information about viewing BOMs, see Section 4.4, How to View a
Bill of Material for an AIA Lifecycle Project.
3.
The application prompts you with two choices:
a. Click Generate to generate the BOM for the PIP project and access it on the
Bill Of Material page. Click this option only if the functional decomposition and project definition
have truly been completed.
Note: If you have not annotated composites and you have not
performed harvesting, you can still use BOM generation functionality by generating the BOM for your project and manually building out
your BOM with annotations using the instructions in this chapter.
4-4 Developers Guide for Oracle Application Integration Architecture Foundation Pack
b. Click Preview to view the BOM. This option is available only before the BOM
has been generated.
4.
The generated BOM displays on the Bill Of Material page. Edit the BOM as necessary and click the Export BOM button, as shown in
Figure 4–1 to export the
BOM as an XML file to be supplied as input to the Deployment Plan Generator to expedite deployment plan generation.
Figure 4–1 Export BOM Button
The recommended location for the saved BOM XML file is AIA_HOMEaia_ instancesinstance_nameconfig.
The recommended file name for the saved BOM XML file is Custom_PIP_ NameBOM.xml.
For more information about supplying the BOM XML file to the Deployment Plan Generator, see
Chapter 6, Generating Deployment Plans and Deploying Artifacts.
For more information about editing BOM, see Section 4.3, How to Edit a Bill of
Material for an AIA Lifecycle Project.
Note: Once you generate the BOM for a project, any changes that are
made to the BOM on the Bill Of Material page will not be reflected in the original project definition and decomposition in the Project
Lifecycle Workbench.
Working with Project Lifecycle Workbench Bills of Material 4-5
4.3 How to Edit a Bill of Material for an AIA Lifecycle Project
Objective Edit a BOM for an AIA Lifecycle Project.
Prerequisites and Recommendations The BOM must have been generated.
For more information about generating BOMs, see Section 4.2, How to Generate a Bill
of Material for an AIA Lifecycle Project.
Actors Only users assigned the AIALifecycleInstallationDeveloper role can edit a BOM for a
PIP project. This user should be a developer who is responsible for producing the deployment plan for all executables in the project for which the BOM is being
generated. This developer will therefore also have a solid overall picture of the project.
To edit a BOM for an AIA Lifecycle Project: 1.
Access the AIA Home Page. Click Go in the Project Lifecycle Workbench area. Select the Project tab.
2. Click the Edit Bill Of Material link.
This option is available only if your user has the AIALifecycleInstallationDeveloper role assigned and the BOM has already been
generated.
■
If the BOM has not already been generated and you have been assigned the AIALifecycleInstallationDeveloper role, you will see the Generate Bill Of
Material link.
For more information about generating BOMs, see Section 4.2, How to
Generate a Bill of Material for an AIA Lifecycle Project.
■
If the BOM has already been generated and you have not been assigned the AIALifecycleInstallationDeveloper role, you will see the View Bill Of
Material link. Click it to view the BOM on the Bill Of Material page.
For more information about viewing BOMs, see Section 4.4, How to View a
Bill of Material for an AIA Lifecycle Project.
3.
The BOM displays on the Bill Of Material page.
4.
Right-click the project root node as shown in Figure 4–2
to view permitted actions.
Note: Any changes that you make to the BOM on the Bill Of Material
page will not be reflected in the original project definition and decomposition in the Project Lifecycle Workbench.
4-6 Developers Guide for Oracle Application Integration Architecture Foundation Pack
Figure 4–2 Project Root Node Actions on the Bill Of Materials Page
Select Add Task to add a new business task to the project. For example, you may need to add a business task that was missed as a part of the original functional
decomposition performed by the functional product manager.
5.
Right-click the business task branch node as shown in Figure 4–3
to view permitted actions.
Working with Project Lifecycle Workbench Bills of Material 4-7
Figure 4–3 Business Task Branch Node Actions on the Bill Of Materials Page
A business task represents a chunk of functionality. The composites associated with a business task collectively realize the business logic embodied by the
business task.
■
The Edit option is available for a business task branch node if the business task was added to the project root node of the generated BOM. The Edit
option is not available if the business task was added to the project prior to BOM generation via the functional decomposition pages.
■
The Remove option is available for a business task branch node if the business task was added to the project root node of the generated BOM. The Remove
option is not available if the business task was added to the project prior to BOM generation via the functional decomposition pages.
■
Select Add New Composite to manually define a composite and its annotations and to associate it with the business task. Enter composite details
in the Detail area that displays.
You may subsequently re-harvest the already added composite directly from source code. At this point, the annotations previously entered via the UI are
overwritten by the harvested data. The Add New Composite option is always available.
Note: The newly added composite and its ensuing annotations are
not harvested from composite source code. Instead, they are manually added via the BOM UI and are stored only in the Project Lifecycle
Workbench.
4-8 Developers Guide for Oracle Application Integration Architecture Foundation Pack
■
Select Search and Add Existing Composite to access the Search and Add Existing Composite page, where you can search for and locate existing
composites and associate one or more with the business task.
For existing composites to be available for selection, they must have already been harvested by running AIAHarvester.sh. Upon selecting one or more
existing composites, any available composite details and annotations appear in the Detail area that appears. The Search and Add Existing Composite
option is always available.
For more information about running AIAHarvester.sh, see Section 3.2, Harvesting
Design-Time Composites into Project Lifecycle Workbench and Oracle Enterprise Repository.
6.
Right-click the composite leaf node to view permitted actions, as shown in Figure 4–4
.
Figure 4–4 Composite Leaf Node Actions on the Bill Of Materials Page
Multiple composites collectively provide functionality encompassed by a business task. A composite can be defined and included in a BOM in either of two ways:
■
Harvested composites A composite can be harvested upon completion of its implementation by
running the AIAHarvester.sh command. A harvested composite can then be added to a generated BOM by selecting the Search and Add Existing
Composite option on the business task branch node.
For more information about running AIAHarvester.sh, see Section 3.2,
Harvesting Design-Time Composites into Project Lifecycle Workbench and Oracle Enterprise Repository.
Working with Project Lifecycle Workbench Bills of Material 4-9
■
Manually defined composites The composite was not harvested, but rather was manually defined as an
associated composite by selecting the Add New Composite option on the business task branch node.
In the case of a manually defined composite, you can select the composite leaf node to display the Detail area, in which you can edit composite-level annotations
by specifying a series of XPath values in the BOM. The internal structure of the composite services and references, for example is not shown in the BOM. All
annotations are flat with respect to manually defined composites.
For both harvested and manually defined composites, you can select the Remove option to disassociate the composite from its parent business task branch node.
This removes the composite definition and association from the BOM. For harvested composites, this does not remove the composite from the Project
Lifecycle Workbench database or the Oracle Enterprise Repository. For manually defined composites, this does not remove the composite from the Project Lifecycle
Workbench database.
7. Once you have finalized all details conveyed in the BOM, click Export BOM to
export the BOM as an XML file to be supplied as input to the Deployment Plan Generator to expedite deployment plan generation.
The recommended location for the saved BOM XML file is AIA_HOMEaia_ instancesinstance_nameconfig.
The recommended file name for the saved BOM XML file is Custom_PIP_ NameBOM.xml.
For more information about supplying the BOM XML file to the Deployment Plan Generator, see
Chapter 6, Generating Deployment Plans and Deploying Artifacts.
4.4 How to View a Bill of Material for an AIA Lifecycle Project
