|
Oracle® Application Server Installing and Getting Started with Standard Edition One
10g Release 2 (10.1.2) for Microsoft Windows (32 Bit) Part No. B15881-02 |
|
![]() Previous |
![]() Next |
This chapter contains screenshots and descriptions of the various Oracle Universal Installer (OUI) installation screens for Oracle Application Server Standard Edition One.
This chapter is designed to aide you in filling out the screens during the Oracle Application Server Standard Edition One installation. It is not meant to be read from start to finish. Installation instructions for J2EE and Web Services can be found in Chapter 3. Installation instructions for OracleAS Portal can be found in Chapter 4. Use this chapter in conjunction with those chapters to complete your Oracle Application Server Standard Edition One installation.
The contents of this chapter are summarized below:
Specify Instance Name and ias_admin Password (J2EE and Web Services Installation)
Specify Instance Names and ias_admin Password (OracleAS Portal Installation)
To start the Oracle Universal Installer:
Log in to the computer as a user who is a member of the Windows Administrators group.
Insert the disk.
CD-ROM users: Insert Oracle Application Server Disk 1 into the CD-ROM drive.
DVD-ROM users: Insert the Oracle Application Server DVD-ROM into the DVD-ROM drive.
If your computer supports the auto run feature, the installer launches automatically.
If your computer does not support the auto run feature, you have to start up the installer manually:
|
Note: If you are running the installer on a computer that is already running Oracle Database 10g, then you have to start up the installer with the following option:E:\> setup.exe -J-Dsun.java2d.noddraw=true -Dsun.awt.nopixfmt=true
If you do not start the installer with the |
CD-ROM users: Double-click setup.exe.
DVD-ROM users: Double-click setup.exe in the application_server directory.
This is the first screen in the installation process, where you will provide the installation directory, and also select whether you want to perform a basic or advanced installation.
Specify the Installation Directory
Specify the full path of the installation directory (the directory where you want to install the software). If you are installing J2EE and Web Services only, this directory will also be the Oracle home directory. For more information about the Oracle home, see Section 1.4.2, "Oracle Home Directory".
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. The installer will configure components by using reasonable default values or computing values if not information is available. If you want to perform a basic installation, click the "Basic Installation" button. Skip to Section 5.2.1, "Completing the Basic Installation for J2EE and Web Services" or Section 5.2.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, the 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, click the "Advanced Installation" button, then click the "Next" button. Skip to Section 5.3, "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 on the "Install" button at the bottom of the window. The installation will begin..
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. This password will be used for the SYS, SYSTEM, SYSMAN, and DBSNMP privileged database administrative accounts (schemas). For more information about the global database name and password, refer to Section 1.4.5.
After you have supplied the necessary information, click on the "Install" button at the bottom of the window. The installation will begin..
Select the product you want to install, then click the "Next" button.
After you click on the "Next" button, 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 the "Next" button when you are finished.
Select the manner in which you want to configure ports.
Click "Automatic" if you want the installer to automatically determine the port numbers. See Appendix C for a list of all the default port numbers and ranges.
Click "Manual" if you want to customize your port numbers. You must supply the full path and filename 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. See Section 1.4.7.5 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 for your J2EE and Web Services instalation.
Instance Name
The instance name uniquely identifies this Oracle Application Server Standard Edition One instance.
For more information about instance names, see Section 1.4.3.
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 the ias_admin password, see Section 1.4.4.
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, enter a DN that you want in the custom namespace field. The installer determines the suggested namespace from the %WINDIR%\system32\drivers\etc\hosts file. See Section 2.5, "The %WINDIR%\system32\drivers\etc\hosts File".
If you plan to integrate your Identity Management components with a third-party directory, you should specify the DN of a namespace that matches the DN of the default namespace in the third-party directory. See the Oracle Internet Directory Administrator's Guide for details on 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", use lowercase characters.
Example: asdb.mydomain.com
Note: Be sure 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", 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, make sure that your database uses the Unicode character set AL32UTF8. If you are installing a new database, select "AL32UTF8" in the Specify Database Configuration Options screen.The reason for this is that Java does not support the NE8ISO8859P10 or CEL8ISO8859P14 character sets. If you configure the database to use a character set not supported by Java, you will get an "Unsupported IANA character encoding" error in OracleAS Portal. |
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.
Example: If you enter C:\oradata, and the SID is asdb, then the data files will be located in C:\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 all accounts.
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 re-enter 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" files and re-enter 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, see Appendix E, "OracleAS Metadata Repository Schemas".
Specify the OracleAS Infrastructure and OracleAS Portal instance names and ias_admin password.
Infrastructure Instance Name
This instance name uniquely identifies the OracleAS Infrastructure instance.
For more information about instance names, see Section 1.4.3.
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, see Section 1.4.3.
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 the ias_admin password, see Section 1.4.4.
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 of 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.
Hostname and Port
Specify the hostname 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 unsure what the service name for your database is, you can obtain it from the SERVICE_NAMES parameter in the database's initialization parameter file. 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 the "Install" button to begin the installation.
This screen shows the progress of the installation.
Click "Stop Installation" if you want to abort 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 the 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 cancelled, the user must correct the problem and successfully run that tool before proceeding to the next tool. |
|
Note: If you choose to install either of the OracleAS Portal services, you will see two Configuration Assistant screens during the installation. This is because both an OracleAS Infrastructure and middle tier are being installed. The first Configuration Screen is for the infrastructure components, and the second is for the middle tier components. For more information, see Section 1.3, "Installation Overview". |
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 cancelled by the user (by clicking "Stop").
In Progress: The tool is currently running.
Skipped: A configuration assistant running before this tool was cancelled or failed. Tools that follow a failed or cancelled 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, click "Stop."
If all tools succeed on the first try, 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, 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 for 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 the tool names and the commands used to run them; you can copy/paste this information directly into a shell script or batch file 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 failed, 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. If necessary, write this information down so that you can remember it.
This information can also be found in the ORACLE_HOME\install\setupinfo.txt file.
To view release notes for the products you have installed, click "Release Information" or see the documentation page on OTN ( http://www.oracle.com/technology/documentation).
Click "Exit" to exit the Oracle Universal Installer. You will be asked to confirm that you want to exit. After you exit the Oracle Universal Installer, a browser will be started and the Welcome page will appear. See Section 7.2 for more information about the Welcome page.
Some Oracle products require additional configuration after you install the software. Some of these configuration assistants run automatically when the installation is complete; others prompt you with a dialog box as soon as you click "Exit" so you can decide whether or not you want to run the configuration assistant at this point in time.
If the software you are installing requires additional configuration assistants, OUI displays a dialog box. The dialog box prompts you to run any additional configuration assistants required.
For additional post-installation information, see Chapter 6, "Post-Installation Tasks".
If you encounter any problems with the installation, configuration assistants, or product in general, refer to Appendix H, "Troubleshooting" for common problems and solutions.