| Oracle® Application Server Installation Guide 10g Release 3 (10.1.3.2.0) for Microsoft Windows (64-Bit) on Intel Itanium Part Number B32408-01 |
|
|
View PDF |
| Oracle® Application Server Installation Guide 10g Release 3 (10.1.3.2.0) for Microsoft Windows (64-Bit) on Intel Itanium Part Number B32408-01 |
|
|
View PDF |
This chapter contains the following topics:
Section 3.3, "Oracle Application Server Instances and Instance Names"
Section 3.4, "The oc4jadmin User and Restrictions on its Password"
Section 3.6, "Using an Assistive Technology with the Installer"
Section 3.7, "Rules for Adding Instances to OracleAS Clusters"
The directory in which you install Oracle Application Server is called the Oracle home. During installation, you specify the full path to this directory.
For example, you can install Oracle WebCenter Framework in C:\oracle\OraHome_webcenter.
Note:
Spaces are not allowed anywhere in the Oracle home directory path. For example, you cannot install in "C:\program files\oracle\webcenter" because of the space character in "program files". The installer does not check for this until several screens after you have entered the path.
You cannot install on another computer by mapping to a drive on that computer. If you want to install on another computer, you can do it through remote control software. See Section 2.8.9, "Installing on Remote Computers Through Remote Control Software" for details.
This section includes the following topics:
Each Oracle home directory is automatically given a name. The Oracle home name is oracleasx, where x is a number that depends on how many Oracle Application Server installations are on the system.
For example, if you are performing your first installation of Oracle Application Server on this system, then your Oracle home is named oracleas1.
Generally, you cannot install Oracle Application Server in an existing Oracle home. See "Oracle home directory" for a list of combinations that are not allowed.
You cannot install Oracle Application Server in a directory that already contains some files, except for the cases mentioned in Section 3.1.2, "Installing in an Existing Oracle Home". 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 in it. Also, the installer cannot "repair" an installation.
By default, the installer installs Oracle Application Server with text in English and in the operating system language. If you need additional languages, click Product Languages button in the Select Installation Type screen.
When you select additional languages to install, the installer installs text in the selected languages. It also installs fonts required to display the languages.
For some components, languages are installed only if you select them during installation. In this case, if you access the application in a language that is not available, it will fall back on the server locale language.
For other components, available languages are installed regardless of what you select during installation. In this case, however, fonts are installed only for the languages that are explicitly selected. When you access the application, it uses text in your language because the language was installed. However, if you do not have the appropriate fonts to render the text, the text appears as square boxes. This usually applies to the Chinese, Japanese, and Korean languages.
You can install fonts after installation. See Section F.3.4, "User Interface Does Not Display in the Desired Language, or Does Not Display Properly".
Note that you cannot install additional languages after installation. You must install all languages that you need during installation. If you run Oracle Application Server in an environment that uses a language that you did not install, the user interface can display text in that language and/or in English, or it can display square boxes (caused by missing fonts) instead of text.
When you install the middle tier, what you get is an Oracle Application Server instance. The installer prompts you to provide a name for the Oracle Application Server instance you are installing. For example, you can name an instance "WebCenter". This name can be different from the Oracle home name.
You cannot change this name after installation.
Oracle Application Server appends the hostname and domain name to the given instance name to form a complete instance name. For example, if you are installing an instance on a computer named c1, and you name the instance WebCenter1, then the full name of the instance is WebCenter1.c1.mydomain.com, assuming the domain name is mydomain.com.
Valid Characters in Instance Names
Instance names can consist only of the alphanumeric characters (A-Z, a-z, 0-9) and the _ (underscore) character.
There is no maximum length restriction for instance names.
Restrictions on Oracle Application Server Instance Names
Do not use the hostname of the computer when naming Oracle Application Server instances.
If you are planning to place the Oracle Application Server instance in an OracleAS Cluster, the instance name must not contain the following:
hostname or IP address of any computer in the OracleAS Cluster
Oracle home of any Oracle Application Server installation in the OracleAS Cluster
How Oracle Application Server Uses Instance Names
Instance names are important because Oracle Application Server uses them to uniquely identify instances. This means that if you install multiple Oracle Application Server instances on the same computer, you must give them different names.
When you administer Oracle Application Server using Oracle Enterprise Manager 10g Application Server Control (or Application Server Control for short), the instance name appears on the screens. You can click the instance name to see details about the instance, such as the components that are installed in that instance, if the components are running or stopped, and the log files for the components. The Application Server Control is a browser-based administration tool for Oracle Application Server. See the Oracle Application Server Administrator's Guide for details about this administration tool.
The Oracle home name is used in the following ways:
OPMN runs as a Windows service. When naming this service, the installer inserts the Oracle home name in the service name using the following format:
Oracle-<InstanceName>ProcessManager
For example: if you use the instance name "WebCenter", the process management service will be called WebCenter-Oc4jProcessManager.
The instance name also appears in menu items in the Start menu for starting and stopping components in the associated instance:
Start > Programs > Oracle - instanceName > Oracle Process Manager > Start Oracle Process Manager
Start > Programs > Oracle - instanceName > Oracle Process Manager > Stop Oracle Process Manager
If you select one of the following installation types, the installer prompts you to specify the password for the oc4jadmin user:
Basic Installation
Advanced Installation: Oracle WebCenter Framework with Oracle HTTP Server
Advanced Installation: Oracle Content Database
Advanced Installation: Oracle WebCenter Framework
The oc4jadmin user is the administrative user for Oracle Application Server instances. To manage Oracle Application Server instances using Application Server Control, you log in as oc4jadmin.
On a computer, you can install multiple Oracle Application Server instances, each with its own unique instance name, but the name of the administrative user is oc4jadmin for all instances. The password for the oc4jadmin user can be different for each instance.
Note:
You cannot log in to the Oracle Content DB application as theoc4jadmin user. See Oracle Content Database for Oracle WebCenter Suite Administrator's Guide for information about how to log in to the Oracle Content DB application.Password for the oc4jadmin User
The password for the oc4jadmin user has these restrictions:
The minimum length is 5 characters.
The maximum length is 30 characters.
At least one of the characters must be a number.
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 Database 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.
Note:
When entering your password, check that the state of the Caps Lock key is what you want it to be. Passwords are case-sensitive.You must remember the password because you need to enter it to perform the following task:
When you log on to Application Server Control to manage Oracle Application Server, you log on as the oc4jadmin user.
If you forget the password, you can reset it. See the Oracle Application Server Administrator's Guide for details.
Note:
If you intend to register your installation with Oracle Internet Directory after you finish installing, the password for theoc4jadmin user must conform to Oracle Internet Directory's password policy. Check with your Oracle Internet Directory administrator to verify the password policy.The installer writes files to the following directories:
Table 3-1 Directories Where the Installer Writes Files
| Directory | Description |
|---|---|
|
Oracle home directory |
This directory contains Oracle Application Server files. You specify this directory when you install Oracle Application Server. |
|
( |
The installer uses the inventory directory to keep track of which Oracle products are installed on the computer. The inventory directory is created when you install the first Oracle product on the computer. In subsequent installations, the installer uses the same inventory directory. |
|
The installer writes files needed only during installation to a "temporary" directory. The "temporary" directory is specified by the TEMP variable. See Section 2.7.4, "TEMP" for details. |
Additionally, the installer also creates entries in the Windows registry.
Java Access Bridge enables assistive technologies, such as JAWS screen reader, to read Java applications running on the Windows platform. Assistive technologies can read Java-based interfaces, such as Oracle Universal Installer and Oracle Enterprise Manager 10g Application Server Control.
Your Oracle Application Server installation media contain the Java Runtime Environment (JRE) 1.4.2, which Oracle Universal Installer uses during installation. The JRE enables use of Java Access Bridge during installation.
To set up Java Access Bridge with JRE 1.4.2, run the following batch file on Oracle installation media. If Java Access Bridge is already running on your system, you must turn off the assistive technology prior to running this batch file.
DRIVE_LETTER:\install\access_setup.bat
After the batch file has run, restart your assistive technology program.
For information on making Enterprise Manager accessible following installation, see "Enabling Enterprise Manager Accessibility Mode" in Oracle Application Server Administrator's Guide.
Instances that are added to OracleAS Clusters are subject to the following operating system restrictions:
Instances in an OracleAS Cluster must be of the same installation type and version and reside on a like operating system (Solaris, Linux, and HP-UX are like operating systems).
You can obtain Oracle products from Oracle E-Delivery at http://edelivery.oracle.com/. Oracle products are distributed as "E-Packs". An E-Pack is an electronic version of the software that is also available to Oracle Customers on CD-ROM or DVD-ROM.
This section includes the following topics:
Refer to the CD/Media Pack description or the list of products that you purchased on your Oracle Ordering Document. Then, view the License List to help you decide which Product Pack you need to select in order to search for the appropriate E-Pack(s) to download. Prior to downloading, verify that the product you are looking for is in the License and Options section of the E-Pack README. Oracle recommends that you print the README for reference.
Refer to the README link that is on each E-Pack Download page. In addition to listing the licensable products and options contained in the pack, the README lists downloadable files that are required to run each product and which downloadable files are optional. Oracle recommends that you print the README for reference.
In addition to having the required disk space necessary to install and run your Oracle software, you'll need to have sufficient disk space to download all the required software files and have enough disk space to extract them.
After extracting the software from the Zip files, you can burn them onto CD-ROM and install from them, or install from your computer's hard drive.
All Oracle E-Delivery files have been archived using Info-ZIP's highly portable Zip utility. After downloading one or more of the archives, you will need the UnZip utility or the WinZip utility to extract the files.You must unzip the archive on the platform for which it was intended. For example, if you download the file for the Solaris Operating System (SPARC) version of Oracle Application Server, you must unzip the file on a Solaris Operating System (SPARC) computer. If you unzip the file on a Windows computer, and then move the stage area to a Solaris Operating System (SPARC) machine, the stage area files will be corrupted because Windows will not preserve the case sensitivity or the permission bits of UNIX file names.
Verify that the file size of your downloaded file matches the file size displayed on E-Delivery. Unzip each Zip file to its own temporary directory. For example, create a directory structure called oraAS10g on your hard drive:
c:\oraAS10g
Then create a new directory for each Zip file you downloaded:
c:\oraAS10g\Disk1 c:\oraAS10g\Disk2
If you plan to burn the files on a CD-ROM, create a separate CD-ROM from the contents of each directory. Do not burn a CD-ROM containing the Zip file itself; you need the unzipped contents of the Zip files to do the installation. When you burn the files to CD-ROM, the contents of each disc must be at the root of the CD image.
To install from CD-ROM or from your hard drive, see Section 3.9, "Starting theOracle 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:
CD-ROM users: Double-click setup.exe.
DVD-ROM users: Double-click setup.exe in the application_server directory.
This launches Oracle Universal Installer, through which you install Oracle Application Server.
