1 Product and Installation Overview

1.3.2.1 OracleAS Portal with a New Metadata Repository

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

Figure 1-2 Configuration for OracleAS Portal with New Metadata Repository

Description of "Figure 1-2 Configuration for OracleAS Portal with New Metadata Repository"

1.3.2.2 OracleAS Portal with an Existing Metadata Repository

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

Figure 1-3 Configuration for OracleAS Portal with Existing Metadata Repository

Description of "Figure 1-3 Configuration for OracleAS Portal with Existing Metadata Repository"

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

For more information about Oracle Application Server Metadata Repository Creation Assistant, see Part III.

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, your Oracle home is named oracleas1.

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

• The <user-specified-dir>\infra directory is named oracleas1.

• The <user-specified-dir>\portal directory is named oracleas2.

Some Oracle Application Server Standard Edition One components run as Windows services. When naming these services, the installer inserts the Oracle home name in the service name using the following format:

Oracle<OracleHomeName><ComponentName>

For example, the process management service (whose component name is ProcessManager) is called Oracleoracleas1ProcessManager (when the ORACLE_HOME_NAME is derived as oracleas1). Note that this name could be different based on the ORACLE_HOME_NAME.

Because middle tiers (for example, OracleAS Portal) depend on OracleAS Infrastructure (for example, OracleAS Metadata Repository) services, the OracleAS Infrastructure services are 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 failed, you have to clean up the directory before you can reinstall Oracle Application Server Standard Edition One in it. Also, the installer cannot "repair" an installation. See Section H.3.2 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, 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 at the following directory:

ORACLE_HOME\portal\admin\plsql\nlsres\ctl

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

In order to load the translation, you can use the following command (for more information, see Oracle Application Server Portal Configuration Guide):

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.

Below 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.

Below 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, do the following 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 machine:

   ORACLE_HOME\jdk\jre\lib\fonts
   

1.4.7.1 About Ephemeral Ports

On rare occasions, Oracle Application Server processes are unable to start up because required ports are not available. Processes may fail to start up or report that they are unable to "bind" to ports. The behavior may be transient in that if you try to restart the affected process later, it does start successfully.

The cause of this problem is that by default, Oracle Application Server uses a number of ports that fall into the range of "ephemeral" ports. Ephemeral ports are usually used on the client ends of client/server TCP/IP connections. Because client processes usually are unconcerned with which port value is used on the client side of the connection, all TCP/IP implementations allow clients to defer to the operating system the choice of which port value to use for the client side. The operating system selects a port from the "ephemeral" port range for each client connection of this type.

On the other hand, server processes (for example, Oracle Application Server processes) cannot use ephemeral ports. They must use fixed port values so that clients can always connect to the same server port to communicate with the server.

Port conflicts with ephemeral ports arise when an Oracle Application Server process is configured to use a port in the ephemeral port range. The Oracle Application Server process tries to start up, but discovers that the port that it needs is already in use by a client process (the client received the ephemeral port assignment from the operating system). This client can be any process on the computer capable of communicating via TCP/IP. The Oracle Application Server process fails to start up when the port that it needs is unavailable.

This problem occurs relatively more frequently on Microsoft Windows than on other operating systems because by default Windows uses a small range of ports for ephemeral client connections.

Ephemeral Port Range

The ephemeral port range on Microsoft Windows is ports 1024 through 5000, inclusive.

Only the upper end of this range is adjustable in Windows. In most other operating systems, the ephemeral range by default is much larger, and the lower and upper bounds of the range are adjustable.

Several Application Server processes, including Oracle HTTP Server, OracleAS Web Cache, Oracle Enterprise Manager Application Server Control, and OC4J, use ports in the ephemeral port range. These processes cannot start up if the ports that they need are already in use by clients.

Avoiding Conflicts with Ephemeral Ports

To avoid conflicts with ephemeral ports, you have these options:

• Install Oracle Application Server Standard Edition One using the staticports.ini file so that Oracle Application Server Standard Edition One components do not use ports within the ephemeral range. In the staticports.ini file, use port numbers below 1024 or above 5000.

  
  

  See Also: Section 1.4.7.5, "Using Custom Port Numbers (the "Static Ports" Feature)"

  
  

• If you have already installed Oracle Application Server Standard Edition One, you can reconfigure the components to use ports below 1024 or above 5000. See the Oracle Application Server Administrator's Guide to learn how to change the current ports used by Application Server processes.

• (This option can be done post-installation.) Modify the ephemeral port range on your computer. Use this option only if you cannot use either of the alternatives above. This option is the least preferred because it makes changes to the Windows registry, and it affects all products that you run on your computer.

  This option moves the ephemeral port range to a new location. Before making the change, you must verify that none of the products you are using (Oracle or non-Oracle) on your computer use non-ephemeral ports within the ephemeral port range. If any products do so, you must relocate them to the new ReservedPorts range (see below), above the new ephemeral range, or below port 1024.

  To implement this option, perform these steps:

  • Raise the upper bound of the ephemeral port range to expand the size of the range.

    Set the MaxUserPort value in the registry to at least 13000, but no higher than 65534. MaxUserPort is the upper bound of the ephemeral port range.

    For steps, see Microsoft Knowledge Base article 196271: http://support.microsoft.com/default.aspx?scid=kb;[LN];196271.

  • Reserve a portion of the newly expanded ephemeral port range for use by Oracle Application Server.

    Set the ReservedPorts value in the registry so that ports 1024 through 8000 are reserved for Oracle Application Server. The reserved range incorporates the range of ports normally used by Oracle Application Server.

    For steps, see Microsoft Knowledge Base article 812873: http://support.microsoft.com/default.aspx?scid=kb;[LN];812873.

  • Restart your computer for the changes to take effect.

  After performing the steps, you end up with the following: ports from 1024 through 8000 are reserved for Oracle Application Server, and ports 8001 through 13000 are the new ephemeral port range (assuming you set the MaxUserPort to 13000). The reserved range incorporates the range of ports normally used by Oracle Application Server, and the ephemeral range has the same size as the original.

