2 Installing Oracle Portal, Forms, Reports and Discoverer

2.1.1 Installing and Configuring a Database and Database Schemas

Oracle Portal and Oracle Discoverer require database schemas on an Oracle database only. For more information about installing and configuring your database, see "Install and Configure a Database" in Oracle Fusion Middleware Installation Planning Guide.

After your database is installed and configured, you need to run the Repository Creation Utility (RCU) to create the schemas for Oracle Portal and Oracle Discoverer. For instructions, see "Creating Schemas" in Oracle Fusion Middleware Repository Creation Utility User's Guide.

2.1.2 Installing Oracle WebLogic Server

Oracle Portal, Forms, Reports and Discoverer requires Oracle WebLogic Server and a Middleware home directory. For more information, see "Install Oracle WebLogic Server" in Oracle Fusion Middleware Installation Planning Guide.

2.1.3 Oracle Fusion Middleware Support of 64-bit JDK

If you are using a 64-bit JVM in your environment, ensure that all your Oracle Fusion Middleware components are using the 64-bit JVM. You cannot mix components using a 32-bit JVM with those using a 64-bit JVM.

Refer to the Oracle Fusion Middleware Certifications matrix for information on the platforms that support a 64-bit JDK:

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

If your Oracle Fusion Middleware components are running in a 64-bit JVM environment, ensure that WebLogic Server is installed with the 64-bit JDK. For 32-bit JVM support, refer to the Oracle Fusion Middleware Release Notes for information on how to configure your environment for 32-bit JVM support for your platform.

2.1.4 Installing Oracle Internet Directory

Oracle Portal requires an existing Oracle Internet Directory (OID) with Oracle Single Sign-On (SSO). If you are also installing Oracle Forms, Reports or Discoverer, you will have the option to configure these products with an OID, but it is not mandatory.

The following OID/SSO combinations are supported:

• Oracle Internet Directory 10g (10.1.4.3) with Oracle Single Sign-On 10g (10.1.4.3)

• Oracle Internet Directory 11g (11.1.1) with Oracle Single Sign-On 10g (10.1.4.3)

If you are not able to use an existing 10g Oracle SSO server, follow this sequence of steps to add a new Oracle SSO server:

1. Install either Oracle Internet Directory 10g (10.1.4.3) or Oracle Internet Directory 11g (11.1.1) on your system.

2. Install Oracle Single Sign-On 10g (10.1.4.3) on your system in a different Oracle home location than your Oracle Internet Directory installation.

   Note:

   Oracle Single Sign-On 10g (10.1.4.3) requires a separate Oracle home if it is installed with Oracle Internet Directory 11g Release 1 (11.1.1). However, installing Oracle Single Sign-On 10g (10.1.4.3) in a separate Oracle home from Oracle Internet Directory 10g (10.1.4.3) will make it easier for you to upgrade to Oracle Internet Directory 11g Release 1 (11.1.1) later if you choose.

   Either during or after you install Oracle Single Sign-On, you must hook up Oracle Single Sign-On with your Oracle Internet Directory installation. For more information, see Oracle Fusion Middleware Installation Guide for Oracle Identity Management.

   If you installed Oracle Internet Directory 11g (11.1.1), you can also refer to Oracle Fusion Middleware Quick Installation Guide for Oracle Identity Management.

3. Test your Oracle Single Sign-On configuration to make sure that it is working properly.

4. Install Oracle Portal, Forms, Reports and Discoverer 11g Release 1 (11.1.1). During configuration, you will be able to hook up your installation with Oracle Single Sign-On.

2.1.5 Upgrading Oracle Web Agent (OWA) for Oracle Portal

Oracle Fusion Middleware 11g Release 1 (11.1.1) includes a new version of the Oracle Web Agent (OWA) packages. Existing packages will be updated to the new version the first time either an Oracle Portal 11g repository is installed or when an existing Oracle Portal repository is upgraded to 11g. When the OWA update takes place, packages from existing Oracle Portal schemas that reside in the same database will become invalid. The OWA update ends with an attempt to revalidate all invalid packages in all Oracle Portal schemas in the existing database instance.

For more information about upgrading OWA, refer to "Updating the Oracle Web Agent (OWA) Packages During an Oracle Portal Upgrade" in Oracle Fusion Middleware Upgrade Guide for Oracle Portal, Forms, Reports, and Discoverer.

2.1.6 Installing Oracle Forms and Oracle Reports on Separate Servers

If you choose to install Oracle Forms and Oracle Reports on different servers, you must perform some manual configuration in order for these two products to be able to communicate properly with each other.

The instructions for doing so are available in section 17.8.1, "Communication Between Reports and Forms When Installed on Different Instances" in Oracle Fusion Middleware Publishing Reports to the Web with Oracle Reports Services.

2.1.7 Installing in a Middleware Home Where Oracle SOA Suite or Oracle Identity Management Already Exist

If you are installing Oracle Portal, Forms, Reports and Discoverer into a Middleware home (MW_HOME) directory that already contains an Oracle SOA Suite or Oracle Identity Management installation, you must do the following before you install:

1. Navigate to the MW_HOME/wlserver_10.3/common/nodemanager (on UNIX operating systems) or MW_HOME\wlserver_10.3\common\nodemanager (on Windows operating systems) directory.

2. Edit the nodemanager.properties file and set the StartScriptEnabled property as follows:

   StartScriptEnabled=true
   

3. Restart Node Manager.

For more information about the Middleware home directory, see "Oracle Fusion Middleware Directory Structure" in Oracle Fusion Middleware Installation Planning Guide.

2.3.1 Installation Log Files

The installer writes logs files to the Oracle_Inventory_Location/log (on UNIX operating systems) or Oracle_Inventory_Location\logs (on Windows operating systems) directory. Refer to Section F.2.1, "Installation Log Files" for more information about the log files and their contents.

2.3.2 Starting the Installer

To start the installer, insert the CD-ROM and run the following command:

On UNIX operating systems:

./runInstaller

On Windows operating systems:

setup.exe

If you are installing on an HP-UX system with a PA-RISC processor, you must specify the location of a JRE on your system as follows:

./runInstaller -jreLoc JRE_LOCATION

Refer to the Oracle Fusion Middleware Certification document to see the JDKs supported for your system:

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

2.3.3 Inventory Screens (UNIX Only)

If you are installing on a UNIX operating system, and if this is the first time any Oracle product is being installed on your system with the Oracle Universal Installer, you will be asked to provide the location of an inventory directory. This is where the installer will set up subdirectories and maintain inventory data for each Oracle product that is installed on this system.

Follow the instructions in Table 2-1 to configure the inventory directory information. For more help, select the screen name in the table below, or click the Help button in the GUI.

If you do not wish to use the Oracle central inventory, you can create a file called oraInst.loc and in this file, include the full path of the inventory directory of your choice in the oraInst.loc file. Then, you can start the installer and point to the oraInst.loc file. For example, on UNIX operating systems:

./runInstaller -invPtrLoc location_of_oraInst.loc_file

On Windows operating systems:

setup.exe -invPtrLoc location_of_oraInst.loc_file

2.3.4 Installing and Configuring the Latest Version of Oracle Portal, Forms, Reports and Discoverer

Follow the instructions in this section to install and configure the latest Oracle Portal, Forms, Reports and Discoverer software.

ORACLE_HOME/bin/config.sh

ORACLE_HOME\bin\config.bat

2.3.5 Manual Configuration for Oracle Discoverer (Windows Only)

If Oracle Discoverer is installed and configured using the Install Software - Do Not Configure option and Configuration Tool, some manual steps need to be performed to create the Windows registry entries for Oracle Discoverer Administrator and Oracle Discoverer Desktop. Run the following java command to do so:

java -classpath ORACLE_HOME_DIR\discoverer\lib\disco-config.jar;ORACLE_HOME_DIR\oui\jlib\OraInstaller.jar;ORACLE_HOME_DIR\opmn\lib\iasprovision.jar -Djava.library.path=ORACLE_HOME_DIR\oui\lib\win32 oracle.disco.install.config.DiscoUtil -oraclehome ORACLE_HOME_DIR -tnsadmin TNS_ADMIN_DIR

• Replace ORACLE_HOME_DIR with the full path to your Oracle Portal, Forms, Reports, and Discoverer Oracle Home directory.

• Replace TNS_ADMIN_DIR with the path to the directory where the tnsnames.ora file is located. If this file does not already exist, create it and supply the directory in place of the TNS_ADMIN_DIR variable.

• The Java class path must be set properly with the -classpath parameter.

• The java.library.path must be set to the directory containing OraInstaller.dll.

2.4.1 Verifying the Installation Logs

Check for the presence of installation log files in logs directory inside your Oracle Inventory directory. On UNIX systems, if you do not know the location of your Oracle Inventory directory, you can find it in the ORACLE_HOME/oraInst.loc file. On Windows systems, the default location for the inventory directory is C:\Program Files\Oracle\Inventory\logs.

For more information about the installation log files, refer to Section F.2.1, "Installation Log Files".

2.4.2 Verifying the Domain Server Logs

Check the domain server logs, which are located in the servers directory inside the domain home directory. For example, on UNIX systems:

ORACLE_HOME/user_projects/domains/domain_name/servers/server_name

On Windows systems:

ORACLE_HOME\user_projects\domains\domain_name\servers\server_name

2.4.3 Verifying OPMN Status

Run the opmnctl status command from the INSTANCE_HOME/bin (on UNIX operating systems) or INSTANCE_HOME\bin (on Windows operating systems) directory in your instance home location. The example below shows the output on a UNIX system:

> ./opmnctl status

Processes in Instance: asinst_1
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status  
---------------------------------+--------------------+---------+---------
emagent_asinst_1                 | EMAGENT            |   11849 | Alive   
wc1                              | WebCache-admin     |   11333 | Alive   
wc1                              | WebCache           |   11332 | Alive   
ohs1                             | OHS                |   11207 | Alive 

This information shows the components configured for this installation. The status "Alive" means the component is up and running.

You can also run the opmnctl status -l command to obtain a list of ports used by the components. The example below shows the output on a UNIX system:

> ./opmnctl status -l

Processes in Instance: asinst_1
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
ias-component                    | process-type       |     pid | status   |        uid |  memused |    uptime | ports
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
emagent_asinst_1                 | EMAGENT            |   11849 | Alive    | 1133259606 |     4204 |   0:09:38 | N/A
wc1                              | WebCache-admin     |   11333 | Alive    | 1133259605 |    43736 |   0:15:35 | http_admin:8091
wc1                              | WebCache           |   11332 | Alive    | 1133259604 |    63940 |   0:15:35 | http_stat:8092,http_invalidation:8093,https_listen:8094,http_listen:8090
ohs1                             | OHS                |   11207 | Alive    | 1133259603 |    50744 |   0:15:43 | https:8889,https:8890,http:8888

2.4.4 Checking Browser URLs

The Installation Complete Screen contains URLs that can be used to access your installed and configured products, as shown in Table 2-4: