Oracle® Application Server

4.1 Check System Requirements

Your computer must meet the following requirements.

Operating Systems Supported

• Solaris 8

• Solaris 9

For the latest information about supported operating systems, visit OracleMetaLink at http://metalink.oracle.com.

Other System Requirements

The following table shows other system requirements.

Notes:

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

(2) Includes OracleAS Identity Management and OracleAS Metadata Repository. 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.6 GB of free space.

4.2 Install Required Solaris Patches

Check that your computer has the following patches:

Patches Required for Solaris 8:

• 108652-82 or higher: X11 6.4.1: Xsun patch

• 108921-21 or higher: CDE 1.4: dtwm patch

• 108940-62 or higher: Motif 1.2.7 and 2.1.1: Runtime library patch

• 108773-18 or higher: IIIM and X input and output method patch

• 111310-01 or higher: /usr/lib/libdhcpagent.so.1 patch

• 109147-28 or higher: Linker patch

• 111308-04 or higher: /usr/lib/libmtmalloc.so.1 patch

• 112438-03 or higher: /kernel/drv/random patch

• 108434-17 or higher: 32-bit shared library patch for C++

• 108435-17 or higher: 64-bit shared library patch for C++

• 111111-04 or higher: /usr/bin/nawk patch

• 112396-02 or higher: /usr/bin/fgrep patch

• 110386-03 or higher: RBAC feature patch

• 111023-03 or higher: /kernel/fs/mntfs and /kernel/fs/sparcv9/mntfs patch

• 111317-05 or higher: /sbin/init and /usr/sbin/init patch

• 113648-03 or higher: /usr/sbin/mount patch

• 115827-01 or higher: /sbin/sulogin and /sbin/netstrategy patch

• 116602-01 or higher: /sbin/uadmin and /sbin/hostconfig patch

• 108987-13 or higher: Patch for patchadd and patchrm

• 108528-29 or higher: Kernel update patch

• 108989-02 or higher: /usr/kernel/sys/acctctl and /usr/kernel/sys/exacctsys patch

• 108993-36 or higher: LDAP2 client, libc, libthread and libnsl libraries patch

• 109326-14 or higher: libresolv.so.2 and in.named patch

• 110615-11 or higher: sendmail patch

Patches Required for Solaris 9

• 113096-03 or higher: X11 6.6.1: OWconfig patch

• 112785-35 or higher: X11 6.6.1: Xsun patch

How to Check for Patches

To determine which patches are installed on your computer:

1. Run the showrev command with the -p option. The following command saves the sorted output to a file called patchList.

   prompt> showrev -p | sort > patchList
   
   

2. Open the file in a text editor, and search for patch numbers.

If You Need Patches

You can download patches from http://sunsolve.sun.com.

4.3 Check Solaris Packages

Check that your computer has the following packages:

• SUNWarc

• SUNWbtool

• SUNWhea

• SUNWlibm

• SUNWlibms

• SUNWsprot

• SUNWsprox

• SUNWtoo

• SUNWi1of (the character after the "i" is the number 1, not the letter "ell")

• SUNWxwfnt

To check if the required operating system packages are installed on your computer, run the following command:

prompt> pkginfo SUNWarc SUNWbtool SUNWhea SUNWlibm
    SUNWlibms SUNWsprot SUNWsprox SUNWtoo SUNWi1of
    SUNWxwfnt

If your computer is missing a package, contact your system administrator.

4.4 Check for 32-bit and 64-bit Application Support

Check that your computer is configured to support 32-bit and 64-bit applications. To check this, run the following command:

prompt> /usr/bin/isainfo -v
64-bit sparcv9 applications
32-bit sparc applications

The output must display both lines. If not, you need to reconfigure your computer. Check with your system administrator.

4.5 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. Run the following command to check that the rlim_fd_max kernel parameter is set to at least 65536:

   prompt> ulimit -Hn
   
   

2. If the command returns a value less than 65536, add this line to the /etc/system file (use a text editor to edit the file):

   set rlim_fd_max=65536
   
   

   You need to be the root user to edit the /etc/system file.

3. Reboot the computer for the new value to take effect.

4.6 Check Kernel Parameters Required by OracleAS Metadata Repository

This section applies only if you are installing the OracleAS Infrastructure.

1. Open the /etc/system file in a text editor.

