Maintaining the Core – Service Repository - Applied SOA Patterns on the Oracle Platform - page 312

Harvesting SOA artifacts from the existing project
Although we successfully completed the harvest, some messages should attract your at-
tention. We extracted all project objects and artifacts from the SOA Suite, but we have a
lot references to OSB. So what about them? Oracle provided an individual harvester with
OSB, which we can use for ESB object retrospection. We already have our OER prepared
and the OSB configuration steps are similar to what we did in JDeveloper: modify Har-
vesterSettings.xml in the
[MIDDLEWARE_HOME]\<Oracle_OSB1>\harvester folder, and set the correct
OER connection parameters and path to our OSB project's export sbconfig.jar file.
After that, encrypt the password. Now, to perform harvesting, run setenv.bat from the
same folder and then osb11g-harvest.bat . You will see the OSB assets in the OER
console by searching for the name of our project (for instance, we used Service Broker in
the previous chapter). The Oracle documentation provides a complete reference to harvest
in different runtime and design-time environments ( http://docs.oracle.com/cd/E23943_01/
admin.1111/e16580/harvest.htm ) . We suggest that you look closely at the relations
between different assets harvested on different platforms.
So far so good. We have established a complete platform for bottom-up project develop-
ment. However, browsing through the Assets Types , all we can see are collections of