The chapter describes the new and changed functionality in Oracle Enterprise Repository 11g Release 1 (11.1.1).
This chapter contains the following sections:
Section 19.1, "What's New in Oracle Enterprise Repository 11g Release 1 (11.1.1)"
Section 19.3, "Enhancements in Oracle Enterprise Repository"
This section describes the new features and functionalities in Oracle Enterprise Repository 11g Release 1 (11.1.1):
Highly Automated Closed Loop Governance
In the Oracle Enterprise Repository 10g R3 release, the enterprise repository was able to harvest from design-time environments. In 11g R1, Oracle Enterprise Repository also harvests at deployment and runtime. The harvesting process automatically creates assets and their relationships in Oracle Enterprise Repository, saving huge amounts of time, providing the visibility that is needed to manage SOA, ensuring that information is fresh, and reducing risk.
In addition to harvesting "down stream", Oracle Enterprise Repository can also harvest BPEL generated from Oracle's BPA product. In this way, you can design business processes in BPA. BPA generates a project in JDeveloper, and Oracle Enterprise Repository harvests the resulting artifacts.
In the Oracle Enterprise Repository 11g R1 release, Oracle Enterprise Repository propagates services to multiple service registries supporting the runtime environments. As a service moves from development to testing, Oracle Enterprise Repository promotes the service to the organization's test registry. As the service moves from testing to staging, Oracle Enterprise Repository promotes the service to the organization's staging registry, and so on. The service keys are consistent across Oracle Enterprise Repository and all registry instances. This means that a Service Bus or SOA Suite project can perform dynamic endpoint discovery as the project moves through the lifecycle.
Oracle Enterprise Repository can also promote partial information to the Service Registry. This enables you to perform late binding. In this scenario, the service descriptions and categorizations are established in Oracle Enterprise Repository at design-time, but the endpoint is not defined until runtime. When the service is deployed, the endpoint is updated in Oracle Enterprise Repository. Oracle Enterprise Repository can promote the endpoint to Oracle Service Registry, or the endpoint can be directly populated to Oracle Service Registry, and harvested back into Oracle Enterprise Repository.
In addition, a summary of runtime performance metrics is being provided to Oracle Enterprise Repository from Enterprise Manager Management Pack Plus for SOA, as well as from third party tools including Amberpoint. This allows you to see whether your services are performing as expected. In addition, developers interested in using the service can determine whether it meets their performance criteria. This builds trust and increases adoption.
Summary of Supported Features:
Harvesting at Deployment
Harvesting at Runtime
Harvesting Oracle BPA artifacts from JDeveloper
Oracle Enterprise Repository promotes services to multiple Service Registries
Support for late binding
Support for Enterprise Manager metrics
Support for Amberpoint metrics
Support for SOA Suite 11g
In Oracle Enterprise Repository 10g R3, Oracle Enterprise Repository was able to harvest standards-based artifacts, including BPEL, WSDL, schemas and transformations. This ensured that Oracle could govern non-Oracle environments. In the 11g release, Oracle Enterprise Repository is harvesting more deeply from Oracle's own products. This provides with additional value - 1+1=3. In this release, Oracle Enterprise Repository can harvest composites from SOA Suite. Not only will Oracle Enterprise Repository capture the composite services and references, but it will capture the components within the composite. In addition, Oracle Enterprise Repository is harvesting more deeply from Oracle Service Bus, so customers will have visibility into the business services and their relationship to the proxy services, as well as xquery and microflows.
Moreover, Oracle Enterprise Repository is providing the "glue" to allow service bus and SOA Suite to seamlessly interoperate. The services from SOA Suite are captured in Oracle Enterprise Repository and are made available to the service bus through the Eclipse development environment. In addition, the proxy services created by Oracle Service Bus are captured in Oracle Enterprise Repository and made available to SOA Suite developers through JDeveloper. Oracle Enterprise Repository is a critical part of the solution for customers that want to take advantage of both SOA Suite and Oracle Service Bus.
Summary of Supported Features:
Harvesting Oracle SOA Suite composites from Oracle JDeveloper
Consuming through Oracle JDeveloper
Harvesting of Oracle Service Bus projects through Eclipse
Consuming services into an Oracle Service Bus project in Eclipse
Support for Applications
The Oracle Enterprise Repository 11g R1 release targets to use Oracle Enterprise Repository to manage application integrations. First of all, Oracle Enterprise Repository is teaming up with Oracle's Application Integration Architecture(AIA). AIA provides pre-built application integrations to speed up the integration efforts. AIA assets are made visible through Oracle Enterprise Repository, so the Enterprise repository is now the container through which you can view their integrations.
The second piece of functionality targeted towards application integration is the ability to view the services and adapters exposed by enterprise applications such as EBusiness, Siebel, Peoplesoft, JD Edwards, and SAP. You can use this information to build out application integrations. Oracle Enterprise Repository also provides end-to-end visibility between applications - from one application, through the adapter or native service, to the second application. This provides visibility needed to conduct impact analysis, and support end to end visibility and control of application integrations and composite applications.
Summary of Supported Features:
AIA 2.5 Solution Pack
AIA 3.0 Solution Pack
Adapter and Application assets included in the Harvester Solution Pack
Additional Features in Oracle Enterprise Repository 11g Release 1 (11.1.1):
Password Encryption - Oracle Enterprise Repository generates encrypted passwords used to interact with the Oracle Enterprise Repository API.
"Rollup" information about Composites, BPEL, WSDL - The Oracle Enterprise Repository User Interface has need refined to show a summary of the artifacts included in a composite application, business process, or Web service.
Harvesting WS-Policy Artifacts - Oracle Enterprise Repository can harvest WS-Policies referenced in WSDL, BPEL, and Composite artifacts.
New Reporting Engine - The Oracle Enterprise Repository Reporting engine is replaced by Oracle BI Publisher. Customers who purchase Oracle Enterprise Repository will receive a limited use license of Oracle BI Publisher for running Oracle Enterprise Repository reports. Customers will need a full use license to develop new reports in BI Publisher.
This section describes the general issues and workarounds in Oracle Enterprise Repository 11g Release 1 (11.1.1). This section contains the following topics:
This section describes the issues and workarounds found in Oracle Enterprise Repository.
In Oracle Enterprise Repository 10g Release 3 (10.3), while you are logged into Oracle Enterprise Repository if admin also logs in and modifies your login password, then you would receive an HTTP Status 500 exception. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
In Oracle Enterprise Repository 11g Release 1 (11.1.1), when use/downloading an asset, the list of associated files are now ordered by name.
In Oracle Enterprise Repository 10g Release 3 (10.3), when exporting an asset to Excel, the true/false properties of an asset that are represented by an option in Excel, were always set to true, regardless of the value in Oracle Enterprise Repository. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
In Oracle Enterprise Repository 10g Release 3 (10.3), some of the XSLTs for the PDF reports had a heading for Registration Status. However, they were showing values for the Active Status, which was incorrect. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1) to show Registration Status Values.
In Oracle Enterprise Repository 10g Release 3 (10.3), when importing multiple assets that were related to each other using the Import/Export tool, if one of those assets already existed in the Oracle Enterprise Repository instance, then the import would not save the relationship between the two assets. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
In Oracle Enterprise Repository 10g Release 3 (10.3), when exporting an asset to Excel, the date fields were not supported. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1) to support date fields.
In Oracle Enterprise Repository 10g Release 3 (10.3), the Advanced Search option was not working with Acceptable Value List values containing "&" character. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
In Oracle Enterprise Repository 10g Release 3 (10.3), the security fix added in the newer versions of JRE such as 1.5.0_15, 1.6.0_05, 1.6.0_06, 1.6.0_07, and 1.6.0_10 RC caused authentication issues launching the Asset Editor window and Import/Export tool. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
When specifying a URI relative to an Artifact Store, the URI must resolve to a file such as a .wsdl or .zip file. The URIs that point to directories are not supported.
The Enterprise Manager has no information about the WSDL Location for Endpoints of WSDL Artifacts from Oracle Service Bus. So,whenever the Enterprise Manager Integration utility creates the missing Endpoints for the matching assets in Oracle Enterprise Repository, it can not relate such Endpoints to its WSDL Artifacts and hence publishing them to Oracle Service Registry is not supported.
In Oracle Enterprise Repository 10g Release 3 (10.3), when an update was made to any property that was present in a .properties file in a clustered environment, then these get updated only on the cluster member server on which the user session was running. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
In Oracle Enterprise Repository 10g Release 3 (10.3), when Oracle Enterprise Repository is integrated with eTrust SiteMinder Single Sign-On (SSO), then the Import/Export tool is not available for a role which has the admin privilege. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
In Oracle Enterprise Repository 10g Release 3 (10.3), there was a synchronization issue between the cluster members when the load on application increases to three users working concurrently on the application. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
In Oracle Enterprise Repository 11g Release 1 (11.1.1), it is expected that artifact assets will have unique fingerprints (SFIDs). When migrating assets from previous releases, multiple artifact assets yield the same fingerprint, then the migration tool logs an error indicating that the assets must be merged before migration. The migration tool can not automatically merge these assets because it would potentially lose data.
During installation of Oracle Enterprise Repository 11g Release 1 (11.1.1), in the Initialize Repository Database Properties dialog, you are prompted to click the Browse button to browse for the JDBC driver file. The JDBC Driver Jar File Selection dialog is displayed, but the text in this dialog do not display correctly.
When you run Oracle Enterprise Repository 11g Release 1 (11.1.1) console on WebLogic Server version 10.3.2 on IBM AIX on Power Systems (64-bit), then the following exception is displayed:
Root cause of ServletException.
weblogic.servlet.jsp.CompilationException: Failed to compile JSP /index.jsp
index.jsp:6:5: No tag library could be found with this URI. Possible causes
could be that the URI is incorrect, or that there were errors during parsing
of the .tld file.
<%@ taglib uri="/skintags" prefix="skin" %>
^----^
index.jsp:6:5: No tag library could be found with this URI. Possible causes
could be that the URI is incorrect, or that there were errors during parsing
of the .tld file.
<%@ taglib uri="/skintags" prefix="skin" %>
^----^
.
at
weblogic.servlet.jsp.JavelinxJSPStub.reportCompilationErrorIfNeccessary(Javeli
nxJSPStub.java:226)
at
weblogic.servlet.jsp.JavelinxJSPStub.compilePage(JavelinxJSPStub.java:162)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:246)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:191)
at
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:235)
Truncated. see log file for complete stacktrace
>
You must apply the WebLogic Server patch 10.3.2, using the Smart Update tool, with the following details:
Patch id: 7LLC
Patch Passcode: 3JWIS7B5
This is valid only when Oracle Enterprise Repository 11gR1 is run on WebLogic Server version 10.3.2 on IBM AIX.
Then, you must set the JAVA_OPTIONS parameter for the Oracle Enterprise Repository Server as follows:
export JAVA_OPTION="$JAVA_OPTIONS
-Dorg.apache.xml.dtm.DTMManager=org.apache.xml.dtm.ref.DTMManagerDefault"
This section describes the issues and workarounds found in the Oracle Enterprise Repository Asset Editor:
In the Asset Editor, the Table elements were not persisting Date sub-elements properly. If you do not enter a value for the Date field within a table element or if you leave it blank, then the field is automatically populated with the current date. Also, if you enter your own date, the Date field would still show the current date. However, when saved, the correct date would then appear.
In the Asset Editor, add a Table element to an Asset Type. Within that table, add a Text element and a Date element.
Pick an asset of that Asset Type and modify the new element. First, add only to the Text field and leave the Date field blank. Click OK to close the child window. The parent window should NOT show any date in the Date field.
Modify the Table element again. Now, add a date that is anything other than the current date. Click OK. The parent window should show the date you entered.
In Oracle Enterprise Repository 11g Release 1 (11.1.1), you have the option of searching for a specific service created by the harvester in the Asset Editor, and viewing that service's Endpoint and Interface Web Services. In the Use - Download dialog, you can either select Endpoint assets or Interface assets. If you select Endpoints, then usage is automatically recorded for Interfaces.
This feature is also extended to Business Process: BPEL assets. When you select a Business Process for a BPEL asset, then a list of all deployments of that asset and a list of all Entry Points for each deployment are displayed in the Use - Download dialog. For each Entry Point that is selected, usage for the defining interface is automatically recorded.
In Oracle Enterprise Repository 10g Release 3 (10.3), when creating an asset, if no version information was provided in the Asset Version field, then it would create duplicate assets. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
In Oracle Enterprise Repository 10g Release 3 (10.3), when submitting large files greater than 34,455,552 bytes in the Asset Editor, the Asset Editor would hang. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
In Oracle Enterprise Repository 10g Release 3 (10.3), the contacts in the Asset Editor were not able to be updated. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
In Oracle Enterprise Repository 10g Release 3 (10.3), the copy/migrate function in the Asset Editor does not create the proper registration status for an asset. If the asset being copied was set to the Registered status and if you selected the Unsubmitted status during the copy/migrate process, then the asset triggers the Registered Asset event. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
In Oracle Enterprise Repository 10g Release 3 (10.3), in the Navigator, the display name for the relationship to Producing Projects was hard coded. However, that display name could be modified in the Type Manager. In past releases, a change to the display name would never appear in the Navigator. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
When you open any asstes in Asset Editor, the post non-preview mode migration leads to "Premature end of file". This fails in Firefox with JDK 1.5.0_09 and lower, and also in WebLogic.
The workaround for this issue is to ensure that you use JRE 1.5.0_10 when you run the Asset Editor. If you run the Asset Editor in Internet Explorer with the JDK version 1.5.0_09 and lower, then it will work. After running it in Internet Explorer, if you run it immediately in Firefox, it again works. But, on the other hand, if you delete the cookies in Internet Explorer and then run in Firefox, then it fails.
In Oracle Enterprise Repository 11g Release 1 (11.1.1), when you resize the navigator window quickly, it does not resize properly as there is a problem redrawing the applet,therefore the navigator window in the size of the original window. This is a noted JDK error.
This section describes the issues and workarounds found in Oracle Enterprise Repository Harvester:
In Oracle Enterprise Repository 10g Release 3 (10.3), when a WSDL was harvested, the documentation element was never stored in the Asset's description field. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
The MDS subsystem can only be initialized once per harvesting run. Therefore, in an ant script with multiple invocations of <repository.submit>, the value of the mdsSettingsFile attribute from the first invocation applies to all the later invocations.
Harvesting any remote hosted artifacts leads to the FileInfo reference to the same remote host URL whereas harvesting the .jar/.zip files refers to the Oracle Enterprise Repository artifacts. When the .jar and .zip files are harvested from a remote server, their artifact contents are stored in Oracle Enterprise Repository. Therefore, downloads of these assets only download the files from Oracle Enterprise Repository. And Exchange Utility does not push these artifacts to UDDI because they are stored in Oracle Enterprise Repository.
When you have two SOA Suite composite projects that have the same name and revision number, then harvester produces duplicate composite assets.
To avoid creating duplicate composite assets, ensure that you specify a different namespace in harvester when harvesting the two projects.
In Oracle Enterprise Repository 10g Release 3 (10.3), WSDL summaries are are not stored on Artifact:WSDL assets by Harvester and Exchange Utility. These are stored on the associated Service and Interface:WebService assets. To view the WSDL Summary, see the Service or Interface:WebService assets.
Whenever a WSDL with imports using the Classpath protocol is harvested and pushed to Oracle Service Registry, its t-models are not accessible in Oracle Service Registry. This is because Oracle Service Registry does not support the Classpath protocol.
In Oracle Enterprise Repository 11g Release 1 (11.1.1), publishing of artifacts using the Classpath protocol to Oracle Service Registry is not supported.
The Harvester command-line and ant task do not support reading the filesystem directory, which backs a project in Oracle Service Bus Workshop. For example, C:\bea\user_projects\workspaces\default\my_project.
To introspect an Oracle Service Bus project, you must either:
introspect it from Oracle Service Bus Workshop using the Oracle Service Bus > Submit to Oracle Enterprise Repository option.
export the project using the Export > Oracle Service Bus > Configuration Jar option, and harvest the exported jar file from the Harvester command-line or ant task.
In Oracle Enterprise Repository 10g Release 3 (10.3), Harvester creates multiple METADATAENTRY tables for every run, without verifying if the table already existed. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1), where the Harvester first verifies if the table exists, if not then creates a METADATAENTRY table.
When harvesting from the SCM systems, the following artifact types are not supported for CVS type SCM systems:
http/https
RawURI
Harvester supports only RawSCM.
When harvesting from the SCM systems, it is not possible to harvest the whole directory files (set of files under a directory) in a SCM system.
When you upgrade to the 10.3.1 Harvester, you must re-harvest your Oracle Service Bus projects to ensure that the projects are in the correct format.Oracle Enterprise Repository does not support Oracle Service Bus projects from Oracle Service Bus Workshop (pre-10.3) in the same Oracle Enterprise Repository instance as Oracle Service Bus projects from the 10.3.1 Harvester.
Harvesting Oracle Service Bus project jars are not supported from JDeveloper because Oracle Service Bus is not yet integrated into JDeveloper. Harvesting Oracle Service Bus project jars must be done from Oracle Service Bus Workshop, the Harvester command-line, or the Harvester Ant task.
By default, the harvester makes all of its changes to Oracle Enterprise Repository in a single transaction. When processing multiple composites on a server, the harvester fails.
The workaround for this problem is to harvest each project separately, in a separate command-line call or ant task by specifying each project:
<remoteProjects>
<projectName>ExternalPartnerSupplierEjb</projectName>
</remoteProjects>
Harvesting from Oracle SOA Suite server fails, if the Oracle SOA Suite managed server has SSL enabled.
The following error messages are displayed by the Harvester:
@ javax.net.ssl.SSLHandshakeException: sun.security.validator.Validator Exception: PKIX path building failed: sun.security.provider.certpath.SunCertPath BuilderException: unable to find valid certification path to requested target
You can workaround this issue by following either of these methods:
export the SSL certificate from the Oracle SOA Suite managed server, and import into the JVM, which is running Harvester.
disable SSL on the Oracle SOA Suite managed server.
This section describes the issues and workarounds that are found in Oracle Enterprise Repository Exchange Utility:
In Oracle Enterprise Repository 10g Release 3 (10.3), the Exchange Utility generates an exception when a service was published that had multiple end points and more than one of those end points had the same access point. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
In Oracle Enterprise Repository 10g Release 3 (10.3), when a WSDL had definitions for multiple services, port types, or bindings, the Exchange Utility was only publishing the first one it found. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
When publishing a service from Oracle Enterprise Repository to Oracle Service Registry, Exchange Utility creates a Binding Template TModel in Oracle Service Registry representing the Endpoint Asset from Oracle Enterprise Repository. If that asset is retired or inactive, Exchange Utility still creates that TModel, which is incorrect. The retired or inactive assets should not be published to Oracle Service Registry. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
While receiving any sample service that already exists in Oracle Service Registry 10.3 to Oracle Enterprise Repository through the Exchange Utility, it fails with an exception due to the following reasons:
The sample services in Oracle Service Registry 10.3 are digitally signed (contained enveloped digital signatures), therefore, Exchange Utility is unable to deserialize the soap response and receiving these services fail.
There are XSD imports in the WSDL that are not resolvable, thus receiving services fails with an exception.
However, Oracle Service Registry receives a sample service through Exchange Utility, when a new service is published within Oracle Service Registry directly and then the utility is run to fetch it to Oracle Enterprise Repository.
In Oracle Enterprise Repository 10g Release 3 (10.3), the Exchange Utility creates temporary files in the configured temp directory. In certain instances these files were not being cleaned up. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
The Exchange Utility supports pushing Amberpoint Metrics to Oracle Enterprise Repository that are stored in Oracle Service Registry. However, those metrics are not published to Oracle Service Registry from Oracle Enterprise Repository because it only supports a one-way transaction.
In Oracle Enterprise Repository 10g Release 3 (10.3), when publishing from Oracle Enterprise Repository to a UDDI Registry, the description of the Business Entity was not being included. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
When publishing a service from Oracle Enterprise Repository to Oracle Service Registry, if the service's endpoint had an invalid access point, Exchange Utility generates an exception. In Oracle Enterprise Repository 11g Release 1 (11.1.1), if the access point is invalid, then no exception is generated, but the service is not published unless the following setting is set to true in the orrxu.properties file:
cmee.import.uddi.publish.ifendpointmissing=true
In Oracle Enterprise Repository 10g Release 3 (10.3), when receiving services with no categorizations from Oracle Service Bus to Oracle Enterprise Repository, the Exchange Utility encountered a null pointer exception. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
When an Oracle Enterprise Repository asset contains internal.alrr.exchange.store metadata from Exchange Utility, then the Data Migration Tool connects to Universal Description, Discovery and Integration (UDDI) registry to update this metadata. If the UDDI registry for a particular Oracle Enterprise Repository asset cannot be accessed, then migration fails for that asset.
In Oracle Enterprise Repository 11g Release 1 (11.1.1), the migration tool, with exceptionally large data sets, may take hours to run. Some application servers may time out the sessions and cause the migration to fail.
To prevent this, the following entry should be added to the web.xml file, within the <webapps> element, where the number is in minutes:
@ <session-config> @ <session-timeout>120</session-timeout> @ </session-config>
In Oracle Enterprise Repository 11g Release 1 (11.1.1), services that are published from ALER 3.x to Universal Description, Discovery and Integration (UDDI) via Exchange Utility are not completely migrated, and therefore, they will fail publishing to UDDI after migration.
Manually update the Service Key on the asset in Oracle Enterprise Repository, before or after data migration.
This section describes the issues and workarounds that are found in Oracle Enterprise Repository Extensibility Framework:
In Oracle Enterprise Repository 10g Release 3 (10.3), the ArtifactStoreQuery query only searched for RawSCMs and does not return the correct list of the artifact stores. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1), where the REX query searches and returns all artifact stores.
In Oracle Enterprise Repository 11g Release 1 (11.1.1), null exception handling is added to REX for querying on Acceptable Value Lists, Assets, Contacts, Departments, Relationship Types, Roles, System Settings, and Vendors.
In Oracle Enterprise Repository 10g Release 3 (10.3), querying in REX by Role Name does not work. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
In Oracle Enterprise Repository 10g Release 3 (10.3), the IN operator was supposed to perform asset searches in REX. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1), which means you can create searches with multiple criteria on the following fields: id, assettypeid, createdbyid, and submittedbyid.
The following is an example of how to create a SearchTerm object to perform this search:
SearchTerm term = new SearchTerm();
term.setKey("assettypeid");
term.setOperator("in");
term.setValue("159, 166");
In Oracle Enterprise Repository 10g Release 3 (10.3), when querying with all of the Repository Extensibility Framework (REX) subsystems, if no criteria is entered for a criteria object, then it returns all results. For Role Type querying, however, it would generate a null pointer exception. This is fixed in Oracle Enterprise Repository 11g Release 1 (11.1.1).
This section describes the enhancements for Oracle Enterprise Repository 11g Release 1 (11.1.1). This section contains the following topics:
Section 19.3.1, "General Oracle Enterprise Repository Enhancements"
Section 19.3.3, "Repository Extensibility Framework (REX) Enhancements"
This section describes the general Oracle Enterprise Repository enhancements:
In Oracle Enterprise Repository 11g Release 1 (11.1.1), Oracle Enterprise Repository Diagnostics page is disabled, by default. When you open the Diagnostics page in the default mode, the following message is displayed:
Diag pages are currently disabled. Please contact your Oracle Enterprise Repository Administrator.
To enable the Diagnostics page, the vm-argument diagPagesEnabled parameter must be set to true, when the system is started.
It is recommended to only enable when necessary and disable once the system is running without any issues.
In Oracle Enterprise Repository 11g Release 1 (11.1.1), it is recommended to use encrypted passwords. The key areas where the encrypted passwords must be used are:
Oracle Enterprise Repository database.properties file
Oracle Enterprise Repository property files
Harvester configuration file and passing passwords on command line
Exchange Utility configuration file and passing passwords on command line
To obtain an encrypted password, Oracle Enterprise Repository provides a encrypt string tool in the Diagnostics page. For Harvester and Exchange Utility, you can also run the encrypt.bat or encrypt.sh scripts to encrypt the passwords in the configuration files page.
For more information, see Oracle Fusion Middleware Exchange Utility User Guide for Oracle Enterprise Repository.
Search results in the Asset Search, in the Web console, are now limited by default, to improve initial search performance. The number of results is configurable on the Admin > System Properties screen: cmee.search.assets.maxresults. If a search exceeds the maximum number of results, then the search results screen shows a result count such as Results (1000 of 2345), and the Show All link brings back all of the results.
Assets that are prefixed with a namespace and are identified by surrounding curly brackets have that prefix parsed out of the name in the search results for Assets, Mystuff, and Projects.
The internally generated Asset Type schema now contains the Unique Element element.
For SSO headers, Oracle Enterprise Repository offers the ability to control overwriting the following user attributes:
Firstname
Middlename
Lastname
Phone
Status
These attributes are overwritten if values for them are passed in during login. Otherwise, the user attributes are unchanged.
Customers can now proxy download requests for asset file attachments to a repository host with a username and password.
The selected credential information is removed from the LDAP log file.
In Oracle Enterprise Repository 11g Release 1 (11.1.1), the default character encoding for Oracle Enterprise Repository is changed to UTF-8.
In Oracle Enterprise Repository 11g Release 1 (11.1.1), the engine for reports has changed from an internal engine, to Oracle BI Publisher. After you have installed and upgraded to 11g Release 1 (11.1.1), you need to install Oracle BI Publisher, deploy reports, and configure Oracle Enterprise Repository to integrate with Oracle BI Publisher, else Reports will not function properly.
In Oracle Enterprise Repository 11g Release 1 (11.1.1), the Harvester is enhanced to support the following:
Harvester now supports introspecting of remote artifacts, by their URL.
Harvester now supports relative imports within local and remote artifacts.
Harvester now supports files and URLs with any extension. For example, this includes URLs that end with ?wsdl. In the case where the file type cannot be determined by the harvester, it can be specified on the command line or in the HarvesterSettings.xml file.
Harvester now supports XSD Schemas with <DOCTYPE> DTD elements.
Repository Extensibility Framework (REX) has been enhanced to support the IN operator for Asset searches. The only fields that are supported with this operator are id, assettypeid, createdbyid, and submittedbyid.
In Oracle Enterprise Repository 11g Release 1 (11.1.1), the Exchange Utility has been enhanced to support the following:
The Exchange Utility now handles receiving Oracle Service Registry services where the service's WSDL contains multiple service definitions.
The Exchange Utility has been enhanced to support Java WSDL Extensions.
The Exchange Utility has been enhanced to receive services from Oracle Service Registry to Oracle Enterprise Repository that have imports that reference a URL with the protocol of classpath.
When publishing the service to a UDDI Registry using the Exchange Utility, the WS-Policies that are applied to a service in Oracle Enterprise Repository are now included as metadata. These policies are represented as categorizations of a service.
The UDDI Registry plugin, which can be applied to an Asset Type and is applied to Service by default, has multiple functions. First, if the asset has not been published to any UDDI registry, then you have the ability to enter in a Service Key that is to be associated with this asset when published to any registries in the future. Once this service has been published, then the service key becomes read-only.
Another function of the plug-in is to show all UDDI registries that this service has been applied to. This list includes the registry name (taken from the orrxu.xml file), the registry URL, and the service key.
This section describes the deprecated features for Oracle Enterprise Repository 11g Release 1 (11.1.1). This section contains the following topics:
Instead of the using the several obsolete importers, which are removed from Oracle Enterprise Repository, use the Harvester tool.
Note:
For more information on how to use the Harvester tool, see Oracle Fusion Middleware Harvester User Guide for Oracle Enterprise Repository.The following import options are removed from Web UI, under Admin > Import:
Import WSDL
Import BPEL
Import from UDDI
The following options have been removed from the Asset Editor:
Import WSDL part of the WSDL Plugin
The UDDI Registries folder in the Assets tree
The support for the following formats are removed from the FlashlineRegistry.importExecute() REX method:
WSDL
BPEL
UDDI
The following system properties that were related to the above are removed:
cmee.import.uddi.enabled
cmee.import.wsdl.enabled
cmee.import.wsdl.service.assettype
cmee.import.wsdl.xsd.assettype
cmee.import.wsdl.dtd.assettype
cmee.import.wsdl.relationship.imports
cmee.import.wsdl.relationship.same-wsdl
cmee.import.bpel.enabled
cmee.import.bpel.service.assettype
cmee.import.bpel.relationship.imports
cmee.import.bpel.relationship.same-bpel
Oracle Enterprise Repository is no longer supported as a UDDI Registry. Therefore, the following system settings are deprecated:
cmee.uddi.server.wsdl.mapping
cmee.uddi.server.accesspointtype.mapping
cmee.uddi.server.accesspoint.mapping
cmee.uddi.server.suppress.instdet
cmee.uddi.user.password
cmee.uddi.user
The Asset Use by Project Within a Department report has been deprecated and removed. You can retrieve the same information by using the Asset Use by Project report.
Jive forums have been completely removed from Oracle Enterprise Repository. It is no longer part of the Oracle Enterprise Repository product.
In Oracle Enterprise Repository 11g Release 1 (11.1.1), the Actuate Reporting Engine has been replaced with Oracle Business Intelligence Enterprise Edition.
This section describes the deprecation planned for the upcoming Oracle Enterprise Repository releases.
In the upcoming Oracle Enterprise Repository releases, support from Tomcat would be changed to JBoss. If you need to install Oracle Enterprise Repository 11g Release 1 (11.1.1) on Tomcat, then contact the Oracle Support team.
In the upcoming Oracle Enterprise Repository releases, the support for the existing Repository Extensibility Framework (REX) API would be replaced with a newer version that would not support the features available in the current API.