Oracle® Application Server Quick Administration Guide
10g Release 2 (10.1.2) Part No. B14126-01 |
|
![]() Previous |
![]() Next |
This chapter describes the tasks that you need to perform after installing Oracle Application Server. It contains the following topics:
Log in as the user who installed Oracle Application Server. In order to use Oracle Application Server, you should set environment variables, as shown in the following tables:
Table 1-1, "Oracle Application Server Environment Variables for UNIX"
Table 1-2, "Oracle Application Server Environment Variables for Windows"
Table 1-1 Oracle Application Server Environment Variables for UNIX
Table 1-2 Oracle Application Server Environment Variables for Windows
Best Practices for Multiple Installations on a UNIX Host
Some Oracle Application Server commands use the ORACLE_HOME
environment variable to determine which installation to operate on, whereas others use the directory location of the command. Therefore, it is not sufficient to simply reset your environment variables or cd
into a different Oracle home to move between installations. If you want to use an installation made by a different user, then you must log in as that user and then set the environment variables, as described in Table 1-1.
Note: You can also use thesu - command to switch to the user. For example, su - username .
|
If you have installed multiple installations as the same user, then ensure that you are in the correct Oracle home and have set the correct environment variables when working on a particular installation.
The Oracle Application Server Welcome page is a quick access point to manage your application server as shown in Figure 1-1.
Accessing the Welcome Page
Locate the URL for accessing the Welcome page on the End of Installation Screen text, which is stored in the ORACLE_HOME/install/setupinfo.txt
file.
If you cannot access the Welcome Page, then perform the following steps:
Check setupinfo.txt
to ensure you are using the correct URL.
Restart Oracle HTTP Server by using the following commands:
opmnctl stopproc ias-component=HTTP_Server opmnctl startproc ias-component=HTTP_Server
If OracleAS Web Cache is configured, then restart it using the following commands:
opmnctl stopproc ias-component=WebCache opmnctl startproc ias-component=WebCache
During installation, Oracle Application Server assigns port numbers to various components and services. Check these port numbers to manage your application server and to ensure that a port number assignment doesn't conflict with a non-Oracle Application Server process.
See Also: Chapter 4, "Changing the HTTP Port and Listener Settings" for information about changing port numbers |
Every component and service has an allotted port range. Oracle Application Server first checks the lowest port number in the port range for a component. If the port number is used by another Oracle Application Server installation on the host, or is used by a currently running process or is listed in the /etc/services
file (UNIX only), then Oracle Application Server moves to the next highest port in the allotted port range and continues checking until it finds a free port.
You can find the complete list of port numbers in the ORACLE_HOME/install/portlist.ini
file. Example 1-1 displays a sample copy of the portlist.ini
file. Another file that displays two important ports, the Application Server Control Console port and the HTTP Server port is the ORACLE_HOME/Apache/Apache/setinfo.txt
file.
Example 1-1 A Sample portlist.ini File
;OracleAS Components reserve the following ports at install time. ;As a postinstallation step, you can reconfigure a component to use a different port. ;Those changes will not be visible in this file. [System] Host Name = host1.mycompany.com [Ports] Oracle HTTP Server port = 7777 Oracle HTTP Server Listen port = 7778 Oracle HTTP Server SSL port = 4443 Oracle HTTP Server Listen (SSL) port = 4444 Oracle HTTP Server Diagnostic port = 7200 Application Server Control RMI port = 1850 Oracle Notification Server Request port = 6003 Oracle Notification Server Local port = 6100 Oracle Notification Server Remote port = 6200 Log Loader port = 44000 Java Object Cache port = 7000 DCM Discovery port = 7101 Application Server Control port = 1810 Enterprise Manager Agent port = 1830 Web Cache HTTP Listen port = 7777 Web Cache HTTP Listen (SSL) port = 4443 Web Cache Administration port = 4000 Web Cache Invalidation port = 4001 Web Cache Statistics port = 4002
The portlist.ini
file contains port numbers for components that are not installed, because Oracle Application Server reserves ports for all components during installation, even those that were not configured. These port numbers will be used if you configure components after installation.
Note: Theportlist.ini file is not updated if you modify port numbers after installation. Once you start managing the application server, use the Application Server Control Console Ports Page for viewing port numbers, because it displays the current port numbers. View the Ports Page by clicking the ports link on the Application Server home page. It also contains links to pages that allow you to change port numbers.
|
This section provides an introduction to managing components. It includes instructions for accessing component administration tools and post-installation notes about components. Components are installed according to the topology selected.
See Also: Oracle Application Server 10g Installation Guide |
Some components are installed by default for every installation. These include the following:
OPMN manages and monitors most Oracle Application Server components. It is installed and configured in every Middle Tier and Infrastructure installation and is essential for running Oracle Application Server. Use OPMN to start and stop your application server, monitor components, and configure event scripts.
DCM allows you to manage configuration information for application server instances, OracleAS Clusters, Oracle HTTP Server, Oracle Application Server Containers for J2EE (OC4J), Oracle Application Server Java Authentication and Authorization Service (JAZN), and OPMN. You can use DCM to save and restore configuration information, deploy applications, and manage clusters.
DCM is installed and configured with every Middle Tier and Infrastructure installation. All DCM installations use a DCM repository. There are two types of DCM repositories:
Database: This repository is stored in OracleAS Metadata Repository of the DCM
schema. It is used by Portal and Wireless, and Business Intelligence installations.
File-based: This repository is stored in the filesystem of your Oracle home.
J2EE and Web Cache installations use the database repository, if you choose Managed OracleAS Clusters during installation. If you chose File-based clusters, then the installations use the File-based repository.
During installation, DCM creates a copy of your initial configuration with the dcmctl saveInstance
command. If you wish to return to the initial configuration, then you can use the dcmctl restoreInstance
command.
Oracle HTTP Server is installed and configured with every Middle Tier and Infrastructure installation. You can access Oracle HTTP Server at http://hostname.domain:port
, where port
is the Oracle HTTP Server Listener port number in the portlist.ini
file.
Depending on the installation type you have chosen, some components may be installed. Table 1-3 provides a brief description of each component as well as details on how to access it.
Table 1-3 Accessing Optional Components
Use the ias_admin
password to log in to the Oracle Application Server Control Console. You can change the ias_admin
user password in the following ways:
Using the emctl Command-line Tool
Caution: If you use Infrastructure Services, then you must adhere to the Oracle Internet Directory password policy when setting theias_admin password. For more information, refer to the Oracle Internet Directory Administrator's Guide
|
To change the ias_admin
user password:
Navigate to the Application Server home page and select Preferences. Then, click Change Password. The Change Password page is displayed.
Change the password, and click OK to reset the password for the current instance.
To change the ias_admin
user password:
Enter the following command in the Oracle home of your Oracle Application Server installation:
ORACLE_HOME/bin/emctl set password
old_passwordnew_password
Restart the Oracle Application Server Control Console.
ORACLE_HOME/bin/emctl stop iasconsole
ORACLE_HOME/bin/emctl start iasconsole