12 Making Migrated Services Deployable

This chapter discusses how to make migrated services into deployable artifacts.

The following sections describe the steps to follow after migrating the services:

Section 12.1, "Step 1: Annotating Composites"
Section 12.2, "Step 2: Harvesting AIA Content"
Section 12.3, "Step 3: Generate Bill of Material"
Section 12.4, "Step 4: Deploy Composites"

12.1 Step 1: Annotating Composites

AIA recommends using annotations in the composite XML file to provide detailed information about:

AIA artifacts and their relationships to other AIA artifacts.
Composite-level descriptor properties that are used to configure the component at deployment and run time.

AIA architecture categorizes SOA composites further as adapter services, requester services, provider services, and so on based on their usage. The meta information of these AIA services is used in maintaining Oracle Enterprise Repository assets of AIA asset types and linking them to Oracle Enterprise Repository assets with native asset types. This is accomplished with the help of AIA Harvester, which harvests the SOA composites.

For more information, see "Annotating Composites" in Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack.

12.2 Step 2: Harvesting AIA Content

After you have unit-tested, source-controlled, and completed your migrated service you can harvest these design-time composites into the Project Lifecycle Workbench 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. Annotations published to Project Lifecycle Workbench are instrumental in facilitating downstream automation, such as bill of material (BOM) generation and deployment plan generation. Annotations and harvesting are required to enable this downstream automation.

For more information, see "Harvesting Oracle AIA Content" in Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack.

12.3 Step 3: Generate Bill of Material

After the design-time composites are complete, they are harvested into the Project Lifecycle Workbench. At this point, you can use the Project Lifecycle Workbench to create a bill of material (BOM) for a PIP.

The BOM specifies the inventory of composites that make up the PIP. Using this feature can help expedite deployment plan generation for a PIP project by enabling the automatic or semiautomatic generation of the PIP's BOM.

For more information, see "Working with Project Lifecycle Workbench Bills of Material" in Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack.

12.4 Step 4: Deploy Composites

Deploying custom built services is a two step process:

Generate the deployment plans and deploy using the AID (Application Integration Architecture Installation Driver).
Deploy custom-built services using the AID.

Note:

You can deploy custom-built services only after installing Foundation Pack.

For more information, see "Generating Deployment Plans and Deploying Artifacts" in Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack.