Oracle® Application Server

4.1 Check System Requirements

Your computer must meet the following requirements.

Operating Systems Supported

• HP-UX 11i (11.11 or 11.23) PA-RISC or later

Other System Requirements

The following table shows other system requirements.

Note:

(1) If you plan to install OracleAS Infrastructure plus either Business Intelligence and Forms or Portal and Wireless on the same computer, then you need to have at least 1.5 GB of memory.

(2) You can install the data files for the OracleAS Metadata Repository database on a disk that is different from the disk where you are installing OracleAS Infrastructure. If you do this, make sure the disk for the data files has at least 1.3 GB of free space.

4.2 Check Software Requirements

Check that the following software are installed on the system:

• Quality Pack for 11.11

  HP-UX 11i (11.11 or 11.23) PA-RISC or higher

• Patches for 11.11(or higher versions)

  • BUNDLE11i B.11.23.0409.3 Required Patch Bundle for HP-UX 11i v2 (B.11.23), September 2004

  • PHKL_29198 s700_800 11.11 Psets Enablement Patch; top(1)

  • PHSS_28871 s700_800 11.11 ld(1) and linker tools cumulative patch

  • PHSS_28880 s700_800 11.11 HP aC++ -AA runtime libraries (aCC A.03.50)

  • PHCO_29960 s700_800 11.11 Pthread enhancement and fixes

  The following patches are required by JDK 1.4.2.05 or higher. JDK 1.4.2.05 is installed with this release. Refer to the HP Support site for a list of all JDK patches.

  • PHKL_25842 s700_800 11.11 Thread Abort syscall

  • PHKL_25993 s700_800 11.11 thread nostop for NFS, rlimit, Ufalloc fix

  • PHKL_25994 s700_800 11.11 detach;NOSTOP,Abrt,Psets;slpq1;FSS;getlwp

  • PHKL_25995 s700_800 11.11 ufalloc;VxFS3.5;SPP fragmentation;AIO;EVP

  • PHKL_26468 s700_800 11.11 vPar, callout, abstime, shared sync perf

  • PHKL_28489 s700_800 11.11 copyin EFAULT, LDCD access type

  • PHNE_29887 s700_800 11.11 cumulative ARPA Transport patch

  The following patches are required if ANSI C and C++ are installed on the system:

  • PHSS_26792 s700_800 11.X ANSI C compiler B.11.11.04 cumulative patch

  • PHSS_26793 s700_800 11.X +O4/PBO Compiler B.11.11.04 cumulative patch

  • PHSS_31849 : s700_800 11.23 linker + fdp cumulative patch

  • PHSS_31852 : s700_800 11.23 aC++ Runtime (IA: A.06.05, PA: A.03.65)

  • PHSS_32511 : s700_800 11.23 HP aC++ Compiler (A.03.63)

  • PHSS_32512 : s700_800 11.23 ANSI C compiler B.11.11.12 cumulative patch

  • PHSS_32513 : s700_800 11.23 +O4/PBO Compiler B.11.11.12 cumulative patch

  Following patch is required if ServiceGuard is installed on the system:

  • PHSS_32740 : s700_800 11.23 Serviceguard A.11.16.00

• Package

  Motif 2.1 Development Environment (X11MotifDevKit.MOTIF21-PRG) B.11.11.01

  Note: This package is not required if you create the symbolic links described in step 5 of the next section.

To ensure that the system meets these requirements, follow these steps:

1. To determine which version of HP-UX is installed, enter the following command:

   # uname -a
   HP-UX hostname B.11.11 U 9000/800 109444686 unlimited-user license
   
   

   In this example, the version of HP-UX 11i is 11.11.

2. To determine whether the Quality Pack is installed, enter the following command:

   # /usr/sbin/swlist | grep QPK
   
   

   If the quality pack is not installed, download it from the following Web site and install it:

   http://www.software.hp.com/SUPPORT_PLUS/qpk.html
   
   

3. To determine whether a bundle or product is installed, enter the following command:

   # /usr/sbin/swlist -l product | more
   
   

   If a required product is not installed, you must install it. See your operating system or software documentation for information on installing products.

