| Oracle® Application Server Installation Guide 10g Release 2 (10.1.2) for hp Tru64 UNIX B25859-01 |
|
 Previous |
 Next |
| Oracle® Application Server Installation Guide 10g Release 2 (10.1.2) for hp Tru64 UNIX B25859-01 |
|
Previous |
Next |
Table 7-1 Contents of This Chapter
When you install an Oracle Application Server middle tier, you select which type of middle tier you want. Oracle Application Server has these types of middle tiers:
J2EE and Web Cache
Portal and Wireless
Forms and Reports
Middle tiers provide components for deploying and running applications. The different types of middle tiers provide different components (refer to Section 7.2, "Components in the Middle Tier").
Middle Tiers and Infrastructure
The Portal and Wireless and the Forms and Reports middle tiers require an OracleAS Infrastructure, because components in these middle tiers need to access their schemas in the OracleAS Metadata Repository.
The J2EE and Web Cache type requires some infrastructure components only if you select the Database-Based Farm and/or the Oracle Identity Management Access options. If you do not select these options during the J2EE and Web Cache middle-tier installation, then you do not need an OracleAS Infrastructure. Refer to Section 7.4, "Configuration Options for the J2EE and Web Cache Middle Tier" for details.
Table 7-2 shows the components that are installed for each type of middle tier.
Note that the components in the smaller middle-tier types are a subset of the larger middle-tier types: the bigger types contain all the components from the smaller types:
The J2EE and Web Cache type is the smallest type.
The Portal and Wireless type contains all the components in the J2EE and Web Cache type plus components specific to the Portal and Wireless type.
The Forms and Reports type contains all middle-tier components.
Table 7-2 Components in the Middle Tier
You deploy your applications on middle-tier instances. Select the middle-tier type that provides the components required by your applications.
If you know what components you will be using in your applications, you can choose the appropriate middle-tier type. For example, if you need portal functionality, then you would install the Portal and Wireless type. You can also install the Forms and Reports type, because it includes the OracleAS Portal component.
If you do not know what you want, but you have the disk space, you can install the Forms and Reports type. This ensures that you have all the components. If you do not have the disk space, you can install a smaller middle-tier type, and later expand it to a larger type if necessary. For example, you can expand a J2EE and Web Cache middle tier to a Forms and Reports middle tier. Refer to Section 7.14, "Expanding a MiddleTier" for details.
Table 7-3 lists some features and appropriate components:
Table 7-3 Mapping Features to Components
| If You Need this Feature: | Select a Middle-tier Type that Provides this Component: |
|---|---|
|
J2EE (for developing JavaServer Pages, servlets, and Enterprise JavaBeans applications) |
Oracle Application Server Containers for J2EE (OC4J) |
|
Web services |
OC4J |
|
UDDI |
OracleAS Portal UDDI requires the Portal and Wireless (or the Forms and Reports) middle-tier type because UDDI depends on OC4J for application deployment, OracleAS Metadata Repository for storing various UDDI data structures, and Oracle Internet Directory for user and group management. The J2EE and Web Cache installation type does not require a OracleAS Metadata Repository or Oracle Internet Directory. |
|
Oracle Ultra Search |
OracleAS Portal Note that you must select OracleAS Portal to create and configure the Oracle Ultra Search instance. If you do not select OracleAS Portal, you cannot create and configure the Oracle Ultra Search instance after installation using the Application Server Control. |
|
Portals |
OracleAS Portal |
|
Reports providers (which you can use with OracleAS Portal) |
OracleAS Reports Services |
|
PL/SQL applications |
Oracle HTTP Server |
|
Delivery to mobile devices such as cell phones and PDAs |
OracleAS Wireless |
|
This middle-tier component enables inventory management by processing information from sensors such as radio frequency ID (RFID) devices, laser diodes, and temperature sensors. For information on managing Oracle Sensor Edge Server, refer to Oracle Application Server Wireless Administrator's Guide. For information on developing Oracle Sensor Edge Server components, refer to Oracle Application Server Wireless Developer's Guide. |
OracleAS Wireless |
|
Data mining |
OracleAS Personalization |
|
Reports |
OracleAS Reports Services |
|
Forms |
OracleAS Forms Services |
If you install the J2EE and Web Cache middle tier, the Select Configuration Options screen displays the options listed in Table 7-4.
Some of these options require certain OracleAS Infrastructure components, as listed in the table. You need to install the required infrastructure components before you can install the J2EE and Web Cache middle tier with these options.
Table 7-4 Options in the Select Configuration Options Screen for the J2EE and Web Cache Middle Tier
| Option | Description and Requirements |
|---|---|
|
Select this option to make this J2EE and Web Cache instance part of a farm. Refer to Section 7.4.1, "What Is a Farm?" and Section 7.4.2, "What Is an OracleAS Cluster?" if you need information on farms and clusters. If you select this option, the installer displays the Select Repository Type screen, in which you select whether you want to create a new file-based repository, join an existing file-based repository, or join a database-based repository.
|
|
|
Select this option if your applications need Oracle Identity Management services such as OracleAS Single Sign-On and Oracle Internet Directory. This option requires the following components to be previously installed: Oracle Internet Directory, OracleAS Single Sign-On, and OracleAS Metadata Repository. You can install these components by installing the OracleAS Infrastructure. Additionally, the OracleAS Metadata Repository must be registered with the Oracle Internet Directory. Refer to Section 6.10, "Registration of OracleAS Metadata Repository in Oracle Internet Directory and Password Randomization". |
|
|
Select this option to install and configure OracleAS Web Cache. No previously installed components are required. |
A farm is a collection of one or more instances that share the same metadata repository. When instances belong to a farm, you can manage them as a group and you can also cluster them.
Oracle Application Server can store repository information in a database ("database-based repository") or file system ("file-based repository"). Repository information includes things such as the list of instances that belong to a farm, whether or not the instances are clustered, and configuration information for clusters.
For a file-based repository, the repository information is stored with a specific instance. This instance is called the "repository host".
For a database-based repository, the repository information is stored in the OracleAS Metadata Repository.
You can set a J2EE and Web Cache instance to belong to a farm during or after installation. If you are unsure during installation, you can install the instance as a standalone instance (that is, not belonging to a farm). After installation, if you so desire, you can associate the instance with a farm. Conversely, you can install an instance as part of a farm and after installation, you can convert the instance to a standalone instance.
For details about farms, refer to Distributed Configuration Management Administrator's Guide and Oracle Application Server High Availability Guide.
You can cluster instances that belong to a farm. All the instances in a cluster have the same configuration. Any instance in a cluster can handle requests directed to any cluster member.
The installer does not cluster instances for you. You have to do this after installation.
For details about OracleAS Clusters, refer to Distributed Configuration Management Administrator's Guide and Oracle Application Server High Availability Guide.
If you are installing J2EE and Web Cache instances that use the OracleAS File-based Repository feature, and the instances are on different sides of a firewall, then you need to ensure that these instances can communicate with each other across the firewall.
A scenario of when you would install the instances in this manner is in the "myJ2EECompany.com" architecture. In this architecture, you install OracleAS Web Cache in the Web tier, and OC4J in the Application tier, and these tiers are separated by a firewall. The myJ2EECompany.com architecture is described in detail in the Oracle Application Server Enterprise Deployment Guide.
To enable instances to communicate with each other across the firewall, you need to open up some ports in the firewall after the first installation. For details, refer to Chapter 3, "Configuring the Application Infrastructure for myJ2EECompany.com", in Oracle Application Server Enterprise Deployment Guide.
If you install the J2EE and Web Cache middle tier with the OracleAS Database-Based Farm Repository option selected, but without the Oracle Identity Management Access option, the installer prompts you to enter the password for the DCM schema in the OracleAS Metadata Repository.
This password is generated randomly. You have two choices:
Change the Random Password
If you did not register the OracleAS Metadata Repository with an Oracle Internet Directory, you need to change the random password to a known value. You can do this using the "alter user" SQL command in SQL*Plus. The following example changes the password to "newpassword":
prompt> $ORACLE_HOME/bin/sqlplus "sys/sys_password as sysdba" SQL> alter user dcm identified by newpassword;
You need to log in as the sys user to change the password.
Determine the Random Password Using Oracle Internet Directory
|
Note: This procedure can only be performed by the Oracle Internet Directory superuser (cn=orcladmin). |
If you did register the OracleAS Metadata Repository with an Oracle Internet Directory, you can use the Oracle Directory Manager to determine the random password.
However, if you do have an Oracle Internet Directory and the OracleAS Metadata Repository is registered with it, it might make more sense to select both OracleAS Database-Based Farm Repository and Oracle Identity Management Access in the Select Configuration Options screen. If you select both, the installer does not prompt you to enter the DCM password.
To determine the random password in Oracle Internet Directory:
Start up Oracle Directory Manager.
prompt> $ORACLE_HOME/bin/oidadmin
Log in to Oracle Internet Directory as the cn=orcladmin superuser.
Expand the structure as shown in Figure 7-1. On the left side, select OrclResourceName=DCM, as shown. The password for the DCM schema is shown in the orclpasswordattribute field on the right side.
Figure 7-1 Viewing the DCM Schema's Password in Oracle Internet Directory
During installation, you might need to know port numbers used by certain components. For example, when you install Oracle Application Server middle tiers, the installer prompts for the Oracle Internet Directory port.
You can get a list of port numbers in the following ways:
Use Oracle Enterprise Manager 10g Application Server Control.
Click the Ports link on the Enterprise Manager home page. This takes you to a page that lists all ports in use and the suggested port ranges for different components.
Look in the ORACLE_HOME/install/portlist.ini file. ORACLE_HOME refers to the directory containing the Oracle Application Server installation.
Note that if you change a component's port number after installation, the portlist.ini file is not updated. The portlist.ini file is not updated after installation.
If you plan to install middle tiers against an Oracle Internet Directory that was upgraded from version 9.2.0.x to the current release, make sure you followed the steps on upgrading Oracle Internet Directory 9.2.0.x as documented in the Oracle Application Server Upgrade and Compatibility Guide. The instructions are in the "Upgrading the Oracle Identity Management Services" chapter.
Perform this procedure to install a J2EE and Web Cache instance that does not require an infrastructure.
Table 7-5 Steps for Installing J2EE and Web Cache
| Screen | Action | |
|---|---|---|
|
1. |
-- |
Start up the installer and complete the first few screens. Refer to Section 7.16, "Install Fragment: The First Few Screens for Installing Middle Tiers" for details. Note:
Click Next. |
|
2. |
Select Configuration Options |
Select OracleAS Web Cache. Do not select Identity Management Access because this option requires Oracle Internet Directory and OracleAS Single Sign-On. Do not select OracleAS Farm Repository. Click Next. |
|
2. |
Specify Port Configuration Options |
If you want to use default ports for the components, select Automatic. If you do not want to use the default ports, and you have created a Click Next. |
|
3. |
Specify Instance Name and ias_admin Password |
Instance Name: Enter a name for this instance. Instance names can contain alphanumeric characters and the _ (underscore) character. If you have more than one Oracle Application Server instance on a computer, the instance names must be unique. Refer to Section 5.9, "Oracle Application Server Instances and Instance Names" for instance name details. Example: ias_admin Password and Confirm Password: Set the password for the ias_admin user. This is the administrative user for the instance. Refer to Section 5.10, "The ias_admin User and Restrictions on its Password" for restrictions on the password. Example: Click Next. |
|
4. |
-- |
Finish the installation. Refer to Section 7.17, "Install Fragment: The Last Few Screens of the Installation". |
Perform this procedure to install a J2EE and Web Cache middle tier in a database-based farm repository and with Oracle Identity Management Access.
Prerequisite: OracleAS Infrastructure
Table 7-6 Steps for Installing J2EE and Web Cache in a Database-Based Farm Repository and with Oracle Identity Management Access
| Screen | Action | |
|---|---|---|
|
1. |
-- |
Start up the installer and complete the first few screens. Refer to Section 7.16, "Install Fragment: The First Few Screens for Installing Middle Tiers" for details. Note:
|
|
2. |
Select Configuration Options |
Select OracleAS Web Cache. Select Identity Management Access. Select OracleAS Farm Repository. Click Next. |
|
3. |
Specify Port Configuration Options |
If you want to use default ports for the components, select Automatic. If you do not want to use the default ports, and you have created a Click Next. |
|
4. |
Select Repository Type |
Select Join an Existing OracleAS Database-based Farm. Click Next. |
|
5. |
Register with Oracle Internet Directory |
Host: Enter the name of the computer where Oracle Internet Directory is running. Port: Enter the port at which Oracle Internet Directory is listening. If you do not know the port number, refer to Section 7.6, "How to Determine Port Numbers Used by Components". Use Only SSL Connections with this Oracle Internet Directory: Select this option if you want Oracle Application Server components to use only SSL to connect to Oracle Internet Directory. Click Next. |
|
6. |
Specify Login for Oracle Internet Directory |
Username: Enter the username to log in to Oracle Internet Directory. You must log in as a user who belongs to the necessary groups in Oracle Internet Directory. Which groups are necessary depends on which components you are installing. Refer to Section 8.3, "Groups Required to Configure or Deinstall Components" for details. Password: Enter the password for the username. Realm: Enter the realm against which to validate the username. This field appears only if your Oracle Internet Directory has multiple realms. Click Next. |
|
7. |
Select Metadata Repository for OracleAS Cluster |
Select the OracleAS Metadata Repository from the list. Click Next. |
|
8. |
Specify Instance Name and ias_admin Password |
Instance Name: Enter a name for this instance. Instance names can contain alphanumeric characters and the _ (underscore) character. If you have more than one Oracle Application Server instance on a computer, the instance names must be unique. Refer to Section 5.9, "Oracle Application Server Instances and Instance Names" for instance name details. Example: ias_admin Password and Confirm Password: Set the password for the ias_admin user. This is the administrative user for the instance. Refer to Section 5.10, "The ias_admin User and Restrictions on its Password" for restrictions on the password. Example: Click Next. |
|
9. |
-- |
Finish the installation. Refer to Section 7.17, "Install Fragment: The Last Few Screens of the Installation". |
Perform this procedure to install a J2EE and Web Cache middle tier in a database-based farm repository, but without Oracle Identity Management access.
Prerequisite: OracleAS Metadata Repository
Table 7-7 Steps for Installing J2EE and Web Cache in a Database-Based Farm Repository but Without Oracle Identity Management Access
| Screen | Action | |
|---|---|---|
|
1. |
-- |
Start up the installer and complete the first few screens. Refer to Section 7.16, "Install Fragment: The First Few Screens for Installing Middle Tiers" for details. Note:
|
|
2. |
Select Configuration Options |
Select OracleAS Web Cache. Select OracleAS Farm Repository. Deselect Identity Management Access. Click Next. |
|
3. |
Specify Port Configuration Options |
If you want to use default ports for the components, select Automatic. If you do not want to use the default ports, and you have created a Click Next. |
|
4. |
Select Repository Type |
Select Join an Existing OracleAS Database-based Farm. Click Next. |
|
5. |
Specify Metadata Repository for DB-Managed Cluster |
Password: Enter the password for the Hostname and Port: Enter the name of the computer where the database is running, and the port number at which it is listening. Use the format: Service Name: Enter the service name of the database. Note that the service name must include the database domain name. Example: Click Next. |
|
6. |
Specify Instance Name and ias_admin Password |
Instance Name: Enter a name for this instance. Instance names can contain alphanumeric characters and the _ (underscore) character. If you have more than one Oracle Application Server instance on a computer, the instance names must be unique. Refer to Section 5.9, "Oracle Application Server Instances and Instance Names" for instance name details. Example: ias_admin Password and Confirm Password: Set the password for the ias_admin user. This is the administrative user for the instance. Refer to Section 5.10, "The ias_admin User and Restrictions on its Password" for restrictions on the password. Example: Click Next. |
|
7. |
-- |
Finish the installation. Refer to Section 7.17, "Install Fragment: The Last Few Screens of the Installation". |
Perform this procedure to install a J2EE and Web Cache middle tier in a file-based farm repository but without Oracle Identity Management access.
Table 7-8 Steps for Installing J2EE and Web Cache in a File-Based Farm Repository but Without Oracle Identity Management Access
| Screen | Action | |
|---|---|---|
|
1. |
-- |
Start up the installer and complete the first few screens. Refer to Section 7.16, "Install Fragment: The First Few Screens for Installing Middle Tiers" for details. Note:
Click Next. |
|
2. |
Select Configuration Options |
Select OracleAS Web Cache. Select OracleAS Farm Repository. Do not select Identity Management Access because this option requires Oracle Internet Directory and OracleAS Single Sign-On. Click Next. |
|
3. |
Specify Port Configuration Options |
If you want to use default ports for the components, select Automatic. If you do not want to use the default ports, and you have created a Click Next. |
|
4. |
Select Repository Type |
If you want to start a new file-based farm, select Create a New OracleAS File-based Farm for this Instance. If you want this instance to join an existing file-based farm, select Join an Existing OracleAS File-based Farm. The installer will prompt for the location of the existing farm. Click Next. |
|
5. |
Specify File-Based Farm Repository |
Enter the location of the existing file-based farm repository on this screen. This screen appears only if you selected Join an Existing OracleAS File-based Farm in the previous screen. Repository Host: Enter the name of the computer where the existing farm is being hosted. Repository Port: Enter the port number for the repository. You can determine the repository host and port by running the " prompt> ORACLE_HOME/dcm/bin/dcmctl getRepositoryID File-based Repository ID mymachine2.mydomain.com:7102
Click Next. |
|
6. |
Specify Instance Name and ias_admin Password |
Instance Name: Enter a name for this instance. Instance names can contain alphanumeric characters and the _ (underscore) character. If you have more than one Oracle Application Server instance on a computer, the instance names must be unique. Refer to Section 5.9, "Oracle Application Server Instances and Instance Names" for instance name details. Example: ias_admin Password and Confirm Password: Set the password for the ias_admin user. This is the administrative user for the instance. Refer to Section 5.10, "The ias_admin User and Restrictions on its Password" for restrictions on the password. Example: Click Next. |
|
7. |
-- |
Finish the installation. Refer to Section 7.17, "Install Fragment: The Last Few Screens of the Installation". |
Perform this procedure to install a J2EE and Web Cache middle tier in a file-based farm repository and with Oracle Identity Management access.
Prerequisite: Oracle Internet Directory
Table 7-9 Steps for Installing J2EE and Web Cache in a File-Based Farm Repository and with Oracle Identity Management Access
| Screen | Action | |
|---|---|---|
|
1. |
-- |
Start up the installer and complete the first few screens. Refer to Section 7.16, "Install Fragment: The First Few Screens for Installing Middle Tiers" for details. Note:
Click Next. |
|
2. |
Select Configuration Options |
Select OracleAS Web Cache. Select OracleAS Farm Repository. Select Identity Management Access. Click Next. |
|
3. |
Specify Port Configuration Options |
If you want to use default ports for the components, select Automatic. If you do not want to use the default ports, and you have created a Click Next. |
|
4. |
Select Repository Type |
If you want to start a new file-based farm, select Create a New OracleAS File-based Farm for this Instance. If you want this instance to join an existing file-based farm, select Join an Existing OracleAS File-based Farm. The installer will prompt for the location of the existing farm. Click Next. |
|
5. |
Specify File-Based Farm Repository |
Enter the location of the existing file-based farm repository on this screen. This screen appears only if you selected Join an Existing OracleAS File-based Farm in the previous screen. Repository Host: Enter the name of the computer where the existing farm is being hosted. Repository Port: Enter the port number for the repository. You can determine the repository host and port by running the " prompt> ORACLE_HOME/dcm/bin/dcmctl getRepositoryID File-based Repository ID mymachine2.mydomain.com:7102
Click Next. |
|
6. |
Register with Oracle Internet Directory |
Host: Enter the name of the computer where Oracle Internet Directory is running. Port: Enter the port at which Oracle Internet Directory is listening. If you do not know the port number, refer to Section 7.6, "How to Determine Port Numbers Used by Components". Use Only SSL Connections with this Oracle Internet Directory: Select this option if you want Oracle Application Server components to use only SSL to connect to Oracle Internet Directory. Click Next. |
|
7. |
Specify Login for Oracle Internet Directory |
Username: Enter the username to log in to Oracle Internet Directory. You must log in as a user who belongs to the necessary groups in Oracle Internet Directory. Which groups are necessary depends on which components you are installing. Refer to Section 8.3, "Groups Required to Configure or Deinstall Components" for details. Password: Enter the password for the username. Realm: Enter the realm against which to validate the username. This field appears only if your Oracle Internet Directory has multiple realms. Click Next. |
|
8. |
Specify Instance Name and ias_admin Password |
Instance Name: Enter a name for this instance. Instance names can contain alphanumeric characters and the _ (underscore) character. If you have more than one Oracle Application Server instance on a computer, the instance names must be unique. Refer to Section 5.9, "Oracle Application Server Instances and Instance Names" for instance name details. Example: ias_admin Password and Confirm Password: Set the password for the ias_admin user. This is the administrative user for the instance. Refer to Section 5.10, "The ias_admin User and Restrictions on its Password" for restrictions on the password. Example: Click Next. |
|
9. |
-- |
Finish the installation. Refer to Section 7.17, "Install Fragment: The Last Few Screens of the Installation". |
Perform this procedure to install a Portal and Wireless or a Forms and Reports middle tier.
Prerequisite: OracleAS Infrastructure
Table 7-10 Steps for Installing Portal and Wireless or Forms and Reports
| Screen | Action | |
|---|---|---|
|
1. |
-- |
Start up the installer and complete the first few screens. Refer to Section 7.16, "Install Fragment: The First Few Screens for Installing Middle Tiers" for details. Note:
|
|
2. |
Select Configuration Options |
Select the components that you will be using, and click Next. You do not have to select all the components. For Portal and Wireless, the options are:
For Forms and Reports, the options are:
|
|
3. |
Specify Port Configuration Options |
If you want to use default ports for the components, select Automatic. If you do not want to use the default ports, and you have created a Click Next. |
|
4. |
Register with Oracle Internet Directory |
Host: Enter the name of the computer where Oracle Internet Directory is running. Port: Enter the port number at which Oracle Internet Directory is listening. If you do not know the port number, refer to Section 7.6, "How to Determine Port Numbers Used by Components". Use Only SSL Connections with this Oracle Internet Directory: Select this option if you want Oracle Application Server components to use only SSL to connect to Oracle Internet Directory. Click Next. |
|
5. |
Specify Login for Oracle Internet Directory |
Username: Enter the username to use to log in to Oracle Internet Directory. You must log in as a user who belongs to the necessary groups in Oracle Internet Directory. Which groups are necessary depends on which components you are installing. Refer to Section 8.3, "Groups Required to Configure or Deinstall Components" for details. Password: Enter the user's password. Realm: Enter the realm against which to validate the user. This field appears only if your Oracle Internet Directory contains more than one realm. If the Oracle Internet Directory contains only one realm, then the installer validates the user against that realm. Click Next. |
|
6. |
Select OracleAS Metadata Repository |
Repository: Select the OracleAS Metadata Repository that you want to use for this middle-tier instance. The installer will register this instance with the selected OracleAS Metadata Repository. Click Next. |
|
7. |
Provide Outgoing Mail Server Information |
This screen appears only if you selected OracleAS Reports Services in the Select Configuration Options screen. 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. |
|
8. |
Specify Instance Name and ias_admin Password |
Instance Name: Enter a name for this instance. Instance names can contain alphanumeric characters and the _ (underscore) character. If you have more than one Oracle Application Server instance on a computer, the instance names must be unique. Refer to Section 5.9, "Oracle Application Server Instances and Instance Names" for instance name details. Example 1: Example 2: ias_admin Password and Confirm Password: Set the password for the ias_admin user. This is the administrative user for the instance. Refer to Section 5.10, "The ias_admin User and Restrictions on its Password" for restrictions on the password. Example: Click Next. |
|
9. |
-- |
Finish the installation. Refer to Section 7.17, "Install Fragment: The Last Few Screens of the Installation". |
After installing a middle tier and using it, you may decide that you need a component that is in a larger middle tier. For example, you installed a J2EE and Web Cache middle tier, and you realize you need OracleAS Portal.
What you can do is to install the Portal and Wireless type (or the Forms and Reports type) in the same Oracle home as the J2EE and Web Cache instance. The installer installs and configures the additional components in the larger middle tier without changing the configuration of existing components.
You can expand middle tiers in the following ways:
J2EE and Web Cache to Portal and Wireless
J2EE and Web Cache to Forms and Reports
Portal and Wireless to Forms and Reports
Expanding a middle tier is the same as installing a new one, with these differences:
In the Specify File Locations screen, you enter the Oracle home directory of the middle tier you want to expand.
You need the password of the ias_admin user of the middle tier you want to expand.
Instead of the Specify Instance Name and ias_admin Password screen, the installer displays the Specify ias_admin Password screen. In this screen, you enter the existing password for the ias_admin user.
The instance name remains the same.
When the installer prompts you to run root.sh, do not run it.
|
Note: You must configure OracleAS Web Cache before expanding a J2EE and Web Cache instance. If you did not configure OracleAS Web Cache during installation, refer to Oracle Application Server Administrator's Guide for instructions on configuring additional components after installation. |
Remember that the Portal and Wireless and the Forms and Reports middle tiers require OracleAS Infrastructure.
You cannot "shrink" a middle tier: you cannot go from a larger middle tier to a smaller middle tier.
Note that you cannot expand an infrastructure.
Procedure: Expanding a Middle Tier
Perform the following procedure to expand a middle tier:
Table 7-11 Steps for Expanding a Middle Tier
| Screen | Action | |
|---|---|---|
|
1. |
-- |
Stop all processes associated with the middle tier that you want to expand. If you need help on how to stop the processes, refer to Oracle Application Server Administrator's Guide. In particular, be sure that you stop the Application Server Control and DCM before performing the expansion. To stop Application Server Control, run the following command:
prompt> $ORACLE_HOME/bin/emctl stop iasconsole
To stop OracleAS Web Cache (if configured), run the following command:
prompt> $ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=WebCache
To ensure that DCM is stopped, run the following command:
prompt> $ORACLE_HOME/dcm/bin/dcmctl shutdown
|
|
2. |
-- |
Start up the installer and complete the first few screens. Refer to Section 7.16, "Install Fragment: The First Few Screens for Installing Middle Tiers" for details. Note:
|
|
3. |
Select Configuration Options |
Select the components that you need, and click Next. For Portal and Wireless, the options are:
For Forms and Reports, the options are:
|
|
4. |
Specify Port Configuration Options |
If you want to use default ports for the components, select Automatic. If you do not want to use the default ports, and you have created a Click Next. |
|
5. |
Register with Oracle Internet Directory |
Host: Enter the name of the computer where Oracle Internet Directory is running. Port: Enter the port number at which Oracle Internet Directory is listening. If you do not know the port number, refer to Section 7.6, "How to Determine Port Numbers Used by Components". Use Only SSL Connections with this Oracle Internet Directory: Select this option if you want Oracle Application Server components to use only SSL to connect to Oracle Internet Directory. Click Next. |
|
6. |
Specify Login for Oracle Internet Directory |
Username: Enter the username to use to log in to Oracle Internet Directory. You must log in as a user who belongs to the necessary groups in Oracle Internet Directory. Which groups are necessary depends on which components you are installing. Refer to Section 8.3, "Groups Required to Configure or Deinstall Components" for details. Password: Enter the user's password. Realm: Enter the realm against which to validate the user. This field appears only if your Oracle Internet Directory contains more than one realm. If the Oracle Internet Directory contains only one realm, then the installer validates the user against that realm. Click Next. |
|
7. |
Select OracleAS Metadata Repository |
Repository: Select the OracleAS Metadata Repository that you want to use for this middle-tier instance. The installer will register this instance with the selected OracleAS Metadata Repository. Click Next. |
|
8. |
Provide Outgoing Mail Server Information |
This screen appears only if you selected OracleAS Reports Services in the Select Configuration Options screen. 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. |
|
9. |
Specify ias_admin Password |
ias_admin Password: Enter the password for the ias_admin user of the middle tier you are expanding. Click Next. |
|
10. |
-- |
Finish the installation. Refer to Section 7.17, "Install Fragment: The Last Few Screens of the Installation". Note: When the installer prompts you to run |
If you did not shut down DCM when you performed the expansion, you may find that OracleAS Web Cache is not enabled after expanding the middle tier. In this case, perform these steps:
Enable OracleAS Web Cache by changing its status to "enabled" in the file ORACLE_HOME/opmn/conf/opmn.xml:
<ias-component id="WebCache" status="enabled">
Reload OPMN.
prompt> ORACLE_HOME/opmn/bin/opmnctl reload
If you have a middle tier from the 10g (9.0.4) release and you want to upgrade it to a 10g Release 2 (10.1.2) middle tier of the same type (for example, J2EE and Web Cache 10g (9.0.4) middle tier to J2EE and Web Cache 10g Release 2 (10.1.2) middle tier), follow the instructions in the Oracle Application Server Upgrade and Compatibility Guide.
If you want to upgrade a middle tier and expand it at the same time (for example, going from J2EE and Web Cache 10g (9.0.4) to Portal and Wireless 10g Release 2 (10.1.2)), you have to perform two procedures:
Upgrade the middle tier to the same type middle tier in 10g Release 2 (10.1.2). This procedure is documented in the Oracle Application Server Upgrade and Compatibility Guide.
Expand the middle tier in the 10g Release 2 (10.1.2) Oracle home. The previous section, Section 7.14, "Expanding a MiddleTier", has details.
The first few screens of the installer are described here because they are the same for all installations. Most installation procedures in this chapter refer to this section as their starting point.
Table 7-12 First Few Screens of the Middle-tier Installation
| Screen | Action | |
|---|---|---|
|
1. |
-- |
Start the installer. Refer to Section 5.19, "Starting Oracle Universal Installer". |
|
2. |
Welcome |
Click Next. |
|
3. |
Specify Inventory Directory and Credentials |
This screen appears only if this is the first installation of any Oracle product on this computer. Enter the full path of the inventory directory: Enter a full path to the inventory directory. Enter a directory that is different from the Oracle home directory for the product files. Example: Specify operating system group name: Select the operating system group that will have write permission for the inventory directory. Example: Click Next. |
|
4. |
Run |
This screen appears only if this is the first installation of any Oracle product on this computer. Run the After running the script, click Continue. |
|
5. |
Specify File Locations |
Name: Enter a name to identify this Oracle home. The name can consist of alphanumeric and the underscore (_) characters only, and cannot be longer than 128 characters. Example: Destination Path: Enter the full path to the destination directory. This is the Oracle home. If the directory does not exist, the installer creates it. If you want to create the directory beforehand, create it as the Example: Click Next. |
|
6. |
Specify Hardware Cluster Installation Mode |
This screen appears only if the computer is part of a hardware cluster. When you are installing a middle tier, select Local Installation because hardware cluster is not supported for middle tiers. Click Next. |
|
7. |
Select a Product to Install |
Select Oracle Application Server to install a middle tier. If you need to install additional languages, click Product Languages. Refer to Section 5.8, "Installing Additional Languages" for details. Click Next. |
|
8. |
Select Installation Type |
The options displayed on this screen depend on what you selected in the Select a Product to Install screen. If you selected Oracle Application Server (which refers to the Oracle Application Server middle tier), the screen displays:
Click Next. If you get an error message saying that the TMP environment variable is not set, it means that the default temp directory does not have enough space. You can either set the TMP environment variable to point to a different directory or free up enough space in the default temp directory. For details on the |
|
9. |
Confirm Pre-Installation Requirements |
Verify that you meet all the requirements listed on the screen. Click Next. |
Refer to Figure 6-2 for a graphic that summarizes the screen sequence. These screens are the same for installing OracleAS Infrastructure or middle tier.
The last few screens of the installer are described in this section because they are the same for all installations. Most installation procedures in this chapter refer to this section as their end point.
Table 7-13 Last Few Screens in the Installation
| Screen | Action | |
|---|---|---|
|
1. |
Summary |
Verify your selections and click Install. |
|
2. |
Install Progress |
This screen shows the progress of the installation. |
|
3. |
Run |
Note: Do not run the script until you see this dialog.
|
|
4. |
Configuration Assistants |
This screen shows the progress of the configuration assistants. Configuration assistants configure components. |
|
5. |
End of Installation |
Click Exit to quit the installer. |
