Installing 9iDS - Release 2 (9.0.2)

by Jeff Hunter, Sr. Database Administrator

Introduction

This section of the documentation explains the basic steps in installing Oracle9i Development Suite (9iDS). While the installation of 9iDS is straightforward, many of the configuration steps for components like Software Configuration Manager (SCM) (formerly known as Oracle Repository) and Oracle Designer are vague and in many situations, not documented at all.

In general, you should install Oracle9iDS before trying to configure tools like SCM and Oracle Designer.

Oracle9i JDeveloper (including Oracle9i Business Intelligence Beans, and UNIX and Bali subcomponents)

Oracle9i Reports Developer

Oracle9i Discoverer Administrator (formerly Discoverer Administration Edition; including Oracle9i Discoverer Desktop)

Oracle9i Warehouse Builder

Oracle9i Clickstream Intelligence Builder

Oracle9i Forms Developer

Oracle9i Software Configuration Manager (formerly Oracle Repository)

Oracle9i Designer

Oracle9iDS should be installed in its own ORACLE_HOME. Oracle9iDS can ONLY coexist in an ORACLE_HOME with any installation of Oracle9i Application Server Release 2, with the exception of Oracle9iSA Infrastructure.

In general, you should install all Oracle9iDS components using the "Complete" install type option.

Port Numbers

Following installation, the OUI creates a file showing the port assignments during installation of Oracle9iDS components. The installation process automatically detects any port conflicts and chooses an alternative port in the range for allocated for that component.

The file portlist.ini is located in the $ORACLE_HOME/install directory (UNIX). This file lists component entries as "port name = port value". The following table lists the default port numbers that the OUI uses for select components during installation:

Components	Default Port Number	Port Number Range
OC4J for JDeveloper Testing
HTTP Listener	8988	8988 - 8998
RMI	23891	23891 - 23901
JMS	9227	9227 - 9237
OC4J for Forms Developer and Reports Developer testing
HTTP Listener	8888	None

OC4J Instances for Oracle9iDS

To start and stop Oracle9iDS OC4J instances for Forms Developer and Reports Developer testing, use the scripts located in the ORACLE_HOME/j2ee/Oracle9iDS directory:

startinst.sh  or  startinst.bat
stopinst.sh   or  stopinst.bat

On Windows, you can also use the Start Menu to access the scripts, as follows:

Start > Programs > Oracle9i Developer Suite - ORACLE_HOME

Enabling Source Code Control (Windows Only)

A connection to an Oracle9i Software Configuration Manager (SCM) repository is required to perform source code control using SCM from JDeveloper. The repository resides within an Oracle database and must be pre-created before attempting configuration. Install either the Rapid Application Developer option or the Complete option, then use the Repository Administration Utility in SCM to create the repository in the database. A complete of steps for configuring Oracle SCM will be included in this section of the document.

Using OC4J in non-embedded mode with JDeveloper

Included with the J2EE Development installation is a fully functioning version of Oracle9i Application Server Containers for J2EE (OC4J). If you are using JDeveloper to test your applications, you will be using the embedded version of OC4J and you will not have to make any modifications to your configuration. If you would like to use the same configuration for you server, you can use the version include with JDeveloper.

To configure the OC4J server for non-embedded mode:

• At the command line, in ORACLE_HOME/j2ee/home run the command:

  java -jar oc4j.jar -install

  The server will auto-unpack several jars. You will then be prompted to enter an admin password.

• Enter an admin password and press Enter.

  You will be prompted to confirm the password.

  Confirm the password by typing it again and press Enter.

• Installation will be complete. You can now start the server.

To start the OC4J server for use in non-embedded mode:

• At the command line, in ORACLE_HOME/j2ee/home run the command:

  java -jar oc4j.jar

• Several jar files will be auto-deployed and you will see the server output:

  Oracle9iAS (2.0.0.0) Containers for J2EE initialized

  NOTE: The server must be running when you deploy projects to it.

  Using the included server will have no impact on using JDeveloper for testing and running your projects.

This section of the documentation is for use when you have already installed Oracle9iDS at a client workstation and wish to use Oracle9i Designer or Oracle9i Software Configuration Manager (Oracle SCM, formerly known as Oracle Repository). Because these components require a server-side repository at the database host, you need to use procedures in this section to install a brand new repository.

The Oracle8i Server or Oracle9i Database software must already be installed on the database server for where the repository will exist. Also, a functionally database should have already been created to store the repository.

Terms Used

Keep in mind that the following terms may be used throughout this section of the documentation:

Client Workstation: A machine connected to a local or remote database; this is the machine on which you install the OracleiDS client software.

Database Server: The computer where the database resides. This is the machine on which you install the repository software.

Repository Instance: All the database objects (e.g. tables, views, packages) required by the Oracle SCM software.

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 to not have access to all the functions within the Repository Administrator Utility.

Server-Side Installation Introduction

For complete instructions on installing Oracle SCM on the database server, see the chapter entitled "SOFTWARE CONFIGURATION MANAGEMENT - (9i SCM)". Then navigate to the section in this chapter entitled "Installing the Server-Side Repository".