This chapter describes how to prepare and then migrate artifacts from the Business Service Repository (BSR) to the Oracle Enterprise Repository (OER).
This chapter includes the following sections:
After you have completed the environment setup (including Oracle Enterprise Repository), prerequisites, service migration, and have annotated the services, you are ready to harvest the services.
For information about the prerequisites and environment setup, see Chapter 2, "Preparing to Migrate AIA Artifacts to AIA 11g Release 1."
For information about the service migration, see Section 7, "Migrating Services."
For information about annotating composites, see "Annotating Composites" in Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack.
This section provides details about how to harvest services to Oracle Enterprise Repository.
The Business Service Repository (BSR) is an integral part of the AIA 2.4 and 2.5 offering. It provides users with SOA visibility, since a BSR instance is created and populated each time a new AIA 2.4 or 2.5 installation occurs.
In AIA Foundation Pack 11g Release 1, this functionality is consolidated in Oracle's SOA repository, Oracle Enterprise Repository. Oracle Enterprise Repository brings you additional asset management capabilities, such as asset lifecycle control, and analytics around asset usage and tracking.
The migration of 2.4 and 2.5 BSR content to an 11g Release 1 Oracle Enterprise Repository instance does not occur in isolation. Instead, it occurs as a part of the overall migration path from AIA 2.4 and 2.5 (on Oracle SOA Suite 10g) to AIA Foundation Pack 11g Release 1 (on Oracle SOA Suite 11g). For instance, it does not make sense to remain on AIA 2.4 or 2.5 (and therefore maintain respective BSR instances) on the 10g SOA Suite, while operating an 11g Oracle Enterprise Repository.
For prebuilt AIA 2.4 and 2.5 content released by Oracle, you need not do anything. The content can be published into Oracle Enterprise Repository using the AIA Solution Pack.
For custom-built content, you must harvest the content into Oracle Enterprise Repository by using the AIA Harvester following the samples and documents delivered in AIA Foundation Pack 11g Release 1.
Custom-build content (EBS.wsdl, EBM.xsd, EBO.xsd, ABCS.wsdl, and composites, for example) must be migrated and annotated in accordance with AIA Foundation Pack 11g Release 1 extension and annotation standards.
You can harvest your custom-built interfaces dynamically by running the AIA Harvester.
For more information about the AIA Harvester, see "Harvesting Design-Time Composites into Project Lifecycle Workbench and Oracle Enterprise Repository" in Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack.
Note that Oracle Enterprise Repository is about SOA asset lifecycle management, whereas, AIA Foundation Pack 11g Release 1 components, such as the Project Lifecycle Workbench, focus on facilitating development lifecycle management from functional definition and process decomposition to bill-of-material auto-generation in the context deployment plan construction.
You may find it convenient to manage and reuse the many types of SOA artifacts produced by AIA's development lifecycle in a SOA repository, such as Oracle Enterprise Repository. If so, you can operate the AIA Project Lifecycle Workbench in concert with Oracle Enterprise Repository.
Oracle Enterprise Repository is an optional component to AIA Foundation Pack installation and execution. You can operate AIA Foundation Pack (including the Project Lifecycle Workbench) without using Oracle Enterprise Repository.