The chapter describes the new and changed functionality in Oracle Enterprise Repository 11g Release 1 (11.1.1).
Note:The issues and workarounds listed here are those that were known at the time of the product's initial release to the public. Additional issues and workarounds may have been discovered since the initial release. To view the latest known issues associated with Oracle SOA Suite, BPM Suite, and related SOA technologies, go to the Oracle Technology Network (OTN) at
This chapter contains the following sections:
This section describes the new features and functionalities in Oracle Enterprise Repository 11g Release 1 (11.1.1):
You can now manage SAP asssets as part of your overall enterprise service portfolio. Oracle Enterprise Repository harvests services that are published to the SAP UDDI v3.0 Registry. These services can be subsequently consumed through Oracle JDeveloper, Eclipse, or VS .Net.
Oracle Enterprise Repository has enhanced the harvesting of BPM assets. Oracle Enterprise Repository now captures the complete BPM metamodel, including BPMN and BPEL 2.0.
Oracle Enterprise Repository is now able to govern additional services managed by Oracle Enterprise Manager (OEM) Fusion Middleware Control using the Oracle Enterprise Repository Exchange Utility. OEM Fusion Middleware Control publishes these services to Oracle Service Registry (OSR) using the UDDI standard and the Oracle Enterprise Repository Exchange Utility is used to bring the services into Oracle Enterprise Repository.
In Oracle Enterprise Manager (OEM) Fusion Middleware Control, the Publishing SOA Web Services to UDDI feature is available in the Services tab of the Services and References page of SOAInfra target.
You can harvest a deployed service from the JDeveloper SOA connection browse tree, or the SOA Composite Navigator.
Oracle Enterprise Repository also supports Converged Application Repository (CAR) tools that are provided in other products to include enterprise application content in Oracle Enterprise Repository. This procedure includes loading Solution Packs into the repository and running the CAR harvester to obtain endpoints for your application services.
You can now see all of the assets that will be created in Oracle Enterprise Repository before the harvest is committed.
It is recommended to migrate from your custom service model to the Oracle provided SOA service model in 11g Relase 1(11.1.1). Migrating to the Oracle provided service model enables you to leverage new functionality in 11g such as the harvester, JDeveloper integration, and so on. Migrating to the Oracle Enterprise Repository 11g SOA asset model also makes it easier to migrate to future releases of the product.
Note:Ensure you contact support in advance if you are planning to upgrade from Oracle Enterprise Repository 10g or earlier releases to Oracle Enterprise Repository 11g.
This section describes the general issues and workarounds in Oracle Enterprise Repository 11g Release 1 (11.1.1). It includes the following topics:
This section describes the general issues and workarounds found in Oracle Enterprise Repository:
This section describes the issues and workarounds found in Oracle Enterprise Repository Asset Editor:
When you launch the Navigator from the Asset detail, a relationship to the consuming project is also displayed, even if that asset has been rejected. This is resolved in Oracle Enterprise Repository 11g Release 1 (11.1.1).
The Navigator has a separate login than the Oracle Enterprise Repository Web tool. Prior to PS3, the Navigator would take the login information from cookies for the automatic login, which occurs when it is launched. This caused issues when cookies were turned off or if the Weblogic Server had the following setting set to false:
This has been resolved by not relying on cookies to pass the user information.
This section describes the issues and workarounds found in Oracle Enterprise Repository Harvester:
Oracle Enterprise Repository throws an exception when you attempt to create a new Type in the Type Manager using Endpoint as the Type for Defaults. This only occurs when the Harvester Solution Pack is not installed. This is resolved in Oracle Enterprise Repository 11g Release 1 (11.1.1).
There was an issue in the password utility when harvesting a composite from the SOA server. If the SOA Server's credentials had a "#" sign in the password, then the harvester failed. This is resolved in Oracle Enterprise Repository 11g Release 1 (11.1.1).
There is a scenario in which a WSDL URL will resolve differently if harvested from one computer and published to Oracle Service Registry from a different computer. To correct this issue, run Exchange Utility and Harvester on the same computer. As an alternative, the Harvester and Exchange Utility may be run on seperate computers, but you must ensure that both resolve to the same WSDL URL.
In the Eclipse plugin, when an Oracle Service Bus project is harvested and you attempt to launch the Oracle Enterprise Repository Access view, then the Oracle Enterprise Repository connections fails. The Oracle Enterprise Repository connection also fails if you do the reverse of it. That is, if you first launch the Oracle Enterprise Repository Access view and then browse for Oracle Enterprise Repository, then also the Oracle Service Bus harvesting fails.
The workaround for this is to restart Eclipse and then reconnect to Oracle Enterprise Repository.
When you run Harvester from the Linux Shell prompt, the Harvest fails with a "No Match" error, as follows:
$ ./harvest.sh -file ./harvest.sh: No Match $
This is a known issue.
Note:The above command runs successfully in Windows as well as in the bash prompt.
You must run the harvester script as follows:
./harvester -file "<URL>"
where URL represents the URL from where you run the the harvester. Also, note that the URL must be specified within the double quotes, for the harvester to run successfully.
While consuming the SAP services in Oracle JDeveloper from Oracle Enterprise Repository, launch JDeveloper with the following option from the command line:
jdev .exe -J"-Dsoa.enable.wsdl.authentication=true"
This is to ensure that SAP WSDLs that are authentication-enabled are consumed properly into JDeveloper, else the WSDL would not be authenticated and downloadable in JDeveloper.
In some circumstances, the harvester prioritizes WSDL-harvested information over the user-supplied metadata. This is specific to the Description and Service Type fields when harvesting assets of the Service Type provided with Oracle Enterprise Repository. You can avoid this by moving the user-supplied metadata to the other fields on Service assets prior to harvesting.
Note:To address this known issue in harvester, contact Oracle support for a patch.
This section describes the issues and workarounds that are found in Oracle Enterprise Repository Exchange Utility(XU):
When a wsdl is harvested with the namespace that is too long, Exchange Utility truncates the full asset name and the asset will not be published properly. This is resolved in Oracle Enterprise Repository 11g Release 1 (11.1.1).
This section describes the enhancements in Oracle Enterprise Repository 11g Release 1 (11.1.1):
Harvester includes the following enhnacements for 11g Release 1 (11.1.1):
Preview Mode feature
BPMN/BPEL 2.0 Introspection
Harvester core supports passing in keywords.
Exchange Utility includes the following enhnacements for 11g Release 1 (11.1.1):
Including policy information when receiving services
Support for integration with SAP
This section describes the deprecated features in Oracle Enterprise Repository 11g Release 1 (11.1.1):
Several system settings are deprecated and should have no impact if changed. However, it is recommended not to change these in a production environment. For example, Database Connection Name, Company Name, and so on.
The APIs in Repository Extensibility Framework (REX) are deprecated, and will be replaced in a major future release, however, you can still continue to use REX APIs in 11g Release 1 (11.1.1) and in other minor releases of Oracle Enterprise Repository 11g.
The next major release of Oracle Enterprise Repository, which is 12g, is planned to include significant modifications to the current APIs in REX in order to align with standards, and improve ease of use and integration.