Oracle® Application Server Administrator's Guide 10g (10.1.4.0.1) Part Number B28185-01 |
|
|
View PDF |
This chapter describes tasks that you can take to get started managing Oracle Application Server after installation.
It contains the following topics:
When you installed Oracle Application Server, you were logged in to your operating system as a particular user. You should always log in as this user to manage your installation because this user has permission to view and modify the files in your installation's Oracle home.
To use Oracle Application Server, you must 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
Environment Variable | Value |
---|---|
Beginning with Oracle Application Server 10g, very few tools require the DISPLAY variable. Only a few tools, such as |
|
On Solaris, make sure the value contains the following directory: $ORACLE_HOME/lib32 On Linux, make sure the value contains the following directory: $ORACLE_HOME/lib On HP-UX, make sure the value contains the following directory: $ORACLE_HOME/lib On IBM AIX, make sure this environment variable is not set. |
|
Make sure the value contains the following directory: $ORACLE_HOME/lib |
|
If the calling application is a 32-bit application, make sure the value contains the following directory: $ORACLE_HOME/lib32 If the calling application is a 64-bit application, make sure the value contains the following directory: $ORACLE_HOME/lib |
|
Make sure the value contains the following directory: $ORACLE_HOME/lib32 |
|
Set to the full path of the installation's Oracle home |
|
(Infrastructure installations only) |
Set to the OracleAS Metadata Repository SID you supplied during installation. The default is |
Make sure the value contains the following directories, which contain basic commands used by all installations: $ORACLE_HOME/bin $ORACLE_HOME/dcm/bin $ORACLE_HOME/opmn/bin When you start to work with specific components, you may want to add additional directories to your path, as recommended by the component documentation. |
Table 1-2 shows the environment variables for Windows.
Table 1-2 Oracle Application Server Environment Variables for Windows
Environment Variable | Value |
---|---|
Set to the full path of the installation's Oracle home. The value is automatically set by Oracle Universal Installer. |
|
(Infrastructure installations only) |
Set to the OracleAS Metadata Repository SID you supplied during installation. The default is |
Set to your temp directory, for example, |
|
Set to your temp directory, for example, |
Best Practices for Multiple Installations on a UNIX Host
If you have multiple installations of Oracle Application Server on a UNIX host, it is very important to completely set your environment when managing a particular installation.
Some Oracle Application Server commands use the ORACLE_HOME environment variable to determine which installation to operate on, and some use the directory location of the command. It is, therefore, not sufficient to simply reset your environment variables or cd
to a different Oracle home as you move between installations. You must fully change to the new installation as follows:
Log in as the user who installed the application server instance that you want to work on.
On UNIX hosts, you may also use the su
command to switch to the user, but be sure to use the dash (-
) option so your environment is set the same as it would have been had you actually logged in as that user.
su - user
Set the correct environment variables for the installation, as described in Table 1-1.
Execute commands in the Oracle home of the correct installation.
Multiple Installations by the Same User If you installed multiple installations as the same user, make sure that you are in the correct Oracle home and have the correct environment variables set when working on a particular installation. You may want to set up some scripts to make it easy to change from one installation to another.
The Oracle Application Server Welcome Page is a great starting point for managing your application server. It includes the following:
Information about the components included in the release
A link to Release Notes
A link to details about New Features in Oracle Application Server 10g (10.1.4.0.1)
A link to the Oracle Enterprise Manager 10g Application Server Control Console—a Web-based tool for managing Oracle Application Server
A link to the Oracle Application Server 10g (10.1.4.0.1) documentation library
Figure 1-1 shows part of the Oracle Application Server Welcome Page.
Figure 1-1 Oracle Application Server Welcome Page
Accessing the Welcome Page
You can locate the URL for accessing the Welcome Page on the End of Installation Screen text, which is in the following file:
(UNIX) ORACLE_HOME/install/setupinfo.txt (Windows) ORACLE_HOME\install\setupinfo.txt
To view the Welcome Page, connect to it using the HTTP listener port on your installation. For example:
http://hostname.domain:port
The default port is 7777.
Tip If you cannot access the Welcome Page, try the following:
Check setupinfo.txt
and make sure you are using the correct URL (hostname and port number).
Try restarting Oracle HTTP Server:
(UNIX) ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=HTTP_Server (UNIX) ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=HTTP_Server (Windows) ORACLE_HOME\opmn\bin\opmnctl stopproc ias-component=HTTP_Server (Windows) ORACLE_HOME\opmn\bin\opmnctl startproc ias-component=HTTP_Server
During installation, Oracle Application Server assigned port numbers to various components and services. It is important to check these port numbers for two reasons:
You need to know these port numbers in order to start managing your application server.
Oracle Application Server takes several measures to ensure that port number assignments are unique. However, it is possible that a port assignment could conflict with a non-Oracle Application Server process on your host that was not running during the installation. If you determine there is a conflict, stop the non-Oracle Application Server process and continue with the tasks in this chapter. Once you have completed the tasks in this chapter and have verified that your installation is running properly, you can consider changing Oracle Application Server port numbers.
You can find the complete list of port numbers in:
(UNIX) ORACLE_HOME/install/portlist.ini (Windows) ORACLE_HOME\install\portlist.ini
Example 1-1 shows a sample of this file from an Infrastructure installation on Windows.
Example 1-1 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 = 7779 Oracle HTTP Server Listen port = 7779 Oracle HTTP Server SSL port = 4443 Oracle HTTP Server Listen (SSL) port = 4443 Oracle Notification Server Request port = 6005 Oracle Notification Server Local port = 6102 Oracle Notification Server Remote port = 6202 ASG port = 7892 Java Object Cache port = 7002 Oracle HTTP Server Diagnostic port = 7202 Log Loader port = 44001 DCM Discovery port = 7101 Oracle Management Agent Port = 18121 Application Server Control RMI port = 18141 Application Server Control port = 18101 Oracle Internet Directory port = 389 Oracle Internet Directory (SSL) port = 636 Enterprise Manager Console HTTP Port (orcl1014) = 5500 Enterprise Manager Agent Port (orcl1014) = 1830
Note the following about portlist.ini
:
You should leave the port numbers as they are until you have completed the tasks in this chapter and confirmed that all of your components are running properly. Then, you can consider changing port numbers, as described in Chapter 4. Note that some port numbers cannot be changed, and some require additional steps for updating other components.
The portlist.ini
file contains port numbers for components you did not select during installation 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. See Section 7.1, "Configuring Additional Components After Installation" for information.
The portlist.ini
file contains the port numbers that were assigned during installation and is very useful for getting started. However, it is not updated if you modify port numbers after installation. Once you start managing the components, you should use the Application Server Control Console Ports property page for viewing port numbers, because it displays the current port numbers.
The portlist.ini
file is not valid after you upgrade Oracle Application Server.
This task provides an introduction to managing components and includes instructions for accessing component administration tools, postinstallation notes about components, and pointers to more information. It contains the following topics:
Many of the following sections refer to specific ports. Review the portlist.ini
file, at the following location, to find the port number for the specific port:
(UNIX) ORACLE_HOME/install/portlist.ini (Windows) ORACLE_HOME\install\portlist.ini
Oracle Process Manager and Notification Server (OPMN) manages and monitors most Oracle Application Server components. It is installed and configured in every middle-tier and OracleAS Infrastructure installation and is essential for running Oracle Application Server.
You can use OPMN to start and stop your application server, monitor components, configure event scripts, and perform many other tasks related to process management. OPMN provides the opmnctl
command. The executable file is located in the following directory:
(UNIX) ORACLE_HOME/opmn/bin (Windows) ORACLE_HOME\opmn\bin
The following command queries the status of the components in your installation:
(UNIX) ORACLE_HOME/opmn/bin/opmnctl status (Windows) ORACLE_HOME\opmn\bin\opmnctl status
Example 1-2 shows sample output from the command on an Infrastructure instance. It displays the component name, process type, operating system process ID (PID), and status of each process.
Example 1-2 Sample Output from opmnctl status Command
Processes in Instance: oraim.myhost.myco.com ------------------+--------------------+--------+--------- ias-component | process-type | pid | status ------------------+--------------------+--------+--------- DSA | DSA | N/A | Down LogLoader | logloaderd | N/A | Down dcm-daemon | dcm-daemon | 4656 | Alive OC4J | OC4J_SECURITY | 2468 | Alive HTTP_Server | HTTP_Server | 3908 | Alive OID | OID | 4364 | Alive
The following commands start and stop OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, and Oracle Internet Directory, on UNIX:
ORACLE_HOME/opmn/bin/opmnctl startall ORACLE_HOME/opmn/bin/opmnctl stopall
On Windows, you can invoke these commands from the Windows Start menu. For example to start all processes, on Windows 2000, select Start, Programs, Oracle Application Server Infrastructure - Oracle_home_name, Start Infrastructure Instance.
See Also:
|
Note that the following two processes are not started after you finish installing Oracle Application Server:
Oracle HTTP Server is installed and configured with every middle-tier and OracleAS Infrastructure installation.
You can access Oracle HTTP Server as follows:
http://hostname.domain:port
In the example, port
is the Oracle HTTP Server Listen port number, which is listed in the portlist.ini
file.
For example:
http://hostname.domain:7777
When you access Oracle HTTP Server, you see the Oracle Application Server Welcome Page. Click the link for log on to Oracle Enterprise Manager 10g Application Server Control to log in to Application Server Control Console. Enter the administrator username (ias_admin
) and password. Then, navigate to the Home page for the instance and click HTTP Server to manage Oracle HTTP Server.
See Also:
|
Oracle Containers for J2EE (OC4J) is a complete Java 2 Enterprise Edition (J2EE) environment.
When you install an Identity Management instance, you get the following OC4J instances, depending on your configuration:
You can use Application Server Control Console to manage OC4J instances. From the Home page for the Oracle Application Server instance, click the OC4J instance.
Table 1-3 describes how to access the administration interfaces for the following Identity Management components:
Oracle Internet Directory: Provides a scalable and highly available LDAPv3 directory service, built on Oracle database technology.
Oracle Identity Federation: Provides standards-based, multi-protocol, and cross-domain single sign-on.
Oracle Application Server Single Sign-On: Provides single sign-on access to Oracle and third-party Web applications.
Oracle Delegated Administration Services: Provides trusted proxy-based administration of directory information by users and application administrators.
Oracle Directory Integration Platform: Provides directory synchronization as well as provisioning tasks in a directory-centric environment.
Oracle Application Server Certificate Authority: Provides support for issuing, revoking, renewing, and publishing X.509v3 certificates to support PKI-based strong authentication methods.
Table 1-3 Accessing Identity Management Components
Component | Command or URL |
---|---|
On UNIX, use the following command: $ORACLE_HOME/bin/oidadmin
On Windows, select Start, Programs, Oracle Application Server Infrastructure - Oracle_Home, Integrated Management Tools, Oracle Directory Manager. |
|
http://host:port/fedadmin In the example, port is the Oracle HTTP Server Listen port number. Log in as |
|
http://host:port/pls/orasso In the example, port is the Oracle HTTP Server Listen port number. Log in as |
|
http://host:port/oiddas In the example, port is the Oracle HTTP Server Listen port number. Log in as |
|
On UNIX, use the following command: $ORACLE_HOME/bin/dipassistant/gui On Windows, select Start, Programs, Oracle Application Server Infrastructure - Oracle_Home, Integrated Management Tools, Oracle Directory Integration Server Administration. |
|
http://host:port/oca/admin
In the example, port is the Oracle Application Server Certificate Authority port. Log in as OracleAS Certificate Authority Administrator using the password supplied during installation. |
During installation, SSL is not configured for most components. If you would like to enable SSL, refer to Part IV, "Secure Sockets Layer (SSL)".