1 Getting Started After Installing Oracle Application Server

1.4.1 Getting Started with Oracle Process Manager and Notification Server (OPMN)

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.

OPMN provides the opmnctl command. The executable file is located in the following directory:

(UNIX) ORACLE_HOME/opmn/bin
(Windows) ORACLE_HOME\opmn\bin

To get started with OPMN, use the opmnctl command to query 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. It displays the component name, process type, operating system process ID (PID), and status of each process.

Processes in Instance: mid.myhost.myco.com
------------------+--------------------+--------+---------
ias-component     | process-type       |   pid  | status  
------------------+--------------------+--------+---------
LogLoader         | logloaderd         |   N/A  | Down   
dcm-daemon        | dcm-daemon         |   2787 | Alive 
DSA               | DSA                |   N/A  | Down   
OC4J              | home               |   2964 | Alive 
OC4J              | OC4J_BI_Forms      |   2965 | Alive 
OC4J              | OC4J_Portal        |   2967 | Alive 
WebCache          | WebCache           |   2958 | Alive 
WebCache          | WebCacheAdmin      |   2959 | Alive 
HTTP_Server       | HTTP_Server        |   2961 | Alive 
Discoverer        | ServicesStatus     |   2960 | Alive 
Discoverer        | PreferenceServer   |   2963 | Alive 
wireless          | performance_server |   2985 | Alive 
wireless          | messaging_server   |   2986 | Alive 
wireless          | OC4J_Wireless      |   2987 | Alive  

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. For example, you can use the following commands to 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 > OracleAS 10g - Oracle_home_name > Start Oracle_home.hostname.

Note that the following two processes are not started after you finish installing Oracle Application Server:

• Log Loader: This is a feature that compiles log messages from various log files into a single repository. If you would like to use Log Loader, you can start it after installation.

  
  

  See Also: Chapter 5, especially Section 5.5.1, "Starting and Stopping Log Loader"

  
  

• DSA: This is the OracleAS Guard server. If you are using OracleAS Guard, you can start this after installation.

  
  

  See Also: Oracle Application Server High Availability Guide

  
  

1.4.2 Getting Started with Distributed Configuration Management (DCM)

With Distributed Configuration Management (DCM), you can 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 (JAAS) Provider (JAZN), and OPMN.

DCM is installed and configured with every middle-tier and OracleAS Infrastructure installation. All DCM installations use a DCM repository. There are two types of DCM repositories:

• Database: This repository is stored in the OracleAS Metadata Repository in the DCM schema. This repository type is used by Portal and Wireless, and Business Intelligence and Forms installations. It is the repository for J2EE and Web Cache installations if you chose to join an OracleAS Database Farm during installation.

• File Based: This repository is stored in the file system in your Oracle home. This repository type is used by J2EE and Web Cache installations if you chose to join a File-Based farm during installation.

You can determine the repository type as follows:

(UNIX) ORACLE_HOME/dcm/bin/dcmctl whichFarm 
(Windows) ORACLE_HOME\dcm\bin\dcmctl whichFarm

During installation, DCM created a copy of your initial configuration. If, after you start configuring your application server, you would like to return to the initial configuration, you can use the dcmctl restoreInstance command.

You can use DCM to save and restore configuration information, deploy applications, manage OracleAS Clusters, and much more.

1.4.3 Getting Started with Oracle HTTP 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:7778

When you access Oracle HTTP Server, you see the Oracle Application Server Welcome Page. Click the link for Oracle Application Server Logins to log in to Application Server Control Console. Then, on the Home page, click HTTP Server to manage Oracle HTTP Server.

1.4.4 Getting Started with Oracle Application Server Containers for J2EE (OC4J)

Oracle Application Server Containers for J2EE (OC4J) is a complete Java 2 Enterprise Edition (J2EE) environment.

When you install an instance, you get the following OC4J instances, depending on your configuration:

• home: The default OC4J instance that comes with every middle-tier installation

• OC4J_BI_Forms: Contains servlets that support OracleAS Reports Services, OracleBI Discoverer, and OracleAS Forms Services

• OC4J_Portal: Contains a servlet that supports OracleAS Portal

• OC4J_Security: Supports Identity Management Services

