2 Installing Oracle Portal, Forms, Reports and Discoverer

2.1.1 System Requirements and Certification

Before performing any installation you should read the system requirements and certification documentation to ensure that your environment meets the minimum installation requirements for the products you are installing. Both of these documents are available on Oracle Technology Network (OTN).

The system requirements document covers information such as hardware and software requirements, minimum disk space and memory requirements, and required system libraries, packages, or patches:

http://www.oracle.com/technology/software/products/ias/files/fusion_requirements.htm

The certification document covers supported installation types, platforms, operating systems, databases, JDKs, and third-party products:

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

2.1.2 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.3 Install Oracle Database

Installation of Oracle Portal and Oracle Discoverer requires the availability of an Oracle database. This database must be up and running, and does not have to be on the same system where you are installing the products.

For the latest information about supported databases, visit the following URL:

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

2.1.4 Create Schemas for Oracle Portal and Oracle Discoverer

Oracle Portal and Oracle Discoverer require that certain schemas exist in the database prior to installation. You must run Repository Creation Utility (RCU) to create the schemas in the database. Follow these instructions to do so:

1. Insert the RCU CD-ROM and start RCU from the bin directory:

   On UNIX operating systems:

   ./rcu
   

   On Windows operating systems:

   rcu.bat
   

   You can also download a .zip file containing RCU from Oracle Technology Network (OTN):

   http://www.oracle.com/technology/
   

   Note:

   On Windows systems, make sure that you do not unzip the RCU .zip file to a directory name containing spaces.

   After downloading the .zip file, extract the contents to a directory of your choice, and run RCU from the RCU_HOME/bin (on UNIX operating systems) or RCU_HOME\bin (on Windows operating systems) directory with the commands shown above, where RCU_HOME is the folder where RCU was unzipped, or the drive or mount point of the CD-ROM.

2. Welcome Screen

   Click Next.

3. Create Repository Screen

   Click Create.

   Click Next.

4. Database Connection Details Screen

   Select the type of database on your system, then provide the necessary credentials for RCU to be able to connect to your database.

   If you are using an Oracle database:

   • Host Name: Specify the name of the machine on which your database resides in the format host.domain.com. For Oracle RAC databases, specify the Virtual IP name or one of the node names as the host name.

   • Port: Specify the database listener port number. The default port number for Oracle databases is 1521.

   • Database Name: Specify the service name for the database. Typically, the service name is the same as the global database name.

     If you are unsure what the service name for your database is, you can obtain it from the SERVICE_NAMES parameter in the database's initialization parameter file. If the initialization parameter file does not contain the SERVICE_NAMES parameter, then the service name is the same as the global database name, which is specified in the DB_NAME and DB_DOMAIN parameters.

     For Oracle RAC databases, specify the service name of one of the nodes in this field. For example: sales.mydomain.com.

   • Username: Specify the name of a user with DBA or SYSDBA privileges. The default user name with SYSDBA privileges is SYS.

   • Password: Specify the password for your database user.

   • Role: Select the database user's role from the drop-down list. The SYS user requires the SYSDBA role.

   If you are using a Microsoft SQL Server database, provide the following credentials:

   • Unicode Support: Select Yes or No from the drop-down list.

     Note:

     Oracle SOA Infrastructure schemas are created with Unicode support (database tables created with NVARCHAR) only, regardless of the option selected in this field.

   • Server Name: Enter the host name, IP address, or complete server name in host\server format of the server where your database is running..

   • Port: Specify the database listener port number.

   • Database Name: Specify the name of your database.

   • Username: Specify the name of a user with DBA or SYSDBA privileges.

   • Password: Specify the password for your database user.

   Click Next. A "Checking Prerequisites" screen will appear. After the checking is complete with no errors, click OK to dismiss the screen.

5. Select Components Screen

   Near the top of the screen, select Create a New Prefix. The default prefix is DEV.

   Table 2-1 lists the required schemas for Oracle Portal and Oracle Discoverer:

   Table 2-1 Required Schemas for Oracle Portal and Oracle Discoverer

   Component	Required Schemas
   Oracle Portal	prefix_PORTAL (Oracle Portal)
   Oracle Portlet Producers	prefix_PORTLET (Oracle Portlet Producers)
   Oracle Discoverer	prefix_DISCOVERER (Oracle Discoverer)

   
   

   Oracle Portal requires the PORTLET schema. During the creation of the schemas, you may choose to de-select the PORTLET schema, at which time you will be reminded that this schema is required for Oracle Portal. If you already have a PORTLET schema created elsewhere, you may ignore this message and proceed.

   Select the components whose schemas you want to install.

   Note:

   You must remember or make a note of these schema names and the prefix value from this screen; you will need them later when you are configuring your products. You will need to provide the schema name in the format prefix_schemaname. For example, if you used the default prefix DEV, you will supply the following schema name for the Portal schema:

   DEV_PORTAL

   Click Next. A "Checking Prerequisites" screen will appear. After the checking is complete with no errors, click OK to dismiss the screen.

6. Schema Passwords Screen

   Near the top of the screen, select Use same password for all schemas.

   In the Password field, enter your password. Enter your password again in the Confirm Password field.

   Note:

   You must remember or make a note of password(s) you specify on this screen; you will need them later when you are configuring your products.

   Click Next.

7. Map Tablespaces Screen

   Click Next. A "Creating Tablespaces" screen will appear. After the tablespaces are created with no errors, click OK to dismiss the screen.

8. Summary Screen

   Click Create. A "CREATE" screen will appear. After the schemas are created with no errors, click OK to dismiss the screen.

9. Completion Summary Screen

   Click Close.

For detailed information about using RCU, refer to Oracle Fusion Middleware Repository Creation Utility User's Guide.

2.1.5 Install Oracle WebLogic Server and Create the Middleware Home

Oracle Portal, Forms, Reports, and Discoverer requires an Oracle WebLogic Server on your system. If you do not already have one, follow the instructions in this section to install Oracle WebLogic Server.

1. Insert the Oracle WebLogic Server CD-ROM or download the installer from the following URL:

   http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html 
   

   You are looking for the following executable files:

   • wls1031_linux32.bin (for 32-bit Linux systems)

   • wls1031_win32.exe (for 32-bit Windows systems)

   • wls1031_generic.jar (for all 64-bit platforms)

   The 32-bit executable files are bundled with the appropriate JDK version. If you use the 64-bit installer, you will need to invoke the installer with a supported JDK for your platform. This JDK must be installed on your system before you install Oracle WebLogic Server.

   Refer to the Oracle Fusion Middleware System Requirements document for a list of supported JDKs for your platform:

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

2. Run your installer file directly from the CD-ROM, or copy the file to your local system and run it locally.

   Some notes for running the installer:

   • Before running the installer, set the DISPLAY environment variable on your system.

   • Replace JAVA_HOME with the installation location of the supported JDK you installed for your platform.

   • If you are installing a 64-bit Oracle WebLogic Server on a 64-bit platform, use the -d64 flag when using 32/64-bit hybrid JDK's (such as the HP JDK for HP-UX and SUN JDK for Solaris SPARC).

     Execute JAVA_HOME/bin/java -version (or JAVA_HOME/bin/java -d64 -version on 32/64-bit hybrid JDKs) to ensure that your JAVA_HOME refers to a 64-bit JDK.

   To run the installer on a 32-bit Linux operating system:

   ./wls1032_linux32.bin
   

   To run the installer on 32-bit Windows operating systems:

   wls1032_win32.exe
   

   To run the installer on 64-bit UNIX operating systems:

   JAVA_HOME/bin/java -jar wls1032_generic.jar
   

   or

   JAVA_HOME/bin/java -d64 -jar wls1032_generic.jar
   

   To run the installer on 64-bit Windows operating systems:

   JAVA_HOME\bin\java -jar wls1032_generic.jar
   

3. Welcome Screen

   Click Next.

4. Choose Middleware Home Directory Screen

   Select Create a new Middleware Home.

   Specify the desired location of your new Middleware Home directory. If this directory already exists on your system, it must be an empty directory. If this directory does not already exist, then it will be created for you.

   For more information about the Middleware Home directory, refer to "Middleware Home and WebLogic Home Directories" in Oracle Fusion Middleware Installation Planning Guide.

   Click Next.

5. Register for Security Updates Screen

   Select whether or not you want to receive the latest product and security updates. If you choose not to receive anything, you will be asked to verify your selection before continuing.

   Click Next.

