1. Working with Oracle Forms
  2. Integration
  3. Using Forms Services with Oracle Access Manager
  4. Post installation Configuration

Post installation Configuration

This section describes specific post installation steps.

These steps are required to perform depending on the choices made in Setup Process.

The following sections are included:

Configuring Forms J2EE application with Oracle Internet Directory

The topics describes how to configure a Forms application to work with Oracle Internet Directory.

To access the Associate/Disassociate page:

  1. Start Fusion Middleware Control.

  2. Navigate to the Forms Home page.

  3. From the Forms menu, select Forms Runtime LDAP Associations.

    The Forms Runtime LDAP Associations page is displayed.

Figure -33 Forms Runtime LDAP Associations

Description of Figure -33 follows
Description of "Figure -33 Forms Runtime LDAP Associations"

To associate OID Host with a Forms Application:

  1. To associate an Oracle Internet Directory host with a Forms application for the first time, from the Associate/Disassociate OID page, select the Forms application. Click Associate.

    The Associate dialog appears.

  2. Enter the Oracle Internet Directory Host details as described in the following table.

  3. Click Associate.

    The Associate/Disassociate OID page reappears.

    Table -29 Oracle Internet Directory Host Details

    Parameter Description

    OID Host

    Select the Oracle Internet Directory Host from the list or select New Oracle Internet Directory (OID) host to add new host details.

    New OID host

    Host name of the Oracle Internet Directory server. This field is enabled if you have selected to add new Oracle Internet Directory (OID) Host.

    New OID Port

    Port number on which Oracle Internet Directory is listening. This field is enabled if you have selected to add new Oracle Internet Directory Host.

    Username

    Oracle Internet Directory Administrator username

    Password

    Oracle Internet Directory Administrator password

    Use SSL Port

    Select this box if the connection to the Oracle Internet Directory Host should use SSL (in which case the port number provided should be the SSL port).

To Disassociate OID Host from a Forms Application:

  1. From the Associate/Disassociate OID page, select the Forms application. Click Disassociate.

    A confirmation box appears.

  2. Click Yes.

    The Oracle Internet Directory host is disassociated from the Forms application.

  3. Restart the Oracle WebLogic Managed Server and the front-end OHS for the changes to take effect.

    To prevent users from being inadvertently disconnected from active forms sessions, ensure you choose to restart Oracle WebLogic Managed Server and the front-end OHS at a convenient time when users are not running any forms sessions.

To re-associate an OID Host with a Forms Application:

  1. From the Associate/Disassociate OID page, select the Forms application. Click Disassociate.
  2. From the Associate/Disassociate OID page, select the Forms application. Click Associate.

    Enter the Oracle Internet Directory Host details as described in the above table.

  3. Generate and apply the access client file.
Access client file, as described in Selecting Oracle Internet Directory or Oracle Platform Security as the Forms Identity Store

Selecting Oracle Internet Directory or Oracle Platform Security as the Forms Identity Store

Oracle Platform Security Services (OPSS) is the set default Forms Identity Store. If the administrator performs the Forms OID association, it will set Oracle Internet Directory as the Forms Identity Store. Users can switch back to Oracle Platform Security Services (OPSS) as Forms Identity Store by un-checking the check box in the Primary Identity Store column for each deployment on Forms Runtime LDAP Associations page.

Registering web-tier instance as OAM partner application and OAM policy configuration

Users have two choices for registering the web-tier instance as the Oracle Access Manager (OAM) partner application and configure the resulting OAM policy.

  • frmconfighelper script

  • OAM console

    Note:

    The Web-tier and its managing Weblogic Admin Server must be restarted after either of the configuration options.

Using frmconfighelper Script for the Web-tier Partner Application Registration and Configuring Policy

Run the frmconfighelper script to perform partner application registration and subsequently configure the policy on the Oracle Access Manager.

The frmconfighelper script uses the Oracle Access Manager's RREG tool to perform these tasks. All the policy configuration details are included in the Forms OAM policy configuration file, $FMW_HOME/forms/provision/FormsOAMRegRequest.xml.

Users need to:

  1. Download RREG.tar located on the Oracle Access Manager Server and untar under the Oracle Forms and Reports Home directory (for example, "Oracle_Home").
  2. Run the frmconfighelper script and pass it enable_sso option.

Using Oracle Access Manager (OAM) console for doing the web-tier partner application registration and configuring policy

