Installation  Locate

This section describes the standalone installation of Oracle Service Registry and all settings.

To install the registry, type the following at a command prompt:

java -jar oracle-service-registry-11.1.1.jar

and follow the wizard panels. If you have associated javaw with *.jar files on Windows, just double-click the icon for the file oracle-service-registry-11.1.1.jar.

Registry Installation Options  Locate

Oracle Service Registry can be installed in several different configurations, depending on customer needs.

Standalone Registry Configuration With a standalone registry installation, there is a single instance of the Registry, shared by service publishers and service consumers. This is the simplest configuration, and allows for immediate sharing of service information. It is the most common choice for initial testing and evaluation use of the Registry.

Multi-Registry Configuration A multi-registry deployment is appropriate for environments where organizations want to impose more control over the contents of the registry available to service consumers. This quality control process is enabled by separating the Publication and Discovery Registries, and using an Approval Process to control promotion of services from staging to production. This approval process can be configured to use either manual or automated approval of promoted information.

  • Note that each registry requires a unique tablespace and schema within a database to serve as a metadata store. However, both tablespaces and schemas can be created safely within the same database instance.

In addition, one or more Intermediate Registry instances may be installed. An Intermediate Registry sits between one or more Publication Registries and a top-level Discovery Registry.

Command-line Options  Locate

Installation may be launched with following optional arguments:

java -jar oracle-service-registry-11.1.1.jar [[--help] | [-h] | [--gui] | [-g]]
[[-u configfile ] | [--use-config configfile ]]
[[-s configfile ] | [--save-config configfile ]]
[--debug]

-g | --gui starts the installation in gui mode (default).

-c | [--console] runs command-line installation

-h | [--help] shows help messages

-s configfile | --save-config configfile saves the installation settings into the configuration file without actually installing the registry. The configuration file contains all passwords entered in the installer. The passwords are normally encoded. If you want clear-text passwords, specify also option -t | --save-clear-text

-u configfile | --use-config configfile installs the registry using the settings contained in the configuration file.

--debug the installation produces more information to localize problems or errors.

Installation Panels  Locate

This section discusses the content of the installation wizard. It goes through installation panels using default settings.

Figure 1. Welcome Panel

Welcome Panel

Figure 1 shows the first panel of the installation wizard. The installation wizard helps you to install Oracle Service Registry to the Oracle WebLogic Server. To continue, click Next. To stop this installation at any time, click Exit. To return to a previous panel, click Back.

Installation Type  Locate

Figure 2. Installation Type

Installation Type

Figure 2 shows several installation scenarios. Select one.

Standalone registry

The default installation installs a standalone registry and enables the creation of a new registry database. The installed registry is usable without other registry installations unlike Discovery, Publication or Intermediate installation options which use several registry installations to define approval processes.

Discovery registry

Installs the discovery registry. This is the second part of the approval process registry installation. The discovery registry allows users to query Oracle Service Registry. For more information, please see Discovery Registry Installation.

Publication registry

Installs the publication registry of the approval process. The publication registry is one part of the approval process registry installation. The publication registry is a space for users to publish and test data prior to its approval for promotion to the discovery server. For more information, please see Publication Registry Installation.

Intermediate registry

Installs an intermediate registry in a multi-step approval process. The intermediate registry is an intermediate step in the process of promoting data from the publication to the discovery registry. For more information, please see Intermediate Registry Installation.

Figure 3. Installation Directory

Installation Directory

On the panel shown in Figure 3, type the path to the installation directory where Oracle Service Registry will be installed. The default directory is the current working c:\oracle\middleware\registry111 on Windows and /opt/oracle/middleware/registry111 on UNIX systems.

If you are installing on a Windows platform you can selected from the following:

Create shortcut icons on the desktop

If selected, icons for accessing the Registry Control, Business Service Control and the Setup tool will be created on the desktop.

Add shortcut icons to the Start menu

If selected, the icons noted above are added to the Start menu.

Program group name

Group name created in the Start menu where shortcut icons will be placed.

[Note]Note

