Skip Headers

Oracle® Application Server Installation Guide
10g Release 2 (10.1.2) for hp HP-UX Itanium, and Linux Itanium
Part No. B15870-01
  Go To Documentation Library
Home
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
Next
Next
 

5 Post-Installation Tasks

This chapter contains the following topics:

5.1 State of Oracle Application Server Instances After Installation

After installation, the components that you have configured are started.

You can view the Welcome page and the Application Server Control page in a browser. The URLs for these pages are displayed in the last screen of the Oracle Universal Installer. You can view the contents of the last screen in the file ORACLE_HOME/install/setupinfo.txt.

You can use scripts or you can use the Oracle Enterprise Manager Application Server Control to start and stop Oracle Application Server components. For details, refer to the Oracle Application Server Administrator's Guide.

5.2 Passwords for Oracle Application Server Components

By default, all passwords for Oracle Application Server components are set to be the same as the Oracle Application Server instance password. For security reasons, you should change the passwords of the various components to have different values.

Refer to the Oracle Application Server Administrator's Guide and the component guides in the Oracle Application Server Documentation Library for details on how to alter the passwords for the components you have installed.

5.3 Backup and Recovery

After installation would be a good time to start backing up the files, and to set up your backup and recovery strategy. For details, refer to the Oracle Application Server Administrator's Guide.

5.4 SSL

By default, most components are not configured for SSL. To enable SSL, refer to the SSL section in the Oracle Application Server Administrator's Guide.

5.5 Operating System Locale and NLS_LANG Environment Variable

If you installed Oracle Application Server in a non-English language environment, please check your settings as described in these sections:

5.5.1 Check the Operating System Locale

To make sure the default locale is set properly, verify that the LC_ALL or LANG environment variables are set with the appropriate values. To check the current setting, run the locale command:

prompt> locale

5.5.2 Check the NLS_LANG Setting

To check the NLS_LANG setting:

  1. Make sure the value of the NLS_LANG environment variable is compatible with the default locale setting of the operating system. See the Oracle Application Server Globalization Guide for details, including a list of files that set this variable. You might need to edit the value of the NLS_LANG variable in these files.

  2. Check that the NLS_LANG setting in the ORACLE_HOME/opmn/conf/opmn.xml file is identical to the NLS_LANG environment variable.

    Example: The NLS_LANG setting in the opmn.xml file might look something like this:

    <environment>
         <variable id="TMP" value="/tmp"/> 
         <variable id="NLS_LANG" value="JAPANESE_JAPAN.JA16SJIS"/> 
    </environment>
    
    

5.6 Component Configuration After Installation

If you did not configure a component during installation (that is, if you did not select the component in the Select Configuration Options screen), then you can configure some components after installation. Some components have dependencies that you have to complete before you can configure the component.

5.7 What to Do Next

After installing Oracle Application Server, you should read the Oracle Application Server Administrator's Guide. Specifically, you should read the "Getting Started After Installing Oracle Application Server" chapter.

You should also perform a complete Oracle Application Server environment backup after installing Oracle Application Server. This enables you to restore a working environment in case something goes wrong. For details on how to perform a complete Oracle Application Server environment backup, refer to the Oracle Application Server Administrator's Guide.

You should also perform a complete Oracle Application Server environment backup after each successful patchset upgrade and after each successful configuration change.