2. Check that these parameters are set at these minimum values:

   • set semsys:seminfo_semmni=100

     Defines the maximum number of semaphore sets in the entire system.

   • set semsys:seminfo_semmns=256

     Defines the maximum semaphores on the system. The 256 is only a minimum value for computers that will be running the OracleAS Metadata Repository.

   • set semsys:seminfo_semmsl=256

     Defines the minimum recommended value, for initial installation only.

   • set shmsys:shminfo_shmmax=4294967295

     Defines the maximum allowable size of one shared memory segment (4 GB = 4294967295).

   • (Solaris 8 only) set shmsys:shminfo_shmmin=1

     Defines the minimum allowable size of a single shared memory segment.

   • (Solaris 8 only) set shmsys:shminfo_shmseg=10

     Defines the maximum number of shared memory segments one process can attach.

   • set shmsys:shminfo_shmmni=100

     Defines the maximum number of shared memory segments in the entire system.

3. If you had to change the value of any of the parameters in the file, reboot the computer for the new values to take effect.

4.7 Create an Operating System Group for the Inventory Directory

If this is the first Oracle product to be installed on the computer, 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 Section 4.9, "Create an Operating System User", you will create an operating system user, and set this 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 /var/opt/oracle/oraInst.loc 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.

How to Create a Group

To create a local operating system group, use the Solaris Management Console:

1. Set the DISPLAY environment variable to point to the monitor where you want the Solaris Management Console window to appear. The format of the DISPLAY environment variable is:

   hostname:display_number.screen_number
   
   

   Example (C shell):

   % setenv DISPLAY test.mycompany.com:0.0
   
   

   Example (Bourne or Korn shell):

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

2. Start up the Solaris Management Console.

   prompt> /usr/sadm/bin/smc
   
   

3. In the left frame, expand This Computer, then expand System Configuration.

4. Click Users. This displays the Log In window.

5. In the Log In window, log in as the root user.

6. In the left frame, expand Users and select Groups.

7. Select Action > Add Group.

8. In Group Name, enter the oinstall as the name of the group.

9. (optional) In Group ID Number, enter an ID number for the group.

10. Click OK.

4.8 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.9 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

To create a local operating system user, use the Solaris Management Console:

1. Set the DISPLAY environment variable to point to the monitor where you want the Solaris Management Console window to appear. The format of the DISPLAY environment variable is:

   hostname:display_number.screen_number
   
   

   Example (C shell):

   % setenv DISPLAY test.mycompany.com:0.0
   
   

   Example (Bourne or Korn shell):

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

2. Start up the Solaris Management Console.

   prompt> /usr/sadm/bin/smc
   
   

3. In the left frame, expand This Computer > System Configuration.

4. Click Users. This displays the Log In window.

5. In the Log In window, in User Name, enter root. In Password, enter the root password.

6. In the left frame, expand Users and select User Accounts.

7. Select Action > Add User > With Wizard.

8. In User Name, enter the name of the user (oracle). The Full Name and Description fields are optional. Click Next.

9. In User ID Number, accept the default value. Click Next.

10. Select User Must Use This Password At First Login, and enter a password for the user. Click Next.

11. In Primary Group, select the primary group for the user. This is the group you created earlier for the inventory directory. See Section 4.7, "Create an Operating System Group for the Inventory Directory". Click Next.

12. In Path, enter a home directory for the user. Click Next.

13. Review the mail server information and click Next.

14. Review the user information and click Finish to create the user.

To check which groups an operating system user belongs to, run the groups command with the name of the user. For example:

prompt> groups oracle

4.10 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.11 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.

See the Oracle Application Server Installation Guide for details.

5.1 Mounting the CD-ROM or DVD-ROM

Follow these steps if your computer does not automount the CD-ROM or DVD-ROM:

1. Insert the CD-ROM or DVD-ROM.

2. Log in as the root user.

   prompt> su
   Password: 
   
   

3. Create the CD-ROM or DVD-ROM mount point directory:

   # mkdir /cdrom
   
   

4. Mount the CD-ROM or DVD-ROM drive on the mount point directory:

   # mount options device_name /cdrom
   
   

   For example:

   # mount -r -F hsfs device_name /cdrom
   
   

   You can also use the same commands and options to mount the DVD-ROM.

5. Log out from the root user.

   # exit
   
   

7.1 Install OracleAS Infrastructure

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

1. Start up the installer. See Section 5, "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

   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 OracleAS Delegated Administration Service.

   Select OracleAS 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 Section 7.1, "Install OracleAS Infrastructure".

1. Start up the installer. See Section 5, "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

   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 10g 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:

   • Oracle Application Server Portal

   • Oracle Application Server Wireless

   For Business Intelligence and Forms, select:

   • Oracle Application Server Portal

   • Oracle Application Server Wireless

   • Oracle Business Intelligence Discoverer

   • Oracle Application Server Personalization

   • Oracle Application Server Reports Services

   • Oracle Application Server 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 OID Login

       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 Section 7.1, "Install OracleAS Infrastructure").

       Click Next.

11. Select Oracle Application Server 10g 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