6. Choose Install Type Screen

   A Typical installation includes all Oracle WebLogic Server components by default. It also includes both Sun SDK 1.6.0_14 and Oracle JRockit SDK 1.6.0_14. If you want to perform a Typical installation, select Typical and click Next to go to the Choose Product Installation Directories Screen.

   A Custom installation gives you the choice of selecting the following components for installation:

   • Core Application Server

   • Administration Console

   • Configuration Wizard and Upgrade Framework

   • Web 2.0 HTTP Pub-Sub Server

   • WebLogic JDBC Drivers

   • Third Party JDBC Drivers

   • WebLogic Server Clients

   • WebLogic Web Server Plugins

   • UDDI and Xquery Support

   • Server Examples (not selected by default)

   If you want to perform a Custom installation, select Custom. You will see the following two screens:

   1. Choose Products and Components Screen

      Select the products you want to install.

   2. JDK Selection Screen

      Select the JDKs you want to install.

      Oracle recommends that you use the Sun SDK if you are installing in a development environment. Typically, this environment provides a more relaxed security configuration and enables you to auto-deploy applications. In a development environment, boot.properties is used for user names and passwords and polling is used for application deployment.

      If you are installing in a production environment, Oracle recommends that you use the Oracle JRockit SDK. Production environments are for applications running in their final form. Full security is enabled and applications may be clustered or use other advanced features. In this mode, user names and passwords are required and polling is not used for application deployment.

   Click Next.

7. Choose Product Installation Directories Screen

   Specify the desired location for your WebLogic Server Home directory.

   For more information about the WebLogic Home directory, refer to "Middleware Home and WebLogic Home Directories" in Oracle Fusion Middleware Installation Planning Guide.

   Click Next.

8. Choose Shortcut Location (Windows only)

   If you are installing on a Windows system, you will be asked to specify a location where you would like Windows to create a shortcut to Oracle products.

   Click Next.

9. Installation Summary Screen

   Click Next.

10. Installation Progress Screen

    No action is required on this screen; the installer will automatically advance to the next screen when installation is complete.

11. Installation Complete Screen

    De-select Run Quickstart.

    Click Done.

For more information about installing and configuring WebLogic Server, refer to Oracle WebLogic Server Installation Guide.

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

   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.7 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.3.1 For UNIX Platforms

On UNIX systems, configure the host to resolve hostnames to the loopback IP address by modifying the /etc/hosts file to contain the following entries:

127.0.0.1 hostname.domainname hostname
127.0.0.1 localhost.localdomain localhost

After doing so, check that the hostname resolves to the loopback IP address by entering the following command:

/bin/ping hostname.domainname

2.3.2 For Windows x86 Platforms

On Windows systems, install a loopback adapter on the DHCP server (see Section 2.3.3, "Installing a Loopback Adapter (Windows Only)"). This assigns a local IP address to your computer.

After installing the adapter, add a line to the %SYSTEMROOT%\system32\drivers\etc\hosts file with the following format, immediately after the localhost line:

IP_address   hostname.domainname   hostname

Replace IP_address with the local IP address of the loopback adapter.

2.3.3 Installing a Loopback Adapter (Windows Only)

To install a loopback adapter on Windows 2003 or Windows XP:

1. Open the Windows Control Panel.

   Windows 2003: Select Start > Control Panel > Add Hardware.

   Windows XP: Select Start > Control Panel, then double-click Add Hardware.

2. In the "Welcome" window, click Next.

3. In the "Is the hardware connected?" window, select Yes, I have already connected the hardware, then click Next.

4. In the "The following hardware is already installed on your computer" window, in the list of installed hardware, select Add a new hardware device, then click Next.

5. In the "The wizard can help you install other hardware" window, select Install the hardware that I manually select from a list, then click Next.

6. In the "From the list of hardware types, select the type of hardware you are installing" window, select Network adapters, then click Next.

7. In the "Select Network Adapter" window, make the following selections:

   • Manufacturer: Microsoft

   • Network Adapter: Microsoft Loopback Adapter

8. Click Next.

9. In the "The wizard is ready to install your hardware" window, click Next.

10. In the "Completing the Add Hardware Wizard" window, click Finish.

11. If you are using Windows 2003, restart your computer.

12. Right-click My Network Places on the desktop and choose Properties. This displays the Network Connections Control Panel.

