|
Oracle® Application Server Installing and Getting Started with Standard Edition One
10g Release 2 (10.1.2) for Linux x86 B16043-02 |
|
 Previous |
 Next |
|
Oracle® Application Server Installing and Getting Started with Standard Edition One
10g Release 2 (10.1.2) for Linux x86 B16043-02 |
|
|
Previous |
Next |
This chapter describes the various Oracle Universal Installer (OUI) installation screens for Oracle Application Server 10g Release 2 (10.1.2). It contains the following sections:
The Oracle Application Server CD-ROMs are in RockRidge format. The DVD is in DVD format. To manually mount or unmount the disk, you must have root privileges. Ensure that you unmount the disk before removing it from the drive.
To mount the first disk, log in as the root user and follow the steps provided in the following section.
Mounting the First Disk on Linux
On most Linux systems, the disk mounts automatically when you insert it into the disk drive. To mount the first disk, follow these steps:
Insert Oracle Application Server Disk 1 into the disk drive.
To verify that the disk mounted automatically, enter the following command:
Red Hat:
# ls /mnt/cdrom
SUSE Linux Enterprise Server:
# ls /media/cdrom
If the command in step 2 fails to display the contents of the disk, then enter the following command:
Red Hat:
# mount -t iso9660 /dev/cdrom /mnt/cdrom
SUSE Linux Enterprise Server:
# mount -t iso9660 /dev/cdrom /media/cdrom
Before starting Oracle Universal Installer, ensure that the /etc/oratab file exists on the same computer where you need to perform the installation. If the oratab file does not exist of the computer, then refer to Section 5.2.1, "If the oratab File Does Not Exist"
In some cases, the /etc/oratab file may not have write permissions. In such cases, refer to Section 5.2.2, "If the oratab File Does Not Have Write Permissions"
To start Oracle Universal Installer:
If the computer does not mount CD-ROMs or DVDs automatically, then you need to set the mount point manually. Refer to Section 5.1, "Setting the Mount Point for CD-ROM or DVD" for details.
Log in as the oracle user.
CD-ROM users: Insert Oracle Application Server Disk 1 into the CD-ROM drive.
DVD users: Insert the Oracle Application Server DVD into the DVD drive.
Run Oracle Universal Installer using the following command:
|
Note:
|
CD-ROM users:
prompt> cd prompt> mount_point/runInstaller
DVD users:
prompt> cd prompt> mount_point/application_server/runInstaller
If the /etc/oratab file does not exist on the computer, then runInstaller script would show the following error message:
Could not find file /etc/oratab, User would need to run "$TMP/rootpreoratab_mm-dd-yyyy_hh:mm:ss.sh" as root........
To run this file as root:
Change user to root.
Run $TMP/rootpreoratab_mm-dd-yyyy_hh:mm:ss.sh.
Exit the session.
Change the user back to the user performing the installation.
Run the installer as mentioned is step 4.
If the /etc/oratab file does not have write permissions, then the following error message is displayed:
/etc/oratab does not have write permissions for current user.Please run chmod 777 /etc/oratab as root. After giving permissions, re-run runInstaller
To change the permissions for the /etc/oratab file:
Change user to root.
Run the following command:
chmod 777 /etc/oratab
Change the user back to the user performing the installation.
Run the installer as mentioned is step 4.
This is the first screen in the installation process. You need to specify the installation directory (or Oracle home) and whether you want to perform a basic or advanced installation.
Specify the Installation Directory
Specify the full path of the installation directory or Oracle home. This is the directory where you want to install the software. For more information about the Oracle home, refer to Section 1.4.2, "Oracle Home Directory" and Section 1.4.2.1, "Naming Your Oracle Home".
Select Basic or Advanced Installation
Select whether you want to perform a basic or advanced installation.
The basic installation prompts you to answer the questions on this screen. Default values for all the components will be used. If you want to perform a basic installation, then click Basic Installation. Skip to Section 5.3.1, "Completing the Basic Installation for J2EE and Web Services" or Section 5.3.2, "Completing the Basic Installation for OracleAS Portal with Identity Management and Metadata Repository", depending on which service you want to install.
The advanced installation provides you with a greater degree of customization and flexibility, allowing for the installation of additional languages, port configuration options, use of an existing database as the Metadata Repository (portal installation only), and database configuration (portal installation only). If you choose to customize your installation and do not want to accept the default values, then click Advanced Installation, then click Next. Skip to Section 5.4, "Select a Product to Install".
To complete the basic installation for J2EE and Web Services:
Select J2EE and Web Services from the drop-down list.
Provide the J2EE and Web Services instance name and ias_admin password. For more information about the instance name, refer to Section 1.4.3. For more information about the ias_admin user and password, refer to Section 1.4.4.
After you have supplied the instance name and ias_admin password, click Install at the bottom of the window. The installation will begin.
After the installation is complete, refer to Chapter 6.
To complete the basic installation for OracleAS Portal with Identity Management and Metadata Repository:
Select OracleAS Portal with Identity Management and Metadata Repository from the drop-down list.
Provide the OracleAS Portal instance name and ias_admin password. For more information about the instance name, refer to Section 1.4.3. For more information about the ias_admin user and password, refer to Section 1.4.4.
Provide the global database name and password. For more information about the global database name and password, refer to Section 1.4.5.
After you have supplied the necessary information, click Install at the bottom of the window. The installation will begin.
After the installation is complete, refer to Chapter 6.
Select the product you want to install, then click Next.
After you click Next, the following warning appears:
Click Yes to continue with the advanced installation.
Select any additional languages you want to install.
Keep in mind that you are selecting languages for the products being installed, and not the installation itself.
Click Next when you finish selecting the languages.
Select the manner in which you want to configure ports.
Click Automatic if you want to use all default port numbers. Refer to Appendix C for a list of all the default port numbers and ranges.
Click Manual if you want to custumize your port numbers. You must supply the full path and file name to an existing port configuration file containing the port numbers you want to use for each component. Typically, this port configuration file is called staticports.ini, although any name is valid as long as the format of the file is correct. Refer to Section 1.4.7.4, "Using Custom Port Numbers (the "Static Ports" Feature)"for more information about the staticports.ini file that is shipped with the product.
Specify the Oracle Application Server instance name and ias_admin Password.
Instance Name
The instance name uniquely identifies this Oracle Application Server Standard Edition One instance.
For more information about instance names, refer to Section 1.4.3, "Oracle Application Server Instances and Instance Names".
ias_admin Password
The ias_admin user is the administrative user for Oracle Application Server Standard Edition One instances. To manage Oracle Application Server Standard Edition One instances using Oracle Enterprise Manager Application Server Control, you log in as the ias_admin user.
For more information about ias_admin password, refer to Section 1.4.4, "The ias_admin User and Restrictions on its Password".
The distinguished name (DN) that you specify on this screen will be designated as the namespace in Oracle Internet Directory where users and groups are administered.
Select the suggested namespace if it meets your deployment requirements. If not, then enter a DN that you want in the custom namespace field. The installer determines the suggested namespace from the /etc/hosts file. Refer to Section 2.7, "The /etc/hosts File".
If you plan to integrate your Identity Management components with a third-party directory, then you should specify the DN of a namespace that matches the DN of the default namespace in the third-party directory.
|
See Also: Oracle Internet Directory Administrator's Guide for details about integration with third-party directories |
Specify the global database name, character set, and data files directory.
Global Database Name
Enter a name for the OracleAS Metadata Repository database. Append a domain name to the database name. This domain name for the global database name can be different from your network domain name.
The domain name portion of the global database name has the following naming restrictions:
Can contain only alphanumeric, underscore (_), and pound (#) characters
Must not be longer than 128 characters
The database name portion of the global database name has the following naming restrictions:
Must contain alphanumeric characters only
Must not be longer than eight characters
Must not contain PORT or HOST in uppercase characters. If you want the name to contain host or port, then use lowercase characters.
Example: asdb.mydomain.com
|
Note: Ensure that you do not enter two or more periods together, for example,asdb..mydomain.com. The installer does not check for this, and this will lead to errors later during the installation process.
|
SID
Enter the system identifier (SID) for the OracleAS Metadata Repository database. Typically this is the same as the global database name, but without the domain name. The SID must be unique across all databases.
SIDs have the following naming restrictions:
Must contain alphanumeric characters only
Must not be longer than eight characters
Must not contain PORT or HOST in uppercase characters. If you want the name to contain host or port, then use lowercase characters.
Example: asdb
Database Character Set
Select the character set from the drop-down list.
|
Note: If you use characters in the NE8ISO8859P10 or CEL8ISO8859P14 character sets, then ensure that your database uses the Unicode character set AL32UTF8. If you are installing a new database, then select AL32UTF8 in the Specify Database Configuration Options screen.The reason for this is that Java does not support the |
Database File Location
Enter the full path to the parent directory for the data files directory. This parent directory must already exist, and you must have write permissions in this directory.
The installer will create a subdirectory in this parent directory, and the subdirectory will have the same name as the SID. The data files will be placed in this subdirectory.
For example, if you enter /oracle/oradata, and the SID is asdb, then the data files will be located in /oracle/oradata/asdb.
Set the passwords for these privileged database administrative accounts (schemas): SYS, SYSTEM, SYSMAN, and DBSNMP.
You can specify a different password for each account or use the same password for each account.
To specify a Different Password for Each Account
Select Use different passwords for these accounts. Then, for each account listed in the table, enter a password in the Enter Password column and reenter the same password in the Confirm Password column.
To Specify the Same Password for All Accounts
Select Use the same password for all accounts, then enter a password in the Enter Password field and reenter the same password in the Confirm Password field.
Password Restrictions
Database schema passwords have the following restrictions:
Passwords must be shorter than 30 characters.
Passwords can contain only alphanumeric characters from your database character set, the underscore (_), the dollar sign ($), and the number sign (#).
Passwords must begin with an alphabetic character. Passwords cannot begin with a number, the underscore (_), the dollar sign ($), or the number sign (#).
Passwords cannot be Oracle reserved words. The Oracle SQL Reference lists the reserved words. You can find this guide on Oracle Technology Network (http://www.oracle.com/technology/documentation), or you can just avoid using words that sound like they might be reserved words.
Passwords cannot be the default passwords, which are change_on_install and manager.
For more information about these and other available schemas, refer to Appendix E, "OracleAS Metadata Repository Schemas".
Specify the Oracle Application Server and OracleAS Portal instance names and the ias_admin password.
Infrastructure Instance Name
This instance name uniquely identifies the OracleAS Infrastructure instance. For more information about instance names, Section 1.4.3, "Oracle Application Server Instances and Instance Names".
Portal Instance Name
This instance name uniquely identifies the OracleAS Portal instance. The restrictions for the OracleAS Portal instance name are the same as the requirements for the infrastructure instance name. However, the two names must not be the same.
For more information about instance names, Section 1.4.3, "Oracle Application Server Instances and Instance Names".
ias_admin Password
The ias_admin user is the administrative user for Oracle Application Server instances. To manage Oracle Application Server instances using Oracle Enterprise Manager, you log in as the ias_admin user.
For more information about ias_admin password, refer to Section 1.4.4, "The ias_admin User and Restrictions on its Password".
Specify the information for the database that contains the existing Metadata Repository.
|
Note: The installer checks that the database contains the Metadata Repository. You could have installed the Metadata Repository previously through the installer, or you could have run the Oracle Application Server Metadata Repository Creation Assistant to install the Metadata Repository in an existing database. |
All the fields on this screen are required and must contain valid entries.
Username
Log in as a DBA user.
Password
Enter the DBA user password.
Host name and Port
Specify the host name and port for the database. Use the format:
hostname:port
Service Name
Specify the service name for the database containing the Metadata Repository. Typically the service name is the same as the global database name.
If you are not sure about the name of database instance, then you can obtain it from the SERVICE_NAMES parameter in the initialization parameter file of the database. If the initialization parameter file does not contain the SERVICE_NAMES parameter, then the service name is the same as the global database name, which is specified in the DB_NAME and DB_DOMAIN parameters.
Check and verify that the installation parameters shown in this window are correct.
Click Install to begin the installation.
This screen shows the progress of the installation.
Click Stop Installation if you want to stop the installation. You will be asked to verify that you want to stop the installation.
This screen also provides the location of the install log, in case you want to view the contents of the log.
This screen shows the name, status, and tool type for tools recommended to be run before completing the installation, along with optional configuration assistants that can be run at your discretion.
|
Note: Recommended tools are run first, followed by optional tools. Recommended tools must be run in order. If a recommended tool fails or is canceled, then the user must correct the problem and successfully run that tool before proceeding to the next tool. |
A tool may have one of the following states, as shown in the status column:
Succeeded: The tool ran successfully.
Failed: The tool ran, but failed.
Pending: The tool is waiting to run.
Cancelled: The tool was canceled by the user (by clicking Stop).
In Progress: The tool is currently running.
Skipped: A configuration assistant running before this tool was canceled or failed. Tools that follow a failed or canceled tool are skipped.
When you select a tool, its details are shown in the Details box. Details are displayed as the tool is running. If you want to stop a configuration assistant while it is running, then click Stop.
If all tools succeed in the first try, then OUI automatically proceeds to the next page. Otherwise, OUI remains on the Configuration Assistants page until all tools are successful. You can then click Next to proceed.
If one or more tools fail, then OUI does not proceed to the next page. Instead, you can read the details of failed tools, fix the problems, and try running the configuration assistant again. You should also consult the installation document of the product being installed for instructions on what to do if a tool fails. For all failed or skipped tools, OUI generates a list of tool names and the commands used to run them. You can copy and paste this information directly into a shell script to run these tools after installation is complete.
By default, the check box in the Retry column will be checked for all tools that failed or were skipped. To retry all checked configuration assistants, click Retry.
To continue without fixing the problem, click Next.
|
Note: The installation is considered successful even if all configuration assistants fail, irrespective of their type (Recommended or Optional). However, failing to successfully run all recommended tools results in an improperly configured product that may not function. |
This screen tells you whether or not your Oracle Application Server Standard Edition One installation was successful and displays some important information that you must remember about the products you have installed. For example, it might contain information about the URLs for particular Web applications. Write down this information so that you can remember it.
To view release notes for the products you have installed, click Release Information or refer to the documentation page on OTN at
http://www.oracle.com/technology/documentation
Click Exit to exit OUI.
Some Oracle products require additional configuration after you install the software. Some of these configuration assistants run automatically when the installation is complete. Other configuration assistants prompt you with a dialog box as soon as you click Exit so that you can decide whether or not to run the configuration assistant at this point in time.
If the software you are installing requires additional configuration assistants, then OUI displays a dialog box. The dialog box prompts you to run any additional configuration assistants required.
