|Oracle® Fusion Middleware Concepts Guide for Oracle Enterprise Repository
11g Release 1 (188.8.131.52)
Part Number E16581-07
|PDF · Mobi · ePub|
This chapter describes using Oracle Enterprise Repository Solution Packs for managed asset visibility. Oracle Service Registry provides asset visibility when synchronized to the repository using Oracle Registry Repository Exchange Utility.
This chapter contains the following sections:
An organization cannot govern what it cannot see. Therefore, the first step is to make the assets you want to manage visible.
Oracle Enterprise Repository Solution Packs include:
Base Data Pack
Harvester Solution Pack (includes Adapter Solution Pack)
AIA Solution Pack (available with the purchase of Oracle's Application Integration Architecture Foundation Pack and PIPs)
Bootstrapping is the initial programmatic loading of assets and asset metadata into the Enterprise repository from sources such as:
A service registry
The runtime environment
Artifacts and artifact stores
Excel spreadsheets and other metadata stores
Organizations can also enter assets manually. Afterward, manual validation ensures that imported assets were harvested properly and allows addition of business-focused metadata.
This section describes the Oracle Enterprise Repository solution packs:
Base Data Pack delivers template assets. These include the business-focused asset metadata that organizations track. The metadata fields have been collected from the best practices of organizations worldwide. The Base Data Pack is automatically installed with Oracle Enterprise Repository. Base Data types can be copied and customized to suit specific organizational assets.
The Harvester Solution Pack delivers assets required by the Harvester tool. The Harvester and Harvester Solution Pack provide metadata about an asset's implementation and relationships. The Harvester Solution Pack defines the format into which Oracle Enterprise Repository harvests artifacts.
The Oracle Enterprise Repository Harvester Solution Pack includes asset types for Oracle's Application Adapters and Applications. These asset types allow the harvest and end-to-end visibility of application integrations.
The Oracle Enterprise Repository Harvester tool makes visible assets from many of Oracle's products, including Oracle SOA Suite, Oracle Service Bus, Oracle Enterprise Manager, Oracle BPEL PM, UDDI Registries, and others. The Oracle Enterprise Repository Harvester tool also allows organizations to harvest any standards-based WSDL, BPEL, XSD, and XSLT artifacts generated by third-party tooling. The harvesting process requires the Harvester Solution Pack.
The Harvester is available in 11.1.1.x.x-OER-Harvester-Solution-Pack.zip, which is bundled with the Oracle Enterprise Repository installation in the following .zip file:
For more information, see Oracle Fusion Middleware Configuration Guide for Oracle Enterprise Repository.
For more information about the AIA Solution Pack, see the "Configuring and Using Oracle Enterprise Repository as the Oracle AIA SOA Repository" section in Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack.
This section describes how to bootstrap Oracle Enterprise Repository. It contains the following topics:
Effective SOA Governance requires a synchronized Enterprise Repository and Service Registry.
The Oracle Registry Repository Exchange Utility synchronizes Oracle Enterprise Repository and Oracle Service Registry so metadata can flow in either direction.
To bootstrap the Oracle Enterprise Repository from a Service Registry, follow these steps:
Configure the Oracle Registry Repository Exchange Utility
Understand how Metadata is Synchronized between Oracle Service Registry and Oracle Enterprise Repository
Review Known Issues
For more information about Oracle Registry Repository Exchange Utility, see http://download.oracle.com/docs/cd/E14571_01/doc.1111/e16580/oereu.htm#CACEFFIH.
You can bootstrap the Enterprise Repository with assets from the organization's runtime containers. Oracle Enterprise Repository uses the Harvester tool to access deployed artifacts. The Harvester reads standards-based files, including BPEL, WSDL, XSD and XSLT files, as assets generated by Oracle SOA Suite and Oracle Service Bus. The Harvester automatically creates assets, populates asset metadata, and generates relationship links based on the information in the artifact files. Note that the Harvester is not restricted to Oracle products - it can harvest standards-based artifacts generated from any tooling. In the runtime environment, you can invoke the Harvester using the command line or an Ant task.
For more information about harvesting from runtime containers, see "Runtime Harvesting Details" in Oracle Fusion Middleware Configuration Guide for Oracle Enterprise Repository.
You can bootstrap the Enterprise Repository with production-grade assets from the organization's version control or file systems. Oracle Enterprise Repository uses the Harvester to access the artifacts in various artifact stores. You can also invoke the Harvester from the command line.
There are limitations on publishing services to OSR when the WSDL is hosted anywhere but on a running endpoint, HTTP, HTTP/S or FTP. Services with artifacts hosted in other types of artifact stores will not publish to OSR/UDDI.
For more information about harvesting production-grade artifacts from artifact stores, see "Configuring the Harvester for the Command Line" in Oracle Fusion Middleware Configuration Guide for Oracle Enterprise Repository.
Organizations just beginning to explore Governance practices might track asset metadata and dependencies in a spreadsheet, on a wiki, or through some other type of tool. At a certain point, however, this becomes unmanageable and it makes sense to move the information to an Enterprise Repository.
The Oracle Enterprise Repository includes a Web Services based API called the Repository Extensibility (REX) Framework, which can bootstrap Oracle Enterprise Repository from spreadsheets and other metadata stores. This requires customization and coding and is covered as an advanced topic.
For more information about the Enterprise Repository's API, see "Developing Custom Integrations" in Oracle Fusion Middleware Integration Guide for Oracle Enterprise Repository.