You must have read and write permissions on the installation directory.

SMTP Configuration  Locate

Figure 4. SMTP Configuration

SMTP Configuration

Figure 4 shows SMTP configuration. The SMTP configuration is important when users needs to receive email notification from subscriptions and from the approval process.

SMTP Host Name

Host name of the SMTP server associated with this installation of Oracle Service Registry

SMTP Port

Port number for this SMTP server

SMTP Password

Self explanatory

Confirm password

Retype the same password. Note that if it is not same as the password in the previous box, you cannot continue.

SMTP Default Sender E-mail, Name

Oracle Service Registry will generate email messages with this identity.

Setup Administrator Account  Locate

Figure 5. Administrator Account

Administrator Account

Figure 5 shows Oracle Service Registry Administrator account setup. You need to provide the administrator's account name and password, so you can log in later and adjust the Oracle Service Registry configuration using Oracle Service Registry tools.

Administrator username

The name for the administrator account (default: admin)

Administrator password

The password for the administrator account.

Confirm password

For verification enter again the administrator password.

Administrator Email

E-mail address to reach the Oracle Service Registry administrator. This value will be displayed by the Oracle Service Registry tools as contact information for the product.

Database Settings  Locate

The registry requires a database which may be created during installation. During installation you can create a new database, create schema in an existing empty database or connect to an existing database with created schema. Using the Setup tool, you can also drop the database or database schema. Select your database creation method on the following panel.

Figure 6. Database Creation Method

Database Creation Method
Create database

Create new database/users/tablespaces (depending on the type of the database server) and database schema. This is the most comfortable way, but please note that you must know the credentials of the database administrator.

Create schema

Create a new schema in an existing database. Use this option if you have access to an existing empty database and the ability to create tables and indexes. This option is suitable when you do not know the administrator's credentials. We assume admin has already created a new database/users/tablespaces for this option.

[Note]Note

See Database Installation, for more information.

Configure database

Configure registry database. Use this option if the registry database already exists (For example, from a previous installation) and fill in only the connection parameters.

No database

Choose it if you intend to create a registry database later. Note that Oracle Service Registry cannot be started without a database.

Figure 7. Select Database

Select Database

Figure 7 shows the supported database engines that can be prepared for Oracle Service Registry.

You can specify the name of Oracle Service Registry installation. The name is saved to the operational business entity. The registry name appears in the upper right corner of Registry Control and Business Service Control.

Select Install demo data if you want to evaluate the provided Oracle Service Registry demos after installation.

The default database to create is the Oracle 10g.

The following list provides links to more information about specific settings for different Oracle database types.

Figure 8. The JDBC Driver

The JDBC Driver

Enter path to JDBC Drivers on the panel shown in Figure 8. The Oracle Service Registry needs to use the JDBC driver to access its database.

You can also check Use custom connection string and specify connection string instead of letting Oracle Service Registry to construct it.

The Oracle Service Registry supports installation on Oracle Database Real Application Clusters (RAC) using a custom connection string. For example:

jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP) (HOST=host1) (PORT=1521)) (ADDRESS=(PROTOCOL=TCP) (HOST=host2) (PORT=1521)) (LOAD_BALANCE=yes) (CONNECT_DATA=(SERVER=DEDICATED) (SERVICE_NAME=SID)))
            

Oracle Service Registry supports basic failover functionality (it does not support fast connection failover). When one node fails, the Oracle Service Registry is able to reconnect without a restart. However, in this case, failed requests must be resubmitted.

For more information, see "Configuring JDBC Client Failover" in the Oracle Database 2 Day DBA + Real Application Clusters Guide at http://download.oracle.com/docs/cd/B28359_01/rac.111/b28252/configwlm.htm#BABJDGJD.

Figure 9. Authentication Provider

Authentication Provider

Figure 9 allows you to select an authentication provider.

Database

All accounts will be stored in the registry database.

LDAP

Registry accounts integrated with LDAP server.

External

Registry accounts integrated with other external storage. The the interface com.systinet.uddi.account.ExternalBackendApi must be implemented and added to the registry installation.

