OSR Cluster Install-Certificate Doesn't Match Host Name (Doc ID 762990.1)

Last updated on JULY 08, 2024

Applies to:

Symptoms

The purpose of this note is to provide further resolution details for an Oracle Service Registry install issue. This information is supplemental information for published known bugs or other provided notes.

You have an Oracle Service Registry/UDDI repository deployed in a clustered topology. You are not using a single repository style deployment. The publication and discovery repositories are split.

These are run by different OC4J instances. This issue is with the discovery repository, deployed to an OC4J instance named "OC4J_OSR" on each machine. When the discovery repository is running in clustered mode, one node has to be designated as the "configurationManager". All nodes running the discovery repository have a "configurationListener".

At startup each configurationListener must register with the designated configurationManager. This registration takes the form of a URL request (the request itself is a SOAP call). The configuration driving this is a file:

<REGISTRY_WEB_MODULE>/app/uddi/conf/configurator.xml

Key entries are:

[1] configManagerUrls

with the <httpsPreferences name="https"> element of the following config file:

[registry.ear]/[registry.war]/conf/oracle-servletconf.xml

You set this in the 'oracle-serveletconf.xml' file but still notice the same error. What can be done now to fix this ?

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.