Oracle Fusion Middleware Support of 64-bit JDK

Installing Oracle Portal, Forms, Reports and Discoverer 2-5

2.1.6 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.7 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 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.8 Installing in a Middleware Home with Existing Fusion Middleware Products

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: ■ Section 2.1.8.1, Setting the StartScriptEnabled Property for Node Manager ■ Section 2.1.8.2, Managing Potential Port Conflicts

2.1.8.1 Setting the StartScriptEnabled Property for Node Manager

To properly set the StartScriptEnabled property: 1. Navigate to the WebLogic_Home commonnodemanager on UNIX operating systems or WebLogic_Home \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.

2.1.8.2 Managing Potential Port Conflicts

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