1 Getting Started After Installing Oracle Application Server

1.1 Task 1: Set Up Your Operating System User Account

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.

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"

$ORACLE_HOME/lib

$ORACLE_HOME/bin
$ORACLE_HOME/dcm/bin
$ORACLE_HOME/opmn/bin

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 into a different Oracle home as you move between installations. You must fully change to the new installation as follows:

• Log in as the user that installed the installation 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 the user.

  su - user
  
  

• Set the correct environment variables for the installation, as described in Table 1-1 and Table 1-2.

• Execute commands in the Oracle home of the correct installation.

1.2 Task 2: Use the Oracle Application Server Welcome Page

The Oracle Application Server Welcome Page is a great starting point for managing your application server. It includes the following:

• Details about New Features in Oracle Application Server 10g (9.0.4)

• A Quick Tour that provides a graphical introduction to Oracle Application Server 10g

• Oracle Application Server 10g (9.0.4) documentation library

• Release Notes for your platform

• A link to the Oracle Enterprise Manager 10g Application Server Control Console—a Web-based tool for managing Oracle Application Server

• Demonstrations and code samples for Oracle Application Server components and features

Figure 1-1 shows the Oracle Application Server Welcome Page.

Figure 1-1 Oracle Application Server Welcome Page

Description of the illustration welcome.gif

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/Apache/Apache/setupinfo.txt
(Windows) ORACLE_HOME\Apache\Apache\setupinfo.txt

The Welcome Page is accessible using the HTTP listener port on your installation. For example:

http://hostname.domain:7777

1. Check setupinfo.txt and make sure you are using the correct URL (hostname and port number).

2. Try restarting Oracle HTTP Server:

   opmnctl stopproc ias-component=HTTP_Server
   opmnctl startproc ias-component=HTTP_Server
   
   

3. If you have OracleAS Web Cache configured, try restarting it:

   opmnctl stopproc ias-component=WebCache
   opmnctl startproc ias-component=WebCache
   

1.3 Task 3: Check Your Port Numbers

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.

  
  

  See Also: Chapter 5, "Managing Ports" for information on changing 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 copy of this file.

;OracleAS Components reserve the following ports at install time.
;As a post-installation 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
Oracle HTTP Server Jserv port = 8007
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 Java Object Cache port = 7101
Application Server Control port = 1810
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

• As you view the portlist.ini file, you may wonder how the application server determines port assignments, or you may wish to change some of the port numbers. 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. Note that some port numbers cannot be changed, and some require additional steps for updating other components.

  
  

  See Also: Chapter 5, "Managing Ports" for information about port assignments and changing port numbers

  
  

• You may notice that portlist.ini contains port numbers for components you did not select during installation. This is 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 Also: Section 7.2, "Configuring Additional Components After Installation"

  
  

• 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 application server, you should use the Application Server Control Console Ports Page for viewing port numbers, because it displays the current port numbers.

• The default ports for Oracle Internet Directory are 389 (non-SSL) and 636 (SSL). However, many UNIX systems have these port numbers listed in /etc/services. This causes Oracle Application Server to assume the port numbers are in use and skip to the next port numbers in the allotted port range, which are 3060 (non-SSL) and 3130 (SSL). If you would rather use the standard port numbers (389 and 636), you can change them, after making sure you are not using those port numbers on your system.

  
  

  See Also: Section 5.6.2, "Changing Oracle Internet Directory Ports"

  
  

1.4 Task 4: Get Started with Managing Components

This task provides an introduction to managing components. It includes instructions for accessing component administration tools, post-installation notes about components, and pointers to more information.

• These components are configured in all installations:

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

  • Getting Started with Distributed Configuration Management (DCM)

  • Getting Started with Oracle HTTP Server

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

• J2EE and Web Cache components:

  • Getting Started with OracleAS Web Cache

• Portal and Wireless components:

  • Getting Started with OracleAS Portal

  • Getting Started with OracleAS Wireless

• Business Intelligence and Forms components:

  • Getting Started with OracleAS Discoverer

  • Getting Started with OracleAS Forms Services

  • Getting Started with OracleAS Reports Services

  • Getting Started with OracleAS Personalization

opmnctl status