Application Server Settings  Locate

The Oracle Service Registry is designed to run within several environments:

  • The Oracle WebLogic Server.

  • Embedded HTTP/HTTPS server.

You can select in which environment you want to run in following installer screen:

Each environment option requires to fill in different sets of details to function properly.

Oracle WebLogic deployment details  Locate

This section describes Oracle WebLogic deployment options. Both Oracle WebLogic 10.3 and Oracle WebLogic 11g are supported.

Invoke Oracle WebLogic installation by selecting WebLogic deployment option in the following installer screen:

[Note]Note

WL_HOME refers to the WebLogic directory or Oracle Middleware Home.

WL_SERVER_HOME refers to the WebLogic server installation directory. The default value is WL_HOME/wlserver_10.3. If you want to use direct deployment from Oracle Service Registry installer, you must provide this path. It is used to locate WebLogic deploy tool JAR files.

REGISTRY_HOME refers to the Oracle Service Registry installation directory. It must be placed under Oracle Middleware Home in case Domain Configuration.

REGISTRY_DEPLOY_DIR refers to the application server directory where the Oracle Service Registry distribution is unpacked. The default path is WL_HOME/user_projects/domains/ DOMAIN_NAME /servers/ SERVER_NAME /tmp/_WL_user/ REGISTRY_CONTEXT / RANDOM_NAME /public on both Oracle WebLogic 10.3 and 11g. Oracle Service Registry Setup tool uses this directory to locate registry configuration files.

The next installation screen requests a method deployment.

Domain Configuration is supported for Weblogic 11g only. Upon completion, you must run the Oracle WebLogic Configuration Wizard to create WebLogic domains. See more at Creating WebLogic Domains Using the Configuration Wizard. If you select Oracle Weblogic 10.3 on the previous page, Domain Configuration will not be shown.

The next installation screen requests URL components (hostname, port, ssl port, context) that Oracle Service Registry uses in its web user interface. If you use proxy or load-balancer, the URL components should point to it. The registry administrator can change the URL later in Registry Management. If the URL is incorrect the web UI cannot be accessed until the URL value is corrected in the configuration files. In the case of domain configuration, the hostname and port values in this page must be the same as the values set when running the Configuration tools to create the weblogic domain.

If you select "Online Server Deployment" in the Deployment method page, the following screen opens:

  • Fill-in the first directory to point to the Oracle Weblogic server directory. This directory should contain the deployer .jar (server/lib/weblogic.jar) inside.

  • The second directory is the JAVA_HOME of the Java Virtual Machine (JVM) to use with the deployer. Both SUN Java and JRockit Java distributed with Oracle WebLogic should work.

  • Hostname field indicates the machine you want to deploy to.

  • Admin username and password refer to the name and password of the administrator account in your WebLogic installation.

If you want to deploy manually you must specify the location of the Oracle Service Registry .war file. This file is in REGISTRY_HOME/conf/porting/weblogic/build/[context_name].war (if installation succeeded).

Other required changes to complete the integration:

  1. If you selected "Use SSL (HTTPS)" in the installer, import the SSL certificate of the WebLogic server to the Oracle Service Registry configuration.

    Use one of the following methods to obtain the WebLogic SSL certificate:

    • Use Internet Explorer 6.0 web browser connected to Oracle WebLogic via HTTPS. Select "Properties" in context menu of the page, button "Certificates", tab "Details", button "Copy to file", and then export certificate in Base 64 encoded X.509 .cer format.

    • Use REGISTRY_HOME/bin/sslTool.sh or REGISTRY_HOME\bin\sslTool.bat to get the certificate. Run command:

      sslTool serverInfo --url https://HOST:9043 --certFile weblogic.cer
      					

      This command connects to the specified host and port using HTTPS and stores the server certificate in the specified file.

    To import this certificate use the following command:

    PStoreTool located in [registry_home]/bin PStoreTool.sh add -config [registry_home]/conf/clientconf.xml -certFile [weblogic.cer]

  2. Enable SSL in WebLogic if not yet enabled and (re)start the Oracle WebLogic server.

Deployment should now be complete. The Oracle Service Registry URL is http://[hostname]:[http_port]/[context]/uddi/web

Creating WebLogic Domains Using the Configuration Wizard  Locate

This section provides information and examples for some common domain configuration tasks using the Configuration Wizard

Create New Domain with default Managed Server  Locate

  1. Start the Configuration Wizard in graphical mode.

    • On Windows: Start—>Programs—>BEA Products—>Tools—>Configuration Wizard or enter <WEBLOGIC_HOME>/common/bin/config.cmd

    • On UNIX: enter <WEBLOGIC_HOME>/common/bin/config.sh

  2. In the Welcome window select Create a new WebLogic domain

  3. In the Select a Domain Source window, select Generate a domain configured automatically to support the following BEA products and the Oracle Service Registry check box is selected

  4. In the Specify Domain Name and Location window, enter the name and location for the domain.

  5. In the Configure Administrator Username and Password window, enter a valid username and password, and click Next. This username is used to boot the Administration Server and connect to it

  6. In the Configure Server Start Mode and JDK window, specify whether to start the server in development mode or production mode, and select which JDK to use

  7. In the Configure JDBC Data Sources window, fill in the empty Password field to connect to the database successfully

  8. In the Test JDBC Data Sources window, check that the JDBC Data Sources configuration in the previous page is correct.

  9. In Select Optional Configuration indicate whether you want to change the distribution of your domain across servers, clusters, and machines

  10. In Configuration Summary, review the values supplied to the configuration and click Create to create the domain

  11. The domain will be created so long as there are no erroneous or conflicting values.

Extend Existing Domain and Target on an existing Managed Server  Locate

  1. Start the Configuration Wizard in graphical mode.

    • On Windows: Start—>Programs—>BEA Products—>Tools—>Configuration Wizard or enter <WEBLOGIC_HOME>/common/bin/config.cmd

    • On UNIX: enter <WEBLOGIC_HOME>/common/bin/config.sh

  2. In the Welcome window, select Extend an existing WebLogic domain

  3. In the Select a WebLogic Domain Directory window, navigate to the domain directory that you want to extend

  4. In the Select Extension Source window, you can choose to extend your domain by selecting an Oracle Service Registry

  5. In the Configure JDBC Data Sources window, fill in the empty Password field to connect to the database successfully

  6. In the Test JDBC Data Sources window, check that the JDBC Data Sources configuration in the previous page is correct.

  7. In Select Optional Configuration, select these options to configure servers, clusters, and machines

  8. After configuring these environments you can extend the existing domain.

Confirmation and Installation Process  Locate

Figure 10. Confirmation

Confirmation

Figure 10 shows a summary of installation information. All required and optional properties are set. If you want to continue with the installation, click Next and the install process will start. If you want to change any property click Back.

Figure 11. Installation Process

Installation Process

Figure 11 shows the installation output and progress. Installation consists of copying files, configuring the server, and installing the database. When the installation has completed successfully, the Next button is enabled. If there is a problem, an error message and Recovery button will appear on the screen.

For more information on recovery, see Troubleshooting

Figure 12. Finish Panel

Finish Panel

On this panel, click Finish to conclude the installation.

Clustering Oracle Service Registry  Locate

This section provides general instructions on clustering Oracle Service Registry (OSR) 11.1.1 instances in all supported application server environments.

Clustering Oracle Service Registry with Oracle WebLogic Server  Locate

In an Oracle WebLogic Server context, an Oracle Service Registry cluster is defined as a cluster of Oracle WebLogic Server instances, each hosting a Standalone Registry instance, with all instances connecting to the same database schema.

In this context, a cluster of Oracle WebLogic Server instances is defined as two or more instances configured in a cluster topology as described in the relevant Oracle WebLogic Server documentation:

  • Using WebLogic Server Clusters Guide.

To install OSR into an Oracle WebLogic Server cluster, you must install a Registry instance into an WLS instance within each Oracle WebLogic Server node. This process is identical to installing OSR in a non-clustered configuration with the following exceptions.

Create the Registry tablespace and schema when you install the first Registry instance.

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 Cluster Configuration .

Installation Summary  Locate

Directory Structure  Locate

The installation directory structure contains the following directories:

bin

Contains command-line scripts for running Oracle Service Registry. See 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 Logs.

work

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

Registry Endpoints  Locate

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 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 port>/<application name>/uddi/bsc/web

  • Registry Control home page: http://<host name>:<http port>/<application name>/uddi/web

  • UDDI Inquiry API endpoint - http://<host name>:<port>/<application name>/uddi/inquiry

    See Developer's Guide, UDDI Version 1, UDDI Version 2, UDDI Version 3.

  • UDDI Publishing API endpoint - http://<host name>:<port>/<application name>/uddi/publishing

    See Developer's Guide, UDDI Version 1, UDDI Version 2, UDDI Version 3.

  • UDDI Security Policy v3 API endpoint - http://<host name>:<port>/<application name>/uddi/security

    See Developer's Guide, UDDI Version 3.

  • UDDI Custody API endpoint - http://<host name>:<port>/<application name>/uddi/custody

    See Developer's Guide, UDDI Version 3.

  • UDDI Subscription API endpoint - http://<host name>:<port>/<application name>/uddi/subscription

    See Developer's Guide, UDDI Version 3.

  • Taxonomy API endpoint - http://<host name>:<port>/<application name>/uddi/taxonomy

    See Developer's Guide, Taxonomy.

  • Category API endpoint - http://<host name>:<port>/<application name>/uddi/category

    See Developer's Guide, Category.

  • Administration Utilities API endpoint - http://<host name>:<port>/<application name>/uddi/administrationUtils

    See Developer's Guide, Administration Utilities.

  • Replication API endpoint - http://<host name>:<port>/<application name>/uddi/replication

    See Developer's Guide, Replication.

  • Statistics API endpoint - http://<host name>:<port>/<application name>/uddi/statistics

    See Developer's Guide, Statistics.

  • WSDL2UDDI API endpoint - http://<host name>:<port>/<application name>/uddi/wsdl2uddi

    See Developer's Guide, WSDL Publishing.

  • XML2UDDI API endpoint - http://<host name>:<port>/<application name>/uddi/xml2uddi

    See Developer's Guide, XML Publishing.

  • XSD2UDDI API endpoint - http://<host name>:<port>/<application name>/uddi/xsd2uddi

    See Developer's Guide, XSD Publishing.

  • XSLT2UDDI API endpoint - http://<host name>:<port>/<application name>/uddi/xslt2uddi

    See Developer's Guide, XSLT Publishing.

  • Extended Inquiry API endpoint - http://<host name>:<port>/<application name>/uddi/inquiryExt

  • Extended Publishing API endpoint - http://<host name>:<port>/<application name>/uddi/publishingExt

  • Configurator API endpoint - http://<host name>:<port>/<application name>/uddi/configurator

  • Account API endpoint - http://<host name>:<port>/<application name>/uddi/account

    See Developer's Guide, Account.

  • Group API endpoint - http://<host name>:<port>/<application name>/uddi/group

    See Developer's Guide, Group.

  • Permission API endpoint - http://<host name>:<port>/<application name>/uddi/permission

    See Developer's Guide, Permission.

Pre-installed Data  Locate

Oracle Service Registry contains the following data:

  • Operational business - This entity holds miscellaneous nodes' registry settings such as the validation service configuration.

  • Built in tModels - tModels required by the UDDI specification.

  • Demo data - Data required by the Oracle Service Registry demos. For more information, please see Demos.

Command-line Scripts  Locate

The bin subdirectory contains scripts, including those for changing configuration.

Setup  Locate

Windows: setup.bat
UNIX: ./setup.sh

Setup may be launched with the following optional arguments:

