9-10 Forms Services Deployment Guide
hostnames into their browsers uncomment out the following lines
PerlModule Apache::ShortHostnameRedirect PerlHeaderParserHandler Apache::ShortHostnameRedirect
3.
Add the following lines to the beginning of forms.conf file. IfModule mod_osso.c
LoadModule osso_module {ORACLE_HOME}ohsmodulesmod_osso.so IfModule
IfModule mod_osso.c OssoHTTPOnly off
IfModule
4.
Associate the OID Host in Enterprise Manager as given in the topic To Associate
OID Host with a Forms Application of the
Section 9.7, Configuring Oracle Internet Directory
.
5.
Restart the Oracle WebLogic Managed Server WLS_FORMS and the front-end OHS for the changes to take effect.
9.5 Integrating Oracle Forms and Reports
Oracle Reports is installed with OracleAS Single Sign-On Server enabled. The best practice for Oracle Forms applications calling integrated Oracle Reports is to
use the Oracle Forms Built-in, RUN_REPORT_OBJECT. When requesting a report from a SSO-enabled Oracle Forms application, the
authenticated users SSO identity is implicitly passed to the Reports Server with each call to RUN_REPORT_OBJECT built-in. The SSO identity is used to authenticate the
user to the Reports Server for further authorization checking, if required.
A Forms application running in non-SSO mode can run a report on a SSO-secured Reports Server, but fails if the Reports Server requires authorization. Also, users must
provide their SSO credentials when retrieving the Reports output on the Web.
For more information on enabling single sign-on in Forms, see Section 9.4, Enabling
OracleAS Single Sign-On for an Application .
For more information on configuring single sign-on in Reports, refer to the Oracle Fusion Middleware Publishing Reports to the Web with Oracle Reports Services.
For more information about integrating Oracle Forms and Oracle Reports, see the white paper Integrating Oracle Forms 11g and Oracle Reports 11g at
http:www.oracle.comtechnologyproductsforms .
9.5.1 Forms and Reports Integration in non-SSO mode
Prior to 11g Release 1 11.1.1, Oracle Reports generated sequential job IDs, making it easy to predict the job ID. This meant that unauthorized or malicious users could
potentially view the job output using GETJOBID through rwservlet to obtain job output that belongs to another user. In 11g, Oracle Reports generates random and
non-sequential job IDs to make it impossible to predict the job ID for a particular job. Only the user who runs a report from Oracle Forms Services is able to see its output.
Other users should not be able to see the report output as job IDs are random non-sequential numbers.
Using Forms Services with Oracle Single Sign-On 9-11
For a non-secure Reports Server, the user ID and password for administrators can be set in the identifier element of the Reports Server configuration file.
For more information on configuring the access levels for the users, refer to the Oracle Fusion Middleware Publishing Reports to the Web with Oracle Reports Services.
9.5.2 Using Multiple Reports Server Clusters in Oracle Forms Services
If your Oracle Forms application from a prior release uses multiple Reports Server cluster names, you can map each of those cluster names to a different Reports Server.
In Oracle Reports 11g Release 1 11.1.1, Reports Server clustering was deprecated. An Oracle Forms application from prior releases that includes a Reports Server cluster
name will fail to bind to the Reports Server cluster it references.
To resolve this issue, the reports_servermap element maps a cluster name to a Reports Server name. This avoids the necessity to change the cluster name in all Oracle Forms
applications.
An Oracle Forms application can call Oracle Reports in the following ways:
■
Using RUN_REPORT_OBJECT: If the call specifies a Reports Server cluster name instead of a Reports Server name, the reports_servermap environment
variable must be set in the Oracle Forms Services default.env file. If your Oracle Forms application uses multiple Reports Server cluster names, you can
map each of those cluster names to a different Reports Server using reports_ servermap in rwservlet.properties, as follows:
reports_servermap cluster1:repserver1;cluster2:repserver2;cluster3:repserver3
reports_servermap For example, if your Oracle Forms application includes 3 clusters with names
dev_cluster, prd_cluster, and qa_cluster in 10.1.2, you can map these cluster names to respective server names in later releases, as follows:
reports_servermap dev_cluster:dev_server;prd_cluster:prd_server;qa_cluster:qa_
server reports_servermap
■
Using WEB.SHOW_DOCUMENT: In this case, the request is submitted to rwservlet. If the call specifies a Reports Server cluster name instead of a Reports Server name,
the reports_servermap element must be set in the rwservlet.properties file. For example:
reports_servermap cluster:repserver
reports_servermap For more information, see the Oracle Fusion Middleware Publishing Reports to the Web
with Oracle Reports Services.
9.5.3 Integrating Forms and Reports Installed in Different Instances