• OC4J_Wireless: Contains a servlet that supports OracleAS Wireless

• oca: Supports OracleAS Certificate Authority

You can use Application Server Control Console to manage OC4J instances.

1.4.5 Getting Started with OracleAS Web Cache

If you configured OracleAS Web Cache during installation, you can access it as follows:

http://hostname.domain:port

In the example, port is the Web Cache HTTP Listen port number as listed in the portlist.ini file.

For example:

http://hostname.domain:7777

When you access OracleAS Web Cache, you will see the Oracle Application Server Welcome Page, which is cached by OracleAS Web Cache. Click the link for Oracle Application Server Logins to log in to Application Server Control Console. Then, on the Home page, click Web Cache to manage OracleAS Web Cache.

Accessing OracleAS Web Cache Manager

In addition to using Application Server Control Console to manage OracleAS Web Cache, as described in Section 2.3, you can use OracleAS Web Cache Manager. OracleAS Web Cache Manager is a graphical user interface tool for configuring and monitoring OracleAS Web Cache.

You can access OracleAS Web Cache Manager by navigating to the following URL:

http://hostname.domain:port/webcacheadmin

In the example, port is the Web Cache HTTP Administration port number listed in the portlist.ini file.

For example:

http://hostname.domain:9400/webcacheadmin

You can log in to OracleAS Web Cache Manager as ias_admin or administrator. The password for both accounts is the ias_admin password you supplied during installation.

1.4.6 Getting Started with OracleAS Portal

If you configured OracleAS Portal during installation, you can access it as follows:

http://hostname.domain:port/pls/portal

In the example, port is the Web Cache HTTP Listen port number listed in the portlist.ini file.

For example:

http://hostname.domain:7777/pls/portal

You can log in as the user portal. If this is the first OracleAS Portal instance to use the OracleAS Metadata Repository, the password is the original ias_admin password you supplied for this middle tier during installation. The original ias_admin password is required, even if you changed the ias_admin password after installation.

1.4.7 Getting Started with OracleAS Wireless

If you configured OracleAS Wireless during installation, you can access it as follows:

http://hostname.domain:port/webtool/login.uix

In the example, port is the Web Cache HTTP Listen port number listed in the portlist.ini file.

You can log in as orcladmin using the orcladmin password.

1.4.8 Getting Started with OracleBI Discoverer

If you configured OracleBI Discoverer during installation, you can access it as follows:

• Discoverer Viewer:

  http://hostname.domain:port/discoverer/viewer
  
  

• Discoverer Plus:

  http://hostname.domain:port/discoverer/plus
  
  

• Discoverer Portlet Provider:

  http://hostname.domain:port/discoverer/portletprovider
  
  

In the example, port is the Web Cache HTTP Listen port number in the portlist.ini file.

Before OracleBI Discoverer end users can start analyzing data, the steps in either or both the following sections must be completed:

• Prepare for Multidimensional Analysis

• Prepare for Relational Analysis

1.4.9 Getting Started with OracleAS Forms Services

If you configured OracleAS Forms Services during installation, you can access it as follows:

http://hostname.domain:port/forms/frmservlet

In the example, port is the Web Cache HTTP Listen port number listed in the portlist.ini file.

1.4.10 Getting Started with OracleAS Reports Services

If you configured OracleAS Reports Services during installation, you can access it as follows:

http://hostname.domain:port/reports/rwservlet/getserverinfo

In the example, port is the Web Cache HTTP Listen port number listed in the portlist.ini file.

You can log in as orcladmin with the orcladmin password.

1.4.11 Getting Started with OracleAS Personalization

Before you use OracleAS Personalization, you must run the OracleAS Personalization Schema Creation Wizard, which creates the required schemas in the Oracle database. Then, you can start managing OracleAS Personalization.

1.4.12 Getting Started with Oracle Application Server Integration Products

For information about getting started with Oracle Application Server Integration components, such as OracleAS Integration B2B, Oracle BPEL Process Manager, and Oracle BPEL Process Analytics, see the Oracle Application Server Integration documentation.

1.4.13 Getting Started with Identity Management Components

Table 1-3 describes how to access Identity Management components.

$ORACLE_HOME/bin/oidadmin