Publishing Reports to the Web - Downloads - Oracle

Choosing the connecting entity for the Oracle Internet Directory
10.3.4 Connecting to the Oracle Internet Directory
As you may recall from Chapter 9, "Securing OracleAS Reports Services", OracleAS
Reports Services must connect to the Oracle Internet Directory to verify user privileges
and obtain existing data source connection information. In connecting to the Oracle
Internet Directory, you must consider:
■ Choosing the Connecting Entity for the Oracle Internet Directory
■ Choosing the Oracle Internet Directory Instance
10.3.4.1 Choosing the Connecting Entity for the Oracle Internet Directory
When OracleAS Reports Services connects to the Oracle Internet Directory, it does so
as an application entity. By default, each OracleAS Reports Services application entity
is unique to its Oracle Application Server installation. Every Reports Server started
from the same Oracle Application Server installation (i.e., ORACLE_HOME) uses the
same application entity to connect the Oracle Internet Directory. This setup ensures
that each Reports Server can only access information in the Oracle Internet Directory
that is relevant to its instance of Oracle Application Server.
For example, suppose you have two instances of Oracle Application Server, one for
your Finance group and one for your Human Resources group. A Reports Server from
the Finance group’s Oracle Application Server instance would be prevented from
accessing information relevant only to the Human Resources group, and vice versa.
Thus, information stored in the Oracle Internet Directory is more secure by default.
In previous releases of OracleAS Reports Services, all Reports Servers connected to the
Oracle Internet Directory as the same application entity. As a result, it was not possible
to restrict a Reports Server’s access to information in the Oracle Internet Directory.
To revert to the less restrictive security mode, refer to the OracleAS Reports Services
chapter of the Oracle Application Server Release Notes.
10.3.4.2 Choosing the Oracle Internet Directory Instance
By default, the Reports Server is configured to use the Oracle Internet Directory
instance installed with Oracle Application Server. If you are building your system
anew, this arrangement is fine. If, however, you have an existing Oracle Internet
Directory instance that you want to use for the Reports Server, you have to make some
adjustments to your configuration.
Changing Oracle Internet Directory instances, though, must be done as part of a
complete change of your Oracle Application Server middle tier. For more information
about this process, please refer to the chapter on reconfiguring application server
instances in the Oracle Application Server 10g Administrator’s Guide.
10.4 Choosing the connecting entity for the Oracle Internet Directory
You can merge serveral application entities so that the Reports Servers installed in
separate ORACLE_HOMEs can share available SSOCONN resources. To achieve this
merge, you must execute an ldif file with the ldapmodify command. The ldif file
should contain the following:
dn: dn of the group which represents the logical grouping of all report instances
changetype: modify
add: uniquemember
uniquemember: dn of the Reports Application Entity
where:
10-12 Oracle Application Server Reports Services Publishing Reports to the Web