16 Oracle Internet Directory

This chapter discusses the following topics:

• Section 16.1, "Administration Issues and Workarounds"

• Section 16.2, "Documentation Errata"

16.1 Administration Issues and Workarounds

This section describes administration issues and their workarounds for Oracle Internet Directory.

16.1.1 Stopping the Oracle Directory Service from the Control Panel Does Not Stop the Oracle Directory Server Processes

To stop the Oracle directory server processes, you must use the OIDCTL utility. However, if you stop the Oracle directory processes by using the OIDCTL utility, then you cannot start them automatically from the control panel. To start the directory server processes, you must use the OIDCTL utility.

16.1.2 Log File oidldap00.log Can Be Ignored

When you access the LDAP main page of EMD, the Oracle directory server may log extra information in a log file named oidldap00.log. This log file can be ignored.

16.2 Documentation Errata

This section describes known errors in the documentation.

In the Oracle Internet Directory Release Notes, Release 9.0.2.1.0, Section 2.4, "Instructions for Manually Deploying the Delegated Administration Service" should read as follows:

The Delegated Administration Service is deployed when the infrastructure is installed. In some situations, there may be a requirement to deploy it on a host other than that on which the infrastructure is deployed. To deploy the Delegated Administration Service on a computer where the middle tier is installed, perform the following steps:

1. Verify that the computer has at least the core installation installed and the installation is pointing to an existing Oracle Internet Directory/SSO.

2. Navigate to the ORACLE_HOME/dcm/bin directory.

3. Create a new component by using the following command:

   dcmctl createcomponent -verbose -debug -ct oc4j -co OC4J_DAS
   
   

4. Start the component by using the following command:

   dcmctl start -verbose -debug -co OC4J_DAS
   
   

5. Deploy the Delegated Administration Service ear file by using the following command:

   dcmctl deployApplication -debug -verbose -a oiddas -f
   ORACLE_HOME/ldap/das/oiddas.ear -co OC4J_DAS
   
   

6. Perform the following steps to add the LD_LIBRARY_PATH and DISPLAY environment variables to the opmn.xml file:

   • Navigate to the ORACLE_HOME/opmn/conf directory and open opmn.xml in a text editor.

   • Add the following lines in the OC4J_DAS section of opmn.xml:

     <environment>
        <prop name="PATH" value="%ORACLE_HOME%\bin"/>
     </environment>
     
     

   • Replace ORACLE_HOME with the appropriate value.

     Note the placement of the section <environment> in the following example.

     <oc4j maxRetry="3" instanceName="OC4J_DAS" gid="OC4J_DAS" numProcs="1">
        <config-file path="C:\home\ias902\j2ee\OC4J_DAS/config/server.xml"/>
        <oc4j-option value="-properties"/>
        <port ajp="3001-3100" jms="3201-3300" rmi="3101-3200"/>
        <environment>
           <prop name="DISPLAY" value="sandal:0.0"/>
           <prop name="PATH" value="C:\home\ias902\bin"/>
        </environment>
     </oc4j>
     
     

7. Navigate to the ORACLE_HOME/dcm/bin directory.

8. Save the changes to the repository by using the following command:

   dcmctl updateconfig -verbose -debug -ct opmn
   
   

9. Restart OPMN by using the following command:

   dcmctl restart -verbose -ct opmn
   
   

10. Stop and start the OC4J_DAS instance by using the following commands:

    dcmctl stop -verbose -debug -ct oc4j -co OC4J_DAS
    dcmctl start -verbose -debug -ct oc4j -co OC4J_DAS