How To Install Oracle Reports Builder 12c

[Magin Sriubas]

Beforeyou begin installing Oracle Forms and Reports, it would be helpful if you understand the installation requirements. To prepare for your Oracle Forms and Reports installation, verify that your system meets the basic requirements, then obtain the correct installation software.

Make sure that you install your product on a supported hardware and software configuration. See the certification document for your release on the Oracle Fusion Middleware Supported System Configurations page.

Oracle has tested and verified the performance of your product on all certified systems and environments. Whenever new certifications are released, they are added to the certification document right away. New certifications can be released at any time. Therefore, the certification documents are kept outside the documentation libraries and are available on Oracle Technology Network.

Oracle recommends that you use the Oracle Fusion Middleware System Requirements and Specifications document to verify that the certification requirements are met. For example, if the certification document indicates that your product is certified for installation on 64-Bit Oracle Linux 6.5, use this document to verify that your system meets the required minimum specifications. These include disk space, available memory, specific platform packages and patches, and other operating system-specific requirements. System requirements can change in the future. Therefore, the system requirement documents are kept outside of the documentation libraries and are available on Oracle Technology Network.

To learn how to install and run multiple Fusion Middleware products from the same release or mixed releases with each other, see Oracle Fusion Middleware 12c Interoperability and Compatibility in Understanding Interoperability and Compatibility.

If you are new to Oracle Fusion Middleware, see About Key Oracle Fusion Middleware Concepts in Understanding Oracle Fusion Middleware to familiarize yourself with some concepts and terminology you will encounter.

The installer for a certified version of Oracle WebLogic Server (FMW Infrastructure). Make sure you refer to the certification document, as described in Reviewing Certification, System, and Interoperability Requirements, to determine which version of Oracle WebLogic Server (FMW Infrastructure) you should obtain.

To install Oracle Forms and Reports on different servers, you must perform manual configuration in order for these two products to be able to communicate properly with each other, as described in Communication Between Reports and Forms When Installed on Different Instances.

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 other user require access to particular files or executables, the UNIX sudo command (or other similar command) should be considered in lieu of changing file permissions.

On Windows operating systems, the user must be a member of the Windows "Admin" group. This gives the user the proper permissions required to start and stop processes after the installation, including the Builders.

The Oracle Fusion Middleware certification document for a specific release provides information about the minimum required Oracle WebLogic Server (FMW Infrastructure) version. See the certification document for your release on the Oracle Fusion Middleware Supported System Configurations page.

If you are installing Oracle Reports on Microsoft Windows operating system, Oracle home directory path should not be not too long, as described in Verify Environment Variable Lengths for Oracle Reports (Windows Only)

Follow the Oracle WebLogic Server (FMW Infrastructure) installation instructions, as described in Installing Oracle WebLogic Server and Coherence for WebLogic Server MT. The WebLogic Server installation must be completed so that an Oracle 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 Oracle Forms and Reports on a Microsoft Windows operating system, you must ensure that the Node Manager utility that was installed with Oracle WebLogic Server is stopped before you begin the installation:

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:

Your Oracle Forms and Reports installation can be protected with Identity Management (see Secure Oracle Forms and Reports With Identity Management). If you choose to secure your Oracle Forms and Reports with Oracle Internet Directory and Oracle Access Manager, you must download and install these products if you do not already have them.

Oracle Identity and Access Management must be installed in a separate Oracle home directory from your Oracle Forms and Reports installation (see Installing Oracle Forms and Reports in a New Oracle home). For performance reasons, Oracle recommends that Oracle Forms and Reports is installed on a separate machine from your Oracle Identity Management product.

The Forms and Reports 12c Disk-1 compressed installer files folder for IBM AIX operating system does not include the rootpre.sh script files. So, you do not need to run the rootpre.sh script as the root user before starting the installer. The rootpre.sh script was used in pervious version of FMW installer to load postwait driver pw-syscall.

Some platforms may have multiple download files or disks, such as Disk-1 and Disk-2. You should extract all the files, for example executable .exe file, from the downloaded compressed (zipped) folder. If the downloaded compressed (zipped) folder contains another compressed (zipped) file, you should not extract that compressed file contained within the original compressed (zipped) folder. You should store all the extracted files from the compressed folder in the same directory before starting the installer.

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. See Installation Log Files for information about 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.

If you do not want 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. For example, a typical oraInst.loc file would contain the following:

Follow these instructions to install Oracle Forms and Reports using Oracle Universal Installer. After invoking Oracle Universal Installer as described in Starting the Oracle Forms and Reports Installer:

Click Next when you have specified your credentials. The Checking Prerequisites dialog window appears. It shows the progress of prerequisites checking. Click OK, when the database checking has passed without errors, to dismiss the dialog window, and go to the next screen.

To complete the configuration, Windows DOS shells must be run with Administrator permissions and Unix shells must be owned by the same user who performed the installation (for example, oracle). Failure to follow this instruction may result in the configuration failing silently.

On Microsoft Windows, the DOS shell used to start these servers the first time must have Administrator permissions. To enable an Administrator shell session, right-click the Command Prompt shortcut and select Run as Administrator. The shell that opens will indicate that it has Administrator privileges in its title bar.

Click Next. The Administrator Account screen appears. Enter the WebLogic Domain administration username and password. This information will be needed to access WebLogic Server Control and Fusion Middleware Control.

Click Next. The Domain Mode and JDK screen appears. Select the Domain Mode (either Development or Production). For our purposes, select Production. Leave the default JDK selection as it appears, unless using another version of the JDK desired.

Enter the Schema Owner and Schema Password. Schema Owner value refers to the schemas created while running the Repository Creation Utility (RCU) in a previous step of the installation process. The trailing _STB should be included along with the prefix value chosen at the time RCU was run previously. For example, if the prefix you provided during the Repository creation was DEMO then the entry for Schema Owner will be DEMO_STB.

Click Next. The Managed Servers screen appears. Create WLS_REPORTS. Verify that the Server Groups is set to REPORTS-APP-SERVERS. The Listen address is All Local Addresses. Add WLS_REPORTS to reports_cluster.

Click Next. The Assign Servers to Clusters screen appears. The default values will be appropriate for most cases. However, if new managed servers were added in the previous step, they should be added to the cluster here.

3a8082e126