Skip Headers
Oracle® Fusion Middleware Installation Guide for Oracle Forms and Reports
11g Release 2 (11.1.2)

Part Number E23960-02
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 Installing and Configuring Oracle Forms and Reports

This chapter describes how to install and configure Oracle Forms and Reports.

The following topics are covered:

2.1 Preparing to Install

Before you begin, read this section carefully to make sure that your environment and other software needs are met prior to installing Oracle Forms and Reports.

2.1.1 Reviewing System Requirements and Specifications

Before performing any installation you should read the system requirements documentation to ensure that your environment meets the minimum installation requirements for the products you are installing.

The system requirements document covers information such as hardware and software requirements, database schema requirements, minimum disk space and memory requirements, and required system libraries, packages, or patches. This document can be found on the Oracle Fusion Middleware System Requirements and Specifications page.

2.1.2 Reviewing Certification Information

Before performing any upgrade or installation you should read the Oracle Fusion Middleware certification document for your particular release. This document contains certification information related to supported 32-bit and 64-bit operating systems, databases, Oracle WebLogic Servers, web servers, LDAP servers, adapters, IPv6, JDKs, and third-party products. It is located on the Oracle Fusion Middleware Supported System Configurations page.

2.1.3 Reviewing Interoperability and Compatibility

Before performing any upgrade or installation you should read the Oracle Fusion Middleware Interoperability and Compatibility Guide. This document contains important information regarding the ability of Oracle Fusion Middleware products to function with previous versions of other Oracle Fusion Middleware, Oracle, or third-party products. This information is applicable to both new Oracle Fusion Middleware users and existing users who are upgrading their existing environment.

Note:

The Oracle Fusion Middleware Interoperability and Compatibility Guide is located in the 11g Release 1 documentation libraries and is not available in the 11g Release 2 (11.1.2) documentation library. However, the concepts in the guide are applicable for both releases.

2.1.4 Understanding Oracle Fusion Middleware Concepts

If you are new to Oracle Fusion Middleware, you should read Oracle Fusion Middleware Concepts to familiarize yourself with some of the concepts and terminology you will encounter.

Note:

The Oracle Fusion Middleware Concepts document is located in the 11g Release 1 documentation libraries and is not available in the 11g Release 2 (11.1.2) documentation library. However, the concepts in the guide are applicable for both releases.

2.1.5 Obtaining the Oracle Fusion Middleware Software

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 and configure Oracle Forms and Reports, you will need to download the following software:

  • The installer for a certified version of Oracle WebLogic Server. Make sure you refer to the certification document (see Section 2.1.2, "Reviewing Certification Information") to determine which version of Oracle WebLogic Server you should obtain.

  • The installer for Oracle Forms and Reports.

    If you are want to install the 32-bit version of Oracle Forms and Reports on a 64-bit Windows operating system, be sure to read "Installing 32-Bit Oracle Forms and Reports on 64-Bit Windows Operating Systems" in the Oracle Fusion Middleware System Requirements and Specifications document.

  • If you want to secure your Oracle Forms and Reports installation with Identity Management, you can also download Oracle Internet Directory with Oracle Access Management.

Make a note of the directory where you download each installer; you will need this information when it is time to run the installer for each product.

2.1.6 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.7 Installing Oracle Forms and Reports in a New Middleware Home

Oracle Forms and Reports must be installed inside a Middleware home directory, which is created when Oracle WebLogic Server is installed.

Oracle Forms and Reports must be installed in its own Middleware home directory that it does not share with any other Oracle Fusion Middleware products.

2.1.8 Installing Oracle Forms and Reports as a Non-Default User

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.

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.

2.2 Installing Oracle WebLogic Server

Oracle Forms and Reports requires Oracle WebLogic Server, which creates the Middleware home directory during installation. This section contains the following topics:

Make sure you read the Oracle Fusion Middleware certification document for your particular release to determine the minimum version of Oracle WebLogic Server that is required. This document is located on the Oracle Fusion Middleware Supported System Configurations page.

2.2.1 Planning Your Middleware Home Location for Oracle Reports (Windows Only)

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 D.3, "Verifying Environment Variable Lengths for Oracle Reports (Windows Only)".

2.2.2 Downloading the Correct Installer for your Operating System

See Section 2.1.5, "Obtaining the Oracle Fusion Middleware Software" for information on where to obtain your Oracle WebLogic Server installer.

2.2.3 Finding Oracle WebLogic Server Installation Instructions

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.2.4, "Stopping Node Manager Before Installing Oracle Forms and Reports (Windows Only)" after your Oracle WebLogic Server installation is complete.

2.2.4 Stopping Node Manager Before Installing Oracle Forms and Reports (Windows Only)

If you are installing Oracle Forms and Reports 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 begin the installation:

  1. Verify the Oracle WebLogic Server Node Manager utility is stopped. If it is running, kill the process.

  2. Determine if the nodemanager.properties file is present in the WebLogic_Home\common\nodemanager directory.

    1. If the nodemanager.properties file is not present, continue installing Oracle Forms and Reports.

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

2.3 Installing Oracle Identity and Access Management

Your Oracle Forms and Reports installation can be protected with Identity Management (see Section 1.4, "Securing 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 Middleware home directory from your Oracle Forms and Reports installation (see Section 2.1.7, "Installing Oracle Forms and Reports in a New Middleware Home"). For performance reasons, Oracle recommends that Oracle Forms and Reports is installed on a separate machine from your Oracle Identity Management product.

Installation instructions for Oracle Identity and Access Management can be found in "Installing and Configuring Oracle Identity and Access Management (11.1.1.5.0)" in Oracle Fusion Middleware Installation Guide for Oracle Identity Management.

Note:

If you configure Oracle Access Manager to use secure (SSL) connections, you must perform the manual steps described in Section 2.5, "Configuring Oracle Forms and Reports with Oracle Access Manager in Secure Mode" after both Oracle Access Manager and Oracle Forms and Reports are installed.

2.4 Installing Oracle Forms and Reports

This section contains information and instructions for installing Oracle Forms and Reports. The following topics are covered:

2.4.1 Running the rootpre.sh Script on IBM AIX Operating Systems

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.

2.4.2 Starting the Oracle Forms and Reports Installer

To start the installer, go to the directory where you downloaded the Oracle Forms and Reports installer and unpacked the archive file. Switch to the Disk1 directory.

On Windows operating systems, double-click on the setup.exe file in the Disk1 directory.

On UNIX operating systems, use the runInstaller command:

cd unpacked_archive_directory/Disk1
./runInstaller

2.4.3 Viewing the 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.4.4 Configuring Your Oracle Inventory (UNIX Only)

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.

Use the inventory screens in Table 2-1 to configure the inventory directory and group information. For more help, select the screen name in the table, or click the Help button in the GUI.

Table 2-1 Inventory Directory and Group Screens

Screen Description

Specify Inventory Directory

Specify the Oracle inventory directory and group permissions for that directory. The group must have write permissions to the Oracle inventory directory.

Inventory Location Confirmation

Run the createCentralInventory.sh script as root.


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

inventory_loc=/home/username/oraInventory
inst_group=group

Then, you can start the installer and point to the oraInst.loc file. For example:

./runInstaller -invPtrLoc location_of_oraInst.loc_file

2.4.5 Following the Installation Screens and Instructions

Follow the instructions in Table 2-2 to install and configure Oracle Forms and Reports.

Note:

If you choose the Install Software - Do Not Configure option, follow the instructions in this flowchart to install the software, then follow the instruction in Section 2.4.6, "Running the Configuration Tool for Oracle Forms and Reports" to configure your components.

If you need additional help with any of the screens, click on the screen name in the "Screen" column in Table 2-2, or click Help on the screen to access the online help.

A flowchart describing the order in which the screens appear is also available in Section A.1, "Flowchart of Oracle Forms and Reports Installation and Configuration Screens".

Table 2-2 Oracle Forms and Reports Installation and Configuration Screens

Screen When This Screen Appears Description

Welcome

Always.

This page introduces you to the Oracle Fusion Middleware installer.

Software Updates

Always.

Select the method you want to use for obtaining software updates, or select Skip Software Updates if you do not want to get updates.

If updates are found, the installer will automatically attempt to apply them at this point; make sure that the server you are using to perform the installation is connected to the Internet.

Some updates will require that the installer be restarted; if this happens, the Software Updates screen will not be seen the next time.

Installation Type

Always.

Choose the installation type you want to use.

If you choose the Install Software - Do Not Configure type, you can follow the instructions in this table to install your software; you will only see the screens marked with "Always" in the "When This Screen Appears" column. After the installation is completed, but must run the configuration tool to configure your components, as described in Section 2.4.6, "Running the Configuration Tool for Oracle Forms and Reports".

Prerequisite Checks

Always.

Verify that your system meets all necessary prerequisites.

Installation Location

Always.

Specify the following installation directories:

  • Middleware home

  • Oracle home

  • WebLogic Server home

  • Oracle Instance location

  • Oracle Instance name

If you selected Install Software - Do Not Configure on the Installation Type screen, you will only be asked for the Middleware home and Oracle home locations.

Configuration Type

If Install and Configure is selected on Installation Type.

Specify whether you want to configure your components for deployment (includes Oracle HTTP Server and Oracle Enterprise Manager) or development (does not include Oracle HTTP Server and Oracle Enterprise Manager.

See Section 1.3, "Understanding Oracle Forms and Reports Configuration Types" for more information.

Select Domain

If Install and Configure is selected on Installation Type.

Select how you want to configure your domain for your components (create a new domain, extend an existing domain, or expand a cluster).

NOTE: You can only extend a domain or expand a cluster that was created by the Oracle Forms and Reports installer for this release (11g Release 2 - 11.1.2).

Security Updates

Always.

Select the method in which you want to receive the latest product information and security updates.

Configure Components

If Install and Configure is selected on Installation Type.

Select the components you want to configure.

Oracle Forms Builder and Reports Builder cannot be installed without Oracle Forms Server and Reports Server, respectively.

If you selected Configure for Development on Configuration Type, Oracle HTTP Server and Oracle Enterprise Manager will not appear on this screen.

Configure Ports

If Install and Configure is selected on Installation Type.

Select the method you want to use for port configuration.

Proxy Details

If Oracle Reports is selected on Configure Components.

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.

Application Identity Store

If Oracle HTTP Server is selected on Configure Components.

Select Use Application Identity Store to secure your installation with Oracle Identity Management, and provide the credentials to your Oracle Internet Directory server.

You can skip this screen by de-selecting Use Application Identity Store. If you decide you want to add security with Oracle Identity Management later, refer to the information in Oracle Fusion Middleware Forms Services Deployment Guide.

Access Control

If Use Application Identity Store is selected on Application Identity Store.

Select which product you want to use for authentication:

  • If you select Use Oracle Access Manager, provide the login credentials to your Oracle Access Manager server.

  • If you select Use Oracle Single Sign-On, you do not need to enter any additional credentials; the credentials provided on the Application Identity Store screen will be used.

Installation Summary

Always.

Verify the information on this screen, then click Install to begin the installation.

Installation Progress

Always.

This screen shows the progress of the installation.

If you are installing on a UNIX operating system, you may be asked to run the ORACLE_HOME/oracleRoot.sh script to set up the proper file and directory permissions.

Configuration Progress

If Install and Configure is selected on Installation Type.

This screen shows the progress of the configuration.

Installation Complete

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.


2.4.6 Running the Configuration Tool for Oracle Forms and Reports

If you selected the Install Software - Do Not Configure option on the Installation Type screen, you must manually run the configuration tool to configure your components after they have been installed. Doing so does the following:

  • If you already have an existing WebLogic Server domain, your components can be associated with this existing domain.

  • If you are creating a new domain, your components can be associated with the newly created domain.

  • Oracle Instances are created for your system components.

2.4.6.1 Starting the Configuration Tool

The configuration tool is located in the bin directory inside your Oracle home.

On UNIX operating systems:

ORACLE_HOME/bin/config.sh

On Windows operating systems:

ORACLE_HOME\bin\config.bat

Note:

Make sure the Oracle Forms and Reports installer is not running; running the installer and configuration tool concurrently is not supported.

2.4.6.2 Following the Configuration Tool Screens and Instructions

After you have started the configuration tool, follow the instructions in Table 2-3.

If you need additional help with any of the screens, click on the screen name in the "Screen" column in Table 2-3, or click Help on the screen to access the online help.

A flowchart describing the order in which the screens appear is also available in Section A.1, "Flowchart of Oracle Forms and Reports Installation and Configuration Screens".

Table 2-3 Oracle Forms and Reports Configuration Tool Screens

Screen When This Screen Appears Description

Welcome

Always.

This page introduces you to the Oracle Forms and Reports configuration tool.

Configuration Type

Always

Specify whether you want to configure your components for deployment (includes Oracle HTTP Server and Oracle Enterprise Manager) or development (does not include Oracle HTTP Server and Oracle Enterprise Manager.

Security Updates

Always.

Select the method in which you want to receive the latest product information and security updates.

Installation Location

Always.

Specify the following installation directories:

  • WebLogic Server home

  • Oracle Instance location

  • Oracle Instance name

Select Domain

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: You can only extend a domain or expand a cluster that was created by the Oracle Forms and Reports installer for this release (11g Release 2 - 11.1.2).

Configure Components

Always.

Select the components you want to configure.

Oracle Forms Builder and Reports Builder cannot be installed without Oracle Forms Server and Reports Server, respectively.

If you selected Configure for Development on Configuration Type, Oracle HTTP Server and Oracle Enterprise Manager will not appear on this screen.

Configure Ports

Always.

Select the method you want to use for port configuration.

Proxy Details

If Oracle Reports is selected on Configure Components.

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.

Application Identity Store

If Oracle HTTP Server is selected on Configure Components.

Select Use Application Identity Store to secure your installation with Oracle Identity Management, and provide the credentials to your Oracle Internet Directory server.

You can skip this screen by de-selecting Use Application Identity Store. If you decide you want to add security with Oracle Identity Management later, refer to the information in Oracle Fusion Middleware Forms Services Deployment Guide.

Access Control

If Use Application Identity Store is selected on Application Identity Store.

Select which product you want to use for authentication:

  • If you select Use Oracle Access Manager, provide the login credentials to your Oracle Access Manager server.

  • If you select Use Oracle Single Sign-On, you do not need to enter any additional credentials; the credentials provided on the Application Identity Store screen will be used.

Installation Summary

Always.

Verify the information on this screen, then click Configure to begin the configuration.

Configuration Progress

Always.

This screen shows the progress of the configuration.

Installation Complete

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.


2.5 Configuring Oracle Forms and Reports with Oracle Access Manager in Secure Mode

If you have installed and configured Oracle Access Manager to use secure (SSL) connections, you must perform the manual steps in this section after Oracle Access Manager and Oracle Forms and Reports are installed:

  1. Preparing the OSSORequest.xml Input File for the RREG Toolkit

  2. Preparing the OSSORequest.xml Input File for the RREG Toolkit

  3. Running the RREG Tool in In-Band Mode for Configuration

  4. Preparing Your Runtime Environment

2.5.1 Setting Environment Variables to Point to the RREG Toolkit

The RREG toolkit is located in the oam directory inside the Oracle home after Oracle Forms and Reports is installed.

Set the following environment variables:

  • Set OAM_REG_HOME to ORACLE_HOME/oam/server/rreg/client (on UNIX operating systems) or ORACLE_HOME\oam\server\rreg\client (on Windows operating systems).

  • Set JAVA_HOME to ORACLE_HOME/jdk (on UNIX operating systems) or ORACLE_HOME\jdk (on Windows operating systems).

2.5.2 Preparing the OSSORequest.xml Input File for the RREG Toolkit

Perform the steps in this section to create the OSSORequest.xml input file for the RREG toolkit:

  1. If not already present, create an input and output directory in ORACLE_HOME/oam/server/rreg/client (on UNIX operating systems) or ORACLE_HOME\oam\server\rreg\client (on Windows operating systems).

  2. Create the OSSORequest.xml file in the input folder. Table 2-4 shows the values that must be set:

    Table 2-4 Parameters for the OSSORequest.xml Input File

    Parameter Description

    Server Address

    The URL for your Administration Server. For example:

    http://admin_server_host:admin_server_port
    

    or

    https://admin_server_host:admin_server_port
    

    Agent Name

    The unique name of your OSSO_AGENT.

    Agent Base URL

    The URL for your web server (Oracle HTTP Server). For example:

    http://web_server_host:web_server_port
    

    or

    https://web_server_host:web_server_port
    

    Host Identified

    The unique name of your OSSO_AGENT.

    Application Domain

    The unique name of your OSSO_AGENT.


Below is a sample OSSORequest.xml input file:

<?xml version="1.0" encoding="UTF-8"?>
<!--
Copyright (c) 2009, 2010, Oracle and/or its affiliates. All rights reserved. NAME: OSSORequest.xml - Template for OSSO Agent Registration Request file DESCRIPTION: Modify with specific values and pass file as input to the tool
-->
<OSSORegRequest>
   <serverAddress>https://ExampleAdminServer:7001</serverAddress>
   <hostIdentifier>110919123715_RREG_OSSO</hostIdentifier>
   <agentName>110919123715_RREG_OSSO</agentName>
   <agentBaseUrl>http://ExampleWebServer:8888</agentBaseUrl>
   <applicationDomain>110919123715_RREG_OSSO</applicationDomain>
   <autoCreatePolicy>true</autoCreatePolicy>
   <ssoServerVersion>v3.0</ssoServerVersion>
   <oracleHomePath>$ORACLE_HOME</oracleHomePath>
   <virtualHost></virtualHost>
   <updateMode></updateMode>
   <adminInfo></adminInfo>
   <adminId></adminId>
</OSSORegRequest>

2.5.3 Running the RREG Tool in In-Band Mode for Configuration

Perform the following to create the osso.conf file in the output folder in your OAM_REG_HOME directory:

  1. Go to the OAM_REG_HOME directory.

  2. Run the following command.

    On UNIX operating systems:

    java -jar rreg-toolkit.jar inband input/OSSORequest.xml
    

    On Windows operating systems:

    java -jar rreg-toolkit.jar inband input\OSSORequest.xml
    

2.5.4 Preparing Your Runtime Environment

Perform the following to prepare your runtime environment.

  1. Copy the osso.conf file from OAM_REG_HOME/output (on UNIX operating systems) or OAM_REG_HOME\output (on Windows operating systems) to your Oracle HTTP Server location at INSTANCE_HOME/config/OHS/instance_name (on UNIX operating systems) or INSTANCE_HOME\config\OHS\instance_name (on Windows operating systems).

  2. Copy the mod_osso.conf file from INSTANCE_HOME/config/OHS/instance_name/disabled (on UNIX operating systems) or INSTANCE_HOME\config\OHS\instance_name\disabled (on Windows operating systems) to INSTANCE_HOME/config/OHS/instance_name/moduleconf (on UNIX operating systems) or INSTANCE_HOME\config\OHS\instance_name\moduleconf (on Windows operating systems).

  3. Copy the following contents to the mod_osso.conf file in the moduleconf folder. Ensure that the OssoConfigFile location points to the appropriate osso.conf file:

    LoadModule osso_module ${ORACLE_HOME}/ohs/modules/mod_osso.so
    <IfModule mod_osso.c>
       OssoIpCheck off
       OssoIdleTimeout off
       OssoConfigFile  INSTANCE_HOME/config/OHS/instance_name/osso.conf
       OssoSecureCookies Off
       OssoHttpOnly Off
    #
    # Insert Protected Resources: (see Notes below for
    # how to protect resources)#
    #
    # 1. Here's what you need to add to protect a resource,
    #    e.g. <ApacheServerRoot>/htdocs/private:
    #    <Location /reports/rwservlet>
            require valid-user
            AuthType Osso
         </Location>
    </IfModule>
    #
    # If you would like to have short hostnames redirected to
    # fully qualified hostnames to allow clients that need
    # authentication via mod_osso to be able to enter short
    # hostnames into their browsers uncomment out the following
    # lines
    #
    #PerlModule Apache::ShortHostnameRedirect
    #PerlHeaderParserHandler Apache::ShortHostnameRedirect
    
  4. Go to the bin directory inside your Oracle HTTP Server Instance home.

    1. Run the following command to stop Oracle HTTP Server:

      opmnctl stopall
      
    2. Run one of the following commands to start Oracle HTTP Server:

      opmnctl startall
      opmnctl startproc ias-component=instance_name
      
  5. Use a browser to access the Oracle Forms or Reports URLs and you should be redirected to the runtime server and prompted for valid credentials.