7 Postinstallation Tasks

Contents:

Section 7.1, "State of Oracle Application Server Instances After Installation"
Section 7.2, "Passwords for Oracle Application Server Components"
Section 7.3, "NFS Installations"
Section 7.4, "Configuring OracleAS Clusters"
Section 7.5, "Backup and Recovery"
Section 7.6, "SSL"
Section 7.7, "Operating System Locale and NLS_LANG Environment Variable"
Section 7.8, "Proxy Settings"
Section 7.9, "What to Do Next"

7.1 State of Oracle Application Server Instances After Installation

After installation, the components that you have configured are started up (unless you have configured them to use ports lower than 1024, in which case you have to start them up manually).

You can view the Welcome page and the Application Server Control page in a browser. The URLs for these pages are shown in the last screen of the installer. You can view the contents of the last screen in the file ORACLE_HOME/install/readme.txt.

You can use scripts or you can use the Oracle Enterprise Manager 10g Application Server Control to start and stop Oracle Application Server instances. See the Oracle Application Server Administrator's Guide for details.

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

See 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.

7.3 NFS Installations

If you installed Oracle Application Server on an NFS disk, you need to edit 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 the Oracle HTTP Server Administrator's Guide for details.

7.4 Configuring OracleAS Clusters

If you did not configure OracleAS Clusters during installation, you can use Oracle Process Manager and Notification Server (OPMN) commands to do so following installation. See "Configuring Cluster Topologies" in the Oracle Application Server Administrator's Guide for details.

7.5 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. See the Oracle Application Server Administrator's Guide for details.

7.6 SSL

By default, all components are configured for SSL. For more information, see the SSL section in the Oracle Application Server Administrator's Guide.

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

Section 7.7.1, "Check the Operating System Locale"
Section 7.7.2, "Check the NLS_LANG Setting"

7.7.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

7.7.2 Check the NLS_LANG Setting

To check the NLS_LANG setting:

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.
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>
```

7.8 Proxy Settings

If you want the Oracle Application Server instance to use a proxy server, perform the following steps:

Run the following command to shutdown all processes:


prompt> ORACLE_HOME/opmn/bin/opmnctl shutdown

To set the proxy server for BPEL, modify the following lines in the ORACLE_HOME/bpel/bin/obsetenv.sh file:


PROXY_SET="true"

...

if [ "${PROXY_SET}" = "true" ]

then

    OB_JAVA_PROPERTIES="-Dhttp.proxySet=true -Dhttp.proxyHost=proxy_server_hostname -Dhttp.proxyPort=proxy_server_port -Dhttp.nonProxyHosts=localhost|non_proxy_host|other_non_proxy_hosts"

To set the proxy server for OC4J, modify the following lines for the OC4J module in the ORACLE_HOME/opmn/config/opmn.xml file:


<process-type id="oc4j_instance_name" module-id="OC4J" status="enabled">

  <module-data>

    <category id="start-parameters">

      <data id="java-options" value= ...

        -Dhttp.proxySet=true -Dhttp.proxyHost=proxy_server_hostname

        -Dhttp.proxyPort=proxy_server_port

        -Dhttp.nonProxyHosts=localhost|non_proxy_host|other_non_proxy_hosts"/>

    </category>

7.9 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, see 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.