1. Introduction to Oracle Service Registry:

Oracle Service Registry is not part of Oracle SOA Suit 11g, Oracle Enterprise Repository /Service Registry is a Critical part of SOA governance. The combination of the Enterprise Repository with a UDDI-compliant Service Registry provides a common communication channel for the automated exchange of metadata and service information between service consumers, producers, providers, and additional governance tooling. It provides the visibility, feedback, controls, and analytics to keep your SOA on track to deliver business value. The intense focus on automation helps to overcome barriers to SOA adoption and streamline governance throughout the lifecycle.

Oracle Service Registry (OSR) is a fully V3-compliant implementation of UDDI (Universal Description, Discovery and Integration), and one of the key components of Oracle SOA Suite 11g. It allows us to publish and discover services and service providers, and manage metadata about services (security, transport, or quality service) using taxonomies. Therefore, it plays an important role when trying to improve visibility and promote service reuse. It is also important in the scope of SOA governance.

Service registry is very important for various reasons. It provides a central place where all service definitions are stored. This becomes important when the number of services (including BPEL processes) grows. It helps to maintain overview of services. Service registry also provides a central place where developers can search for existing services. This improves service reuse, which is one of the most important aspects of SOA. Of course, service registry also provides means to publish services for other developers to discover and reuse.

In addition to reuse, service registry can also be helpful when we need to migrate services from one server to the other. This can happen because of various reasons, but one of the most common reasons is the migration between the development, test, and production environments. Service registry is also helpful when we need to version services and manage changes. With service registry we can also develop more loosely-coupled composite applications, because we do not need to hard-code the service URLs. Rather, the application will resolve URLs at run-time. In all cases, service registry is often used together with the ESB. We will not discuss all OSR details in this article. We will demonstrate how to publish a service, how to export/import resources between OSB and OSR, how to browse the OSR using JDeveloper, and how to enable dynamic endpoint lookup in a SOA composite application.

2. OSR User Creation in DB:

2.1. First we need to create OSR user in oracle DB with admin privileges as sysdba.

2.2. Next run the osr jar file from command line welcome window open click on next.

2.3. Select Installation type as Standalone registry click on next.

2.4.Create registry folder in middleware home directory

2.5. Select Registry home path from middleware and select check boxes for shortcuts for the Registry from start and desktop.

2.6. This windows is optional if we want email configuration we need to configure SMPT server details.

2.7. Administrator Account Configuration here we need give user name and password to the service Registry controls click on next.

2.8.Database setup here we have to connect to the schema here selecting Populate schema then Click on next.

2.9. Select DB type here select Oracle 10g/11g click on next.

2.10. Provide DB Details of OSR Schema user.

2.11. Select JDBC Data source as default no need to change.

2.12. Next select JDBC Driver location from your db or from web logic server click on next.

2.13. Select account provider information store in DB click on next.

2.14. Select Application server as Oracle Web logic 11g

2.15. Choose deployment of Domain Configuration.

2.16. Select HTTP port for Service Registry Console click on next.

2.17. Confirmation window click on next if we want change the property go back.

3. Installing Oracle Service Registry in the Same Domain as Oracle SOA Suite:

When installing Oracle Service Registry 11g in the same Weblogic Domain as Oracle SOA Suite, you may see the following error message on the WebLogic Server console when Oracle Service Registry is starting up:

java.lang.LinkageError: loader constraint violation in interface itable

initialization:....

To work around this issue:

Please refer below link:

http://docs.oracle.com/cd/E23549_01/relnotes.1111/e10133/install.htm

Solution: Better to create managed server in separate web logic domain.

4. Domain Configuration for Service Registry

4.1. We can configure the domain at levels extending the existing domain. Create new domain with new

Application server and managed server.

Here I am creating separate domain for service registry.

Click on next.

4.2. Select Domain Source as Oracle Service Registry click on next.

4.3. Enter domain location click on next.

4.4. Enter Password for web logic user click on next.

4.5. Select JDBC Data source as jdbc/registry enter osr db password and click next.

4.6. Select Admin Server setting click on next.

4.7. Change the Admin server port by default it is 7001 we can use any port out of Web logic click on next.

4.8. Click on Done.

5. OSR Server Start:

Now we can start the Server from OSR_Domain.

From command line we need to start admin server and osr server as below:

6. Oracle Service Registry Consoles:

Console windows for login to Oracle Service Registry Console and Business Service Control go to Programs-> Oracle Service Registry 11.1.1 click on here we can open consoles.

6.1. Oracle Service Registry: