Known Issues Select IDE Connections.

Configuring and Using Automated Harvesting in Design-time and Runtime Environments 6-45

6.3.11.10 Harvesting from Oracle JDeveloper 11g

It is not recommended to change namespace when harvesting from Oracle JDeveloper 11g. Also, it is recommended not to harvest same composite from JDeveloper 11g using two different status, for example, registered and submitted.

6.3.11.11 Harvesting a File in the Harvester Folder

It is recommended not to harvest a file that is located within the unzipped Harvester folder, 11.1.1.x.x-OER-Harvester.zip. Currently, this is not supported.

6.3.11.12 Running Harvester and Exchange Utility on the Same Computer

When publishing a service to Oracle Service Registry, it is recommended that you run Exchange Utility and Harvester on the same computer so they resolve to the same URL. You can also run these on separate computers where the access points in a WSDL are not fully formed, but you must ensure that they resolve to the same URL on both computers. If the access points are resolved to different URL for Harvester and Exchange Utility, then the service fails to publish with error.

6.3.11.13 Harvesting Composite Service WSDL

It is recommended that a WSDL of exposed composite service should never be harvested separately by itself. It is always best to harvest as whole Composite Project to get the complete and correct SOA asset model in Oracle Enterprise Repository.

6.3.12 Known Issues

This section describes the following known Harvester issues: ■ Section 6.3.12.1, Asset Types Must be Present in the System ■ Section 6.3.12.2, Two Versions of an Asset Type ■ Section 6.3.12.3, Do Not Delete the Harvester-Specific Metadata Entries in a in a Harvested Asset ■ Section 6.3.12.4, Supported Remote Server Types ■ Section 6.3.12.5, Using Incorrect Encrypted Password ■ Section 6.3.12.6, View in Repository Option

6.3.12.1 Asset Types Must be Present in the System

As a prerequisite to using Harvester features, the asset types must be present in the system. The necessary asset types are installed with 11.1.1.x.x-OER-Harvester-Solution-Pack.zip.

6.3.12.2 Two Versions of an Asset Type

If some of the existing asset type names in your Oracle Enterprise Repository have the same names as the asset types installed with 11.1.1.x.x-OER-Harvester-Solution-Pack.zip, the asset type names for the Harvester will have a version number appended to them. This does not affect the functioning of the Harvester asset types and harvester refers to these asset types based on its UUID. 6-46 Oracle Fusion Middleware Configuration Guide for Oracle Enterprise Repository

6.3.12.3 Do Not Delete the Harvester-Specific Metadata Entries in a in a Harvested Asset

When the Harvester creates assets during the harvesting proces, it attaches metadata entries to the asset of metadata entry Type: internal.inspector.store and internal.harvester.manifest.store. Do not modify or delete these metedata entries. Doing so can cause the system to behave unpredictably. Note that it is not possible to delete these metadata entries using Oracle Enterprise Repository user interface.

6.3.12.4 Supported Remote Server Types

Currently, the Harvester only supports connecting to the remote Oracle SOA Suite, Oracle Service Bus, and WebLogic Server projects that are running on WebLogic 10.x.

6.3.12.5 Using Incorrect Encrypted Password

If you configure the HarvesterSettings.xml file with incorrect encrypted password, then a long stack trace is displayed, which is as follows: log4j:WARN No appenders could be found for logger org.apache.axis.i18n.ProjectResourceBundle. log4j:WARN Please initialize the log4j system properly. com.oracle.oer.sync.framework.MetadataIntrospectionException: com.oracle.oer.sync.framework.MetadataIntrospectionException: Unable to read plugin file: C:\Drive-E\XU-harvest-tools\dec16\OER-Harvester\.\plugins\biz.introspector at com.oracle.oer.sync.framework.MetadataManager.initMetadataManager.java:308 at com.oracle.oer.sync.framework.Introspector.init Introspector.java:188 at com.oracle.oer.sync.framework.Introspector.mainIntrospector.java:395 Caused by: com.oracle.oer.sync.framework.MetadataIntrospectionException: Unable to read plugin file: C:\Drive-E\XU-harvest-tools\dec16\OER-Harvester\.\plugins\biz.introspector at com.oracle.oer.sync.framework.impl.DefaultPluginManager.processIntrospectorDe faultPluginManager.java:127 at com.oracle.oer.sync.framework.impl.DefaultPluginManager.initDefaultPluginMa nager.java:73 at com.oracle.oer.sync.framework.MetadataManager.initMetadataManager.java:306 ... 2 more Caused by: java.lang.IllegalArgumentException: The char 0x12 in java.lang.Ill egalArgumentException: The char 0x12 in E?8597;?8597;H?rd is not a valid XML character. is not a valid XML character. at org.apache.axis.components.encoding.AbstractXMLEncoder.encodeAbstrac tXMLEncoder.java:110 at org.apache.axis.utils.XMLUtils.xmlEncodeStringXMLUtils.java:131 at org.apache.axis.AxisFault.dumpToStringAxisFault.java:366 at org.apache.axis.AxisFault.printStackTraceAxisFault.java:796 at com.oer.log4j.spi.ThrowableInformation.getThrowableStrRepThrow ableInformation.java:42 at Configuring and Using Automated Harvesting in Design-time and Runtime Environments 6-47 com.oer.log4j.spi.LoggingEvent.getThrowableStrRepLoggingEvent.java:217 at com.oer.log4j.WriterAppender.subAppendWriterAppender.java:298 at com.oer.log4j.RollingFileAppender.subAppendRollingFileAppender.java:294 at com.oer.log4j.WriterAppender.appendWriterAppender.java:157 at com.oer.log4j.AppenderSkeleton.doAppendAppenderSkeleton.java:251 at com.oer.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppendersAppen derAttachableImpl.java:57 at com.oer.log4j.Category.callAppendersCategory.java:255 at com.oer.log4j.Category.forcedLogCategory.java:445 at com.oer.log4j.Category.logCategory.java:882 at com.oracle.oer.sync.framework.logger.DefaultMetadataLogger.errorDefaultMetada taLogger.java:98 at com.oracle.oer.sync.plugin.writer.oer.OERConnectionCache.getAuthTokenOERCon nectionCache.java:138 at com.oracle.oer.sync.plugin.writer.oer.OERAssetQueries.getTokenOERAssetQueri es.java:82 at com.oracle.oer.sync.plugin.writer.oer.OERAssetQueries.assetTypeQueryByUUIDAL ERAssetQueries.java:159 at com.oracle.oer.sync.framework.MetadataManager.putAssetTypeMetadataManager.jav a:204 at com.oracle.oer.sync.framework.impl.DefaultPluginManager.processIntrospectorDe faultPluginManager.java:104 ... 4 more

6.3.12.6 View in Repository Option

From Oracle JDeveloper 11g, when you click the View in Repository option, it opens up the asset details in JDeveloper, which is for read-only purpose and the links within this page will not work. As a workaround, you need to login to Oracle Enterprise Repository console and click links for further information. 6-48 Oracle Fusion Middleware Configuration Guide for Oracle Enterprise Repository 7 Configuring Metrics 7-1 7 Configuring Metrics This chapter provides an introduction to metrics configuration and how metrics can be used. If your organization is creating asset types, then you may want to add metrics fields. This chapter contains the following sections that provides the instructions to do so: ■ Section 7.1, Introduction ■ Section 7.2, Metrics Elements ■ Section 7.3, Validate the Elements on the Asset Type ■ Section 7.4, Running Queries Against the Database

7.1 Introduction

This section addresses metrics enhancements available in Oracle Enterprise Repository. Information in this guide will assist those who wish to add metrics fields to asset types, which do not already have them. The metrics fields provided by this guide are, Total Development Hours TDH, Production Investment Pinv, Consumption Factor Cfac, Predicted Number of Annual Reuse Opportunities n, and Hourly Burden Rate B. These fields most commonly appear on the Metrics tab in the Asset Editor.

7.2 Metrics Elements

This section describes an overview to metrics elements and various operations using metrics. This section contains the following topics: ■ Section 7.2.1, Overview ■ Section 7.2.2, Adding a Reusable Metrics Tab

7.2.1 Overview

This document explains how to add metrics elements to a Type. These metrics are used to estimate the value of each asset and to determine the ROI of the asset portfolio. A total of five metrics elements must be added, and the Development Hours element must already exist in the Type. If it does not, or if it has been deleted, it, too, must be added. The necessary changes are made in the Type Manager and the database; instructions for both are included here. The new metrics elements are listed below: ■ Total Development Hours TDH - the total development effort expended to create this asset.