1 Product and Installation Overview

1.3.2.1 OracleAS Portal with a New Metadata Repository

If you use a new metadata repository, then the Oracle Application Server Standard Edition One infrastructure (Identity Management and Metadata Repository) is installed as shown in Figure 1-2.

1.3.2.2 OracleAS Portal with an Existing Metadata Repository

If you use an existing metadata repository, then the Oracle Application Server Standard Edition One infrastructure (Identity Management only) is installed, as illustrated in Figure 1-3.

For this configuration, you must use Oracle Application Server Metadata Repository Creation Assistant (OracleAS Metadata Repository Creation Assistant) to create the Metadata Repository in an existing database before you install OracleAS Portal and Identity Management. OracleAS Metadata Repository Creation Assistant is available on a separate CD.

1.4.2.1 Naming Your Oracle Home

Each Oracle home directory is automatically given a name.

If you are installing only J2EE and Web Services, then your Oracle home is named oracleas1.

If you are installing either of the two available OracleAS Portal services, then:

• The user-specified-dir/infra directory is named oracleas1

• The user-specified-dir/portal directory is named oracleas2

The Oracle home name can consist of alphanumeric and the underscore (_) characters, and cannot be longer than 128 characters.

Because middle tiers (for example, OracleAS Portal) depend on OracleAS Infrastructure (for example, OracleAS Metadata Repository) services, the OracleAS Infrastructure services must be started before the middle tier services are started.

1.4.2.2 Installing in a Non-Empty Oracle Home

You cannot install Oracle Application Server Standard Edition One in a directory that already contains some files. For example, if you cancel an installation or if an installation fails, then you have to clean up the directory before you can reinstall Oracle Application Server Standard Edition One in it. In addition, the installer cannot repair an installation. Refer to Section G.3.4, "Message About Installing in a Non-Empty Directory" for instructions on how to clean up a non-empty directory.

1.4.6.1 Installing Additional Languages After Installing Oracle Application Server Standard Edition One

If you need to support more languages after the installation, then you must run the Portal Language Assistant tool to load the translations for those languages, and also copy necessary font files to your middle tier directory from the OracleAS Metadata Repository Upgrade Assistant and Utilities CD-ROM.

1.4.6.2 Portal User Interface Message Installation

You can find Portal translated resource files in the following directory:

$ORACLE_HOME/portal/admin/plsql/nlsres/ctl

These files must be loaded into a repository database to support the additional languages.

To load the translation, you can use the following command:

ptllang -lang lang_code [-i install_type]
                        [-s portal_schema]
                        [-sp portal_schema_password]
                        [-c portal_db_connect_string]

Table 1-3 describes the optional configuration parameters for this command.

Following is an example of the ptllang command:

ptllang -lang ja -i custom -s portal -sp welcome1 -c host:1521:orasid

1.4.6.3 Oracle Unicode Font Installation Requirements

Only fonts required by Application Server Control Console and Help (for example, Albany fonts ALBANWTJ.TTF and ALBANWTK.TTF) for the languages you select during the installation will be installed. This means that some text might be displayed as control characters for the languages you did not choose during the installation.

The additional required fonts are stored in the /utilities/fonts folder on the Oracle Application Server Metadata Repository Upgrade Assistant and Utility CD-ROM.

Following is the font list for the languages you might need to support:

• ALBANWTJ - Non English, plus Japanese

• ALBANWTK - Korean

• ALBANWTS - Simplified Chinese

• ALBANWTT - Traditional Chinese

To install these fonts, perform the following steps after the middle tier is installed:

1. Navigate to the /utilities/fonts folder on the Oracle Application Server Metadata Repository Upgrade Assistant and Utility CD-ROM.

2. Copy the contents of the /utilities/fonts directory to the following folder on the middle tier:

   $ORACLE_HOME/jdk/jre/lib/fonts
   
   

1.4.7.1 Checking If a Port Is Being Used

To check if a port is being used, you can run the netstat command as follows:

/> netstat -an | grep portnum

1.4.7.2 Getting a List of Port Numbers

