Skip Headers
Oracle® Application Server Installing and Getting Started with Standard Edition One
10g Release 2 (10.1.2) for Linux x86
B16043-02
  Go To Documentation Library
Home
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
Next
Next
 

6 Postinstallation Tasks

This chapter covers the following sections:

6.1 Starting Oracle Application Server Instances After Installation

After installation, the components that you have configured get started automatically unless you configure the ports to values lower than 1024. If the ports are configured to values lower than 1024, then you must to start the ports manually.

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

You can use either scripts or Oracle Enterprise Manager Application Server Control to start and stop Oracle Application Server instances.


See Also:

Oracle Application Server Administrator's Guide for details

6.2 Setting the Passwords for Oracle Application Server Components

By default, all passwords for Oracle Application Server components, with the exception of the OracleAS Metadata Repository schema passwords, 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.


See Also:

Oracle Application Server Administrator's Guide and the component guides in the Oracle Application Server Documentation Library for details about altering the passwords for the components you have installed

6.3 Other Postinstallation Tasks

This section covers the other postinstallation tasks that you need to perform. It contains the following topics:

6.3.1 NFS Installations

If you install Oracle Application Server on an NFS disk, then you need to modify the LockFile directive in the $ORACLE_HOME/Apache/Apache/conf/httpd.conf file so that it points to a local disk. This file is used by the Oracle HTTP Server component.


See Also:

Oracle HTTP Server Administrator's Guide for details

6.3.2 Backup and Recovery

Back up the software files, configuration files, and OracleAS Metadata Repository files and set up your backup and recovery strategy after completing the installation. This enables you to restore a working environment in case something goes wrong. For details about performing a complete Oracle Application Server environment backup, refer to Chapter 14, "Backup and Recovery" or Oracle Application Server Administrator's Guide.

In addition, you should perform a full Oracle Application Server environment backup after each successful patch set upgrade and configuration change.


See Also:

Chapter 14, "Backup and Recovery" and Oracle Application Server Administrator's Guide for more information

6.3.3 Enabling SSL

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

6.3.4 Operating System Locale and NLS_LANG Environment Variable

If you installed Oracle Application Server in a non-English language environment, then check the settings as described in the following sections:

6.3.4.1 Checking the Operating System Locale

To ensure that the default locale is configured correctly, verify that the LC_ALL or LANG environment variables have the required values. To check the current setting, run the locale command as follows:

prompt> locale

6.3.4.2 Checking the NLS_LANG Setting

To check the NLS_LANG setting:

  1. Ensure that the value of the NLS_LANG environment variable is compatible with the default locale setting of the operating system. Refer to Oracle Application Server Globalization Guide for details, including a list of files that set this variable. You may 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.

    For example, the NLS_LANG setting in the opmn.xml file may be similar to the following:

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

6.4 Components that Require Postinstallation Tasks

If you plan to use Oracle Ultra Search in Oracle Application Server Standard Edition One, you need to perform some steps specific to this component after installation before you can use Oracle Ultra Search. For more information, refer to Oracle Ultra Search Administrator's Guide.

6.5 What to Do Next?

After installing Oracle Application Server Standard Edition One, refer to chapters in Part II, especially Chapter 7, "Getting Started" and Oracle Application Server Administrator's Guide.