Beruflich Dokumente
Kultur Dokumente
12c (12.2.1.3.0)
E80069-03
April 2018
Oracle Fusion Middleware Installing Oracle Forms and Reports, 12c (12.2.1.3.0)
E80069-03
Copyright © 2017, 2018, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify,
license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.
Reverse engineering, disassembly, or decompilation of this software, unless required by law for
interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are
"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-
specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the
programs, including any operating system, integrated software, any programs installed on the hardware,
and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron,
the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro
Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise
set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be
responsible for any loss, costs, or damages incurred due to your access to or use of third-party content,
products, or services, except as set forth in an applicable agreement between you and Oracle.
Contents
Preface
Audience vi
Documentation Accessibility vi
Related Documents vi
Conventions vi
iii
2.4.7.1 Creating Reports Tool Components 2-14
2.4.7.2 Resolving Report Server access error 2-15
2.4.7.3 Provisioning a Machine 2-16
2.4.7.4 Configure Reports Builder as Run to web 2-16
2.4.8 Configuring Form Builder Standalone 12c Using the Configuration
Wizard 2-17
2.4.9 Verifying the Installation and Configuration 2-18
2.4.9.1 Reviewing the Installation Logs 2-18
2.4.9.2 Reviewing the Domain Server Logs 2-18
2.4.9.3 Checking the Installed Products and Product Versions 2-18
2.4.9.4 Checking Browser URLs 2-18
2.4.9.5 Performing Basic Administration Tasks 2-19
2.5 Installing Oracle Forms and Reports in Silent Mode 2-19
2.6 Oracle Forms and Reports Accessibility Information 2-20
iv
4.5.2.1 Running the Upgrade Assistant to upgrade the Domain Schema 4-5
4.5.2.2 Reconfiguring the 12.2.1.1.0 Domain using the WLS
Reconfiguration Wizard 4-6
4.5.2.3 Running the Upgrade Assistant to upgrade the Forms installation 4-6
4.5.3 Upgrading to Oracle Forms 12c (12.2.1.3.0) from 12c (12.2.1.2.0) 4-7
4.5.3.1 Running the Upgrade Assistant to upgrade the Domain Schema 4-7
4.5.3.2 Reconfiguring the 12.2.1.2.0 Domain using the WLS
Reconfiguration Wizard 4-7
4.5.3.3 Running the Upgrade Assistant to upgrade the Forms installation 4-8
4.6 Post-Upgrade Steps after Upgrading Oracle Forms 4-8
4.7 Planning an Upgrade of Oracle Reports 4-8
4.8 Preparing to Upgrade Oracle Reports 4-9
4.9 Upgrading Oracle Reports 4-9
4.9.1 Re-Configuring the 11g Domain Using the WLS Reconfiguration Wizard 4-9
4.9.2 Using the Upgrade Assistant to Perform an Upgrade 4-10
4.10 Post-Upgrade Steps after Upgrading Oracle Reports 4-11
4.11 Upgrading Forms and Reports Together from 11g to 12c 4-12
B Troubleshooting
B.1 General Troubleshooting Tips B-1
B.2 Installation and Configuration Log Files B-2
B.2.1 Installation Log Files B-2
B.2.2 Configuration Log Files B-3
B.3 Verify Environment Variable Lengths for Oracle Reports (Windows Only) B-3
v
Preface
Preface
This document covers requirements, instructions, and troubleshooting tips for installing
and configuring Oracle Forms and Reports.
Audience
This guide is intended for users who are installing Oracle Fusion Middleware for the
first time and are comfortable running some system administration operations, such as
creating users and groups, adding users to groups, and installing operating system
patches on the computer where you products will be installed. Users in UNIX systems
who are installing need root access to run some scripts.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=docacc.
Related Documents
You can refer the Oracle Fusion Middleware Library for additional information.
• For 12c Oracle Forms information, see Oracle Forms and Reports Documentation
Library.
• Oracle Forms Developer Online Help, available from the Help menu in Oracle
Forms Developer.
• For Oracle Forms white papers and other resources, see http://www.oracle.com/
technetwork/developer-tools/forms/documentation/index.html
Conventions
The following text conventions are used in this document:
vi
Preface
Convention Meaning
boldface Boldface type indicates graphical user interface elements associated
with an action, or terms defined in text or the glossary.
italic Italic type indicates book titles, emphasis, or placeholder variables for
which you supply particular values.
monospace Monospace type indicates commands within a paragraph, URLs, code
in examples, text that appears on the screen, or text that you enter.
vii
1
Installation and Configuration Overview
This chapter provides a summary and roadmap for Oracle Forms and Reports
installation and configuration.
The following sections are included
• Oracle Forms and Reports Components
• Secure Oracle Forms and Reports With Identity Management
• Installation and Configuration Roadmap for Oracle Forms and Reports
• Installation and Configuration Roadmap for Standalone Form Builder
1-1
Chapter 1
Installation and Configuration Roadmap for Oracle Forms and Reports
Securing Oracle Forms and Reports With Oracle Access Manager 11g
This release of Oracle Forms and Reports supports Oracle Internet Directory 11g
(11.1.1.7 and 11.1.1.9) with Oracle Access Manager 11g Release 3 (11.1.2.3).
To install and configure Oracle Internet Directory with Oracle Access Manager, you
have to perform the following task:
1. Install Oracle Identity and Access Management, as described in Preparing to
Install and Configure Oracle Access Management
2. Configure a WebLogic Server domain for Oracle Access Manager, as described in
Preparing to Install and Configure Oracle Access Management
3. Integrate Oracle Access Manager with Oracle Internet Directory, as described in
Configuring the Oracle OAM Suite Domain
If you have an existing Oracle Internet Directory with Oracle Single Sign-On, you can
upgrade to Oracle Internet Directory with Oracle Access Manager, as described in
Upgrading Oracle Forms and Reports
Note:
If you are planning to use the Standalone Form Builder installation option,
see Table 1-2
Table 1-1 Tasks in the Oracle Forms and Reports Installation and Configuration Flowchart
1-2
Chapter 1
Installation and Configuration Roadmap for Oracle Forms and Reports
Table 1-1 (Cont.) Tasks in the Oracle Forms and Reports Installation and Configuration
Flowchart
1-3
Chapter 1
Installation and Configuration Roadmap for Standalone Form Builder
Table 1-2 Tasks in the Standalone Form Builder Installation and Configuration Flowchart
1-4
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:
• Preparing to Install
• Installing Oracle WebLogic Server (FMW Infrastructure)
• Installing Oracle Identity and Access Management
• Installing and Configuring Oracle Forms and Reports
• Installing Oracle Forms and Reports in Silent Mode
• Oracle Forms and Reports Accessibility Information
2-1
Chapter 2
Preparing to Install
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.
2. Using the system requirements document to verify certification
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.
3. Verifying interoperability among multiple products
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.
2-2
Chapter 2
Preparing to Install
2-3
Chapter 2
Installing Oracle WebLogic Server (FMW Infrastructure)
Planning Your Oracle Home Location for Oracle Reports (Windows Only)
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)
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 ensure 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,
end the process.
2. Determine if the nodemanager.properties file is present in the WebLogic_Home\common
\nodemanager directory.
2-4
Chapter 2
Installing Oracle Identity and Access Management
2-5
Chapter 2
Installing and Configuring Oracle Forms and Reports
Note:
• 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.
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 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:
inventory_loc=/home/username/oraInventory
inst_group=group
Then, you can start the installer and point to the oraInst.loc file. For example:
2-6
Chapter 2
Installing and Configuring Oracle Forms and Reports
Screen Description
Welcome This screen introduces you to RCU.
2-7
Chapter 2
Installing and Configuring Oracle Forms and Reports
Screen Description
Create Repository Select Create Repository, then select System Load
and Product Load (default).
Database Connection Details Specify RCU database connection credentials.
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.
Select Components Select the Create new prefix radio button and provide a
schema prefix (such as DEMO).
You must remember the prefix and schema names for
the components you are installing. It is recommended
that you write down these values.
Select the following components:
• Oracle Platform Security Services
• User Messaging Service (UMS)
Tip:
If Forms Application Deployment
Services (FADS) is also planned to be
configured, include User Messaging
Services (UMS).
• Audit Services
• Audit Services Append
• Audit Services Viewer
Note:
Additional dependent
components will
automatically be selected.
2-8
Chapter 2
Installing and Configuring Oracle Forms and Reports
Screen Description
Map Tablespaces Use this screen to configure the desired tablespace
mapping for the schemas that you want to setup.
When you click Next, Repository Creation Utility dialog
window appears, asking you to confirm that you want to
create these tablespaces. Click OK to proceed and
dismiss the dialog window.
A second dialog window, Creating Tablespaces appears
showing the progress of tablespace creation. Click OK,
after the tablespaces are created, to dismiss this window
and go to the next screen.
Summary Verify the information on this screen, then click Create
to begin schema setup.
A System Load progress dialog window appears,
showing progress. The dialog window will disappear
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.
Note:
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.
2-9
Chapter 2
Installing and Configuring Oracle Forms and Reports
5. Click Next. The Administrator Account screen appears. Enter the desired
WebLogic Domain administration username and password. This information will
be needed to access WebLogic Server Control and Fusion Middleware Control.
6. Click Next. The Domain Mode and JDK screen appears. Select the Domain Mode
(either Development or Production). To ensure the highest degree of security,
selecting Production is recommended. Leave the default JDK selection as it
appears, unless using another version of the JDK desired.
7. Click Next. The Database Configuration Type screen appears. Enter the RCU DB
connection information. This information was created when running the Repository
Creation Utility (RCU) in an earlier step. After entering the requested information,
click Get RCU Configuration. Verify that a successful message is presented in
the Results Log panel. If an indication of success is not indicated, check the
databases entries made in this step. Mostly it will only be necessary to enter data
for DBMS/Service, Host Name, Port, Schema Owner, and Schema Password.
Other entries can remain as the default value.
8. Click Next. The JDBC Component Schema screen appears. These instructions
assume each Repository schema uses the same password. If not, enter the
correct schema passwords.
9. Click Next. The JDBC Component Schema Test screen appears. If any tests fail, it
may be necessary to go back and make corrections.
10. Click Next. The Advanced Configuration screen appears. Select Topology and
System Components. Depending on the level of customization desired, other
selections may be used.
Tip:
If you want to configure server templates and dynamic server, see:
• Using Server Templates in Understanding Domain Configuration for
Oracle WebLogic Server.
• Creating and Configuring Dynamic Clusters in Administering
Clusters for Oracle WebLogic Server.
11. Click Next. The Managed Servers screen appears. Verify that the Server Groups
is set to FORMS-MAN-SVR (for Forms). This screen can also be used to add
additional managed servers if desired.
12. Click Next. The Clusters screen appears. Default entries will be acceptable
mostly, unless adding new clusters is desirable.
13. 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.
14. Click Next. The Coherence Clusters screen appears. The default values will be
appropriate for most cases.
15. Click Next. The Machines screen appears. Use this screen to override the
machine name or add addition machine names for extend domain scenarios (add
remote Forms nodes).
16. Click Next. The Assign Servers to Machines screen appears. Move the
AdminServer to the AdminServerMachine by clicking the > button.
2-10
Chapter 2
Installing and Configuring Oracle Forms and Reports
17. Click Next. The Virtual Targets screen appears. Used with WebLogic Server
Partitions. Refer to the WebLogic Server documentation for details.
18. Click Next. The Partitions screen appears. Use this screen to add Weblogic
Partitions if desired. Refer to the WebLogic Server documentation for details on
how to use Partitions.
19. Click Next. The System Components screen appears. The default values will be
appropriate for most cases. You can add additional Forms or other System
Component instances on this screen (for example, extending a domain).
a. If Oracle HTTP Server (OHS) was selected in the Templates screen, the OHS
component would need to be added in this step.
b. Click the Add button to add the OHS component and then click Next button.
c. Accept the default settings for the OHS Server component and then click Next
button.
20. The Assign System Components to Machines screen appears. The default values
will be appropriate for most cases. If OHS added in the previous step, move it to
the Machines column under the Admin Server using the > button.
Note:
In case of extend domain scenario; assign the Forms System
Component to the relevant Machine.
23. Depending on the location and performance of the Repository database, this
process may take a few minutes. Click Finish. The End of Configuration screen
appears.
To complete the Configuration, Node Manager and the Admin Server must be
successfully started.
On Unix/Linux platforms, the shell used to start these servers the first time, must be
the installation owner's (for example, oracle).
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.
2-11
Chapter 2
Installing and Configuring Oracle Forms and Reports
Note:
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.
2-12
Chapter 2
Installing and Configuring Oracle Forms and Reports
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 Get RCU Configuration. You should receive a success message.
8. Click Next. The JDBC Component Schema screen appears. These instructions
assume each Repository schema uses the same password. If not, enter the
correct schema passwords.
9. Click Next. The JDBC Component Schema Test screen appears. The tests are
run and the results given.
10. Click Next. The Advanced Configuration screen appears. Select Administration
Server, Node Manager, Managed Servers, Clusters and Deployment and
Services.
11. Click Next. The Administration Server screen appears. The default values will be
appropriate for most cases.
12. 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.
13. Click Next. The Clusters screen appears. Default entries will be acceptable
mostly, unless adding new clusters is desirable.
14. 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.
15. Click Next. The Coherence Clusters screen appears. The default values will be
appropriate for most cases.
16. Click Next. The Machines screen appears. Add a machine, for example:
AdminServerMachine (default).
17. Click Next. The Assign Servers to Machines screen appears. Add AdminServer
and WLS_REPORTS to AdminServerMachine by clicking the > button. The
Reports App is targeted to WLS_REPORTS by default.
Development Configuration can be used for development mode where sufficient
system resources are not available. To perform this configuration, follow these
steps:
a. In the Admin Server screen, in Server groups drop down list, select
REPORTS-APP-SVR as one of the groups. This will configure AdminServer
with reports.
b. The rest of the steps are the same as before.
2-13
Chapter 2
Installing and Configuring Oracle Forms and Reports
Note:
One ReportsTools component is compulsory. Reports Server and
Reports Bridge are optional.
This configuration is not supported for use with production, multiuser
environments. It is further not recommended in cases where
sufficient system resources are available. This configuration should
only be used on development environments where adequate
resources such as system memory are limited.
Oracle Forms is not supported for use in this configuration.
18. Click Next. The System Components screen appears. The default values will be
appropriate for most cases. You can add additional Forms or other System
Component instances on this screen (for extend domain scenario). For example, if
adding OHS, it would appear here.
19. Click Next. The Assign System Components screen appears. The default values
will be appropriate for most cases.
Note:
In case of extend domain scenario; assign the Forms System
Component to the relevant Machine.
To resolve this errors, the first step you should complete after running the
Configuration Wizard in a new environment with Oracle Reports 12c, is to run the
following WLST command:
• createReportsToolsInstance(): This command will create all the components at file
system level required for Oracle Reports.
For example:
2-14
Chapter 2
Installing and Configuring Oracle Forms and Reports
The following are some of the key folders that will be created for Oracle Reports 12c
after the third steps in the preceding example:
• DOMAIN_HOME/reports/bin
• DOMAIN_HOME/reports/cache
• DOMAIN_HOME/reports/fonts
• DOMAIN_HOME/reports/plugins
• DOMAIN_HOME/reports/server
The Oracle Reports environment is now complete and ready to be used.
• REP-50503: No server found in the network. Then error also occurs when
running the command rwdiag.sh -findAll.
This is firewall permission related problem, because the Reports server trace
files shows Reports server is up and running. There are no errors in the trace files.
To resolve this problem, perform the following steps:
1. Open the rwnetwork UDP port on the firewall to allow the Reports Server to be
accessible.
a. Run command: rwdiag.sh –findAll
b. From output, check what value is used for Channel port.
For example:
Broadcast mechanism used to locate servers
Channel address = ###.###.###.###
Channel port = 14021
c. Open the channel port on the firewall.
As per the example in the previous step, it is port 14021.
2. In the firewall, authorize requests from your host's IP address to ###.###.###.###.
The Channel address as shown in the example in the first step.
2-15
Chapter 2
Installing and Configuring Oracle Forms and Reports
The above steps will solve the Reports server access related problem.
Note:
It the above steps do not solve the problem, add the name of the machine
where Reports Server is located and the IP for that machine to the hosts file
(/etc/hosts or C:\WINDOWS\system32\drivers\etc\hosts).
2. Start Adminserver
$DOMAIN_HOME/bin/startWebLogic.sh
createReportsToolsInstance(instanceName='<reportsToolsName>',
machine='AdminServerMachine')
createReportsServerInstance(instanceName='<reportsServerName>',
machine='AdminServerMachine')
exit()
4. Start WLS_REPORTS
$DOMAIN_HOME/bin/startManagedWebLogic.sh WLS_REPORTS (Inprocess server starts)
2-16
Chapter 2
Installing and Configuring Oracle Forms and Reports
</pluginParam>
The port is the OHS port. If OHS is not there, it should be the WLS_REPORTS
port.
Note:
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.
3. Enter a name for the Form Builder Instance path in the Configuration Wizard,
Instance Configuration screen. Click Next.
4. After configuration is complete, the Configuration Progress screen shows
Configuration Succeeded message. Click Next.
5. End of Configuration screen shows the Oracle Home and Form Builder Instance
location. Click Finish to exit the installer.
2-17
Chapter 2
Installing and Configuring Oracle Forms and Reports
On Windows operating systems, the location for the inventory directory is C:\Program
Files\Oracle\Inventory\logs.
For information about installation log files, see Installation Log Files.
2-18
Chapter 2
Installing Oracle Forms and Reports in Silent Mode
Note:
If you installed in development mode, there would not be an Enterprise
Manager Console URL to verify, and your Oracle Forms and Reports URLs
would use the Administration Server port. In deployment mode, Enterprise
Manager Console and EMAgent would use the Administration Server port,
while Oracle Forms and Reports could be verified using their respective
Managed Server ports or the Oracle HTTP Server port number.
Additionally, if your Oracle Forms and Reports are protected by Oracle Identity
Management, then you will be prompted to provide login credentials when you attempt
to access the Oracle Forms and Oracle Reports URLs.
2-19
Chapter 2
Oracle Forms and Reports Accessibility Information
Oracle Forms
You can configure you system and use features supporting accessibility while running
Forms. Oracle Forms Builder 12c also supports a range of features that are designed
to support accessibility. The Oracle Forms 12c runtime is accessible if coded based on
the instructions provided in the following link. Information is also provided about the
minimum requirement that assistive technology must meet to run with Oracle Forms.
See: Accessibility Features and Tips for Oracle Forms.
Oracle Reports
Accessible enterprise reports can be created using features and options available in
Oracle Reports. You can also use specific techniques for designing reports to increase
accessibility of report output, see: Accessibility Features and Tips for Oracle Reports
2-20
3
Deinstalling Oracle Forms and Reports
Follow the instruction in this chapter to deinstall Oracle Forms and Reports.
It is recommended that you always use the instructions provided in this chapter to
remove the software. If you try to remove the software manually, you may encounter
problems when you try to reinstall the software again at a later time. Following the
procedures in this chapter will ensure that the software is properly removed. If you
need to remove a particular product component, you must remove the entire domain
containing the component. It is not possible to remove a single product from a domain
containing multiple products.
The following topics are covered:
• Preparing to Deinstall Oracle Forms and Reports
• Dropping the Associated Repository
• Deinstalling the Software
• Removing the Oracle Home Directory Manually
• Removing the Program Shortcuts on Windows Operating Systems
• Removing the Domain and Application Data
• Reinstalling the Software
3-1
Chapter 3
Deinstalling the Software
Note:
Schemas should not be dropped if the associated domain will be used for
other components. Only drop schemas when the domain is to be deleted.
Dropping the repository schemas will also delete all data stored in them.
3-2
Chapter 3
Removing the Oracle Home Directory Manually
Screen Description
Welcome Introduces you to the product deinstaller. The
deinstallation Welcome screen contains a
navigation pane on the left that summarizes
the tasks the deinstaller will help you
complete.
Deinstallation Summary Shows the Oracle home directory and its
contents that will be deinstalled. Verify that this
is the correct directory.
If you want to save these options to a
response file, click Save Response File and
enter the response file location and name. You
can use the response file later during a silent
deinstallation. See Running the Oracle
Universal Installer for Silent Deinstallation in
Installing Software with the Oracle Universal
Installer.
Click Deinstall, to begin removing the
software.
Deinstallation Progress Shows the deinstallation progress.
Deinstallation Complete Appears when the deinstallation is complete.
Review the information on this screen, then
click Finish to close the deinstaller.
You should repeat the steps in Starting the Deinstallation Program and this section, for
each product (Forms, Reports) in the Oracle home you want to deinstall.
3-3
Chapter 3
Removing the Program Shortcuts on Windows Operating Systems
2. If you only have one product installed in your Oracle home, delete the ORACLE_HOME
directory. If you have multiple products installed in your Oracle home, delete all
products before you delete the ORACLE_HOME directory.
Note:
The program shortcuts and folder names on your system may be different;
you have to remove them from C:\ProgramData\Microsoft\Windows\Start Menu
\Programs.
cd /home/Oracle/config/domains
rm -rf frs_domain
On a Windows operating system, if your Domain home directory is C:\Oracle
\Config\domains\frs_domain, use a file manager window and navigate to the C:
\Oracle\Config\domains directory. Right-click on the frs_domain folder and select
Delete.
2. Remove your Application home directory. For example:
On a UNIX operating system, if your Application home directory is /home/Oracle/
config/applications/frs_domain, enter the following commands:
cd /home/Oracle/config/applications
3-4
Chapter 3
Reinstalling the Software
rm -rf frs_domain
On a Windows operating system, if your Application home directory is C:\Oracle
\Config\applications\frs_domain, use a file manager window and navigate to the
C:\Oracle\Config\applications directory. Right-click on the frs_domain folder and
select Delete.
3. Back up the domain_registry.xml file in your Oracle home, then edit the file and
remove the line associated with the domain that you are removing. For example,
to remove the frs_domain, find the following line and remove it:
<domain location="/home/Oracle/config/domains/frs_domain"/>
3-5
4
Upgrading Oracle Forms and Reports
This chapter describes how to upgrade Oracle Forms and Reports from 11g or
previous 12c version to the latest version.
Upgrading Oracle Form and Reports from a previous release is an in-place upgrade
performed by using the Upgrade Assistant.
The following topics are covered:
• Planning an Upgrade of Oracle Forms
• Preparing to Upgrade Oracle Forms from 11g
• Create Copy of Oracle Forms Template Files
• Upgrading Oracle Forms from 11g to 12c
• Upgrading Oracle Forms from a Previous 12c Release
• Post-Upgrade Steps after Upgrading Oracle Forms
• Planning an Upgrade of Oracle Reports
• Preparing to Upgrade Oracle Reports
• Upgrading Oracle Reports
• Post-Upgrade Steps after Upgrading Oracle Reports
• Upgrading Forms and Reports Together from 11g to 12c
4-1
Chapter 4
Create Copy of Oracle Forms Template Files
2. Copy the artifacts from all the remote nodes to the Admin Server node.
3. Run the forms-upgrade-ext.sh (forms-upgrade-ext.bat) script on the Admin Server
node and pass it the apply option. It will extract the Forms configuration from the
remote node artifacts and apply it to the Domain.
4-2
Chapter 4
Upgrading Oracle Forms from a Previous 12c Release
Note:
In 11g, Forms do not require the Repository Creation Utility (RCU) schemas,
but starting with 12c all the WebLogic Server 12c domains require RCU
schemas to be setup. Hence, before you perform these steps, ensure that
you create the required schemas (see Configuring the Oracle Fusion
Middleware Infrastructure Domain) in RCU before you run the WLS
Reconfiguration Wizard.
4-3
Chapter 4
Upgrading Oracle Forms from a Previous 12c Release
Note:
Running forms-upgrade-ext.sh on remote nodes is not required when
upgrading from 12.2.1.
4-4
Chapter 4
Upgrading Oracle Forms from a Previous 12c Release
4-5
Chapter 4
Upgrading Oracle Forms from a Previous 12c Release
4-6
Chapter 4
Upgrading Oracle Forms from a Previous 12c Release
4-7
Chapter 4
Post-Upgrade Steps after Upgrading Oracle Forms
5. Leave the default selections on the Node Manager screen. Enter user name and
password if needed.
6. Select JRF-MAN-SVR and FORMS-MAN-SVR server groups for all the Forms
managed servers, including the default Forms managed servers WLS_FORMS,
WLS_FORMS1, etc., and any other Forms managed servers users that may have
been added after the 11g installation.
7. Click Next until you get to the last screen of the Reconfiguration Wizard.
4-8
Chapter 4
Preparing to Upgrade Oracle Reports
2. Copy the artifacts from all the remote nodes to the Admin Server node.
3. Run the reports-upgrade-ext.sh (reports-upgrade-ext.bat) script on the Admin
Server node in apply mode. It will extract the Reports configuration from the
remote node artifacts and apply it to the Domain.
4. Run the Upgrade Assistant in readiness mode and ensure that it is working
properly.
$ORACLE_HOME/oracle_common/upgrade/bin/ua -readiness
4-9
Chapter 4
Upgrading Oracle Reports
Note:
In 11g, Reports do not require the Repository Creation Utility (RCU)
schemas, but starting with 12c all the WebLogic Server 12c domains require
RCU schemas to be setup. Hence, before you perform these steps, ensure
that you create the required schemas (see Configuring the Oracle Fusion
Middleware Infrastructure Domain) in RCU before you run the WLS
Reconfiguration Wizard.
4-10
Chapter 4
Post-Upgrade Steps after Upgrading Oracle Reports
– Repeat for each reports managed server which is targeted to remote machine.
– Copy the respective jars to remote machine where that managed server is
targeted.
$ORACLE_HOME/reports/plugins/upgrade/reports-upgrade-ext.sh applyRemote
<domainHome> <instanceHome> <wlsName> <jarFileName>
• Regenerate the Reports application files: rep's and rdf's (optional), to run on
Oracle Reports Server 12c (12.2.1.3.0).
• Manually copy any customizations to the shell scripts in the source Oracle home to
the equivalent shell scripts that reside in Oracle Fusion Middleware 12c
(12.2.1.3.0) Oracle instance directory.
4-11
Chapter 4
Upgrading Forms and Reports Together from 11g to 12c
Note:
To start Oracle Reports server and components after upgrading to 12c, see
Starting and Stopping Oracle Reports Services.
4-12
Chapter 4
Upgrading Forms and Reports Together from 11g to 12c
WLS_REPORTS1, etc., and any other Reports managed servers users that may
have been added after the 11g installation.
7. Click Next until you get to the Reconfiguration Progress screen.
8. The Reconfiguration Progress screen displays the progress of the reconfiguration
process.
9. The End of Configuration screen indicates whether the reconfiguration process
completed successfully or failed.
If the reconfiguration process did not complete successfully, an error message is
displayed indicates the reason. Take appropriate action to resolve the issue.
Note:
In 11g, Forms and Reports do not require the Repository Creation Utility
(RCU) schemas, but starting with 12c all the WebLogic Server 12c domains
require RCU schemas to be setup. Hence, before you perform these steps,
ensure that you create the required schemas (see Configuring the Oracle
Fusion Middleware Infrastructure Domain) in RCU before you run the WLS
Reconfiguration Wizard.
4-13
A
Integrating Oracle Internet Directory with
Oracle Access Manager
This appendix describes post-installation enablement of a centralized LDAP store for
use with Oracle Access Manager. Oracle Internet Directory is featured in this
discussion. However, tasks are the same regardless of your chosen LDAP provider.
Oracle Access Manager addresses each user population and LDAP directory store as
an identity domain. Each identity domain maps to a configured LDAP User Identity
Store that is registered with Oracle Access Manager. Multiple LDAP stores can be
used with each one relying on a different supported LDAP provider.
During initial WebLogic Server domain configuration, the Embedded LDAP is
configured as the one and only User Identity Store for Oracle Access Manager. Within
the Embedded LDAP, the Administrators group is created, with weblogic seeded as the
default Administrator:
• Only the User Identity Store designated as the System Store is used to
authenticate Administrators signing in to use the Oracle Access Manager, remote
registration, and custom administrative commands in WLST.
• Users attempting to access an Oracle Access Manager-protected resource can be
authenticated against any store, not necessarily the only one designated as the
Default User Identity Store.
• Oracle Security Token Service uses only the Default User Identity Store. When
adding User constraints to a Token Issuance Policy, for instance, the identity store
from which the users are to be chosen must be Default User Identity Store.
After registering a User Identity Store with Access Manager, administrators can
reference the store in one or more authentication modules, which form the basis for
Oracle Access Manager Authentication Schemes and Policies. When you register a
partner (either using the Oracle Access Manager Console or the remote registration
tool), an application domain can be created and seeded with a policy that uses the
designated default Authentication Scheme. When a user attempts to access an Oracle
Access Manager-protected resource, she is authenticated against the store
designated by the authentication module.
The following topics are covered:
• Installing and Setting Up Required Components
• Defining Authentication in Oracle Access Manager for Oracle Internet Directory
• Managing Oracle Access Manager Policies that rely on your LDAP Store
• Validating Authentication and Access
A-1
Appendix A
Installing and Setting Up Required Components
A-2
Appendix A
Defining Authentication in Oracle Access Manager for Oracle Internet Directory
Note:
Do not set the All Groups filter; the default works fine as is.
Click Save.
3. Set DefaultIdentityAsserter:
a. From Security Realms, myrealm, Providers, click Authentication, click
DefaultIdentityAsserter to see the configuration page.
b. Click Common tab and set the Control Flag to SUFFICIENT.
c. Click Save.
4. Reorder Providers:
a. On Summary page, where providers are listed, click Reorder.
b. On Reorder Authentication Providers page, select a provider name and use
the arrows beside the list to order the providers as follows:
WebLogic Provider
IAMSuiteAgent
OracleInternetDirectoryAuthenticator
DefaultIdentityAsserter
c. Click OK, to save your changes.
5. Activate Changes: In the Change Center, click Activate Changes, then Restart
Oracle WebLogic Server.
6. Proceed to the next section.
A-3
Appendix A
Defining Authentication in Oracle Access Manager for Oracle Internet Directory
Note:
Before you perform the steps to use the identity store for authentication with
Access Manager, for
• Registering Oracle Internet Director, see Registering and Managing User
Identity Stores
• Defining Authentication Modules and Plug-ins, see Native LDAP
Authentication Modules and Orchestrating Multi-Step Authentication with
Plug-in Based Modules
• Defining Authentication Scheme Challenge Methods, see Creating an
Authentication Scheme
To use your identity store for authentication with Access Manager perform the
following steps.
1. Register Oracle Internet Directory with Oracle Access Manager.
2. Define Authentication Modules and Plug-ins: From System Configuration tab,
Access Manager Settings section, expand the Authentication Modules node.
a. LDAP Modules: Open LDAP Authentication module, select your User
Identity Store, and click Apply.
b. Custom Authentication Modules: In LDAPPlugin Steps (stepUI,
UserIdentificationPlugIn), specify your KEY_IDENTITY_STORE_REF, and
click Apply.
For example,
Authentication Modules
Custom Authentication module
LDAPPlugin
Steps tab
stepUI UserIdentificationPlugIn
Repeat this step for the stepUA UserAuthenticationPlugIn plug-in, and Apply
your changes, as shown here:
3. Define Authentication Scheme Challenge Methods: Form and Basic Challenge
Methods require a reference to the LDAP Authentication Module or Plug-in that
points to your User Identity Store.
For example:
Oracle Access Manager Console
Policy Configuration tab
Shared Components node
Authentication Schemes node
DesiredScheme (OAMAdminConsoleScheme or any Form or Basic scheme)
a. Confirm that the Authentication Module references the LDAP module or plug-
in that points to your Identity Store.
A-4
Appendix A
Managing Oracle Access Manager Policies that rely on your LDAP Store
b. Click Apply to submit the changes (or close the page without applying
changes).
c. Dismiss the Confirmation window.
4. Proceed to the next section.
Note:
Before you perform the steps to create an application domain and policies
that use LDAP authentication, for
• Resource Definitions, see Adding and Managing Policy Resource
Definitions.
• Authentication Policies, see Defining Authentication Policies for Specific
Resources.
• Authorization Policies, see Defining Authorization Policies for Specific
Resources.
• Token Issuance Policies. See Managing Token Issuance Policies,
Conditions, and Rules.
A-5
Appendix A
Validating Authentication and Access
Internet Directory User Identity Store. Add specific resources and complete the
policy for your environment.
c. Authorization Policies: Create or modify an Authorization Policy for specific
resources and include any Responses and Constraints you need.
d. Token Issuance Policies: Choose the desired User Identity Store when
setting Identity Conditions in Token Issuance Policies.
4. Proceed to the next section.
A-6
B
Troubleshooting
This appendix describes solutions to common problems that you might encounter
when installing Oracle Forms and Reports.
The following sections are included:
• General Troubleshooting Tips
• Installation and Configuration Log Files
• Verify Environment Variable Lengths for Oracle Reports (Windows Only)
If this Troubleshooting appendix does not solve the problem you encountered, try
looking for a solution on My Oracle Support, see https://support.oracle.com/ (formerly
Oracle MetaLink). You can also raise a service request, if you are unable to find a
solution for your problem.
B-1
Appendix B
Installation and Configuration Log Files
The following log files contains information that can help you to troubleshoot problems
during installation or configuration:
• Installation Log Files
• Configuration Log Files
The following install log files are written to the log directory:
• installdate-time-stamp.log
This log file contains the output and error streams during the installation.
• installActionsdate-time-stamp.log
This file is used by the installer GUI to keep track of internal information.
• installProfiledate-time-stamp.log
This log file contains the overall statistics like time taken to complete the
installation, also configuration, memory and CPU details.
• oraInstalldate-time-stamp.log
This log file contains the output stream of the copy session.
If you start the installer with the -printtime parameter, the timeTakendate-time-
stamp.log and timedate-time-stamp.log files are created in the same directory:
• timeTakendate-time-stamp.log
This file contains information for the amount of time taken to move between
screens (applicable for GUI installations only).
B-2
Appendix B
Verify Environment Variable Lengths for Oracle Reports (Windows Only)
• timedate-time-stamp.log
If you specify an absolute path with your log_filename then your log file will be created
there. If you only specify a file name with no path, then the log files are created in the
ORACLE_HOME/common/bin (on UNIX operating systems) or ORACLE_HOME\common\bin (on
Windows operating systems) directory.
B-3