1
Getting Started After Installing Oracle Application Server

This chapter contains tasks to help you get started managing Oracle Application Server after installation.

It contains the following topics:

• Task 1: Set Up Your Operating System User Account

• Task 2: Use the Oracle Application Server Welcome Page

• Task 3: Check Your Port Numbers

• Task 4: Get Started with Managing Components

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

• Task 6: Enable SSL (Optional)

• What's Next?

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.

You should set or modify some environment variables for this user, as described in Table 1-1.

Table 1-1   Oracle Application Server Environment Variables

Environment Variable	Value
DISPLAY	hostname:display_number.screen_number Beginning with Oracle Application Server 10g, very few tools require the DISPLAY variable. Only a few tools, such as oidadmin, require it.
LD_LIBRARY_PATH	Make sure this contains the following directory: $ORACLE_HOME/lib
ORACLE_HOME	Set to the full path of the installation's Oracle home
ORACLE_SID (Infrastructure installations only)	Set to the Metadata Repository SID you supplied during installation. The default is asdb.
PATH	Make sure this 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.

Best Practices for Multiple Installations on One Host

If you have multiple installations of Oracle Application Server on one 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.

• 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, that is fine. Just make sure 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 enable you to easily change from one installation to another.

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 Oracle Enterprise Manager Application Server Control--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

Text 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:

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

Tip

If you cannot access the Welcome Page, try the following:

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

2. Try restarting Oracle HTTP Server:

   ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=HTTP_Server
   ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=HTTP_Server
   
   

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

   ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=WebCache
   ORACLE_HOME/opmn/bin/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:

ORACLE_HOME/install/portlist.ini

Example 1-1 shows a sample copy of this file.

Example 1-1 A Sample portlist.ini 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

Some things to note about portlist.ini are:

• 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 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

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 Infrastructure installation and is essential for running Oracle Application Server.

To get started with OPMN, use the opmnctl command to query the status of the components in your installation:

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.

Example 1-2 Sample Output from 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    

Notice that the LogLoader process is always down after installation. Log Loader is a feature that compiles log messages from various log files into a single repository. You can start Log Loader after installation.

See Also: Section 4.5.1, "Starting and Stopping Log Loader"

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.

See Also: Oracle Process Manager and Notification Server Administrator's Guide

1.4.2 Getting Started with Distributed Configuration Management (DCM)

