16 Post-Installation Tasks

Contents:

Section 16.1, "State of Oracle Application Server Instances After Installation"
Section 16.2, "If You Restart the Computer After Installation"
Section 16.3, "Passwords for Oracle Application Server Components"
Section 16.4, "OracleAS File-Based Clustering"
Section 16.5, "Application Server Control Service Not Needed for OracleAS Metadata Repository Only Installations"
Section 16.6, "Service Dependencies"
Section 16.7, "Backup and Recovery"
Section 16.8, "SSL"
Section 16.9, "Regional and Language Option Settings and the NLS_LANG Parameter"
Section 16.10, "Component Configuration After Installation"
Section 16.11, "Components that Require Post-Installation Tasks"
Section 16.12, "What to Do Next"

16.1 State of Oracle Application Server Instances After Installation

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

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\setupinfo.txt.

Some of the Oracle Application Server components run as Windows services. You can see them in the Services dialog. To display the Services dialog:

Windows 2000: Select Start > Programs > Administrative Tools > Services.

Windows 2003: Select Start > Administrative Tools > Services.

Windows XP: Select Start > All Programs > Administrative Tools > Services.

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.

16.2 If You Restart the Computer After Installation

If you restart the computer after installation, be aware that not all components will be started up automatically upon restart. Only services are started up automatically. Components that do not use services, such as OracleAS Portal or Oracle Internet Directory, will remain down until you start them up manually. For instructions on how to start up processes and the start-up order, see the Oracle Application Server Administrator's Guide.

Also, for the services to start up correctly, you may need to configure them. See Section 16.6, "Service Dependencies".

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

16.4 OracleAS File-Based Clustering

If you want to set up OracleAS Clusters managed using a file-based repository, you need to perform the steps listed in the Oracle Application Server High Availability Guide.

Note that when you run the "dcmctl joinFarm" command, it invokes "opmnctl stopall", which stops all components. After the "dcmctl joinFarm" command completes, you have to run "opmnctl startall" to restart the components.

16.5 Application Server Control Service Not Needed for OracleAS Metadata Repository Only Installations

If you install only the OracleAS Metadata Repository, you do not need the Application Server Control (Oracle<OracleHomeName>ASControl) service. However, the installer installs the service with its startup type set to automatic and starts it up. After installation, you should stop the service and change its startup type to manual so that it is not started up automatically each time you restart your computer.

16.6 Service Dependencies

This section is applicable only if you installed OracleAS Infrastructure and middle tier on the same computer.

Ensure that Windows starts up the ProcessManager service of the OracleAS Infrastructure before it starts up the ProcessManager service of the middle tier. Windows starts up services in alphabetical order. If the Oracle home name you gave to OracleAS Infrastructure comes later alphabetically than the middle-tier Oracle home name, then you have to set up a service dependency using the Registry Editor.

Start up the Registry Editor: select Start > Run, enter regedt32, and click OK.

Note:
For this procedure, you have to run regedt32, not regedit.
In the Registry Editor, select the HKEY_LOCAL_MACHINE window, and navigate to HKEY_LOCAL_MACHINE / SYSTEM / CurrentControlSet / Services, and locate the ProcessManager service for the middle tier. The name of the service is:
- OracleMiddleTierOracleHomeNameProcessManager
For the ProcessManager service on the middle tier:
1. Select the service in the left frame.
2. Select Edit > Add Value. This displays the Add Value dialog.
3. In the Add Value dialog:
  
  Value Name: enter DependOnService.
  
  Data Type: select REG_MULTI_SZ.
  
  Click OK. This displays the Multi-String Editor.
4. In the Multi-String Editor, enter the name of the ProcessManager service for the OracleAS Infrastructure.
  
  Example: if the Oracle home name for your OracleAS Infrastructure is "Infra", then enter the following line in the Multi-String Editor:
```
OracleInfraProcessManager
```
5. Click OK.

