Clustering Oracle Service Registry with Oracle WebLogic Server

Connect each subsequent Registry instance you install to this database schema. Supply the existing database username and password as part of this configuration. The next key difference in the installation process is that you must supply the same values for the following fields in the Deployment to Application Server panel of the installer for each Registry installation. These values, which are described below, will enable all Registry instances within the cluster to receive requests from the same Oracle HTTP Server instance. HTTP Port Oracle HTTP Server listener port SSL Port secure listener port Hostname Oracle WebLogic Server HTTP Server hostname – not Oracle WebLogic Server instance hostname Application Server Context Ensure that this value is the same across all instances Application Server Name Ensure that this value is the same across all instances If these values are configured correctly, then the Oracle WebLogic Server HTTP Server is able to route requests to any OSR instance in the cluster. For more information, see Section 7, Cluster Configuration .

2.5. Installation Summary

2.5.1. Directory Structure

The installation directory structure contains the following directories: bin Contains command-line scripts for running Oracle Service Registry. See Section 2.6, Command-line Scripts . conf Contains the Oracle Service Registry configuration files demos Contains demos of Oracle Service Registry functionality. For more information, please see Demos . dist Contains Oracle Service Registry client packages. doc Contains the Oracle Service Registry documentation. etc Contains additional data and scripts. lib Contains the Oracle Service Registry libraries log Contains logs of installation, setup, and server output. See Section 2.9, Logs . Page 61

2.5.1. Directory Structure

work This directory is a working area used by the command line tools.

2.5.2. Registry Endpoints

Oracle Service Registry is configured as follows. The host name, http port and ssl port are specified during installation and the application name are specified earlier. See Section 2.3.5, Application Server Settings for details. For each endpoint you can use either http or ssl port. • Business Service Control home page: http:host name:http portapplication nameuddibscweb • Registry Control home page: http:host name:http portapplication nameuddiweb • UDDI Inquiry API endpoint - http:host name:portapplication nameuddiinquiry See Developers Guide, Section 2.1.2, UDDI Version 1 , Section 2.1.3, UDDI Version 2 , Section 2.1.4, UDDI Version 3 . • UDDI Publishing API endpoint - http:host name:portapplication nameuddipublishing See Developers Guide, Section 2.1.2, UDDI Version 1 , Section 2.1.3, UDDI Version 2 , Section 2.1.4, UDDI Version 3 . • UDDI Security Policy v3 API endpoint - http:host name:portapplication nameuddisecurity See Developers Guide, Section 2.1.4, UDDI Version 3 . • UDDI Custody API endpoint - http:host name:portapplication nameuddicustody See Developers Guide, Section 2.1.4, UDDI Version 3 . • UDDI Subscription API endpoint - http:host name:portapplication nameuddisubscription See Developers Guide, Section 2.1.4, UDDI Version 3 . • Taxonomy API endpoint - http:host name:portapplication nameudditaxonomy See Developers Guide, Section 2.2.2, Taxonomy . • Category API endpoint - http:host name:portapplication nameuddicategory See Developers Guide, Section 2.2.3, Category . • Administration Utilities API endpoint - http:host name:portapplication nameuddiadministrationUtils See Developers Guide, Section 2.2.5, Administration Utilities . • Replication API endpoint - http:host name:portapplication nameuddireplication See Developers Guide, Section 2.2.6, Replication . • Statistics API endpoint - http:host name:portapplication nameuddistatistics See Developers Guide, Section 2.2.7, Statistics . • WSDL2UDDI API endpoint - http:host name:portapplication nameuddiwsdl2uddi Page 62

2.5.2. Registry Endpoints