You can get a list of port numbers in the following ways:

• Use Oracle Enterprise Manager Application Server Control.

  Click the Ports link on the Oracle Enterprise Manager Application Server Control home page. This takes you to a page that lists all ports in use and the suggested port ranges for different components.

• Look in the $ORACLE_HOME/install/portlist.ini file. ORACLE_HOME refers to the directory containing the Oracle Application Server installation.

  If you change the port number of a component after installation, then the portlist.ini file is not updated because the portlist.ini file is not updated after installation.

1.4.7.3 Using Default Port Numbers

If you want to use the default port numbers for such components, then you do not have to do anything. Refer to Appendix C, "Default Port Numbers" for a list of the default port numbers and ranges. Ensure that at least one port is available in the port range for each component. If the installer is unable to find a free port in that range, then the installation will fail.

1.4.7.4 Using Custom Port Numbers (the "Static Ports" Feature)

To instruct the installer to assign custom port numbers for components:

1. Create a file containing the component names and port numbers. This file is typically called the staticports.ini file, but you can name it anything you want.

2. In the installer, on the Specify Port Configuration Options screen, select Manual and enter the full path to the staticports.ini file.

   If you do not specify the full path to the file, then the installer will not be able to find the file. The installer will then assign default ports for all the components, and it will do this without displaying any warning.

Format of the staticports.ini File

The staticports.ini file has the following format. Replace port_num with the port number that you want to use for the component.

# staticports.ini Template File
 
# This file is a template for specifying port numbers at installation time.
# To specify a port number, uncomment the appropriate line (remove #) and
# replace "port_num" with the desired port number.
# 
# Please refer to Oracle Application Server  10g Standard Edition one 
# Installation Guide for instructions on how to use this file.
# This file cannot be specified on the command line when launching OUI
 
[Infrastructure]
#Oracle Internet Directory port = port_num
#Oracle Internet Directory (SSL) port = port_num
#Oracle Certificate Authority SSL Server Authentication port = port_num
#Oracle Certificate Authority SSL Mutual Authentication port = port_num
#Ultra Search HTTP port number = port_num
#Oracle HTTP Server port = 80
#Oracle HTTP Server Listen port = port_num
#Oracle HTTP Server SSL port = port_num
#Oracle HTTP Server Listen (SSL) port = port_num
#Oracle HTTP Server Diagnostic port = port_num
#Java Object Cache port = port_num
#DCM Java Object Cache port = port_num
#DCM Discovery port = port_num
#Oracle Notification Server Request port = port_num
#Oracle Notification Server Local port = port_num
#Oracle Notification Server Remote port = port_num
#Application Server Control port = port_num
#Application Server Control RMI port = port_num
#Oracle Management Agent port = port_num
#Log Loader port = port_num
 
 
[Portal]
#Ultra Search HTTP port number = port_num
#Oracle HTTP Server port = port_num
#Oracle HTTP Server Listen port = port_num
#Oracle HTTP Server SSL port = port_num
#Oracle HTTP Server Listen (SSL) port = port_num
#Oracle HTTP Server Diagnostic port = port_num
#Java Object Cache port = port_num
#DCM Java Object Cache port = port_num
#DCM Discovery port = port_num
#Oracle Notification Server Request port = port_num
#Oracle Notification Server Local port = port_num
#Oracle Notification Server Remote port = port_num
#Application Server Control port = port_num
#Application Server Control RMI port = port_num
#Oracle Management Agent port = port_num
#Web Cache HTTP Listen port = port_num
#Web Cache HTTP Listen (SSL) port = port_num
#Web Cache Administration port = port_num
#Web Cache Invalidation port = port_num
#Web Cache Statistics port = port_num
#Log Loader port = port_num
#Discoverer OSAgent port = port_num
 
 
[j2ee]
#Ultra Search HTTP port number = port_num
#Oracle HTTP Server port = port_num
#Oracle HTTP Server Listen port = port_num
#Oracle HTTP Server SSL port = port_num
#Oracle HTTP Server Listen (SSL) port = port_num
#Oracle HTTP Server Diagnostic port = port_num
#Java Object Cache port = port_num
#DCM Java Object Cache port = port_num
#DCM Discovery port = port_num
#Oracle Notification Server Request port = port_num
#Oracle Notification Server Local port = port_num
#Oracle Notification Server Remote port = port_num
#Application Server Control port = port_num
#Application Server Control RMI port = port_num
#Oracle Management Agent port = port_num
#Web Cache HTTP Listen port = port_num
#Web Cache HTTP Listen (SSL) port = port_num
#Web Cache Administration port = port_num
#Web Cache Invalidation port = port_num
#Web Cache Statistics port = port_num
#Log Loader port = port_num

