test

Service Registry 3 2005Q4 Administration Guide

ProcedureTo Configure Service Registry After a Configure Later Installation Using Custom Properties

Before You Begin

To configure the Registry, you must be logged in as root or become superuser.

Steps

  1. Change to the ServiceRegistry-base/install directory.

  2. Edit the modifiable properties in the file install.properties.

    For security reasons, it is recommended that you not edit this file to change the password values. Instead, specify these values on the command line.

  3. After editing the file, run the following command (all on one line):

    On Solaris: /usr/sfw/bin/ant -f build-install.xml install

    On Linux: /opt/sun/bin/ant --noconfig -f build-install.xml install

    The ant command requires the JAVA_HOME environment variable to be set. Ordinarily, you set this variable to the following value:

    /usr/jdk/entsys-j2se

    To specify changed passwords on the command line, specify the following options to the command (all on one line):


    /usr/sfw/bin/ant -f build-install.xml
-Dregistry.install.RegistryServerKeystorePassword=passwd1
-Dregistry.install.AdministratorPassword=passwd2
-Dregistry.install.ApplicationServerKeystorePassword=passwd3 install

    The Registry configuration process creates an Application Server domain at RegistryDomain-base/domains/${registry.install.DomainName}. The default domain name is registry. The configuration process then starts the domain, deploys the Registry, and leaves the domain running.

    The Registry configuration process installs the Registry database and server keystore in the directory RegistryDomain-base/3.0. This directory is not removed when the Registry is uninstalled, so that the database can be preserved for use in a future release. The administrator has control over when and whether to remove this directory.

    The RegistryDomain-base location is /var/opt/SUNWsoar in the Solaris operating environment and /var/opt/sun/SUNWsoar on Linux systems.

  4. Review the output of the ant install command for any errors.

    If there are no errors, you can now begin using the Web Console or the Admin Tool.