Oracle Internet Directory Component Characteristics
8.3.1.1 Oracle Internet Directory Component Characteristics
Oracle Internet Directory, which is Oracle’s LDAP store, is a C-based component that uses a database as its persistence store. It is a stateless process and stores all of the data and the majority of its configuration information in the back-end database. It uses Oracle Net Services to connect to the database.8.3.1.1.1 Runtime Processes Oracle Internet Directory has the following runtime
processes: Oracle directory replication server Also called a replication server, it tracks and sends changes to replication servers in another Oracle Internet Directory system. There can be only one replication server on a node. You can choose whether to configure the replication server. If there are multiple instances of Oracle Internet Directory that use the same database, only one of them can be running replication. This is true even if the Oracle Internet Directory instances are on different nodes. The replication sever process is a process within Oracle Internet Directory. It only runs when replication is configured. For more information about Oracle Internet Directory replication, refer to Chapter 10, Configuring Identity Management for Maximum High Availability. . Oracle Database Server Stores the directory data. Oracle strongly recommends that you dedicate a database for use by the directory. The database can reside on the same node as the directory server instances. Oracle Process Manager and Notification Server OPMN Manages Oracle Internet Directory as an Oracle Fusion Middleware component. OPMN uses the directives in the OID component snippet in ORACLE_INSTANCEopmn.xml and invokes OIDMON and OIDCTL as required. The command-line utility is opmnctl. OID Monitor OIDMON Initiates, monitors, and terminates the LDAP server and replication server processes. When you invoke process management commands, such as oidctl or opmnctl, or when you use Fusion Middleware Control to start or stop server instances, your commands are interpreted by this process. OIDMON also monitors servers and restarts them if they have stopped running for abnormal reasons. OIDMON starts a default instance of OIDLDAPD. If the default instance of OIDLDAPD is stopped using the OIDCTL command, then OIDMON stops the instance. When OIDMON is restarted by OPMN, OIDMON restarts the default instance. All OID Monitor activity is logged in the file ORACLE_ INSTANCE diagnosticslogOIDcomponent_ id oidmon-xxxx.log. This file is on the Oracle Internet Directory server file system. OID Monitor checks the state of the servers through mechanisms provided by the operating system. OID Control Utility OIDCTL Communicates with OID Monitor by placing message data in Oracle Internet Directory server tables. This message data includes configuration parameters required to run each Oracle directory server instance. Normally used from the command line only to stop and start the replication server. Table 8–4 Cont. An Oracle internet Directory Node Element Description Configuring High Availability for Identity Management Components 8-17 ■ OIDLDAPD: This is the main process for Oracle Internet Directory. OIDLDAPD consists of a dispatcher process and a server process. The dispatcher process spawns the OIDLDAPD server processes during startup. Each OIDLDAPD dispatcher process has its own SSL and non-SSL ports for receiving requests. Every OID instance has one dispatcher and one server process by default. The number of server processes spawned for an instance is controlled by the orclserverprocs attribute. ■ OIDMON: OIDMON is responsible for the process control of an Oracle Internet Directory instance. This process starts, stops, and monitors Oracle Internet Directory. During startup OIDMON spawns the OIDLDAPD dispatcher process and the replication server process, if replication is configured for the instance. ■ Replication server process: This is a process within Oracle Internet Directory that runs only when replication is configured. The replication server process is spawned by OIDMON during startup. ■ OPMN: The Oracle Process Manager and Notification Server OPMN is a daemon process that monitors Oracle Fusion Middleware components, including Oracle Internet Directory. Oracle Enterprise Manager Fusion Middleware Control uses OPMN to stop or start instances of Oracle Internet Directory. If you stop or start Oracle Internet Directory components from the command line, you use opmnctl, the command-line interface to OPMN. OPMN is responsible for the direct start, stop, restart and monitoring of OIDMON. It does not start or stop the server process directly.8.3.1.1.2 Process Lifecycle OPMN is responsible for the direct start, stop, restart and
monitoring of the daemon process, OIDMON ORACLE_HOMEbinoidmon. OIDMON is responsible for the process control of an Oracle Internet Directory instance. In 11g Release 1 11.1.1, you can have multiple instances of Oracle Internet Directory on the same Oracle instance on the same node. For details, refer to Oracle Fusion Middleware Administrators Guide for Oracle Internet Directory. Process Status Table Oracle Internet Directory process information is maintained in the ODS_PROCESS_ STATUS table in the ODS database user schema. OIDMON reads the contents of the table at a specified interval and acts upon the intent conveyed by the contents of that table. The interval is controlled by the value of the sleep command line argument used at OIDMON startup, and the default value is 10 seconds. Starting and Stopping Oracle Internet Directory An Oracle Internet Directory instance can be started and stopped using the Oracle Enterprise Manager Fusion Middleware Control or the command opmnctl. Start Process The start process for Oracle Internet Directory is: 1. Upon receiving the start command, OPMN issues an oidmon start command with appropriate arguments, as specified in the opmn.xml file. 2. OIDMON then starts all Oracle Internet Directory Server instances whose information in the ODS_PROCESS_STATUS table has state value 1 or 4 and ORACLE_INSTANCE, COMPONENT_NAME, INSTANCE_NAME values matching the environment parameters set by OPMN. Stop Process The stop process for Oracle Internet Directory is: 8-18 Oracle Fusion Middleware High Availability Guide 1. Upon receiving the stop command, OPMN issues an oidmon stop command. 2. For each row in the ODS_PROCESS_STATUS table that matches the environment parameters ORACLE_INSTANCE, COMPONENT_NAME, and INSTANCE_ NAME, the oidmon stop command kills OIDMON, OIDLDAPD, and OIDREPLD processes and updates the state to 4. Monitoring OPMN does not monitor server processes directly. OPMN monitors OIDMON and OIDMON monitors the server processes. The events are: ■ When you start OIDMON through OPMN, OPMN starts OIDMON and ensures that OIDMON is up and running. ■ If OIDMON goes down for some reason, OPMN brings it back up. ■ OIDMON monitors the status of the Oracle Internet Directory dispatcher process, LDAP server processes, and replication server process and makes this status available to OPMN and Oracle Enterprise Manager Fusion Middleware Control.8.3.1.1.3 Request Flow Once the Oracle Internet Directory process starts up, clients
access Oracle Internet Directory using the LDAP or LDAPS protocol. There is no impact on other running instances when an Oracle Internet Directory instance starts up. Oracle Internet Directory listenerdispatcher starts a configured number of server processes at startup time. The number of server processes is controlled by the orclserverprocs attribute in the instance-specific configuration entry. The default value for orclserverprocs is 1. Multiple server processes enable Oracle Internet Directory to take advantage of multiple processor systems. The Oracle Internet Directory dispatcher process sends the LDAP connections to the Oracle Internet Directory server process in a round robin fashion. The maximum number of LDAP connections accepted by each server is 1024 by default. This number can be increased by changing the attribute orclmaxldapconns in the instance-specific configuration entry, which has a DN of the form: cn=componentname,cn=osdldapd,cn=subconfigsubentry Database connections from each server process are spawned at server startup time, depending on the value set for the instance configuration parameters ORCLMAXCC and ORCLPLUGINWORKERS. The number of database connections spawned by each server equals ORCLMAXCC + ORCLPLUGINWORKERS + 2. The Oracle Internet Directory server processes communicate with the Oracle database server through Oracle Net Services. An Oracle Net Services listenerdispatcher relays the request to the Oracle database. For more information, refer to Oracle Fusion Middleware Administrators Guide for Oracle Internet Directory.8.3.1.1.4 Configuration Artifacts The storage location requires a DB connect string.
TNSNAMES.ORA is stored in ORACLE_INSTANCEconfig. The wallet is stored in ORACLE_INSTANCE OIDadmin The DB ODS user password is stored in the wallet.8.3.1.1.5 External Dependencies Oracle Internet Directory uses an Oracle database to
store configuration information as well as data. It uses the ODS schema to store this information. The Oracle directory replication server uses LDAP to communicate with an Oracle directory LDAP server instance. To communicate with the database, all components Configuring High Availability for Identity Management Components 8-19 use OCIOracle Net Services. Oracle Directory Services Manager and the command-line tools communicate with the Oracle directory servers over LDAP.8.3.1.1.6 Oracle Internet Directory Log File Log files for Oracle Internet Directory are
under the following directory: ORACLE_INSTANCE diagnosticslogOID Table 8–5 shows Oracle Internet Directory processes and the log file name and location for the process. For more information on using the log files to troubleshoot Oracle Internet Directory issues, see Section 8.3.6, Troubleshooting Oracle Internet Directory High Availability .8.3.2 Oracle Internet Directory High Availability Concepts
Parts
» Oracle Fusion Middleware Online Documentation Library
» High Availability Problems High Availability Solutions
» High Availability Information in Other Documentation
» What Is the Administration Server? Understanding Managed Servers and Managed Server Clusters
» What Is a System Component Domain? What Is a Middleware Home? What Is a WebLogic Server Home?
» Oracle Fusion Middleware High Availability Terminology
» Server Load Balancing Oracle Fusion Middleware High Availability Technologies
» Local High Availability Active-Passive Deployment
» About Active-Active and Active-Passive Solutions
» Disaster Recovery Oracle Fusion Middleware High Availability Solutions
» Protection from Planned and Unplanned Down Time
» What Is a WebLogic Server Cluster? WebLogic Server Clusters and WebLogic Server Domains
» Application Failover Migration Key Capabilities of a Cluster
» Benefits of Clustering Types of Objects That Can Be Clustered
» Communications in a Cluster Cluster-Wide JNDI Naming Service
» Startup Process in a Cluster with Migratable Servers
» Administration Servers Role in Whole Server Migration Migratable Server Behavior in a Cluster
» Node Managers Role in Whole Server Migration Cluster Masters Role in Whole Server Migration
» Load Balancing Oracle Fusion Middleware Online Documentation Library
» Multi Data Sources Cluster Configuration and config.xml
» Java-Based Oracle Fusion Middleware Components Deployed to Oracle WebLogic Server
» Configuring Multi Data Sources for MDS Repositories
» Log on to SQLPlus as a system user, for example:
» Log on to SQLPlus as a user with sysdba privileges. For example:
» Configuring Multi Data Sources with Oracle RAC
» Oracle RAC Failover with WebLogic Server JDBC Clients
» Oracle Reports and Oracle Discoverer
» Troubleshooting Real Application Clusters
» SCAN Run Time Implications and Limitations
» Oracle SOA Service Infrastructure Protection from Failures and Expected Behavior
» Oracle SOA Service Infrastructure Cluster-Wide Configuration Changes
» Oracle BPEL Process Manager Request Flow and Recovery
» Oracle BPEL Process Manager Protection from Failures and Expected Behavior
» Oracle BPM Suite Component Characteristics
» Oracle BPM Suite Component Interaction
» Oracle BPMN Service Engine Single Instance Characteristics
» Oracle BPMN Service Engine High Availability Considerations
» Oracle Business Process Web Applications Single Instance Characteristics
» Oracle Business Process Analytics Single Instance Characteristics
» Oracle Mediator Component Characteristics Oracle Mediator Startup and Shutdown Lifecycle
» Oracle Mediator Request Flow
» Oracle Mediator Protection from Failures and Expected Behavior
» Troubleshooting Oracle Mediator High Availability
» Troubleshooting Oracle Human Workflow High Availability
» Oracle B2B Component Characteristics Oracle B2B Startup and Shutdown Lifecycle
» Oracle B2B Protection from Failures and Expected Behavior
» Oracle WSM Component Characteristics Oracle WSM Startup and Shutdown Lifecycle
» Oracle WSM Protection from Failures and Expected Behavior
» Oracle WSM Cluster-Wide Configuration Changes Configuring the Java Object Cache for Oracle WSM
» Configuring Distributed Notifications for the MDS Repository
» Oracle User Messaging Service Component Characteristics
» Oracle User Messaging Service Protection from Failures and Expected Behavior
» Oracle User Messaging Service Cluster-Wide Configuration Changes
» Oracle JCA Adapters Component Lifecycle
» Oracle JCA Adapters Reliability and Transactional Behavior
» Oracle JCA Adapters - Rejected Message Handling
» Oracle JCA Adapters High Availability Error Handling Oracle Database Adapters High Availability
» Oracle JMS Adapters High Availability
» Oracle JCA Adapters Log File Locations
» Oracle Business Activity Monitoring Component Characteristics
» Oracle Business Activity Monitoring Configuration Artifacts
» Oracle Business Activity Monitoring Protection from Failures and Expected Behavior
» Oracle Business Activity Monitoring Cluster-Wide Configuration Changes
» Oracle Service Bus Session State Oracle Service Bus External Dependencies
» Oracle Service Bus Configuration Artifacts Oracle Service Bus Deployment Artifacts
» Oracle Service Bus Protection from Failures and Expected Behavior
» Database Prerequisites VIP and IP Prerequisites Shared Storage Prerequisites
» Configuring Virtual Server Names and Ports for the Load Balancer
» Validating Oracle HTTP Server To verify that Oracle HTTP Server is set up
» Setting Connection Destination Identifiers for B2B Queues
» Starting Node Manager on SOAHOST2 Starting and Validating the WLS_SOA2 Managed Server
» Setting the Front End HTTP Host and Port
» Setting the WLS Cluster Address for Direct BindingRMI Invocations to Composites
» Deploying Applications Click Next.
» Configuring Server Migration for the WLS_SOA Servers
» Connect to the database as the leasing user. Run the leasing.ddl script in SQLPlus.
» Click Save. Oracle Fusion Middleware Online Documentation Library
» Enabling VIP1 and VIP3 in SOAHOST1 and VIP2 and VIP4 in SOAHOST2
» Configure Oracle Coherence for the Oracle Service Bus Result Cache
» Configuring a Default Persistent Store for Transaction Recovery Deploying Applications
» Configuring Server Migration for the WLS_OSB Servers
» Enabling VIP0 and VIP1 on BAMHOST1
» Oracle ADF Components Understanding Oracle ADF
» Oracle ADF Single Node Architecture Oracle ADF External Dependencies
» Oracle ADF Scope and Session State
» Oracle ADF Failover and Expected Behavior Oracle ADF Active Data Services
» Troubleshooting Oracle ADF Development Issues
» Deploying the ADF Application Validating Access through Oracle HTTP Server
» Select the Control tab. Select Environment Servers from the Administration Console. Select Clone.
» Oracle WebCenter Components Understanding Oracle WebCenter
» Oracle WebCenter Single-node Architecture Oracle WebCenter State and Configuration Persistence
» Oracle WebCenter External Dependencies
» Oracle WebCenter Configuration Considerations
» Oracle WebCenter Analytics Communications
» Oracle WebCenter State Replication Understanding the Distributed Java Object Cache
» Maintaining Configuration in a Clustered Environment
» Installing Oracle Fusion Middleware for Oracle WebCenter
» Enabling the Administration Server VIP
» Configuring a Virtual Host for Oracle Pagelet Producer and Sharepoint
» Configuring Activity Graph Click Start.
» Converting Discussions from Multicast to Unicast
» Configuring a Cluster for Oracle WebCenter Portal Applications
» Agent Startup and Shutdown Cycle Oracle Data Integrator External Dependencies
» Java EE Agent Configuration Standalone Agent Configuration
» Oracle Data Integrator Clustered Deployment
» WebLogic Server or Standalone Agent Crash Repository Database Failure
» About the 11g Oracle Identity Management Products
» Database Prerequisites Installing and Configuring the Database Repository
» Oracle Internet Directory Component Characteristics
» Oracle Internet Directory High Availability Architecture
» Protection from Failures and Expected Behavior
» Installing Oracle Fusion Middleware for Identity Management The next step is to
» Registering Oracle Internet Directory with a WebLogic Domain If you want to
» Creating boot.properties for the Administration Server on OIDHOST1 This section
» Configuring Oracle Internet Directory on OIDHOST2 Ensure that the Oracle Internet
» Validating Oracle Internet Directory High Availability
» Performing an Oracle Internet Directory Failover Performing an Oracle RAC Failover
» Troubleshooting Oracle Internet Directory High Availability
» Changing the Password of the ODS Schema Used by Oracle Internet Directory
» Oracle Virtual Directory Runtime Considerations Oracle Virtual Directory Component Characteristics
» Oracle Virtual Directory High Availability Architecture
» Configuring Oracle Virtual Directory on OVDHOST2 Follow these steps to configure
» Registering Oracle Virtual Directory with a WebLogic Domain It is recommended
» On the Installation Complete screen, click Finish to confirm your choice to exit.
» Troubleshooting LDAP Adapter Creation
» Oracle Directory Integration Platform Component Characteristics
» Oracle Directory Integration Platform High Availability Architecture
» Configuring Oracle HTTP Server for Oracle Directory Services Manager High
» If WebLogic Node Manager Fails to Start Operation Cannot Be Completed for Unknown Errors Message
» Oracle Directory Services Manager Component Characteristics
» Oracle Directory Services Manager High Availability Architecture
» Protection from Failures and Expected Behaviors
» Performing a WebLogic Server Instance Failover
» Using Oracle Directory Services Manager to Validate a Failover of a Managed Server
» Collocated Architecture Overview Troubleshooting Collocated Components Manager High Availability
» Additional Considerations for Collocated Components High Availability
» Oracle Access Manager Component Characteristics
» Oracle Access Manager High Availability Architecture
» Oracle Security Token Service High Availability Architecture
» Oracle Security Token Service Component Characteristics
» In the Customize Server and Cluster Configuration screen, select Yes, and click
» On the Configuration Summary screen, click Create to begin the creation process.
» Oracle Identity Manager Component Characteristics
» Runtime Processes Component and Process Lifecycle
» Starting and Stopping Oracle Identity Manager Configuration Artifacts External Dependencies
» Oracle Identity Manager High Availability Architecture
» On the Welcome screen, select Create a WebLogic Domain.
» Connect to the database as the leasing user.
» Select Environment - Servers from the Administration Console. Select Clone.
» Select the Automatic Server Migration Enabled option. This enables the Node Click Save.
» Click the OIMMSServerXXXXXX subdeployment. Add the new JMS Server
» Click Save. Authorization Policy Manager High Availability
» Oracle Adaptive Access Manager Component Characteristics
» Oracle Adaptive Access Manager High Availability Architecture
» On the Welcome screen, click Next.
» Oracle Identity Federation Component Characteristics
» High Availability Considerations for Integration with Oracle Access Manager
» Oracle Internet Directory Oracle Virtual Directory Oracle HTTP Server Node Manager
» WebLogic Administration Server Oracle Identity Manager
» Oracle Access Manager Managed Servers Oracle Adaptive Access Manager Managed Servers
» Oracle Identity Federation Starting and Stopping Oracle Identity Management Components
» Oracle HTTP Server and Oracle WebLogic Server
» Prerequisites Configuring Oracle HTTP Server for High Availability
» Install Oracle HTTP Server on WEBHOST2
» Oracle Web Cache Request Flow
» Oracle Web Cache Stateless Load Balancing
» Oracle Web Cache Backend Failover Oracle Web Cache Session Binding
» Oracle Web Cache Cluster-Wide Configuration Changes
» Oracle Web Cache as a Software Load Balancer
» From the Session Name list, select a session to enable binding for a specific
» Click Add. In the Component field, enter the name of the cache member.
» Adding a Node in Oracle Advanced Database Multimaster Replication
» Deleting a Node in Oracle Advanced Database Multimaster Replication
» Oracle IPM Component Characteristics
» Oracle IPM High Availability Architecture
» Creation of Oracle IPM Artifacts in a Cluster Troubleshooting Oracle IPM
» Oracle UCM Component Characteristics
» Oracle UCM High Availability Architecture
» Oracle UCM and Inbound Refinery High Availability Architecture
» Oracle URM High Availability Protection from Failure and Expected Behaviors
» Shared Storage Configuring the Oracle Database
» Installing Oracle ECM on ECMHOST1
» On the Welcome screen, select Create a new WebLogic domain.
» In the Select JMS Distributed Destination Type screen, select UDD from the
» Configuring Oracle HTTP Server on WEBHOST1
» Terminology for Directories and Directory Environment Variables
» Administration Server Topology 1 Transforming Oracle Fusion Middleware Infrastructure Components
» Administration Server Topology 2 Transforming Oracle Fusion Middleware Infrastructure Components
» Click Activate Changes. Choose Environment Servers. Click Control. Select WLS_EXMPL. Click Start.
» Transforming Oracle Internet Directory and Its Clients
» Select the Connect to a directory -- Create A New Connection link in the
» Click JDBC Connection under Data Sources.
» Click Administration. Click Scheduler Configuration under System Maintenance Click Apply.
» Database Instance Platform-Specific Considerations
» Example Topology 1 Example Topology 2
» Destination Topologies Cold Failover Cluster Transformation Procedure
» Introduction to Oracle Clusterware Cluster Ready Services and Oracle Fusion Middleware
» Upgrading Older Versions of ASCRS to the Current ASCRS Version Installing ASCRS
» Configuring ASCRS with Oracle Fusion Middleware
» Creating a Virtual IP Resource Creating a Shared Disk Resource
» Creating an Oracle Database Listener Resource Creating an Oracle Database Resource
» Creating a Middleware Resource
» Updating Resources Starting Up Resources Shutting Down Resources Resource Switchover
» Oracle Portal, Forms, Reports, and Discoverer Architecture
» Oracle Forms Runtime Considerations Oracle Forms Process Flow
» Oracle Forms Configuration Files Oracle Forms External Dependencies Oracle Forms Log Files
» Oracle Discoverer Runtime Considerations
» Preference Server Failover Session State Replication and Failover Performance Recommendation
» Dependencies Network Requirements Prerequisites
» Install Oracle WebLogic Server Install Oracle Portal, Forms, Reports, and Discoverer Validation
» Oracle BI EE Component Characteristics
» Oracle BI EE and EPM High Availability Architecture
» Shared Files and Directories
» Cluster-Wide Configuration Changes Oracle BI EE High Availability Concepts
» Oracle Essbase Component Characteristics
» Oracle Essbase High Availability Architecture Protection from Failures and Expected Behaviors
» Oracle Hyperion Provider Services Component Characteristics
» Oracle Hyperion Provider Services High Availability Architecture
» Workspace Component Characteristics Oracle EPM Workspace Component Architecture
» Workspace High Availability Architecture
» Oracle Hyperion Financial Reporting Component Characteristics
» Oracle BI Publisher Component Characteristics
» Oracle BI Publisher High Availability Architecture
» Oracle RTD Component Characteristics
» Oracle RTD High Availability Architecture
Show more