Processes in Instance: biforms.myhost.myco.com
-------------------+--------------------+-------+---------
ias-component      | process-type       |   pid | status  
-------------------+--------------------+-------+---------
wireless           | OC4J_Wireless      |   404 | Alive   
Discoverer         | PreferenceServer   |   403 | Alive   
Discoverer         | OAD                |   405 | Alive   
Discoverer         | OSAgent            |   402 | Alive   
WebCache           | WebCacheAdmin      |   401 | Alive   
WebCache           | WebCache           |   400 | Alive   
HTTP_Server        | HTTP_Server        |   399 | Alive   
OC4J               | OC4J_BI_Forms      |   445 | Alive   
OC4J               | OC4J_Portal        |   413 | Alive   
OC4J               | home               |   412 | Alive   
dcm-daemon         | dcm-daemon         |   715 | Alive   
LogLoader          | logloaderd         |   N/A | Down    

dcmctl whichFarm

http://hostname.domain:port

(UNIX) ORACLE_HOME/install/portlist.ini
(Windows) ORACLE_HOME\install\portlist.ini

http://hostname.domain:7778

http://hostname.domain:port

(UNIX) ORACLE_HOME/install/portlist.ini
(Windows) ORACLE_HOME\install\portlist.ini

http://hostname.domain:7777

http://hostname.domain:port/webcacheadmin

(UNIX) ORACLE_HOME/install/portlist.ini
(Windows) ORACLE_HOME\install\portlist.ini

http://hostname.domain:4000/webcacheadmin

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

(UNIX) ORACLE_HOME/install/portlist.ini
(Windows) ORACLE_HOME\install\portlist.ini

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

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

(UNIX) ORACLE_HOME/install/portlist.ini
(Windows) ORACLE_HOME\install\portlist.ini

(UNIX) ORACLE_HOME/install/portlist.ini
(Windows) ORACLE_HOME\install\portlist.ini

http://hostname.domain:port/forms90/f90servlet/admin

(UNIX) ORACLE_HOME/install/portlist.ini
(Windows) ORACLE_HOME\install\portlist.ini

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

(UNIX) ORACLE_HOME/install/portlist.ini
(Windows) ORACLE_HOME\install\portlist.ini

1.5 Task 5: Check the Status of OracleAS Metadata Repository Schemas

If you installed an OracleAS Metadata Repository, you may be interested to know the status of the various schemas accounts and passwords. This information can be found in the following tables:

• Table 1-3, "Post-Installation Status of Schemas in a Metadata Repository Registered with OID"

  Consult this table if you registered the Metadata Repository with Oracle Internet Directory.

• Table 1-4, "Post-Installation Status of Schemas in a Metadata Repository Not Registered with OID"

  Consult this table if you did not register the Metadata Repository with Oracle Internet Directory.

The tables contain the account status and initial password for each schema. They also contain recommended actions to perform immediately after installation, depending on your requirements.

To unlock an account using SQL*Plus (be sure to have your ORACLE_HOME and ORACLE_SID environment variables set before you run these commands):

ORACLE_HOME/bin/sqlplus "SYS/password_for_sys AS SYSDBA"
SQL> ALTER USER schema ACCOUNT UNLOCK;

To lock an account:

ORACLE_HOME/bin/sqlplus "SYS/password_for_sys AS SYSDBA"
SQL> ALTER USER schema ACCOUNT LOCK;

The method for changing passwords varies by schema. Refer to Section 6.2, "Changing Schema Passwords" to determine the proper way to change a password.

Table 1-3 displays the postinstallation status of schemas in a Metadata Repository registered with Oracle Internet Directory.

Table 1-4 displays the postinstallation status of schemas in a Metadata Repository that is not registered with Oracle Internet Directory

1.6 Task 6: Enable SSL (Optional)

During installation, SSL is not configured for some components. If you would like to enable SSL, you can consult the component documentation for instructions.

SSL is not enabled for the following components during installation:

• Oracle HTTP Server—refer to Oracle HTTP Server Administrator's Guide.

• OracleAS Web Cache—refer to Oracle Application Server Web Cache Administrator's Guide.

• Oracle Enterprise Manager 10g Application Server Control Console—refer to Section A.4, "Configuring Security for Enterprise Manager the Application Server Control Console".

• OracleAS Personalization—refer to Oracle Application Server Release Notes for your platform.

1.7 What's Next?

Several more tasks to get you started are:

• Learn about Oracle Application Server administration tools—refer to Chapter 2, "Introduction to Administration Tools".

• Learn how to start and stop Oracle Application Server—refer to Chapter 3, "Starting and Stopping".

• Learn about Oracle Application Server backup and recovery, and perform a backup of your installation—refer to Part IV, "Backup and Recovery".