13. Right-click the connection that was just created. This is usually named "Local Area Connection 2". Choose Properties.

14. On the "General" tab, select Internet Protocol (TCP/IP), then click Properties.

15. In the "Properties" dialog box, click Use the following IP address and do the following:

    1. IP Address: Enter a non-routable IP for the loopback adapter. Oracle recommends the following non-routable addresses:

       192.168.x.x (x is any value between 1 and 255)
       10.10.10.10
       

    2. Subnet mask: Enter 255.255.255.0.

    3. Record the values you entered, which you will need later in this procedure.

    4. Leave all other fields empty.

    5. Click OK.

16. In the "Local Area Connection 2 Properties" dialog, click OK.

17. Close Network Connections.

18. Restart the computer.

2.3.4 Removing a Loopback Adapter (Windows Only)

To remove a loopback adapter on Windows 2003 or Windows XP:

1. Start the System Control panel.

   Windows 2003: Select Start > Control Panel > System.

   Windows XP: Select Start > Control Panel, then double-click System.

2. In the "Hardware" tab, click Device Manager.

3. In the "Device Manager" window, expand Network adapters. You should see Microsoft Loopback Adapter.

4. Right-click Microsoft Loopback Adapter and select Uninstall.

5. Click OK.

2.8.1 Installation Types

The Oracle Portal, Forms, Reports and Discoverer installer provides two installation options:

• Installation Instructions for "Install and Configure" Install Type

• Installation Instructions for "Install Only" Install Type

The Install and Configure option installs the product binaries in an Oracle Home directory and creates and configures a working instance in an Oracle Instance directory. After this is complete, you should be able to access the Welcome Page to begin configuring and managing your products.

Instructions for this installation type are provided in Section 2.8.5, "Installation Instructions for "Install and Configure" Install Type".

The Install Software - Do Not Configure option only installs the software binaries in an Oracle Home directory. You must then manually run the Configuration Tool from your ORACLE_HOME/bin (on UNIX operating systems) or ORACLE_HOME\bin (on Windows operating systems) directory to configure your products before you can use them. This option can be used to quickly create multiple instances of the software that share a common disk.

Instructions for this installation type are provided in Section 2.8.6, "Installation Instructions for "Install Only" Install Type".

2.8.2 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 D.2.1, "Installation Log Files" for more information about the log files and their contents.

2.8.3 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.8.4 Inventory Screens (UNIX Only)

If you are installing on a UNIX 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-2 to configure the inventory directory information. For more help, click on the screen name in the table below, or click the Help button in the GUI.

2.8.5 Installation Instructions for "Install and Configure" Install Type

Follow the instructions in Table 2-3 to install and configure Oracle Portal, Forms, Reports and Discoverer.

If you need additional help with any of the installation screens, refer to Appendix A, "Oracle Portal, Forms, Reports and Discoverer Installation Screens" or click Help to access the online help.

2.8.6 Installation Instructions for "Install Only" Install Type

Follow the instructions in Table 2-4 to install Oracle Portal, Forms, Reports and Discoverer.

If you need additional help with any of the installation screens, refer to Appendix A, "Oracle Portal, Forms, Reports and Discoverer Installation Screens" or click Help to access the online help.

After the installation is complete, you must configure the components. This is done by running a separate configuration tool.

On UNIX systems:

ORACLE_HOME/bin/config.sh

On Windows systems:

ORACLE_HOME\bin\config.bat

By default, the configuration tool will use the Oracle JRockit SDK that can be found inside the Middleware Home directory. If you want to invoke the configuration tool with a Sun JDK, you must point to the specific JDK from the command line:

On UNIX operating systems:

ORACLE_HOME/bin/config.sh -jreLoc Sun_JDK_Location

On Windows operating systems:

ORACLE_HOME\bin\config.bat -jreLoc Sun_JDK_Location

You must specify the full path to your Sun JDK location.

After you have started the Configuration Tool, follow the instructions in Table 2-5.

2.8.7 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 -D java.library.path=ORACLE_HOME_DIR\oui\lib\win32\oraInstaller.dll 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.9.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 D.2.1, "Installation Log Files".

2.9.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.9.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.9.4 Checking Browser URLs

The Install Completed Screen contains URLs that can be used to access your installed and configured products, as shown in Table 2-6: