4 groups required to install middle tiers, 3 example, Groups require – Oracle B32100-01 User Manual
Page 97
Groups Required to Install Middle Tiers
Configuring Oracle Internet Directory for Oracle Application Server Installation Privileges
5-7
-b "" -s base "objectclass=*" orclreplicaid
b.
Then run this command.
prompt> ldapsearch -h oidhostname -p oidport -D cn=orcladmin -w password
-b "orclreplicaid=value_from_previous_command,cn=replication
configuration"
-s base "objectclass=*" seealso
This returns a "seealso" value in the format: cn=Metadata repository DB
Name,cn=oraclecontext
.
5.4 Groups Required to Install Middle Tiers
When you install middle tiers, the installer prompts you to log in to Oracle Internet
Directory. Log in as a user who is a member of these groups:
■
Section 5.4.1, "Groups Required to Install Against the Desired Metadata
Repository"
■
Section 5.4.2, "Groups Required to Install Middle-tier Components"
5.4.1 Groups Required to Install Against the Desired Metadata Repository
To install middle tiers against a metadata repository, the user must belong to these
groups:
■
IAS Admins group
■
Mid-Tier Admins group for the metadata repository to be used with the middle
tier. When the installer prompts for the OracleAS Metadata Repository to use with
this middle tier, the installer displays only the metadata repositories for which the
user is a mid-tier admin. For example, in
, userA can see only the
repository for orcl.oracle.com, and userB can see only the repository for
orcl1.oracle.com.
5.4.2 Groups Required to Install Middle-tier Components
To install middle-tier components, such as OracleAS Portal and OracleAS Wireless, the
user must belong to additional groups. See
for a list of components and
required groups.
5.4.3 Example
shows an Oracle Internet Directory with one metadata repository and one
middle-tier instance. userA can install middle tiers against the orcl metadata
repository because userA belongs to the Mid-Tier Admins and the IAS Admins
groups. userA can also install middle-tier components because userA belongs to the
Trusted Application Admins group, the IAS & User Management Application Admins
group, and the Component Owners group for Wireless.