4. To determine whether a patch is installed, enter a command similar to the following:

   # /usr/sbin/swlist -l patch | grep PHKL_29198
   
   

   Alternatively, to list all installed patches, enter the following command:

   # /usr/sbin/swlist -l patch | more
   
   

   If a required patch is not installed, download it from the following URL and install it:

   http://itresourcecenter.hp.com
   
   

5. If the Motif package mentioned earlier is not installed on the computer, create the following symbolic links:

   1. Log in as root.

   2. Change to the /usr/lib directory:

      # cd /usr/lib
      
      

   3. Create the required links:

      # ln -s libX11.3 libX11.sl
      # ln -s libXIE.2 libXIE.sl
      # ln -s libXext.3 libXext.sl
      # ln -s libXhp11.3 libXhp11.sl
      # ln -s libXi.3 libXi.sl
      # ln -s libXm.4 libXm.sl
      # ln -s libXp.2 libXp.sl
      # ln -s libXt.3 libXt.sl
      # ln -s libXtst.2 libXtst.sl
      
      

4.3 Check Kernel Parameters Required by OracleAS Web Cache

This section applies if you are installing OracleAS Web Cache:

• If you are installing the J2EE and Web Cache middle tier, the OracleAS Web Cache component is optional.

• If you are installing the Portal and Wireless or Business Intelligence and Forms middle tier, the OracleAS Web Cache component is always installed.

1. Start System Administration Manager (SAM) as the root user:

   # /usr/sbin/sam
   
   

2. Choose the Kernel Configuration area, then choose the Configurable Parameters area.

3. Check the value for maxfiles_lim is at least 65536. If necessary, modify that value. Refer to the SAM online help for more information on completing this step.

4. Exit from SAM.

5. If you modified the value, restart the system as follows:

   # /sbin/shutdown -r now
   
   

4.4 Check Kernel Parameters Required by OracleAS Metadata Repository

Verify that the kernel parameters shown in the following table are set either to the formula shown, or to values greater than or equal to the recommended value shown. The procedures following the table describe how to verify and set the values.

To view the current value specified for these kernel parameters, and to change them if necessary, follow these steps:

1. Optionally, set the DISPLAY environment variable to specify the display of the local system:

   • Bourne, Bash, or Korn shell:

     $ DISPLAY=localhost:0.0 ; export DISPLAY
     
     

   • C shell:

     $ setenv DISPLAY localhost:0.0
     
     

2. Start System Administration Manager (SAM):

   # /usr/sbin/sam
   
   

3. Choose the Kernel Configuration area, then choose the Configurable Parameters area.

4. Check the value or formula specified for each of these parameters and, if necessary, modify that value or formula.

   If necessary, see the SAM online help for more information on completing this step.

5. Exit from SAM.

6. If you modified the value specified for any parameter, reboot the system:

   # /sbin/shutdown -r now
   
   

7. If necessary, when the system restarts, log in and switch user to root.

4.5 Create an Operating System Group for the Inventory Directory

If this is the first Oracle product to be installed on the computer, then create an operating system group for the inventory directory. The installer creates files in the inventory directory to keep track of the Oracle products that are installed on the computer.

This guide uses the name oinstall for this group.

In the "Create an Operating System User" section, you will create an operating system user, and set the oinstall group to be the user's primary group.

By having a separate group for the inventory directory, you allow different users to install Oracle products on the computer. Users need write permission for the inventory directory. They can achieve this by belonging to the oinstall group.

The default name of the inventory directory is oraInventory.

If you are unsure if there is already an inventory directory on the computer, look in the file. This file lists the location of the inventory directory and the group who owns it. If the file does not exist, the computer does not have Oracle products installed on it.

/var/opt/oracle/oraInst.loc

4.6 Create an Operating System Group for Database Administration

Using the same steps in the previous section, create an operating system group called dba. When you create an operating system user in the next step, you will set this dba group to be the user's secondary group.

4.7 Create an Operating System User

Create an operating system user to install and upgrade Oracle products. This guide refers to this user as the oracle user.

How to Create a User

Perform the following procedure:

1. To create the oracle user, enter a command similar to the following:

   # /usr/sbin/useradd -g oinstall -G dba[,oper] oracle
   
   

   In this command:

   • The -g option specifies the primary group, which must be the Oracle Inventory group, for example oinstall

   • The -G option specifies the secondary groups, which must include the OSDBA group and if required, the OSOPER group, for example dba or dba, oper

2. Set the password of the oracle user as follows:

   # passwd oracle
   
   

4.8 Check Environment Variables

The operating system user who will be installing Oracle Application Server needs to set (or unset) the following environment variables.

% setenv variable_name value

% setenv DISPLAY test.mycompany.com:0.0

$ variable_name=value; export variable_name

$ DISPLAY=test.mydomain.com:0.0; export DISPLAY

4.9 Check If Port 1521 Is in Use

This section is applicable only if you are installing the OracleAS Infrastructure.

The OracleAS Infrastructure installs an Oracle database, which uses port 1521 by default. To check if port 1521 is in use:

prompt> netstat -an | grep 1521

If port 1521 is in use by a third-party application, you need to configure the application to use a different port.

If port 1521 is in use by an existing Oracle database listener, you need to stop the listener before installing the OracleAS Infrastructure.

Refer to Oracle Application Server Installation Guide for details.

7.1 Install OracleAS Infrastructure

To install OracleAS Infrastructure with a new database and a new Oracle Internet Directory:

1. Start up the installer. Refer to "Starting Up the Installer" for details.

2. Welcome screen

   Click Next.

3. If this is the first Oracle product to be installed on this computer, the installer displays these additional screens:

   1. Specify Inventory Directory and Credentials screen

      Enter the full path of the inventory directory: Enter a full path to the inventory directory. This directory is different from the Oracle home directory for the product files.

      Example: /opt/oracle/oraInventory

      Specify operating system group name: Select the operating system group that will have write permission for the inventory directory.

      Example: oinstall

      Click Next.

   2. Run orainstRoot.sh dialog

      When prompted, run the orainstRoot.sh script as the root user in a different shell. The script is located in the inventory directory.

      After running the script, click Continue.

4. Specify File Locations screen

   Name: Enter a name to identify this Oracle home.

   Example: OH_INFRA

   Destination Path: Enter the full path to the destination directory. This is the Oracle home. If the destination directory does not exist, Oracle Universal Installer creates it.

   Example: /opt/oracle/oraInfra

   Click Next.

5. Select a Product to Install screen

   Select OracleAS Infrastructure and click Next.

6. Select Installation Type screen

   Select Identity Management and OracleAS Metadata Repository and click Next.

7. Confirm Pre-Installation Requirements screen

   Check that you meet the requirements listed on this screen, select all the checkboxes, and click Next.

8. Select Configuration Options screen

   Select Oracle Internet Directory.

   Select OracleAS Single Sign-On.

   Select Delegated Administration Service.

   Select Oracle Directory Integration and Provisioning.

   Do not select OracleAS Certificate Authority.

   Do not select High Availability and Replication.

   Click Next.

9. Specify Port Configuration Options screen

   Select Automatic and click Next.

10. Specify Namespace in Internet Directory screen

    Select Suggested Namespace and click Next.

11. Specify Database Configuration Options screen

    Global Database Name: Enter a name for the OracleAS Metadata Repository database, and append your domain name to the database name.

    The database name portion of the global database name:

    • can contain only alphanumeric characters

    • must not be longer than eight characters

    • must not contain the word "PORT" or "HOST" in uppercase characters. If you need to use these words, use lowercase characters.

    The domain name portion of the global database name:

    • can contain alphanumeric, underscore (_), minus (-), and pound (#) characters

    • must not be longer than 128 characters

    Example: orcl.yourcompany.com

    SID: Enter the system identifier for the OracleAS Metadata Repository database. Typically this is the global database name, but without the domain name. The SID must be unique across all databases.

    The SID name has the same naming restrictions as the database name portion of the global database name (listed above).

    Example: orcl

    Select Database Character Set: Select the character set that you want to use for the database.

    Database File Location: Specify the full path to the parent directory for the data files directory. The directory you specify must exist, and you must have write permissions in it.

    The installer installs the data files in a subdirectory of the path you specify. The installer uses the database name for the name of the subdirectory. For example, if you specify orcl.yourcompany.com for the global database name and /data/dbfiles for the database file location, the installer places database files in the following directory: /data/dbfiles/orcl.

    The file system that contains the directory must have at least 1.3 GB of free disk space. Additional disk space is required for production databases, depending on the amount of data that you plan to store.

    Click Next.

12. Specify Database Schema Passwords screen

    Set the passwords for the administrative database users, which are privileged accounts used for database administration. You can use the same password for all users, or specify different passwords for each user.

    Click Next.

13. Specify Instance Name and ias_admin Password screen

    Instance Name: Enter a name for this instance. Instance names can contain alphanumeric and _ (underscore) characters. If you have more than one Oracle Application Server instance on a computer, the instance names must be unique.

    Example: infra

    ias_admin Password and Confirm Password: Enter and confirm the password for the ias_admin user. This is the administrative user for this instance.

    Passwords must consist of at least five characters, and one of the characters must be a number.

    Example: welcome99

    Click Next.

14. Summary screen

    Verify your selections and click Install. The installer now installs the files.

15. Run root.sh dialog

    Note: do not run this script until you see the dialog.

    In a different window, log in as the root user and run the root.sh script. The script is located in this instance's Oracle home directory.

    After you have run the root.sh script, click OK.

16. Configuration Assistants screen

    This screen displays the progress of configuration assistants, which configure Oracle Application Server components.

17. End of Installation screen

    Click Exit to quit the installer.

7.2 Install Portal and Wireless or Business Intelligence and Forms Middle tier

The following procedure installs a Portal and Wireless or Business Intelligence and Forms middle tier and configures it to use the OracleAS Infrastructure installed in "Install OracleAS Infrastructure".

1. Start up the installer. See "Starting Up the Installer" for details.

2. Welcome screen

   Click Next.

3. If this is the first Oracle product to be installed on this computer, the installer displays these additional screens:

   1. Specify Inventory Directory and Credentials screen

      Enter the full path of the inventory directory: Enter a full path to the inventory directory. This directory is different from the Oracle home directory for the product files.

      Example: /opt/oracle/oraInventory

      Specify operating system group name: Select the operating system group that will have write permission for the inventory directory.

      Example: oinstall

      Click Next.

   2. Run orainstRoot.sh dialog

      When prompted, run the orainstRoot.sh script as the root user in a different shell. The script is located in the inventory directory.

      After running the script, click Continue.

4. Specify File Locations screen

   Name: Enter a name to identify this Oracle home.

   Example: OH_PORTAL

   Destination Path: Enter the full path to the destination directory. This is the Oracle home. If the destination directory does not exist, Oracle Universal Installer creates it.

   Example: /opt/oracle/oraPortal

   Click Next.

5. Select a Product to Install screen

   Select Oracle Application Server and click Next.

6. Select Installation Type screen

   Select Portal and Wireless or Business Intelligence and Forms and click Next.

7. Confirm Pre-Installation Requirements screen

   Check that you meet the requirements listed on this screen, select all the checkboxes, and click Next.

8. Select Configuration Options screen

   For Portal and Wireless, select:

   • OracleAS Portal

   • OracleAS Wireless

   For Business Intelligence and Forms, select:

   • OracleAS Portal

   • OracleAS Wireless

   • OracleBI Discoverer

   • OracleAS Personalization

   • OracleAS Reports Services

   • OracleAS Forms Services

   Click Next.

9. Specify Port Configuration Options screen

   Select Automatic and click Next.

10. Enter connect information for Oracle Internet Directory, which you installed when you installed the OracleAS Infrastructure:

    1. Register with Oracle Internet Directory screen

       Hostname: Enter the name of the computer where Oracle Internet Directory is running.

       Port: Enter the port number at which Oracle Internet Directory is listening. To determine Oracle Internet Directory's port number, look in the ORACLE_HOME/install/portlist.ini file, where ORACLE_HOME is where you installed the OracleAS Infrastructure.

       If you select Use only SSL connections with this Oracle Internet Directory, then you must obtain the port number from "Oracle Internet Directory (SSL)" parameter in the portlist.ini file.Click Next.

    2. Specify Login for Oracle Internet Directory screen

       Username: Enter orcladmin. This is the name of the Oracle Internet Directory administrator.

       Password: The password for the orcladmin user is the same as the password for the ias_admin user in the infrastructure. You entered this password when you installed the infrastructure (see Step 13 in "Install OracleAS Infrastructure").

       Click Next.

11. Select Metadata Repository screen

    Repository: Select the OracleAS Metadata Repository that you want to use for this middle-tier instance and click Next.

12. Provide Outgoing Mail Server Information

    This screen appears only if you selected a Business Intelligence and Forms installation.

    Enter the name of the outgoing mail (SMTP) server for use by OracleAS Reports Services. You can leave it blank and configure it later. Click Next.

13. Specify Instance Name and ias_admin Password screen

    Instance Name: Enter a name for this instance. Instance names can contain alphanumeric and _ (underscore) characters. If you have more than one Oracle Application Server instance on a computer, the instance names must be unique.

    Example: PORTAL

    ias_admin Password and Confirm Password: Enter and confirm the password for the ias_admin user. This is the administrative user for this instance.

    Passwords must consist of at least five characters, and one of the characters must be a number.

    Example: welcome99

    Click Next.

14. Summary screen

    Verify your selections and click Install. The installer now installs the files.

15. Run root.sh dialog

    Note: do not run this script until you see the dialog.

    In a different window, log in as the root user and run the root.sh script. The script is located in this instance's Oracle home directory.

    After you have run the root.sh script, click OK.

16. Configuration Assistants screen

    This screen displays the progress of configuration assistants, which configure Oracle Application Server components.

17. End of Installation screen

    Click Exit to quit the installer.

10.1 Oracle Support Services

If you purchased Oracle Product Support, you can call Oracle Support Services for assistance. Oracle Support Services include phone assistance, version updates and access to our service offerings. You have access to phone support 24 hours a day, 7 days a week. In the U.S.A., you can call Product Support at 1-800-223-1711.

Make sure you have your CSI (CPU Support Identifier) number ready when you call. Keep the CSI number for your records, because it is your key to Oracle Support Services. The Oracle Store sends the CSI number to you in an e-mail alert when it processes your order. If you do not have your CSI number and you are in the U.S.A., you can look up your CSI number by accessing our online Order Tracker which provides detailed order information. Go to the Oracle Store and click on Order Tracker located above the top navigation bar.

For Oracle Support Services locations outside the U.S.A., call your local support center for information on how to access support. To find the local support center in your country, visit the Support Web Center at http://www.oracle.com/support.

At the Support Web Center you will find information on Oracle Support Services, such as:

• contact information

• instructions on how to access electronic services

• helpful Web sites

• Support Resources

• Oracle Support Portfolio

• Oracle Support Services news

With Oracle Product Support, you have round-the-clock access to OracleMetaLink, Oracle Support Services premier Web support offering. OracleMetaLink offers you access to installation assistance, product documentation, and a technical solution knowledge base.

It has technical forums, where you can post questions about your Oracle products and receive answers from Oracle Technical Support Analysts and other Oracle users. The questions and answers remain posted for the benefit of all users.

OracleMetaLink options include:

• Technical Assistance Request (TAR) access

• patch downloads

• bug database query accessproduct life-cycle information

You can access OracleMetaLink at http://metalink.oracle.com.

10.2 Version Updates

If you do not have a currently supported license, you can purchase the most recent version of an Oracle product from the Oracle Store at:

http://oraclestore.oracle.com

If you do have a currently supported license, you can place non-urgent requests for version update shipments through the iTAR feature on OracleMetaLink. You will need to log the iTAR type as a U.S. Client Relations/Non-Technical Request.

You can also request Version Update shipments in the U.S.A. by calling Client Relations. When requesting a Version Update, provide the following information to the Client Relations Analyst:

• CSI number

• contact information

• platform

• product name

• shipping address

• version number of the product

Outside the U.S.A., call your local Oracle Support Center.

10.3 Premium Services

For information on our Premium Services, including onsite support, OracleGOLD, remote services, and upgrade packages, visit the Support Web Center at http://www.oracle.com/support

or call your Support Sales Representative in the U.S.A at 1-800-833-3536.

10.4 Quick Reference