Getting Started with the Harvester

The Harvester harvests Oracle SOA Suite artifacts, including BPEL, WSDL, XSD and XSLT files and file directories, and 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 be used to harvest standards-based artifacts generated from any tooling. The Harvester can be used from the command line, it can be integrated with Oracle JDeveloper and then run within Oracle JDeveloper, or it can be invoked using an Ant task.

Prerequisites

Before using the Harvester, users must import the SOA/BPM Suite Solution Pack, which includes the required Asset Types and Relationships, into Oracle Enterprise Repository. Import the BEA_HOME/Tools/Solutions/OER103-SOA-BPM-Suite-Solution-Pack.zip file from the Oracle Enterprise Repository installation home. See the Oracle Enterprise Repository Import/Export Guide for information about importing.

High Level Use Cases

Publish standard SOA artifacts such as BPEL (from Oracle and other vendors), WSDL, XSD, and XSLT to Oracle Enterprise Repository.
Capture dependencies between the artifacts for impact analysis.
Handle nested WSDLs and XSDs.
Create abstract Interface assets and concrete deployment / Endpoints.
Capture BPEL partnerlink dependencies and relating them to Interfaces.
Capture BPEL PM dependencies to Transformations.
Store artifact content in OER for reusability.
Calculate Software File IDs (SFIDs) for artifacts for duplicate detection.
Publish artifacts from nested directories or zip files, jar files, or a BPEL suitcase.
Publish artifacts in a transactional fashion.
Publish artifacts from command line, and from automated Ant build process using the Harvester Ant task.

Harvester User Guide

Getting Started with the Harvester

What is the Harvester?

Prerequisites

High Level Use Cases

Related Documentation