1.4.7.2 Checking If a Port Is Being Used

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

C:\> netstat -an | find "portnum"

Note that you need double-quotes around the port number.

1.4.7.3 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 Standard Edition One installation.

  Note that if you change a component's port number after installation, the portlist.ini file is not updated. The portlist.ini file is not updated after installation.

1.4.7.4 Using Default Port Numbers

If you want to use the default port numbers for components, you do not have to do anything. See Appendix C for a list of the default port numbers and ranges. Make sure 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 the range, the installation will fail.

Note the following points:

• The installer assigns the default ports to components only if the ports are not in use by other applications. If the default port is in use, the installer tries other ports in the port number range for the component. For example, the default non-SSL port for Oracle HTTP Server for the middle tier is port 80. If this port is in use by another application, the installer assigns a port in the 7777 - 7877 range.

• The default ports for Oracle HTTP Server depend on the installation type (Table 1-4). The middle tier gets ports 80 and 443 because it is where you would deploy your applications. Users would send requests to the middle tier's Oracle HTTP Server to access the applications.

  In Table 1-4, the values in parenthesis indicate the ports that the installer will try to assign to Oracle HTTP Server if the default port is already in use.

  Table 1-4 Default Ports for Oracle HTTP Server

  Installation Type	Default Non-SSL Port	Default SSL Port
  OracleAS Portal	80 or 7777 (7777 - 7877)Foot 1	4443 (4443 - 4543)
  J2EE and Web Services	80 (7777 - 7877)	443 (4443 - 4543)

  
  
  ^Footnote 1 OracleAS Infrastructure will pick port 7777 by default, and OracleAS Portal will pick port 80 by default, if available.
  

1.4.7.5 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. The format of this file is shown below. 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, 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-ROM as a template:

1. Copy the staticports.ini file from the CD-ROM or DVD-ROM to your hard disk.

   Table 1-5 Location of the staticports.ini File on CD-ROM and DVD-ROM

   Media	Location of staticports.ini File (assumes E: is your CD-ROM or DVD-ROM drive)
   CD-ROM	Disk 1: E:\stage\Response\staticports.ini
   DVD-ROM	E:\application_server\stage\Response\staticports.ini

   
   

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, 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 the 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 installation is complete, you can check the ORACLE_HOME\install\portlist.ini file to see the assigned ports.

The installer verifies that the ports specified in the file are available by checking 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, 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 the portlist.ini File 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 an installation. If you have installed Oracle Application Server Standard Edition One and you want to use the same port numbers in another installation, you can use the portlist.ini file from the first installation as the staticports.ini file for subsequent installations.

However, note this difference: in 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.

Here are some things that you should check:

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

• If you have syntax errors in the staticports.ini file (for example, if you omitted the = character for a line), 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, 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, 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"), 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 Port 1521 Is In Use by an Existing Oracle Database

If you are installing a new database for the OracleAS Metadata Repository on a computer that is already running an Oracle database, 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-6 shows scenarios and outcomes.

You can change the OracleAS Metadata Repository listener to use a different port after installation. See the Oracle Application Server Administrator's Guide for details.

To check the listener version, run the following command:

C:\> cd ORACLE_HOME\bin
C:\> 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 an example of the command's output:

C:\OraHome_1\BIN>lsnrctl VERSION
LSNRCTL for 32-bit Windows: Version 10.1.0.3.0 - Production on 17-MAY-2005 18:42:10
Copyright (c) 1991, 2004, Oracle.  All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=seone-pc.oracle.com)(PORT=1521)))
TNSLSNR for 32-bit Windows: Version 10.1.0.3.0 - Production
        TNS for 32-bit Windows: Version 10.1.0.3.0 - Production
        Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 10.1.0.3.0 - Production
        Windows NT Named Pipes NT Protocol Adapter for 32-bit Windows: Version 10.1.0.3.0 - Production
        Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows: Version 10.1.0.3.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.

   C:\> cd ORACLE_HOME\bin
   C:\> lsnrctl stop
   
   

   ORACLE_HOME is the home directory for your existing database.

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

2. Install the OracleAS Metadata Repository.

   See 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 existing listener's configuration file.

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

      • TCP Port 1521

      • IPC key EXTPROC

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

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

      If the existing listener's configuration file contains SID_DESC entries for the existing database, you need to add these entries to the OracleAS Metadata Repository listener's 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 any more.

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 Port 1521 Is In Use by Some Other Application

If you have some other application listening on port 1521, you need to reconfigure it to listen on a different port. If that is not possible, shut it down while you install the OracleAS Metadata Repository. After installation, you can reconfigure the OracleAS Metadata Repository to use a port other than 1521. See the Oracle Application Server Administrator's Guide for instructions on how to do this.