Oracle Service Registry 11g Installation Strategies

To follow up on my recent post on the new OSR 11g release and Edwin Biemond's excellent blog Using Oracle Service Registry in SOA Suite 11g, I wanted to report on common practices and OSR 11g various install and deployment options. First, it is assumed that you will be using the new Domain deployment option which is described in the docs and in Edwin's blog. You need to choose a directory such as registry111 inside of the Middleware home where you installed WebLogic. The registry home will be a peer to wlserver and JDK directories as shown below. If you do not do this, you will end up will registry installer files that live in the WebLogic home and as they say, results are unpredictable.

WebLogic Directory Sructure
C:\Oracle\Middleware\11gR1PS1                                                <--WebLogic Home
C:\Oracle\Middleware\11gR1PS1\registry111                           <--OSR Home
C:\Oracle\Middleware\11gR1PS1\jdk160_14_R27.6.5-32     <--JDK Home
C:\Oracle\Middleware\11gR1PS1\wlserver_10.3                     <--WebLogic Server home

Other WL directories

Database Install Options
Another area that causes some confusion is the installer database options for which I will describe in detail. The UDDIUSER and UDDINODE names are the defaults and can be substituted for your preferred names.

1) Create New Tablespace Database
This is typically used when installing the first time and the installer knows the database system administrator username and password. It will create the UDDINODE tablespace, UDDIUSER database user and populate the schema. I use this when installing on my own laptop where the database resides.

2) Create Schema
This is typically used when you do not have database administrator's user and password and the UDDINODE tablespace and UDDIUSER have been pre-created for you by a database administrator. This is very common for organizations where a shared database is used and managed by a system administrator. The installer only prompts your for the UDDIUSER username and password and will populate this users schema. Note that all config files and logs do not expose whitespace passwords.

3) Connect to Schema
This is used for when you already have a fully populated database tablespace and user created typically from either one of the 2 options above or from the setup utility. All you have to provide for this option is the UDDIUSER user and password for later use. The installer will check the connection but not populate with seed data as it is assumed it has already been completed.

4) No database
This final option is when you just want to lay down the bits of the installer and use the OSR setup utility to create the database connection later. The setup utility lives in \bin\setup.bat.

Generally, you should use the database driver that ships with WebLogic in the following location.

As mentioned in Edwin's blog, if you want WebLogic to manage the database connections, you should check both boxes on the Data Sources screen to Use and Create a JDBC data source in WebLogic. This will be done in the post install step where you run the WebLogic configuration utility which lives at \wlserver_10.3\common\bin\config.cmd.

Some WebLogic Deployment Recommendations
OSR can be deployed to either it's own WebLogic managed server or the Admin server. It doesn't matter but make sure that you specify in the OSR installer to use the same port as you plan to use in WebLogic. For example, if you want to deploy to the admin server and it is using the default port of 7001, then make sure you specify port 7001 in the OSR installer. If you want to deploy to a separate WebLogic managed server and it is using the default like 7101, then specifiy port 7101 in the OSR installer. These values can be changed in the OSR setup utility mentioned above if you forget and use the incorrect port.

Finally, we have seen "loader constraint violation" startup errors when installing OSR into the same WebLogic domain as SOA Suite. A couple of workarounds for this are:
1) Put OSR into it's own WebLogic Managed Server and Machine
2) Create a separate WLS domain for deploying OSR to WebLogic until that is resolved.

Since the new OSR domain deployment feature only supports WebLogic 10.3.1(11gR1) and later, you should use the OSR Online Admin server deployment option for deploying alongside OSB 10.3 and 10.3.0. As promised, I'll post some info on clustering strategies and OER co deployment in future blogs.

Edwin Biemond: Using Oracle Service Registry in Soa Suite 11g


Is it possible to install Oracle Service Registry 11g to work with OAS 10g? Thanks, Andres

Posted by Andres Romero on February 10, 2010 at 05:11 AM PST #

OSR 10.3 was the last release to support deploying to OAS. OSR 11 deployed to WLS or Juddi DOES however support OAS SOA and JDev integration but 11g cannot be deployed to OAS itself. This sort of question would be great for the forums.

Posted by Dave Berry on February 10, 2010 at 05:24 AM PST #

Hi, I am working with Configuration management of OSR11g. Is it possible to create a new configuration file and associate it with a collection. I tried but am unable to create a new configuration file.

Posted by Abhishek Jana on March 25, 2010 at 04:30 PM PDT #

Hi Dave, I'm looking for information on OER and OSR co deployment - as per your post, you were planning to post that? Did you post that, if so can you pls send the link to it? Thanks Vinay

Posted by Vinay Kshirsagar on November 29, 2010 at 02:24 AM PST #

Hi Vinay, Did you see the blog entry at the following location? The direct link to the HA guide is at his link. dave

Posted by Dave Berry on November 29, 2010 at 03:23 AM PST #

Post a Comment:
  • HTML Syntax: NOT allowed

Latest news, updates, best practices and thoughts on Oracle SOA Governance products

Oracle SOA Governance includes Oracle Enterprise Repository, Oracle SOA Management Pack and our API Management Solution


« April 2014