This chapter describes how to install and configure Oracle Portal, Forms, Reports and Discoverer.
The following topics are covered:
Make sure you have read "Before you Begin" in Oracle Fusion Middleware Installation Planning Guide before you install Oracle Portal, Forms, Reports and Discoverer.
Note:
If you are installing the 32-bit version of the product, the system on which you are installing must also be a supported 32-bit system. Installing a 32-bit version of the product on a 64-bit system is not supported.The following topics are covered in this section:
Section 2.1.1, "Installing and Configuring a Database and Database Schemas"
Section 2.1.3, "Oracle Fusion Middleware Support of 64-bit JDK"
Section 2.1.5, "Upgrading Oracle Web Agent (OWA) for Oracle Portal"
Section 2.1.6, "Installing Oracle Forms and Oracle Reports on Separate Servers"
Section 2.1.7, "Installing in a Middleware Home with Existing Fusion Middleware Products"
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.
Note:
Although IBM DB2 and Microsoft SQL Server databases are supported in the latest release, the schemas for Oracle Portal and Oracle Discoverer are only supported on Oracle databases. You must create the schemas for Oracle Portal and Oracle Discoverer on a certified Oracle database.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.
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.1.2.1, "Finding Oracle WebLogic Server Installation Instructions"
Section 2.1.2.2, "Planning Your Middleware Home Location for Oracle Reports (Windows Only)"
For instructions, see "Install an Application Server" in Oracle Fusion Middleware Installation Planning Guide.
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 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)".
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
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 System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document for information on the platforms that support a 64-bit JDK. This document is available on the Oracle Fusion Middleware Supported System Configurations page:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.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.
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.2.3) with Oracle Single Sign-On 10g (10.1.2.3)
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.2.3)
Oracle Internet Directory 11g (11.1.1) with Oracle Single Sign-On 10g (10.1.4.3)
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.This section contains information for the following scenarios:
Section 2.1.4.1, "Using Your Existing Oracle Internet Directory 10g Environment"
Section 2.1.4.2, "Upgrading Oracle Internet Directory 10g to 11g"
Section 2.1.4.3, "Building a New Oracle Identity Management Architecture"
If you already have a supported combination of Oracle Internet Directory 10g in place, you can leave your existing architecture as-is, or you can upgrade to the latest available 11g release. In either case, you will be able to configure Oracle Portal, Forms, Reports and Discoverer with your Oracle Internet Directory and Single Sign-On configuration.
To upgrade your existing Oracle Internet Directory 10g environment, see "Upgrading Your Oracle Internet Directory Environment" in Oracle Fusion Middleware Upgrade Guide for Oracle Identity Management.
To build a new Oracle Identity Management architecture containing Oracle Internet Directory 11g (11.1.1) with Oracle Single Sign-On 10g (10.1.4.3), refer to the following documentation:
"How to Install SSO with Oracle Fusion Middleware 11g" (Doc ID 1069426.1) on My Oracle Support.
"Installing Oracle Single Sign-On and Oracle Delegated Administration Services Against Oracle Internet Directory" in Oracle Fusion Middleware Installation Guide for Oracle Identity Management.
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:
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.
This section contains important information if you are installing Oracle Portal, Forms, Reports and Discoverer into a Middleware home directory that already contains a Fusion Middleware product.
The following topics are covered:
To properly set the StartScriptEnabled property:
Navigate to the WebLogic_Home/common/nodemanager (on UNIX operating systems) or WebLogic_Home\common\nodemanager (on Windows operating systems) directory.
Edit the nodemanager.properties file and set the StartScriptEnabled property as follows:
StartScriptEnabled=true
Restart Node Manager.
The potential for port conflicts exists when you are installing Oracle Portal, Forms, Reports and Discoverer into a Middleware home with existing Fusion Middleware products, and the existing Oracle instance and WebLogic domain are shut down when you arrive at the Configure Ports Screen during your installation.
If you choose Automatic Port Configuration, the ports in your domain are allocated from a default range of port numbers. If your existing Oracle instances and domain are running, the configuration tool recognizes which ports are already actively in use and will avoid allocating these ports to the Oracle instance and domain you are currently creating with your installation.
However, if your existing instances and domains are shut down, the configuration tool will assume that the initial default port numbers are available and will assign these port numbers to the instance and domain you are creating.
In such cases, conflicts with the following ports can arise:
The OPMN local and remote port values.
The WebLogic Domain Administration Server port value.
These port conflicts mean that OPMN and WebLogic Administration Server can only start for one of the configurations under the Middleware home.
To proactively prevent this problem, you should leave your existing Oracle instances and WebLogic Domain up and running as you install your software and create your new Oracle instance and domain. The configuration tool will recognize which ports are already in use and will avoid allocating these ports to your new Oracle instance and WebLogic Domain.
Alternatively, you can select Specify Ports using Configuration File on the Configure Ports Screen and manually keep track of your port numbers in a staticports.ini file.
The Oracle Portal, Forms, Reports and Discoverer installer provides two installation options:
Install and Configure
This option installs the product binaries in an Oracle home directory and creates and configures a working instance in an Oracle instance directory. The common product binaries are also copied to the oracle_common directory. After this is complete, you should be able to begin configuring and managing your products using the Administration Console or Enterprise Manager.
Note:
If you choose this installation type on a Windows operating system, there are manual configuration steps required for Oracle Discoverer. For more information, see Section 2.3.6, "Manual Configuration for Oracle Discoverer (Windows Only)".Install Software - Do Not Configure
This option only installs the software binaries in an Oracle home directory and the common product binaries in the oracle_common 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.
To install the latest Oracle Portal, Forms, Reports and Discoverer software, you must choose the Install Software - Do Not Configure installation type, as described in Section 1.2, "Installation Roadmap".
This section contains information and instructions for installing Oracle Portal, Forms, Reports and Discoverer. The following topics are covered:
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.
On UNIX operating systems, the installation of Fusion Middleware products is owned and controlled as a known user (for example, "oracle"). The file permissions associated with this installation are configured to ensure the highest level of security possible, which by default are 700 (meaning all files are owned and accessible by the owner only).
Changing the default permissions settings will reduce the security of the installation and possibly your system. Therefore, making such a change is not recommended. If access to particular files or executables is required by other users, the UNIX sudo command (or other similar command) should be considered in lieu of changing file permissions.
Refer to your UNIX operating system Administrator's Guide or contact your operating system vendor if you need further assistance.
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
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
| No. | Screen | Description and Action Required |
|---|---|---|
|
1 |
Specify the Oracle inventory directory and group permissions for that directory. The group must have write permissions to the Oracle inventory directory. Click OK to continue. |
|
|
2 |
Run the Click OK to continue. |
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 this section to install and configure the latest Oracle Portal, Forms, Reports and Discoverer software.
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 Screens" or click Help to access the online help.
Table 2-2 Installation Flow for Install Only Option
| No. | Screen | Description and Action Required |
|---|---|---|
|
1 |
Click Next to continue. |
|
|
2 |
Select Install Software - Do Not Configure. Click Next to continue. |
|
|
3 |
Click Next to continue. |
|
|
4 |
Specify the Middleware home and Oracle home locations. For more information about these directories, see "Oracle Fusion Middleware Directory Structure and Concepts" in Oracle Fusion Middleware Installation Planning Guide. Click Next to continue. |
|
|
5 |
Provide your E-mail address if you want to be informed of the latest product issues by E-mail. Provide your E-mail address and My Oracle Support password if you want to be informed of the latest product issues through the My Oracle Support web site. Click Next to continue. |
|
|
6 |
Verify the information on this screen. Click Install to begin the installation. |
|
|
7 |
If you are installing on a UNIX operating system, you may be asked to run the Click Next to continue. |
|
|
8 |
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 with the Patch Set Installers" in Oracle Fusion Middleware Patching Guide.
After you have patched your software to the latest version, you are ready to configure your components. Go to Section 2.3.5.3, "Configuring Your Components" for instructions.
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.After you have started the Configuration Tool, follow the instructions in Table 2-3.
Table 2-3 Configuration Tool Flow
| No. | Screen | When Does This Screen Appear? | Description and Action Required |
|---|---|---|---|
|
1 |
Always |
Click Next to continue. |
|
|
2 |
Always |
Click Next to continue. |
|
|
3 |
Always |
Select whether you want to create a new domain, extend an existing domain, or expand an existing cluster. NOTE - Only existing domains configured by the Oracle Portal, Forms, Reports, and Discoverer installer can be extended. For more information about domains, see "WebLogic Server Domain" in Oracle Fusion Middleware Installation Planning Guide. Click Next to continue. |
|
|
4 |
Always |
Provide your E-mail address if you want to be informed of the latest product issues by E-mail. Provide your E-mail address and My Oracle Support password if you want to be informed of the latest product issues through the My Oracle Support web site. Click Next to continue. |
|
|
5 |
Always |
Specify the WebLogic Server directory, Oracle Instance location, and Oracle Instance name. 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. Click Next to continue. |
|
|
6 |
Always |
Select the component(s) you want to configure. Click Next to continue. |
|
|
7 |
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. Click Next to continue. |
|
|
8 |
Only if Oracle Reports is selected on the Configure Components Screen. |
Specify whether or not you want to use a proxy server. Click Next to continue. |
|
|
9 |
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. Click Next to continue. |
|
|
10 |
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. Click Next to continue. |
|
|
11 |
If any one of Oracle Portal, Forms, Reports, and Discoverer is selected on the Configure Components Screen. |
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. Click Next to continue. |
|
|
12 |
Always |
Verify the information on this screen. Click Configure to begin the configuration. |
|
|
13 |
Always |
Click Next to continue. |
|
|
14 |
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. |
When configuration is complete, go to Section 2.4, "Verifying the Installation".
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.
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:
ORACLE_HOME/user_projects/domains/domain_name/servers/server_name
On Windows systems:
ORACLE_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 Screen 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 |
|