setup.sh (.bat) [[--help] | [-h] | [--gui] | [-g] | [-u file ] | [--use-config file ]] [[-s file ] | [--save-config file ]] [--debug]

-h | --help shows help message

-g | --gui starts the setup wizard. The wizard is the default mode.

-u | --use-config file starts setup in non-interactive mode; it reads all properties from the specified file.

-s | --save-config file starts the setup wizard. All configuration will be saved into specified file instead of execute configuration. The file may be used later in a non-interactive installation. The configuration file contains all passwords entered in the setup. The passwords are normally encoded. If you want clear-text passwords, specify also option -t | --save-clear-text

--debug the setup produces more information to localize problems or errors.

To change the Oracle Service Registry configuration after installation follow Reconfiguring After Installation.

Signer  Locate

Windows: signer.bat
UNIX: ./signer.sh

The Signer is a graphical application that can be used to add, remove, and verify the signatures of UDDI structures you have published. Follow Signer Tool.

SoapSpy  Locate

Windows: SoapSpy.bat
UNIX: ./SoapSpy.sh

Debugging tool to control low level soap communication. Follow How to Debug.

PStoreTool  Locate

Windows: PStoreTool.bat
UNIX: ./PStoreTool.sh

Protected security storage manipulation tool. See PStore Tool.

Windows: env.bat
UNIX: ./env.sh

Helper script to set system variables. We recommend not to use it directly.

Reconfiguring After Installation  Locate

Many settings may be changed after installation using the Setup tool.

The Setup tool also facilitates other functions such as deployment to application server and data migration from previous installation (described in Migration).

The Setup tool contains similar panels to those in the installation tool. To run this tool, execute the following script from the bin subdirectory of your installation:

Windows: setup.bat
UNIX: ./setup.sh

See command-line parameters in Setup.

By default setup starts in wizard mode (GUI) as shown here:

The first screen prompts for a directory which is used to find configuration files. This directory should contain most current configuration files. Setup asks for different directories to find configurations depending on deployment type:

  • Oracle WebLogic - The Setup Tool will ask for directory where Registry is unpacked inside WebLogic. The exact location differs, but it usually follows this pattern: WL_DIR/user_projects/domains/ DOMAIN_NAME /servers/AdminServer/tmp/_WL_user/registry/ RANDOM_NAME /public

  • Embedded HTTP/HTTPS Server - The Setup Tool will ask for Registry installation directory (which is also called REGISTRY_HOME).

[Caution]Caution

If you do not set up the Deployment location properly, most of Setup Tool functions do not work properly. The Setup Tool checks whether the location is filled correctly and warns you before proceeding to further panels if necessary.

The following main screen allows you to choose which setup task you want to perform:

The following topics may be configured:

Configuration

Change server and registry configuration. Follow Server Configuration.

Registry Server URLs

Change Registry server URLs in database. Follow Change Server URLs.

Database

Create, drop, or connect to a database. Follow Database Installation.

Migration

Migrate registry data from other registry. Follow Migration.

Backup and Restore

Backup and restore Oracle Service Registry. Follow Backup

Authentication account provider

Change account backend configuration. Follow External Accounts Integration.

[Caution]Caution

Before you run any of the tasks, except undeploy, you have to shut down the running Oracle Service Registry. After the task completes, you may run the Oracle Service Registry again.

Server Properties  Locate

System properties are the main means of configuring Oracle Service Registry as deployed into Oracle WebLogic Server. Default property values can be overridden in the init-param elements in the web application deployment descriptor, web.xml.

The following properties are checked when Oracle Service Registry is initialized:

PropertyDescription
wasp.location

This property is mandatory for running a Oracle Service Registry server. It must point to the directory in which Oracle Service Registry is installed.

wasp.config.location

This is an absolute or wasp.location-relative path pointing to the registry configuration file. Setting this property is optional; the default value is conf/clientconf.xml.

wasp.config.include

Comma-separated list of additional config paths to include. These paths can be either absolute or relative to the working directory. This property is optional.

wasp.impl.classpath

Sets a classpath for the registry implementation. This property is optional; if it is not set, registry interfaces and implementation are loaded in the same classloader.

wasp.shutdownhook

Set to true if Oracle Service Registry should be automatically destroyed just before JVM is destroyed. Set to false if you want to manage the shutdown process yourself. The default setting is true.

idoox.debug.level

Determines the number of debugging messages produced by Oracle Service Registry:

  • 0: none

  • 1: errors

  • 2: warnings

  • 3: infos

  • 4: debugs

This property is optional; the default value is 2 for the client and 3 for the server. The debug level is available in the non-stripped distribution only.

The logging level specified by the idoox.debug.level property overrides the level specified in the configuration file determined by the log4j.configuration property

idoox.debug.logger

Specifies which logging system is used, waspLogger or log4j. Default is log4j. Setting the value of this property to waspLogger uses this logger, instead.

log4j.configuration

Specifies the location of the configuration (properties file) for log4j. This property can contain a relative (conf/log4j.config) or absolute (/home/waspuser/log4j.config) path to the configuration file.

If it is not set, the default configuration (ConsoleAppender with the pattern %p: %c{2} - %m\n) will be used.

An example configuration file for log4j, log4j.config, is located in the conf subdirectory of the Oracle Service Registry installation directory.

Logs  Locate

Log files are created by the Install and Setup tools, and by the running Oracle Service Registry instance. The tool log files can be found in INSTALL_DIR/log directory.

These two log files are produced by the Installation and Setup processes and placed into the INSTALL_DIR/log directory:

install.log

This log contains installation output information including all properties set during installation, and output from the installation process. If an error occurs during installation, see this log for details.

setup.log

The log of the Setup tool. Any execution of the Setup tool writes the set properties and output from setup processes here. Errors occurring during setup are written to this log.

The server logs are placed to the deployed application root directory on the Oracle WebLogic Server. The default server logs are:

logEvents.log

The standard server output contains informative events which occur on the Oracle Service Registry server.

errorEvents.log

This file contains detailed logs of error events which occur on the Oracle Service Registry server.

replicationEvents.log

Replication process logs can be found in the REGISTRY_HOME/log/replicationEvents.log file.

configuratorEvents.log

Cluster configuration events are logged in the REGISTRY_HOME/log/configuratorEvents.log file

The server logs may be configured by one of two logging systems, the in-house waspLogger and log4j. By default, log4j is used. The default log4j configuration file is located in REGISTRY_HOME/conf/log4j.config.

[Note]Note

An explanation of using log4j is outside the scope of this documentation; please see the Apache log4j documentation for more information.

Using the syslog Daemon with Oracle Service Registry  Locate

The log4j system used in Oracle Service Registry can be configured to send log messages to the syslog daemon. In order to utilize this feature, your system must be configured as follows:

  1. Edit log4j in REGISTRY_HOME/conf/log4j.config to add a syslog appender, as shown below:

    # Appender to syslog
    log4j.appender.syslog=org.apache.log4j.net.syslogAppender
    log4j.appender.syslog.syslogHost=localhost         
    log4j.appender.syslog.Facility=local6         
    log4j.appender.syslog.layout=org.apache.log4j.PatternLayout         
    log4j.appender.syslog.layout.ConversionPattern=%p: %c{2} - %m%n
                    

    Note the following properties in particular:

    • syslogHost - Set to host name of the computer where syslog is running.

    • Facility - Oracle Service Registry log message facility recognized by syslog

  2. Edit log4j in REGISTRY_HOME/conf/log4j.config to add syslog to the value of the property log4j.category.com.systinet.wasp.events, as shown below:

    # Appender to syslog
    log4j.category.com.systinet.wasp.events=INFO,eventLog,syslog
                    
  3. Set the syslogd configuration to recognize log messages from Oracle Service Registry. Implicitly, Oracle Service Registry sends log messages to syslog under the facility local6. Therefore, modify the /etc/syslog.conf file by adding the following line of text:

    local6.* /var/log/registry.log
                    
    [Note]Note

    The local6 facility is not mandatory in any way. You may use other localX facilities instead.

    Oracle Service Registry will now log messages of all priorities into the file /var/log/registry.log. You should create this file now with appropriate permissions (otherwise syslogd will create it for you automatically with default permissions, which may not be suitable for you).

  4. Your syslog daemon must be started with remote logging enabled (the -r command line option). To make sure that:

    • syslogd is running, use the pgrep syslogd command.

    • remote logging is enabled, use the netstat -l command (syslog's udp port is 514).

Running Oracle Service Registry as a UNIX Daemon  Locate

On UNIX platforms, Oracle Service Registry can be forced to start as a system daemon using the script REGISTRY_HOME/etc/bin/registry.sh. This script can be renamed registry as per UNIX conventions. The directions for using this script follow.

  1. Tailor the service script as needed. The meaning of variables is shown in the following table:

    Variable NameDescriptionDefault Value

    REGISTRY_HOME

    Home directory of Oracle Service Registry

    Oracle Service Registry Installation directory

    JAVA_HOME

    Home directory of Java

    None. This variable must be set manually.

    REGISTRY_USER

    User under whom the Oracle Service Registry server should run. If this is set to root, it will be changed to “nobody”.

    None. This variable must be set manually.

    TIMEOUT

    Number of seconds the system waits for Oracle Service Registry to successfully start up.

    60 seconds

  2. Rename the script registry (without the .sh extension) and save it in the /etc/init.d/ directory.

  3. Optionally, to start Oracle Service Registry automatically in the appropriate run-level, create SXXregistry and KXXregistry symbolic links in the appropriate /etc/rcX.d/ directory.

  4. Start and stop Oracle Service Registry using the installed script. You can invoke this script directly or by using specific OS tools. For example, on RedHat, by using the redhat-config-services command. The parameters of the script are shown in the following table:

    Variable NameDescription 

    start

    Starts Oracle Service Registry

     

    stop

    Stops Oracle Service Registry

     

    restart

    Restarts Oracle Service Registry

     

    condrestart

    Restarts Oracle Service Registry only if it is already running

     

    status

    Displays whether Oracle Service Registry is running or not

     

Troubleshooting  Locate

If errors occur during the installation process, the installer displays a message and a Recovery button.

Execution of Task fails. You can click Recovery and correct erroneous selections or click Exit to exit the installation.

If you click Recovery, the installation returns to the step that should be corrected. For example, if the installation fails during copying files, it will return to the installation type panel. If the process fails during configuring database it will return to the database panels.

If errors occur when using the Setup tool, only the error message is displayed, you can continue by clicking Next.

The following general problems may occur:

Installation backend timeout

If the task does not respond for a long time, a timeout error is thrown and the task is stopped. The default timeout is 30 minutes. If you have a slow machine, try to redefine the timeout system property for a greater value in minutes at a java command line.

For 60 minutes, run installation by following command: java -Dtimeout=60 -jar oracle-service-registry-11.1.1.jar

For 60 minutes, edit the setup.sh (setup.bat) file; add the -Dtimeout=60 option into the java command line so it looks like:

Windows: "%JAVA_CMD%" -Dtimeout=60
UNIX: "$JAVA_CMD" -Dtimeout=60

Cannot find JDBC driver, java.lang.ClassNotFoundException

Some external classes cannot be found. Usually the path to JDBC driver does not contain the needed *.jar or *.zip files. Another reason this error may be thrown is that the JDBC driver is not supported by Oracle Service Registry. See Database Installation for more information about supported databases.

Cannot access database, java.sql.SQLException

This usually happens during the creation of database which already exists. To resolve this error, try to connect or drop this database first.

This error is also thrown when trying to drop a database which is currently in use, or does not exist. Note that some set properties must exist on the database engine and some of them are optional. Please see Database Installation for more information about supported databases.

Couldn't create or access important files. Wrong path

This error is displayed when the installation directory specified is bad or the user does not have read and write permissions for it. Try to install to another directory or reset the read and write permissions.

Consult support if problems persist or any other problems occur.