The easiest way to create the file is to use the staticports.ini file on the CD-ROM (Disk 1) or DVD as a template:

1. Copy the staticports.ini file from the CD-ROM or DVD to the hard disk. Table 1-4 provides the location of the file on the CD-ROM and DVD.

   Table 1-4 Location of the staticports.ini file on the CD-ROM and DVD

   Media	Location of the staticports.ini File
   CD-ROM	Disk1/stage/Response/staticports.ini
   DVD	CD-ROM

   
   

2. Edit the local copy (the file on the hard disk) to include the desired port numbers.

   You do not need to specify port numbers for all components in the staticports.ini file. If a component is not listed in the file, then the installer uses the default port number for that component.

   You cannot change the port used by the OracleAS Metadata Repository (port 1521) during installation, but you can do so after installation.

   
   

   See Also: Oracle Application Server Administrator's Guide for details.

   
   

   The following example sets the Application Server Control port and some OracleAS Web Cache ports. For components not specified, the installer will assign the default port numbers.

   Application Server Control port = 2000
   Web Cache Administration port = 2001
   Web Cache Invalidation port = 2002
   Web Cache Statistics port = 2003
   
   

   When the installation is complete, you can check the $ORACLE_HOME/install/portlist.ini file to view the assigned ports.

   
   

   Note: Port numbers cannot be greater than 65535.

   
   

   The installer verifies that the ports specified in the file are available by checking the memory. This means that it can only detect ports that are being used by running processes. It does not look in configuration files to determine which ports an application is using.

   If the installer detects that a specified port is not available, then it displays an alert. The installer will not assign a port that is not available. To fix this:

   1. Edit the staticports.ini file to specify a different port, or shut down the application that is using the port.

   2. Click Retry. The installer re-reads the staticports.ini file and verifies the entries in the file again.

Using portlist.ini as the staticports.ini File

The staticports.ini file uses the same format as the $ORACLE_HOME/install/portlist.ini file, which is created after the installation. If you have installed Oracle Application Server Standard Edition One and you want to use the same port numbers in another installation, then you can use the portlist.ini file from the first installation as the staticports.ini file for subsequent installations.

However, note this difference in the staticports.ini: the line Oracle Management Agent port corresponds to Enterprise Manager Agent port in portlist.ini.

Error Conditions That Will Cause the Installer to Use Default Ports Instead of Custom Ports

Check your staticports.ini file carefully because a mistake can cause the installer to use default ports without displaying any warning.

Following are some things that you should check:

• If you specify the same port for more than one component, then the installer will use the specified port for the first component, but for the other components, it will use the default ports of the components. If you have specified the same port for multiple components, then the installer does not warn you.

• If you have syntax errors in the staticports.ini file (for example, if you omitted the = character for a line), then the installer ignores the line. For the components specified on such lines, the installer assigns the default ports. The installer does not display a warning for lines with syntax errors.

• If you misspell a component name, then the installer assigns the default port for the component. Names of components in the file are case sensitive. The installer does not display a warning for lines with unrecognized names.

• If you specify a non-numeric value for the port number, then the installer ignores the line and assigns the default port number for the component. It does this without displaying any warning.

• If you specify a relative path to the staticports.ini file (for example, ./staticports.ini. or just staticports.ini), then the installer will not find the file. The installer continues without displaying a warning and it will assign default ports to all components. You must specify a full path to the staticports.ini file.

1.4.8.1 If an Existing Oracle Database Is Using Port 1521

If you are installing a new database for the OracleAS Metadata Repository on a computer that is already running an Oracle database, then ensure that the listeners for both databases do not conflict.

You might be able to use the same listener for both the existing database and the OracleAS Metadata Repository database. You have to consider the version of the existing listener as well as the port number. Table 1-5 provides various scenarios and outcomes.

You can change the OracleAS Metadata Repository listener to use a different port after installation.

To check the listener version, run the following command:

/> cd $ORACLE_HOME/bin
/> lsnrctl version

where ORACLE_HOME is the home directory for your database.

You can also use the same command to check the listener port.

Here is a sample output of the command:

/> ./lsnrctl VERSION LSNRCTL for Linux: Version 10.1.0.3.0 - Production on 19-MAR-2005 19:46:54
Copyright (c) 1991, 2004, Oracle.  All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(PORT=1521))TNSLSNR for Linux: Version 10.1.0.2.0 - Production
        TNS for Linux: Version 10.1.0.2.0 - Production
        Unix Domain Socket IPC NT Protocol Adaptor for Linux: Version 10.1.0.2.0 -         Production
        Oracle Bequeath NT Protocol Adapter for Linux: Version 10.1.0.2.0 - Production
               TCP/IP NT Protocol Adapter for Linux: Version 10.1.0.2.0 - Production,,
The command completed successfully

Scenario 1: Existing Listener Uses Port 1521 and Listener Version Is Earlier Than 10.1.0.2

Listeners earlier than version 10.1.0.2 are not compatible with the OracleAS Metadata Repository from this Oracle Application Server release (10.1.2). What you need to do is to install the OracleAS Metadata Repository, which installs a version 10.1.0.3 listener. You can then use this new listener to service your existing database and the OracleAS Metadata Repository database.

1. Stop the existing listener before you install the OracleAS Metadata Repository using the following command:

   /> cd $ORACLE_HOME/bin
   /> lsnrctl stop
   
   

   ORACLE_HOME is the home directory for your existing database.

   If you do not stop the existing listener, then the installation will fail.

2. Install the OracleAS Metadata Repository.

   Refer to any of the procedures that install an OracleAS Metadata Repository in Chapter 4, "Installing OracleAS Portal".

3. Update the configuration file of the new listener, as necessary. The name of the listener configuration file is listener.ora, located in the $ORACLE_HOME/network/admin directory.

   1. Check network address entries in the configuration file of the existing listener.

      If the configuration file of the existing listener contains only the following network addresses, then you do not have to edit the OracleAS Metadata Repository configuration file of the listener for the following network addresses:

      • TCP Port 1521

      • IPC key EXTPROC

      If the configuration file contains other network addresses, then you need to add them to OracleAS Metadata Repository configuration file of the listener.

   2. Check SID_DESC entries in the existing listener configuration file.

      If the existing listener configuration file contains SID_DESC entries for the existing database, then you need to add these entries to the OracleAS Metadata Repository listener configuration file.

   3. Do not start the existing listener (version earlier than 10.1.0.2). Now that the new listener supports both databases, you do not need to run the existing listener.

Scenario 2: Existing Listener Uses Port 1521 and Listener Version Is 10.1.0.2 or Later

The existing listener will support both the existing database and the OracleAS Metadata Repository. The installer will perform this configuration automatically.

The listener can be running during installation.

Scenario 3: Existing Listener Uses a Port Other Than 1521

You will end up running two listeners: one for the existing database and one for the OracleAS Metadata Repository, regardless of the version of the existing listener.

The existing listener can be running during installation, because it is not using port 1521.

1.4.8.2 If Some Other Application Is Using Port 1521

If you have some other application listening on port 1521, then you need to reconfigure it to listen on a different port. If that is not possible, then shut it down while you install the OracleAS Metadata Repository. After installation, you can reconfigure OracleAS Metadata Repository to use a port other than 1521.