Distributed Configuration Management (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.

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 the 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 use Managed OracleAS Clusters during installation.

• File Based--this repository is stored in the filesystem in your Oracle home. This repository type is used by J2EE and Web Cache installations if you chose to use File-based clusters during installation.

You can determine your repository type as follows:

ORACLE_HOME/dcm/bin/dcmctl whichFarm

During installation, DCM created a copy of your initial configuration with the dcmctl saveInstance command. 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 clusters, and much more.

See Also: Distributed Configuration Management Reference Guide

1.4.3 Getting Started with Oracle HTTP Server

Oracle HTTP Server is installed and configured with every middle-tier and Infrastructure installation.

You can access Oracle HTTP Server as follows:

http://hostname.domain:port

port is the Oracle HTTP Server Listen port number in:

ORACLE_HOME/install/portlist.ini

For example:

http://hostname.domain:7778

When you access Oracle HTTP Server, you will see the Oracle Application Server Welcome Page.

See Also: Oracle HTTP Server Administrator's Guide

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 and OracleAS Discoverer

• 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

  See Also: Oracle Application Server Containers for J2EE User's Guide

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

port is the Web Cache HTTP Listen port number in:

ORACLE_HOME/install/portlist.ini

For example:

http://hostname.domain:7777

When you access OracleAS Web Cache, you will see the Oracle Application Server Welcome Page.

Accessing OracleAS Web Cache Manager

OracleAS Web Cache 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

port is the Web Cache HTTP Administration port number in:

ORACLE_HOME/install/portlist.ini

For example:

http://hostname.domain:4000/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.

See Also: Oracle Application Server Web Cache Administrator's Guide for a list of post-installation configuration tasks

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

port is the Web Cache HTTP Listen port number in:

ORACLE_HOME/install/portlist.ini

For example:

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

You can log in as portal using the ias_admin password you supplied during installation.

See Also: Oracle Application Server Portal Configuration Guide for information on getting started and managing OracleAS Portal

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

port is the Web Cache HTTP Listen port number in:

ORACLE_HOME/install/portlist.ini

You can log in as orcladmin using the orcladmin password.

See Also: Oracle Application Server Wireless Administrator's Guide

1.4.8 Getting Started with OracleAS Discoverer

If you configured OracleAS 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
  
  

port is the Web Cache HTTP Listen port number in:

ORACLE_HOME/install/portlist.ini

See Also: Oracle Application Server Discoverer Configuration Guide for additional steps for configuring Discoverer, including installing Discoverer workbooks and End User Layer (EUL) into each database that contains data to be analyzed

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/forms90/f90servlet/admin

port is the Web Cache HTTP Listen port number in:

ORACLE_HOME/install/portlist.ini

See Also: Refer to the OracleAS Forms Services online help for more information on configuring and using Forms

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

port is the Web Cache HTTP Listen port number in:

ORACLE_HOME/install/portlist.ini

You can log in as orcladmin with the orcladmin password.

See Also: Oracle Application Server Reports Services Publishing Reports to the Web for more information on configuring and using Reports

1.4.11 Getting Started with OracleAS Personalization

You must run the OracleAS Personalization Schema Creation Wizard, which creates the required schemas in the Oracle9i database. You can then start managing OracleAS Personalization.

See Also: Oracle Application Server Personalization Administrator's Guide

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-2, "  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-3, "  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-2 displays the postinstallation status of schemas in a Metadata Repository registered with Oracle Internet Directory.

Table 1-2   Post-Installation Status of Schemas in a Metadata Repository Registered with OID

Schema	Account Status	Password	Recommended Action after Installation
Standard Oracle Database Schemas
AURORA$JIS$UTILITY$	OPEN, NO CREATE SESSION	RANDOM
AURORA$ORB$UNAUTHENTICATED	OPEN	RANDOM
CTXSYS	LOCKED	RANDOM
DBSNMP	OPEN	DBSNMP	This schema is not used by Oracle Application Server; you can change the password and lock the account
MDSYS	LOCKED	EXPIRED
ORDPLUGINS	LOCKED	EXPIRED
ORDSYS	LOCKED	EXPIRED
OSE$HTTP$ADMIN	OPEN	RANDOM
OUTLN	LOCKED	EXPIRED
SCOTT	OPEN	TIGER	You can change the password if you want. Some demos may not work if you do so.
SYS	OPEN	Set by user during installation
SYSTEM	OPEN	Set by user during installation
Oracle Application Server Schemas
DCM	OPEN	RANDOM - Stored in OID
DISCOVERER5	OPEN	RANDOM - Stored in OID
DSGATEWAY	OPEN	RANDOM - Stored in OID
INTERNET_APPSERVER_REGISTRY	LOCKED, NO CREATE SESSION	EXPIRED
IP	OPEN	RANDOM - Stored in OID
OCA	OPEN	RANDOM - Stored in OID
ODS	OPEN	Same as the ias_admin password supplied during installation
ORAOCA_PUBLIC	OPEN	RANDOM - Stored in OID
ORASSO	OPEN	RANDOM - Stored in OID
ORASSO_DS	OPEN	RANDOM - Stored in OID
ORASSO_PA	OPEN	RANDOM - Stored in OID
ORASSO_PS	OPEN	RANDOM - Stored in OID
ORASSO_PUBLIC	OPEN	RANDOM - Stored in OID
OWF_MGR	OPEN	RANDOM - Stored in OID
PORTAL	OPEN	RANDOM - Stored in OID
PORTAL_APP	OPEN	RANDOM - Stored in OID
PORTAL_DEMO	OPEN	RANDOM - Stored in OID
PORTAL_PUBLIC	OPEN	RANDOM - Stored in OID
UDDISYS	OPEN	RANDOM - Stored in OID
WCRSYS	OPEN	RANDOM - Stored in OID
WIRELESS	OPEN	RANDOM - Stored in OID
WK_TEST	LOCKED	EXPIRED	If you would like to run Oracle Ultra Search demos, unlock and set a password
WKPROXY	OPEN	RANDOM - Stored in OID
WKSYS	OPEN	RANDOM - Stored in OID

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

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

Schema	Account Status	Password	Recommended Action after Installation
Standard Oracle Database Schemas
AURORA$JIS$UTILITY$	OPEN, NO CREATE SESSION	RANDOM
AURORA$ORB$UNAUTHENTICATED	OPEN	RANDOM
CTXSYS	LOCKED	RANDOM
DBSNMP	OPEN	DBSNMP	This schema is not used by Oracle Application Server; you can change the password and lock the account
MDSYS	LOCKED	EXPIRED
ORDPLUGINS	LOCKED	EXPIRED
ORDSYS	LOCKED	EXPIRED
OSE$HTTP$ADMIN	OPEN	RANDOM
OUTLN	LOCKED	EXPIRED
SCOTT	OPEN	TIGER	You can change the password if you want. Some demos may not work if you do so.
SYS	OPEN	Set by user during installation
SYSTEM	OPEN	Set by user during installation
Oracle Application Server Schemas
DCM	LOCKED	EXPIRED	If you intend to use Managed OracleAS Clusters using Database Repository, unlock and set a password
DISCOVERER5	LOCKED	EXPIRED
DSGATEWAY	LOCKED	EXPIRED
INTERNET_APPSERVER_REGISTRY	LOCKED, NO CREATE SESSION	EXPIRED
IP	LOCKED	EXPIRED
OCA	LOCKED	EXPIRED
ODS	LOCKED	EXPIRED
ORAOCA_PUBLIC	LOCKED	EXPIRED
ORASSO	LOCKED	EXPIRED
ORASSO_DS	LOCKED	EXPIRED
ORASSO_PA	LOCKED	EXPIRED
ORASSO_PS	LOCKED	EXPIRED
ORASSO_PUBLIC	LOCKED	EXPIRED
OWF_MGR	LOCKED	EXPIRED
PORTAL	LOCKED	EXPIRED
PORTAL_APP	LOCKED	EXPIRED
PORTAL_DEMO	LOCKED	EXPIRED
PORTAL_PUBLIC	LOCKED	EXPIRED
UDDISYS	LOCKED	EXPIRED
WCRSYS	LOCKED	EXPIRED
WIRELESS	LOCKED	EXPIRED
WK_TEST	LOCKED	EXPIRED
WKPROXY	LOCKED	EXPIRED
WKSYS	LOCKED	EXPIRED

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 Application Server Control--refer to Section A.4, "Configuring Security for Enterprise Manager Application Server Control".

• 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".