For more information, see Microsoft Knowledge Base article 193888, "How to Delay Loading of Specific Services," at the Microsoft site (http://www.microsoft.com).

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

16.8 SSL

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

16.9 Regional and Language Option Settings and the NLS_LANG Parameter

Make sure the language setting of your account is consistent with the system default language. Based on the language setting, the NLS_LANG parameter is automatically defined in the Windows registry.After installation, do not change the system default language. Otherwise, the NLS_LANG parameter and the language setting will be inconsistent.

16.10 Component Configuration After Installation

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

16.10.1 Configuring mod_osso (Required for 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.
```
include "ORACLE_HOME\Apache\Apache\conf\mod_osso.conf"
```
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 PATH environment variable to contain %ORACLE_HOME%\lib.

Run the following command (all on one line). Note: for the -classpath parameter, do not type any space characters after the semicolon (;) 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;<no spaces>
 %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 16-1 describes the parameters where you have to supply values:

Table 16-1 Parameters for Configuring mod_osso

Parameter	Description
`-h` `OIDhost`	Specifies the name of the computer where Oracle Internet Directory is running. You can determine this value from the `OIDhost` parameter in the `ORACLE_HOME\config\ias.properties` file.
`-p` `OIDport`	Specifies the port number on which Oracle Internet Directory is listening. You can determine this value from the `OIDport` parameter in the `ORACLE_HOME\config\ias.properties` file.
`-u` `OIDadminName`	Specifies the login name for Oracle Internet Directory. Use the superuser: `cn=orcladmin`.
`-w` `OIDclearTextPassword`	Specifies the password for the Oracle Internet Directory user.
`-o` `ORACLE_HOME`	Specifies the full path to the directory where you installed OracleAS Infrastructure.
`-m` `ASinstanceName`	Specifies the name of the OracleAS Infrastructure instance where you want to configure mod_osso. You can determine this value from the `IASname` parameter in the `ORACLE_HOME\config\ias.properties` file.
`-infra` `infraGlobalDBname`	Specifies the name of the OracleAS Metadata Repository database. You can determine this value from the `InfrastructureDBCommonName` parameter in the `ORACLE_HOME\config\ias.properties` file.
`-mh` `host`	Specifies the full hostname (including the domain name) of the computer where you want to configure Oracle Delegated Administration Services.
`-sslp` `sslPort`	Specifies the SSL port for Oracle Internet Directory. You can determine this value from the `OIDsslport` parameter in the `ORACLE_HOME\config\ias.properties` file.

Restart OC4J and Oracle HTTP Server. You can do this using the opmnctl command.

C:\> %ORACLE_HOME%\opmn\bin\opmnctl restartproc ias-component=OC4J
C:\> %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.

16.11 Components that Require Post-Installation Tasks

If you plan to use any of the components listed in Table 16-2, you need to perform some steps specific to the component after installation before you can use the component. Table 16-2 lists the component guides that describe the steps.

Table 16-2 Components Requiring Post-Installation Steps

Component	Guide That Describes the Post-Installation Steps
OracleAS Portal	Oracle Application Server Portal Configuration Guide
OracleAS Wireless	Oracle Application Server Wireless Administrator's Guide
Oracle Ultra Search	Oracle Ultra Search Administrator's Guide
OracleBI Discoverer	To prepare your relational data for analysis, enable users and roles, and set up security, refer to the Oracle Business Intelligence Discoverer Administration Guide. To find out about middle tier post-installation tasks, refer to the Oracle Business Intelligence Discoverer Configuration Guide. Note: You can find these guides on the Oracle Business Intelligence Tools CD.
OracleAS Reports Services	Oracle Application Server Reports Services Publishing Reports to the Web
OracleAS Personalization	Oracle Application Server Personalization Administrator's Guide
OracleAS Certificate Authority	Oracle Application Server Certificate Authority Administrator's Guide

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