6-18 Oracle Fusion Middleware Configuration Guide for Oracle Enterprise Repository
Alternatively, harvester can be pointed to a different adf-config.xml file, through the mdsSettingsFile element in HarvesterSettings.xml or in the Harvester
ant task.
For more information about configuring MDS, see Oracle ADF XML Files in the Oracle Fusion Middleware Fusion Developers Guide for Oracle Application Development
Framework.
6.2.7.2 Classpath URLs
Harvester supports reading files from the java classpath. These files are referenced through the classpath: URL protocol. These files are located inside any jar file or
directory in Harvesters classpath. For example, classpath:META-INFwsdlServiceException.wsdl.
6.2.8 Configuring Logging for the Harvester
The Harvester uses log4j for logging the detailed tasks performed and the log file is placed in the Harvester Home directory. The logging options can be changed by
updating the log4fl.properties file located in the Harvester Home directory.
6.2.9 Transaction Handling in Harvester
By default, the harvester makes all of its changes to Oracle Enterprise Repository in a single transaction. Transactional operations in the harvester function is based on the
following rules:
■
In 11g R1, the Oracle Enterprise Repository server only supports one transaction at a time. If a transaction cannot be started, then the harvester informs you about it.
■
There is a set of timeouts associated with the transactions. These will terminate a harvester operation if the timeouts are exceeded.
– The setting, cmee.extframework.impexp.monitor.rex.maxidle,
specifies the maximum amount of time the transaction is kept alive if it loses connectivity with the client. This allows the transaction to be cancelled if the
client-side harvester process is killed.
– The setting, cmee.extframework.impexp.monitor.maxruntime,
specifies the maximum amount of time that the entire transaction will take. It is possible that a single operation will exceed the
cmee.extframework.impexp.monitor.rex.maxidle maxidle setting and cause all subsequent operations to fail. When this occurs, the last error in the log
will state that An error occurred while attempting to rollback because a transaction has not been started.. This is because the transaction automatically rolls back when the
statement exceeds the maxidle and the transaction is no longer available when the client application attempts a forceful rollback, having detected errors. The result is
that no data, from the harvester operation, is added to Oracle Enterprise Repository.
6.2.10 Advanced Configuration
This section contains the advanced configuration options for Harvester:
Adapters and Applications Harvester contains a configuration file called adapters.xml, that governs which
Adapter and Application assets are supported. It has the following structure:
Configuring and Using Automated Harvesting in Design-time and Runtime Environments 6-19
■
adapter
adapter name=AQ Adapter jcaSpecBinding=oracle.tip.adapter.aq.inbound.AQDequeueActivationSpec
adapter name=AQ Adapter jcaSpecBinding=oracle.tip.adapter.aq.outbound.AQEnqueueInteractionSpec
adapter name=PeopleSoft Adapter jcaSpecBinding=com.ibi.afjca.cci.IWAFInteractionSpec
jcaCSAdapterName=PeopleSoft adapter name=PeopleSoft Adapter
namespace=http:xmlns.oracle.comEnterprise adapter name=PeopleSoft Adapter namespace=http:peoplesoft.com
■
adapterAsset
adapterAsset name=AQ Adapter adapterAsset
adapterAsset name=PeopleSoft Adapter applicationName=PeopleSoft Application
adapterAsset
Each adapterAsset element must correspond to an Adapter asset andor Application asset that exists in Oracle Enterprise Repository. The Harvester does
not create Adapter assets or Application assets. These must be imported via an Oracle Enterprise Repository solution pack or created manually in Oracle
Enterprise Repository. The 11.1.1.x.x-OER-Harvester-Solution-Pack.zip contains all of the
Adapter and Application assets that are configured in the default adapters.xml file.
Each adapter element indicates an Adapter Configuration andor Application Deployment asset that is created. The name attribute must match the name of a
corresponding adapterAsset element. Each adapter element must have either the jcaSpecBinding or namespace attribute present.
■
jcaSpecBinding
The jcaSpecBinding attribute corresponds to the fully-qualified classname of a JCA interactionSpec or activationSpec class, as appears in WSDLs created
by Oracle SOA Suite. If jcaSpecBinding is present, then an Adapter Configuration asset is created.
■
jcaCSAAdapterName
The jcaCSAAdapterName attribute is optional. It may be specified if the JCA interactionSpecactivationSpec is not enough to distinguish the adapter
type. If specified, then it must match the cs.AdapterName attribute in the jca:address section of the WSDL.
■
namespace
The namespace attribute corresponds to the targetNamespace of a WSDL created by Oracle SOA Suite, using the Oracle BSE framework. If namespace is
present, then an Adapter Configuration asset will NOT be created, only an Application Deployment gets created.
Note: An Application Deployment asset may also be created if the
corresponding adapterAsset element has the applicationName attribute present.
6-20 Oracle Fusion Middleware Configuration Guide for Oracle Enterprise Repository
If an adapter or application has several possible JCA classes or XML namespaces, then multiple adapter elements can correspond to one adapterAsset. Each
adapterAsset element indicates an adapter andor application asset that is created. The name attribute must match the name of a corresponding adapter
element. Only one adapter andor application asset is created in Oracle Enterprise Repository for each adapterAsset element.
■
applicationName
The applicationName attribute, if present, indicates that an application asset should also be created. Each property element will result in the specified data
being set in the Harvester Properties section for the adapter asset created.
For more information about the harvester properties, see Section A.10, Harvester
Properties Matrix .
6.3 Harvesting of Artifacts
