Oracle® Fusion Middleware Release Notes 11g Release 1 (11.1.1) for HP-UX Itanium E14773-21 |
|
![]() Previous |
![]() Next |
The chapter describes the new and changed functionality in Oracle Enterprise Repository 11g Release 1 (11.1.1.3).
This chapter contains the following sections:
Section 22.1, "What's New in Oracle Enterprise Repository 11g Release 1 (11.1.1.3)"
Section 22.3, "Enhancements in Oracle Enterprise Repository"
This section describes the new features and functionalities in Oracle Enterprise Repository 11g Release 1 (11.1.1.3):
Closed Loop Governance for Oracle Service Bus 11g Release 1 (11.1.1.3)
Oracle Service Bus (OSB) can now consume SOA Suite Business Services through Oracle Enterprise Repository from the Eclipse environment. When OSB generates proxy services, the proxy services are harvested into Oracle Enterprise Repository. Oracle Enterprise Repository promotes the proxy services to the Oracle Service Registry, and Enterprise Manager provides runtime performance metrics for the proxy service to the Enterprise Repository.
Change in Oracle JDeveloper 11g Release 1(11.1.1.3) Connection to Oracle Enterprise Repository
In Oracle JDeveloper 11g Release 1(11.1.1.2) release, the Oracle Enterprise Repository adapter and the SOA adapter were bundled together. When you installed SOA, you automatically received the Oracle Enterprise Repository adapter.
In the Oracle JDeveloper 11g Release 1(11.1.1.3) release, there are three separate plugins:
a plugin for the SOA extensions
a plugin for Oracle Enterprise Repository that provides Oracle Enterprise Repository search capability
an Oracle Enterprise Repository harvester plugin
To obtain the Oracle Enterprise Repository plugins for Oracle JDeveloper:
In Oracle JDeveloper, click Help, Check for Updates.
In the Check for Updates wizard, select the Internal Automatic Updates option and click Next to install the updates.
Note: The Oracle Enterprise Repository adapters work with the Oracle Enterprise Repository 11g Release 1 (11.1.1.2) Oracle Enterprise Repository server. |
Basic Visibility for OWSM and WLS Policies
When Oracle Enterprise Repository harvests assets with OWSM or WLS policy attachments, the relationship between the assets and the policies is reflected in the Oracle Enterprise Repository metadata.
Critical Bug Fixes for Customer Escalations
The bug fixes and workarounds are identified in Section 22.2, "General Issues and Workarounds".
Support for 11g Release 1 (11.1.1.3) Components and Platforms
The Oracle Enterprise Repository 11g Release 1 (11.1.1.3) list of Supported Platforms is available from the Oracle Enterprise Repository OTN page:
http://www.oracle.com/technology/products/soa/repository/index.html
Certify with Enterprise Manager 11g Release 1 (11.1.1) Grid Control
Oracle Enterprise Repository has also been certified with Enterprise Manager (EM) 11g Release 1 (11.1.1) Grid Control, ensuring that runtime performance metrics monitored by EM are provided to Oracle Enterprise Repository.
This section describes the general issues and workarounds in Oracle Enterprise Repository 11g Release 1 (11.1.1.3). It includes the following topics:
This section describes the issues and workarounds found in Oracle Enterprise Repository.
When you select the Edit button in the Edit Project dialog, the Add/Remove Users dialog is displayed. In earlier Oracle Enterprise Repository releases, the Search utility in the Add/Remove Users dialog was ignoring the criteria and returning all users, and thus was not working. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1.3).
In Oracle Enterprise Repository 11g Release 1 (11.1.1), all the Workflow shell scripts were hardcoded with the JDK path. This is modified in Oracle Enterprise Repository 11g Release 1 (11.1.1.3) to accept the JAVA_HOME
parameter set by you.
When Oracle Enterprise Repository is installed using the Container Managed Authentication with Role synchronization enabled, the Oracle Enterprise Repository Admin role is not recognized by the container.
Workaround:
Prior to enabling the Oracle Enterprise Repository Container Managed Authentication process, you need to create a role that at least one user will be a member of within the container's user directory, for example, LDAP/DB/XML File, etc. Then, set the enterprise.security.roletype.admin
value to this new 'group/role' name just prior to resetting the authentication properties and then, restart the Oracle Enterprise Repository application.
When the container is prompted, since the value of the enterprise.security.roletype.admin
property contains the name of a 'real' roletype, it is then assigned to the user's account and thus allowed the 'admin' level privileges within the Oracle Enterprise Repository application.
Oracle Enterprise Repository performance testing revealed high transaction response times and Database CPU utilization times on the Oracle Enterprise Repository homepage. This may be observed with a large number of concurrent users and more than 30,000 assets. This issue is caused by the five search queries included in the Oracle Enterprise Repository home page.
Workaround
Customize the Oracle Enterprise Repository homepage and remove some or all of the queries.
The Linux environment setup script, setenv.sh
, file found in the OBPM_SetupScripts
folder was out of sync with its .bat
version. The setenv.sh
file was missing variables and included incorrect paths. This script file has been updated to be in sync with the Windows environment setup script, setenv.bat
.
If the JRE of the browser is set to a version higher than JRE 1.6.0_10 and when the browser window for navigator is maximised to monitor screen, then the asset navigator diagram is not redrawn to the new window size.
Workaround
Click the graph icon in the Asset Description pane of the window. This redraws the asset diagram to the new window size.
This section describes the issues and workarounds found in the Oracle Enterprise Repository Asset Editor:
When the automatic login using cookies were disabled (enterprise.security.cookielogin.allow
) in WebLogic, then the navigator fails to launch.
If the asset name is greater than 123 characters, then Oracle Enterprise Repository truncates the character count to 123 and adds "v???". This problem only occurs when importing assets that already exist in Oracle Enterprise Repository. This does not occur when new assets are imported into Oracle Enterprise Repository.
This section describes the issues and workarounds found in Oracle Enterprise Repository Harvester:
When harvesting Oracle Service Bus projects, the assets are no longer created for policies. Instead, a harvester property is added to the service called Runtime Policies.
Harvested files with multi-byte characters (MBCS) are not being saved properly.
In Oracle Enterprise Repository 11g Release 1 (11.1.1), when harvesting a remote SOA composite that has a SOA Direct transport, the endpoint asset is created. However, the endpoint properties are incomplete as they are missing the endpoint URIs. In addition, the harvester was not recognizing the direct binding service. Thus, the endpoint was related to a wrong service. These issues are fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1.3).
In Oracle Enterprise Repository 11g Release 1 (11.1.1), the SOA Suite harvester was introspecting WSDL References in a composite. This caused duplicate endpoints to be created. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1.3), by not introspecting references in a composite.
When harvesting a WSDL, the Endpoint URI is obtained from the Address element that is a child of the Port element. However, if the Port element contained multiple child elements and the Address element was not the first one in the list, it would fail to retrieve the address. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1.3).
When harvesting SOA composites, if a promoted service has a direct binding, then the Transport type harvester property is set to soa-direct.
This section describes the issues and workarounds that are found in Oracle Enterprise Repository Exchange Utility(XU):
In Oracle Enterprise Repository 11g Release 1 (11.1.1), if the XU installation directory name had spaces, then the Exchange Utility publishing and receiving fails. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1.3).
Exchange Utility publishes only Web services that support SOAP, HTTP, and JMS protocols. EJB and Java services are not published to Oracle Service Registry.
The out-of-the-box XU configuration file now supports publishing of proxy services to Oracle Service Registry.
Exchange Utility (XU) comes with a default configuration file called the orrxu.xml file. You can define your own configuration file and place it under any directory. When you run XU, you must ensure that you point to that file. However, there are sections in XU that still point to the out-of-the-box configuration file. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1.3).
This section describes the issues and workarounds that are found in Oracle Enterprise Repository Extensibility Framework:
In earlier releases of REX, when the assetDelete
method was called, it would delete the asset type records from the database. However, in Oracle Enterprise Repository 11g Release 1 (11.1.1.3), the asset type records are not deleted from database, instead they are just marked as inactive.
There are no enhancements in Oracle Enterprise Repository 11g Release 1 (11.1.1.3).
This section describes the deprecated features for Oracle Enterprise Repository 11g Release 1 (11.1.1.3). This section contains the following topics:
Deprecating Support for Tomcat
In Oracle Enterprise Repository 11g Release 1 (11.1.1.3), the support for tomcat is deprecated. If you need to install Oracle Enterprise Repository 11g Release 1 (11.1.1.3) on Tomcat, then contact the Oracle Support team.