This chapter describes how to install and configure Oracle Portal, Forms, Reports and Discoverer.
The following topics are covered:
Section 2.2, "Securing Your Installation with Identity Management"
Section 2.4, "Installing and Configuring a Database and Database Schemas"
Section 2.6, "Installing Oracle Portal, Forms, Reports and Discoverer"
Section 2.7, "Patching Oracle Portal, Forms, Reports and Discoverer"
Section 2.8, "Configuring Oracle Portal, Forms, Reports and Discoverer"
Make sure you have read and, if necessary, performed the tasks in this section before you install Oracle Portal, Forms, Reports and Discoverer:
Section 2.1.1, "Verifying Your System and Network Environment"
Section 2.2, "Securing Your Installation with Identity Management"
Section 2.1.2, "Running the rootpre.sh Script on IBM AIX Operating Systems"
Section 2.1.3, "Upgrading Oracle Web Agent (OWA) for Oracle Portal"
Section 2.1.4, "Installing Oracle Forms and Oracle Reports on Separate Servers"
To verify that your system environment meets the minimum requirements for installation, refer to the following documents, available on Oracle Technology Network (OTN):
Oracle Fusion Middleware System Requirements and Specifications
This document contains information related to hardware and software requirements, minimum disk space and memory requirements, database schema requirements, and required system libraries, packages, or patches.
If you are installing on a DHCP server, non-networked computer, or multihomed computer, there are additional configuration steps that are required. These steps are also available in the system requirements document in the "Oracle Fusion Middleware System Configuration Requirements" section.
If you are installing on a Windows operating system and want to install and configure Java Access Bridge for Section 508 Accessibility, read the "Installing and Configuring Java Access Bridge" section in this document.
Oracle Fusion Middleware Supported System Configurations
This page contains various certification documents for current and previous product releases. The System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document contains certification information related to supported 32-bit and 64-bit operating systems, databases, web servers, LDAP servers, adapters, IPv6, JDKs, and third-party products.
Oracle Fusion Middleware Interoperability and Compatibility Guide
This document covers the compatibility and interoperability issues that may arise when installing or upgrading Oracle Fusion Middleware 11g products.
If you are installing on an IBM AIX operating system, you must run the rootpre.sh script as the root user from the Disk1 directory before you start the installer. The rootpre.sh script should be run only once on a system, to load the right kernel extensions required for Oracle Database or Oracle Fusion Middleware.
Once the installer is started on IBM AIX, the following message appears:
Answer 'y' if root has run 'rootpre.sh' so you can proceed with Oracle installation. Answer 'n' to abort installation and then ask root to run 'rootpre.sh'. Has 'rootpre.sh' been run by root? [y/n] (n) Answer 'y', if root has run 'rootpre.sh' so that you can proceed with Oracle installation. Answer 'n', to abort installation and then ask root to run 'rootpre.sh'.
To skip this message on systems where rootpre.sh has run before, set the SKIP_ROOTPRE environment variable to TRUE.
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.
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 "Communication Between Reports and Forms When Installed on Different Instances" in Oracle Fusion Middleware Publishing Reports to the Web with Oracle Reports Services.
Oracle Portal, Forms, Reports and Discoverer must be installed inside a Middleware home directory, which is created when Oracle WebLogic Server is installed.
Oracle recommends that Oracle Portal, Forms, Reports and Discoverer be installed in its own Middleware home directory that it does not share with any other Oracle Fusion Middleware products. This recommendation is because Oracle recommends the contents of Middleware home consist of products that are compatible as described in "Domain Extension Interoperability" in Oracle Fusion Middleware Interoperability and Compatibility Guide.
If necessary, Oracle Portal, Forms, Reports and Discoverer can be installed in the same Middleware home as another Oracle Fusion Middleware product provided that it does not share a domain with any other product, and also provided that all products in the Middleware home are the same version.
For more information, see the Oracle Fusion Middleware Interoperability and Compatibility Guide.
Oracle Portal requires an existing Oracle Internet Directory (OID) with Oracle Single Sign-On (SSO) 10g. If you are also installing Oracle Forms, Reports or Discoverer, you will have the option to configure these products with your existing Oracle Single Sign-On, but it is not mandatory.
Important information about Oracle Single Sign-On 10g is provided in the "Evaluating Single Sign-On Installations" section in Oracle Fusion Middleware Installation Guide for Oracle Identity Management. It is highly recommended that you read this before you continue with your Oracle Portal, Forms, Reports and Discoverer installation.
After your Oracle Portal instance is configured, it is automatically integrated with your Oracle Internet Directory and Oracle Single Sign-On. Oracle Forms and Oracle Reports are not automatically configured. For more information, see:
"Using Forms Services with Oracle Single Sign-On" in Oracle Fusion Middleware Forms Services Deployment Guide.
"Configuring and Administering OracleAS Single Sign-On" in Oracle Fusion Middleware Publishing Reports to the Web with Oracle Reports Services.
Depending on your specific needs, there are multiple places where you can obtain Oracle Fusion Middleware software. For details, refer to the Oracle Fusion Middleware Download, Installation, and Configuration ReadMe Files page, where you can find the ReadMe file for your specific release.
To install Oracle Portal, Forms, Reports and Discoverer, you will need to obtain the following:
If you want to protect your Oracle Portal, Forms, Reports and Discoverer installation with Oracle Identity Management, obtain Oracle Identity Management.
Note that Oracle Portal requires an existing Oracle Internet Directory with Single Sign-On on your system.
The latest version of Repository Creation Utility for creating the database schemas. You must also have a database that is supported for use with RCU.
The latest version of Oracle WebLogic Server for creating the Middleware home.
Oracle Portal, Forms, Reports and Discoverer 11g Release 1 (11.1.1.2.0).
Patch Set Installer for Oracle Portal, Forms, Reports and Discoverer 11g Release 1 (11.1.1.6.0).
Select one of the download locations and download the required software. Each download will be saved to your system as a .zip archive file.
After you download the archive file, unpack the archive file into a directory of your choice on the machine where you will be performing the installation.
Oracle Portal and Oracle Discoverer require database schemas on an Oracle database. These schemas can be created by using the Repository Creation Utility (RCU).
The System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document lists the databases that are certified for use with RCU and Oracle Fusion Middleware. This document is located on the Oracle Fusion Middleware Supported System Configurations page.
To ensure that your Oracle database is configured properly, see "RCU Requirements for Oracle Databases" in the Oracle Fusion Middleware System Requirements and Specifications document.
After your database is installed and configured, run 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.
Oracle Portal, Forms, Reports and Discoverer requires Oracle WebLogic Server, which creates the Middleware home directory during installation. For more information, see "Oracle Fusion Middleware Directory Structure" in Oracle Fusion Middleware Installation Planning Guide.
This section contains the following topics:
Section 2.5.1, "Planning Your Middleware Home Location for Oracle Reports (Windows Only)"
Section 2.5.2, "Finding Oracle WebLogic Server Installation Instructions"
If you are going to install Oracle Reports on a Windows operating system, make sure the path to your Middleware home directory is not too long. For more information, see Section F.3, "Verifying Environment Variable Lengths for Oracle Reports (Windows Only)".
For Oracle WebLogic Server installation instructions, see "Running the Installation Program in Graphical Mode" in Oracle WebLogic Server Installation Guide. The WebLogic Server installation must be completed so that a Middleware home directory is created; you do not have to create a WebLogic Server domain as the Oracle Forms and Reports installer will allow you to do this for your Oracle Forms and Reports products.
If you are installing on a Windows operating system, be sure to read Section 2.5.3, "Stopping Node Manager Before Installing Oracle Portal, Forms, Reports and Discoverer (Windows Only)" after your Oracle WebLogic Server installation is complete.
Note:
If you choose to install WebLogic Server using the Custom installation type on the "Choose Install Type" screen, you must make sure that the following components are installed in order for Oracle Discoverer to work properly:UDDI and Xquery Support
WebLogic JDBC Drivers
Third Party JDBC Drivers
If you are installing Oracle Portal, Forms, Reports and Discoverer on a Microsoft Windows operating system, you must make sure that the Node Manager utility that was installed with Oracle WebLogic Server is stopped before you install your Oracle Portal, Forms, Reports and Discoverer software:
Verify the Oracle WebLogic Server Node Manager utility is stopped. If it is running, kill the process.
Determine if the nodemanager.properties file is present in the WebLogic_Home\common\nodemanager directory.
If the nodemanager.properties file is not present, continue installing Oracle Portal, Forms, Reports and Discoverer.
If the nodemanager.properties file does exist, open it and verify that the ListenPort parameter is included and that it is set. If the ListenPort parameter is not included or set, edit the nodemanager.properties file so that it is similar to the following, where NODE_MANAGER_LISTEN_PORT represents the port the Node Manager listens on, such as 5556:
ListenPort=NODE_MANAGER_LISTEN_PORT
This section contains information and instructions for installing the latest Oracle Portal, Forms, Reports and Discoverer software. The following topics are covered:
Section 2.6.2, "Configuring Your Oracle Inventory (UNIX Only)"
Section 2.6.3, "Following the Installation Screens and Instructions"
To start the installer, go to the directory where you unpacked the archive file and switch to the Disk1 directory.
On UNIX operating systems:
cd unpacked_archive_directory/Disk1
./runInstaller
On Windows operating systems:
cd unpacked_archive_directory\Disk1
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
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.
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.
Table 2-1 Inventory Directory and Group Screens
| Screen | Description and Action Required |
|---|---|
|
Specify the Oracle inventory directory and group permissions for that directory. The group must have write permissions to the Oracle inventory directory. |
|
|
Run the |
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
Follow the instructions in Table 2-2 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 and Configuration Screens" or click Help to access the online help.
Table 2-2 Installation Flow for Install Only Option
| Screen | Description |
|---|---|
|
This page introduces you to the Oracle Fusion Middleware installer. |
|
|
Select Install Software - Do Not Configure. |
|
|
Verify that your system meets all necessary prerequisites. |
|
|
Specify the following installation directories:
|
|
|
Select the method in which you want to receive the latest product information and security updates. |
|
|
Verify the information on this screen, then click Install to begin the installation. |
|
|
This screen shows the progress of the installation. If you are installing on a UNIX operating system, you may be asked to run the |
|
|
Click Save to save your configuration information to a file. This information includes port numbers, installation directories, URLs, and component names which you may need to access at a later time. After saving your configuration information, click Finish to dismiss the installer. |
After the installation is complete, you must run the Patch Set Installer for Oracle Portal, Forms, Reports and Discoverer to update your software to the latest version.
For instructions, go to "Applying the Latest Oracle Fusion Middleware Patch Set" in Oracle Fusion Middleware Patching Guide.
After you have patched your software to the latest version (Section 2.7, "Patching Oracle Portal, Forms, Reports and Discoverer"), you are ready to configure your components.
Run the Configuration Tool to create your WebLogic Domain and configure your components.
On UNIX systems:
ORACLE_HOME/bin/config.sh
On Windows systems:
ORACLE_HOME\bin\config.bat
Note:
Make sure the Oracle Portal, Forms, Reports and Discoverer installer is not running; running the installer and Configuration Tool concurrently is not supported.Follow the instructions in Table 2-3 to 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 and Configuration Screens" or click Help to access the online help.
Table 2-3 Configuration Tool Flow
| Screen | When This Screen Appears | Description and Action Required |
|---|---|---|
|
Always |
This page introduces you to the Oracle Fusion Middleware configuration tool. |
|
|
Always |
Verify that your system meets all necessary prerequisites. |
|
|
Always |
Select how you want to configure your domain for your components (create a new domain, extend an existing domain, or expand a cluster). NOTE - If you are creating a WebLogic domain, the domain will be created under the NOTE - If you are extending a domain, only existing domains configured by the Oracle Portal, Forms, Reports, and Discoverer installer that have been patched to the latest version can be extended. For more information about domains, see "WebLogic Server Domain" in Oracle Fusion Middleware Installation Planning Guide. |
|
|
Always |
Select the method in which you want to receive the latest product information and security updates. |
|
|
Always |
Specify the following installation directories:
If you are in a scenario where you are extending a domain or expanding a cluster involving remote machines, you must make sure that the Middleware home and Oracle home directory structures are identical on all the machines. For more information about these directories, see "Oracle Fusion Middleware Directory Structure and Concepts" in Oracle Fusion Middleware Installation Planning Guide. |
|
|
Always |
Select the component(s) you want to configure. Oracle Forms Builder and Reports Builder cannot be installed without Oracle Forms Server and Reports Server, respectively. If you are installing Oracle Discoverer on a Windows operating system, be sure follow the instructions in Section 2.8.1, "Manual Configuration for Oracle Discoverer (Windows Only)" after your software is configured. |
|
|
Always |
Select whether you want automatic or manual port configuration. NOTE - If you choose to use the See "Port Numbers" in Oracle Fusion Middleware Administrator's Guide for more information. |
|
|
Only if Oracle Reports is selected on the Configure Components screen. |
Some features of Oracle Reports Server support retrieving or sending information through a firewall. For these features to function properly, Oracle Reports Server requires the proxy information on this screen. |
|
|
Only if Create Domain or Extend Domain are selected on the Select Domain screen, and only if Oracle Portal or Oracle Discoverer are selected on the Configure Components screen. |
Specify the connection string to your database and Portal and Discoverer schema names and passwords. |
|
|
Only if Create Domain or Extend Domain are selected on the Select Domain screen, and only if Oracle Portal is selected on the Configure Components screen. |
Specify the connection string to your database and Portlet schema names and passwords. |
|
|
Always. |
Specify the connection credentials for your LDAP server. For Oracle Portal, this screen is mandatory. For Oracle Forms, Reports, and Discoverer, configuring an LDAP server is optional. |
|
|
Always |
Verify the information on this screen, then click Install to begin the installation. |
|
|
Always |
This screen shows the progress of the configuration. |
|
|
Always |
Click Save to save your configuration information to a file. This information includes port numbers, installation directories, URLs, and component names which you may need to access at a later time. After saving your configuration information, click Finish to dismiss the installer. |
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\discoverer\lib\disco-config.jar; ORACLE_HOME\oui\jlib\OraInstaller.jar; ORACLE_HOME\opmn\lib\iasprovision.jar -Djava.library.path=ORACLE_HOME\oui\lib\win32 oracle.disco.install.config.DiscoUtil -oraclehome ORACLE_HOME -tnsadmin TNS_ADMIN_DIR
Replace ORACLE_HOME 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.
After you have successfully run the installer and configuration wizard, you can verify the status of your installation by performing any combination of the following:
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".
Check the domain server logs, which are located in the servers directory inside the domain home directory. For example, on UNIX systems:
MW_HOME/user_projects/domains/domain_name/servers/server_name
On Windows systems:
MW_HOME\user_projects\domains\domain_name\servers\server_name
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
The Installation Complete contains URLs that can be used to access your installed and configured products, as shown in Table 2-4:
Table 2-4 Oracle Portal, Forms, Reports, and Discoverer Product URLs
| Product or Component | URL |
|---|---|
|
Administration Server Console |
|
|
Enterprise Manager Console |
|
|
Enterprise Manager Agent |
|
|
Oracle Portal |
|
|
Oracle Forms |
|
|
Oracle Reports |
|
|
Oracle Discoverer Viewer |
|