|Oracle® Application Server Installation Guide
10g (10.1.4.0.1) for HP-UX PA-RISC (64-Bit)
Part Number B32097-01
This chapter contains the following topics:
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
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.
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 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.
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.
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.
By default, most components are not configured for SSL. To enable SSL, see the SSL section in the Oracle Application Server Administrator's Guide.
If you installed Oracle Application Server in a non-English language environment, please check your settings as described in these sections:
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
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>
If you did not configure a component during installation (that is, you did not select the component in the Select Configuration Options screen), you can configure some components after installation. Some components have dependencies that you have to complete before you can configure the component. Section 11.7.1, "Configuring mod_osso (Required for Oracle Delegated Administration Services)" describes how to configure mod_osso, which has to be configured before you can configure Oracle Delegated Administration Services.
If you did not configure Oracle Delegated Administration Services during installation, you can do it after installation using Oracle Enterprise Manager 10g Application Server Control.
Oracle Delegated Administration Services requires OracleAS Single Sign-On and mod_osso. mod_osso is an Oracle HTTP Server module that communicates with the Single Sign-On server. If mod_osso is not configured, you have to configure it before you can configure Oracle Delegated Administration Services. Here are the steps:
Ensure that OracleAS Single Sign-On is configured against Oracle Internet Directory. This is done for you if you have installed and configured these two components from the installer.
Check if mod_osso is configured in the ORACLE_HOME where you want to configure Oracle Delegated Administration Services.
Examine the following line in the
ORACLE_HOME/Apache/Apache/conf/httpd.conf file. ORACLE_HOME refers to the directory where you want to configure Oracle Delegated Administration Services.
If the line starts with
#, then it is commented out and mod_osso is not configured in this installation. Perform step 3 to configure mod_osso.
If the line is not commented out, mod_osso is already configured. You can go ahead and configure Oracle Delegated Administration Services using Application Server Control. Go to step 5.
To configure mod_osso manually, perform these steps:
Set the ORACLE_HOME environment variable to the full path of the directory where you want to configure Oracle Delegated Administration Services.
Set the LD_LIBRARY_PATH environment variable to contain
Set the LD_LIBRARY_PATH_64 environment variable to contain
Run the following command (all on one line). Note: for the
-classpath parameter, do not type any space characters after the colon (
:) characters, as indicated by <no spaces>:
prompt> $ORACLE_HOME/jdk/bin/java -classpath .:$ORACLE_HOME/sso/lib/ossoreg.jar:<no spaces> $ORACLE_HOME/jlib/ojmisc.jar:<no spaces> $ORACLE_HOME/jlib/repository.jar:<no spaces> $ORACLE_HOME/j2ee/home/jazn.jar:$ORACLE_HOME/jdk/lib/dt.jar:<no spaces> $ORACLE_HOME/jdk/lib/tools.jar:$ORACLE_HOME/jlib/infratool.jar oracle.ias.configtool.UseInfrastructure i -f $ORACLE_HOME/config/infratool_mod_osso.properties -h OIDhost -p OIDport -u OIDadminName -w OIDclearTextPassword -o ORACLE_HOME -m ASinstanceName -infra infraGlobalDBName -mh host -sso true -sslp sslPort -sslf false
Table 11-1 describes the parameters where you have to supply values:
Table 11-1 Parameters for Configuring mod_osso
Specifies the name of the computer where Oracle Internet Directory is running. You can determine this value from the
Specifies the port number on which Oracle Internet Directory is listening. You can determine this value from the
Specifies the login name for Oracle Internet Directory. Use the superuser:
Specifies the password for the Oracle Internet Directory user.
Specifies the full path to the directory where you installed OracleAS Infrastructure.
Specifies the name of the OracleAS Infrastructure instance where you want to configure mod_osso. You can determine this value from the
Specifies the name of the OracleAS Metadata Repository database. You can determine this value from the
Specifies the full hostname (including the domain name) of the computer where you want to configure Oracle Delegated Administration Services.
Specifies the SSL port for Oracle Internet Directory. You can determine this value from the
Restart OC4J and Oracle HTTP Server. You can do this using the
prompt> $ORACLE_HOME/opmn/bin/opmnctl restartproc ias-component=OC4J prompt> $ORACLE_HOME/opmn/bin/opmnctl restartproc ias-component=HTTP_Server
Once mod_osso is configured, you can configure Oracle Delegated Administration Services using the Application Server Control. See the Oracle Internet Directory Administrator's Guide for details.
If you plan to use any of the components listed in Table 11-2, you need to perform some steps specific to the component after installation before you can use the component. Table 11-2 lists the component guides that describe the steps.
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.