1. Installing Oracle Forms
  2. Installing and Configuring Oracle Forms
  3. Installing the Forms Application Deployment Services

Installing the Forms Application Deployment Services

The Forms Application Deployment Services (FADS) simplifies the process of packaging applications, deploying, configuring, and storing archived copies of the applications. Follow the instructions in this section to install and configure Forms Application Deployment Services (FADS) to an existing domain.

The following sections are included:

Configuring Forms Application Deployment Services

After you have completed the installation steps, you can start configuring Forms Application Deployment Services applications by creating the domain.

You have to perform the following FADS application configuration steps in a Fusion Middleware domain:

Setting up RCU Schema

Add missing Repository Creation Utility (RCU) schemas when configuring a domain containing Oracle Forms or FADS. Configuring FADS requires the Repository's User Messaging Service (UMS) and its dependencies.

Note:

If this is a new installation and not an upgrade, you can skip this RCU Schema step. All the needed schemas should already be installed if you followed the installation instructions.

If this was an upgrade from a previous release, needed schemas may be missing and will need to be added.

To add the UMS schema to the domain repository:

  1. After the installation of Oracle Fusion Middleware Infrastructure and the Oracle Forms and Reports software, run this command from ORACLE_HOME/oracle_common/bin to launch RCU:

    $ORACLE_HOME/oracle_common/bin/rcu.sh

    Note:

    This example assumes that the ORACLE_HOME environment variable has already been set.
  2. Work your way through the screens described in

    Table 2-6 Schema Setup Steps

    Screen Description
    Welcome This screen introduces you to RCU.
    Create Repository Select Create Repository, then select System Load and Product Load (default).
    Database Connection Details

    Specify the desired repository database connection details and credentials to connect to the desired database. The user will need DBA privileges.

    When done, click Next to open the Checking Prerequisites dialog and start prerequisite checking.

    If the database checking passes without errors, click OK

    If a DB "editions" warning is shown, click OK to acknowledge it and continue.

    If you are not familiar with this database feature, refer to Using Edition-Based Redefinition in the Database Development Guide for details.

    Select Components

    Click Select Existing Prefix and choose the prefix used for the repository associated with this domain.

    Select User Messaging Service (UMS) to enable UMS.

    Click Next to start the prerequisite check. The Checking Prerequisites dialog is shown. When it is complete, click OK to close the dialog and go to the next screen.

    Schema Passwords Type in the desired password for this schema (UMS). If you chose to use the same password for the other schemas in this repository, it is recommended that you use that same password here.
    Map Tablespaces

    In most cases, there will be no reason to make changes to the tablespace assignments. If it is necessary do so here, then click Next.

    Click OK in the dialog to grant permission to create the selected tablespace.

    Click OK to acknowledge the summary of tasks about to be performed.

    Summary

    Verify the information on this screen, then click Create to begin the process.

    A System Load progress dialog window appears, showing the progress. The dialog window will close when complete.

    Completion Summary Review the information on this screen to verify that the operation was completed successfully. Click Close to complete the schema setup and close RCU.

Applying the FADS Template to an Existing Forms Domain

Apply the FADS extension template to an existing Forms domain using the Configuration Wizard.

Note:

Be sure that the Universal Messaging Service (UMS) repository schema exists before continuing. Refer to Setting up RCU Schema for adding UMS if the schema is missing.
  1. Run the following command to start the Configuration Wizard:
    $ORACLE_HOME/oracle_common/common/bin/config.sh
  2. Work your way through the screens of the wizard described in :

    Table 2-7 Configuration Wizard Screens

    Screen Description
    Create Domain Select Update an existing domain, then type in the existing domain path. In most cases, the correct path will be entered by default. Verify that it is correct before continuing.
    Templates Select Oracle Forms Application Deployment Service (FADS) from the Available Templates box.
    Database Configuration Type In most cases, the default values are populated automatically and should be correct. If so, click Get RCU Configuration to load the schema details.
    Component Datasources Click Next to continue.
    JDBC Test A brief test is performed.
    Advanced Configuration Select Deployments and Services.
    Deployments Targeting
    1. In the Deployment list box, select WSM-PM under AppDeployments.
    2. In the Deployment Targets list box, select AdminServer then click the move right button.

    The wsm-pm entry should now also appear in the list on the right side.

    Service Targeting Click Next to continue.
    Configuration Summary Review the proposed changes, then click Update.
    Configuration Progress Click Next to continue.
    End of Configuration Review the results, then click Finish.
Start the Administration Server, when you finish updating the Forms domain, and then perform the post configuration task described in Run FADS Post Configuration Steps.

Run FADS Post Configuration Steps

After creating or updating your Forms domain or after patching, perform these steps.

Note:

If the domain was created with Secure Mode enabled and you plan to use the demo SSL/TLS certificate provided with the installation (not recommended for production use), set the following before executing the WLST commands provided below.

For UNIX/Linux:

export WLST_PROPERTIES="-Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.TrustKeyStore=DemoTrust"

For MS Windows

set WLST_PROPERTIES="-Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.TrustKeyStore=DemoTrust"

  1. If you created or updated your Forms domain, start the Node Manager, then the Administration Server.
  2. Run the appropriate commands below based on your situation:
    • If you created or updated your Forms domain, use:

      $ORACLE_HOME/oracle_common/common/bin/wlst.sh $ORACLE_HOME/forms/fads/fads_config.py config

    • If you applied a new Forms patch set or one-off, execute the FADS post configuration script with the updateHostPort arguments.

      $ORACLE_HOME/oracle_common/common/bin/wlst.sh $ORACLE_HOME/forms/fads/fads_config.py updateHostPort <ADMINSERVER.DOMAIN> <ADMINSERVER PORT> <PATH TO DOMAIN HOME>

      For example:

      $ORACLE_HOME/oracle_common/common/bin/wlst.sh $ORACLE_HOME/forms/fads/fads_config.py updateHostPort www.example.com 7001 $MIDDLWARE_HOME/user_projects/applications/base_domain

  3. Follow the prompts to complete the configuration.
  4. Perform one of the following steps:
    • If you created or updated the Forms domain, restart the Node Manager, then the Administration Server, and Forms Managed Servers.
    • If you applied a new Forms patch set or one-off, complete other patching steps and then start the Node Manager, Administration Server, and Forms Managed Servers.