Preface

Welcome to Oracle RepositoryDesigner. This guide provides information necessary to help you get started with Oracle RepositoryDesigner. Specifically, this document provides the following information:

Audience

This guide is for all users who wish to perform a new installation of Oracle RepositoryDesigner, to upgrade an existing release 6i repository, or to migrate an existing pre-6i repository.

Prerequisites

Installation of Oracle RepositoryDesigner consists of two parts: a client-side part and a server-side part. You perform the client-side part at each workstation that is connected to the server. You perform the server-side part once only, either at the machine where the repository resides or remotely from a correctly-configured client workstation.

You should have a basic understanding of client/server networks and how they operate, and be familiar with the elements of an application window.

For the client-side part, you should be familiar with the workstation and its user interface. For example, you should know how to locate, delete and copy files and understand the concepts of the search path, subdirectories, and path names. Refer to your operating system documentation for more information.

You should know how to run programs from the desktop and how to use Windows Explorer.

You should already have the Windows software installed and operational.

For the server-side part, you will need to be familiar with SQL and the principles of Oracle database management. The Oracle8i or Oracle9i database software must already be installed on the database server. You will also need to know the appropriate commands for file management under the server operating system (for example, UNIX or Windows NT).

For full details of hardware and software requirements, see the section "System Requirements " in Chapter 1.

Organization

This manual consists of the following chapters and appendices:

Section	Description
Chapter 1	Describes how to install the Oracle RepositoryDesigner tools software on a client workstation.
Chapter 2	Contains detailed information about installing a new repository, or migrating or upgrading an existing one.
Chapter 3	Contains instructions for users who want to install Oracle RepositoryDesigner on a local area network (LAN).
Appendix A	Describes how to customize your Oracle configuration by changing the parameter values defined in the Windows Registry.
Appendix B	Lists the log files produced by a successful installation, migration or upgrade.
Appendix C	Provides information on some common error messages relating to an Oracle RepositoryDesigner installation or upgrade.

Conventions

The following conventions are used in this manual:

Convention Meaning

fixed-width font Text in a fixed-width font indicates commands that you must enter exactly as shown. Such text is not case-sensitive unless noted otherwise.

italics Characters in italics in a command statement represent a variable. Substitute an appropriate value.

UPPERCASE Uppercase characters within the text represent command names, file and directory names, SQL reserved words, and keywords.

Punctuation In commands, punctuation other than brackets and vertical bars must be entered exactly as shown.

\DIRECTORY A backslash before a directory name indicates that this directory is a subdirectory.

Convention	Meaning
fixed-width font	Text in a fixed-width font indicates commands that you must enter exactly as shown. Such text is not case-sensitive unless noted otherwise.
italics	Characters in italics in a command statement represent a variable. Substitute an appropriate value.
UPPERCASE	Uppercase characters within the text represent command names, file and directory names, SQL reserved words, and keywords.
Punctuation	In commands, punctuation other than brackets and vertical bars must be entered exactly as shown.
\DIRECTORY	A backslash before a directory name indicates that this directory is a subdirectory.

Terms Used

Throughout this guide the following terms are used:

Term Meaning

Application Programming Interface (API) packages PL/SQL packages which manage the storage of all repository data. These ensure that validation is performed in an entirely consistent way by all tools that store data in the repository.

client workstation A machine connected to a local or remote database (see below). This is the machine on which you install the Oracle RepositoryDesigner client software.

database administrator
(DBA) The person responsible for performing tasks such as installing the database, enrolling users, and creating database objects. The DBA and the network administrator might be the same person.

database server The computer where the database resides. A remote database (see below) may be located on a computer such as a minicomputer or mainframe, or on a dedicated PC, or your database may reside on a file server if your system supports that configuration. This is the machine on which you install the repository software.

definition tables A subset of repository tables; they contain the lookup or driving data used by the API packages, the generators and the User Extensibility facilities. These are created during the installation or upgrade process, in the same Oracle schema as the other objects in a repository instance.

file server A network PC or other computer where shared program and data files reside.

instance tables A subset of the repository tables; used to record the data entered by repository users.

local database A database located on a machine that is also used as a client workstation.

network administrator The person responsible for maintaining the network operating system.

remote database A database located on a network computer other than the client workstation. A remote database is usually on the same network as the client workstation, but it may be located on a different server from a machine acting as the file server.

repository instance All the database objects (e.g., tables, views, packages) required by the Oracle RepositoryDesigner software.

repository owner A repository user who owns the repository objects and who performs administrative tasks associated with the repository. Only the repository owner has access to all the functions of the Repository Administration Utility. The repository owner cannot be either of the Oracle users SYSTEM or SYS.

repository user An Oracle database user who has been granted access to the repository.

subordinate user Any repository user other than the repository owner. There can be many subordinate users of the repository, but only one repository owner. In particular, subordinate users do not have access to all the functions of the Repository Administration Utility.

Term	Meaning
Application Programming Interface (API) packages	PL/SQL packages which manage the storage of all repository data. These ensure that validation is performed in an entirely consistent way by all tools that store data in the repository.
client workstation	A machine connected to a local or remote database (see below). This is the machine on which you install the Oracle RepositoryDesigner client software.
database administrator (DBA)	The person responsible for performing tasks such as installing the database, enrolling users, and creating database objects. The DBA and the network administrator might be the same person.
database server	The computer where the database resides. A remote database (see below) may be located on a computer such as a minicomputer or mainframe, or on a dedicated PC, or your database may reside on a file server if your system supports that configuration. This is the machine on which you install the repository software.
definition tables	A subset of repository tables; they contain the lookup or driving data used by the API packages, the generators and the User Extensibility facilities. These are created during the installation or upgrade process, in the same Oracle schema as the other objects in a repository instance.
file server	A network PC or other computer where shared program and data files reside.
instance tables	A subset of the repository tables; used to record the data entered by repository users.
local database	A database located on a machine that is also used as a client workstation.
network administrator	The person responsible for maintaining the network operating system.
remote database	A database located on a network computer other than the client workstation. A remote database is usually on the same network as the client workstation, but it may be located on a different server from a machine acting as the file server.
repository instance	All the database objects (e.g., tables, views, packages) required by the Oracle RepositoryDesigner software.
repository owner	A repository user who owns the repository objects and who performs administrative tasks associated with the repository. Only the repository owner has access to all the functions of the Repository Administration Utility. The repository owner cannot be either of the Oracle users SYSTEM or SYS.
repository user	An Oracle database user who has been granted access to the repository.
subordinate user	Any repository user other than the repository owner. There can be many subordinate users of the repository, but only one repository owner. In particular, subordinate users do not have access to all the functions of the Repository Administration Utility.

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle Corporation is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program web site at http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation

JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.

Contents