Skip Headers
Oracle® Fusion Middleware Publishing Reports to the Web with Oracle Reports Services
11g Release 1 (11.1.1)

Part Number B32121-05
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

17.4 Choosing the Connecting Entity for Oracle Internet Directory

You can merge several 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 representing the logical grouping of all report instances
changetype: modify
add: uniquemember
uniquemember: dn of the Reports Application Entity

where:

dn of the group representing the logical grouping of all report instances is
cn=Virtual Application Group, orclApplicationCommonName=reports_application_
entity_name**, cn=Reports, cn=Products, cn=OracleContext
dn of the Reports Application Entity is
orclApplicationCommonName=reports_application_entity_name**, cn=Reports, cn=Products, cn=OracleContext

** reports_application_entity_name is in the format reportsApp_hostname_GUID. For
example, reportsApp_serv1.us.oracle.com_C7543D42A9E26726E034080020A46EE

Example

Entry in the LDIF file:

dn: cn=Virtual Application Group,

  orclApplicationCommonName=reportsApp_Group.us.oracle.com_C7543D42A9E26726E0340
  80020A46EE2, cn=Reports, cn=Products, cn=OracleContext
changetype: modify
add: uniquemember
uniquemember:
  orclApplicationCommonName=reportsApp_serv1.us.oracle.com_A8654E53B0F37837F1451
  91131B57FF3, cn=Reports, cn=Products, cn=OracleContext

Corresponding ldapmodify command on the command line:

ldapmodify -D cn=orcladmin -w welcome1 -h reportsApp_Group.us.oracle.com -p 389 -f mergeentity.ldif