Installation Guide

Installation Summary

This section contains information about your installation. It includes the following topics:

Directory Structure

The installation directory structure contains the following directories:

app

Contains BEA AquaLogic Service Registry deployed as Web services in Systinet Server for Java.

bin

Contains command-line scripts for running BEA AquaLogic Service Registry. See Command Line Scripts.

conf

Contains the BEA AquaLogic Service Registry configuration files

demos

Contains demos of BEA AquaLogic Service Registry functionality. For more information, see "Demos" in Using the AquaLogic Service Registry.

dist

Contains BEA AquaLogic Service Registry client packages.

doc

Contains the BEA AquaLogic Service Registry documentation.

etc

Contains additional data and scripts.

hsqldb

Contains the pre configured HSQL database with registry data.

lib

Contains the BEA AquaLogic Service Registry libraries

log

Contains logs of installation, setup, and server output. See Logs.

work

This directory is available after the first launch of the server; it is a working image of the app directory.

Registry Endpoints

BEA AquaLogic Service Registry is configured as follows. The <host name>, <http port> and <ssl port> are specified during installation. For more information, see Server Settings. For each endpoint you can use either http or ssl port.

Note:

The following endpoint information references topics in the Developer's Guide, which is available as part of the Using the AquaLogic Service Registry document at the following URL:

Note:

http://download.oracle.com/docs/cd/E13173_01/alsr/docs21/registry/index.html

Business Service Console home page: http://<host name>:<http port>/uddi/bsc/web
Registry Console home page: http://<host name>:<http port>/uddi/web
UDDI Inquiry API endpoint - http://<host name>:<port>/uddi/inquiry

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

UDDI Publishing API endpoint - http://<host name>:<port>/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>/uddi/security

See Developer's Guide, UDDI Version 3.

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

See Developer's Guide, UDDI Version 3.

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

See Developer's Guide, UDDI Version 3.

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

See Developer's Guide, Taxonomy.

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

See Developer's Guide, Category.

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

See Developer's Guide, Administration Utilities.

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

See Developer's Guide, Replication.

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

See Developer's Guide, Statistics.

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

See Developer's Guide, WSDL Publishing.

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

See Developer's Guide, XML Publishing.

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

See Developer's Guide, XSD Publishing.

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

See Developer's Guide, XSLT Publishing.

Extended Inquiry API endpoint - http://<host name>:<port>/uddi/inquiryExt
Extended Publishing API endpoint - http://<host name>:<port>/uddi/publishingExt
Configurator API endpoint - http://<host name>:<port>/uddi/configurator
Account API endpoint - http://<host name>:<port>/uddi/account

See Developer's Guide, Account.

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

See Developer's Guide, Group.

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

See Developer's Guide, Permission.

Pre-installed Data

BEA AquaLogic 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 BEA AquaLogic Service Registry demos. For more information, see Demos in Using the AquaLogic Service Registry.

Command Line Scripts

The bin subdirectory contains scripts, including those for launching the server, installing Windows services, and changing configuration.

Setup

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. --debug the setup produces more information to localize problems or errors. To change the BEA AquaLogic Service Registry configuration after installation follow Reconfiguration After Installation.

Signer

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 in the User's Guide in Using the AquaLogic Service Registry.

SoapSpy

Windows: SoapSpy.bat

UNIX: ./SoapSpy.sh Debugging tool to control low level soap communication. Follow How to Debug in the Developer's Guide in Using the AquaLogic Service Registry.

PStoreTool

Windows: PStoreTool.bat

UNIX: ./PStoreTool.sh Protected security storage manipulation tool. See PStore Tool in the Administrator's Guide in Using the AquaLogic Service Registry.

env

Windows: env.bat

UNIX: ./env.sh Helper script to set system variables. We recommend not to use it directly.

Reconfiguration After Installation

The Setup tool also facilitates other functions such as the 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 for Setup in Command Line Scripts.

By default, setup starts in wizard mode as shown in the following figure.

Figure 7-1 Wizard Mode Setup

The following topics may be configured:

Configuration

Change server and registry configuration.

Database

Create, drop, or connect to a database.

Portation

Port registry to an application server.

Migration

Migrate registry data from other registry.

Backup and Restore

Backup and restore BEA AquaLogic Service Registry.

Authentication account provider

Change account back-end configuration.

Server Properties

System properties are the main means of configuring AquaLogic Service Registry as deployed into Systinet Server for Java. Default values for these properties are in the resource META-INF/wasp.properties, which is located in lib/runner.jar.

To alter system properties for AquaLogic Service Registry deployed into WebLogic Server as a Servlet: 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 BEA AquaLogic Service Registry is initialized.

Table 7-1 Properties Checked When BEA AquaLogic Service Registry is Initialized
Property	Description
wasp.location	This property is mandatory for running a BEA AquaLogic Service Registry server. It must point to the directory in which BEA AquaLogic 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 BEA AquaLogic 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 BEA AquaLogic 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 BEA AquaLogic Service Registry installation directory.

Logs

There are four log files in REGISTRY_HOME/log directory.

The following log files are produced by the Installation and Setup processes:

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 default server logs are:

logEvents.log—The standard server output contains informative events which occur on the BEA AquaLogic Service Registry server.
errorEvents.log—This file contains detailed logs of error events which occur on the BEA AquaLogic 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
wasp_NTService.log—Events of the server are written into the REGISTRY_HOME\log\wasp_NTService.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: An explanation of using log4j is outside the scope of this documentation; please see the Apache log4j documentation for more information:

Note: http://logging.apache.org/log4j/docs/index.html

Troubleshooting Your Installation

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 BEA-aqualogic-service-registry-2.1.0.jar

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

Note: Windows: "%JAVA_CMD%" -Dtimeout=60

Note:

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 BEA AquaLogic Service Registry. For more information about supported databases, see Database Installation in Using the AquaLogic Service Registry.

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. For more information about supported databases, see Database Installation in Using the AquaLogic Service Registry.

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.