Users need to perform these steps:

  1. Configure Webgate on the web-tier instance.

    Webgate is installed with Oracle HTTP Server, but not configured in the OHS instance. Users can follow the instructions in the Oracle HTTP Server Webgate documentation or run the frmconfighelper script and pass the enable_Webgate option.

  2. Creating Webgates on the OAM console and configure the resulting policy.

    Use OAM console to create a Webgate agent, pass in the OHS host and port information and add the following to the Protected Resource List:

    /forms/frmservlet?*oamMode=true*

    Edit resources in the generated policy using the OAM console and all the following the Excluded List.

    /* and /.../*

  3. Copy ObAccessClient.xml and cwallet.sso from the OAM server to the relevant OHS under the directory DOMAIN_HOME/config/fmwconfig/components/OHS/<ohs instance>/Webgate/config.

Unsupported Client Configurations

For information on the frmconfighelper script, see Oracle Forms Configuration Helper Script.

If you try to use an unsupported client configuration like an "embedded applet" or "embedded jnlp", you may see a Java exception error the first time you attempt to access an SSO-enabled Oracle Forms application . To avoid this, have the administrator disable the HTTPOnly parameter, which is set in OAM.

Note:

Understand that this change, as well as the use of an embedded applet, is not recommended. Disabling HTTPOnly may create a security issue. Also, the use of Microsoft Internet Explorer or Microsoft Edge with IE-mode is no longer supported. This information has been included for backward compatibility reference only.

To achieve this, perform these steps:

  1. Log in to the OAM Administration Console.
  2. Select Authentication Schemes and navigate to LDAPScheme.
  3. Set the ssoCookie parameter value to disablehttponly.
  4. Click Apply.

Administering Resource Access Descriptors

Resource Access Descriptors or RADs are used by Oracle Forms to allow its runtime to connect to an Oracle Database when applications are SSO-enabled. They are managed from the Resource Administration pages of Fusion Middleware Control.

To manage RADs:

  1. Log in to Fusion Middleware Control.
  2. Expand the sidebar by clicking on the Target Navigation icon (Sidebar) near the upper left corner next to the domain name.
  3. Expand the Forms node then click the desired Forms instance, for example "forms1".
  4. Expand the Forms drop-down near the upper left.
  5. Select Security, then either Forms OPSS Resource Administration or Forms LDAP Resource Administration, depending on whether you are using OPSS or Oracle Internet Directory (LDAP) to store RAD information.

    Note:

    RADs are stored in OPSS by default.

    Figure -34 shows the OPSS Administration Resources page:

    Figure -34 Resources page


    Description of Figure -34 follows
    Description of "Figure -34 Resources page"

  6. To administer individual users or groups, use the Add, Edit, or Delete buttons on the Resources page as required.
  7. To upload one or more RADs at a time, click Upload and provide a properly formatted text file with the desired RAD entries using this syntax:

    Note:

    Each RAD entry must be on a new line within the text file and each value must be quoted.

    For individual user RADs:

    appName="<application name>" isGroup="<true/false>" " description="<description>" dbUsername="<database username>" dbPassword="<database password>" dbName="<database alias>"

    For group RADs:

    appName="<application name>" isGroup="<true/false>" description="<description>" ssoUserName="<SSO username>" dbUsername="<database username>" dbPassword="<database password>" dbName="<database alias>"

    Figure -35 shows the Upload RADs dialog with two RAD entries:

    Figure -35 Upload RADs dialog


    Description of Figure -35 follows
    Description of "Figure -35 Upload RADs dialog"

Resource Migration Assistant

The Resource Migration Assistant page allows for the migration of Oracle Forms RADs stored in Oracle Internet Directory (OID) to be moved to Oracle Platform Security Services (OPSS). This utility is intended for the purpose of migration from OID to OPPS only.

To access the Resource Migration Assistant page, perform the following steps:

  1. Log into Fusion Middleware Control.
  2. Expand the sidebar by clicking on the icon near the upper left corner, next to the domain name sidebar
  3. Expand the Forms node then click the desired Forms instance, for example "forms1".
  4. Expand the Forms drop-down near the upper left.
  5. Select Security then select Resource Migration.
  6. The Resource Migration page will be displayed. You will be required to enter information about the Oracle Internet Directory (OID) server to be accessed for the migration process. This selection can be changed after accessing the page by clicking on the Connect OID button.

    Figure -36 Resource Migration Assistant

    Description of Figure -36 follows
    Description of "Figure -36 Resource Migration Assistant"
  7. Once on the Resource Migration page, the table will display all the resources found in the OID selected. Select the entries in the table that should be migrated to OPSS then click Migrate. The status of the transfer will be displayed in a popup dialog.

    Figure -37 Resource Migration Assistant page

    Description of Figure -37 follows
    Description of "Figure -37 Resource Migration Assistant page"