Installation Notes

This chapter tells you where to download Directory Server Enterprise Edition software, and lists primary installation requirements.

This chapter includes the following sections:

• Support Services and Licenses

• What's New in Directory Server Enterprise Edition Bundle Patch 6.3.1.1.1

• Getting the Software

• Hardware Requirements

• Operating System Requirements

• Software Dependency Requirements

• Installation Privileges and Credentials

• Installation Instructions

• Uninstallation Instructions

Refer to the Oralce Directory Services blog for the most current information about the Directory Server product line.

Support Services and Licenses

Before you start with the product installation, make sure you read your Oracle terms and conditions.

What's New in Directory Server Enterprise Edition Bundle Patch 6.3.1.1.1

Directory Server Enterprise Edition Bundle Patch 6.3.1.1.1 is a patch release that corrects known issues in the Directory Server Enterprise Edition versions 6.0 through 6.3, including some enhancements in the Directory Server and Directory Proxy Server. The following highlights important changes in this release:

• The repack of the database now can be applied to individual database files.

  The dsadm repack command repacks or compacts an existing suffix. Usage:

  dsadm repack [-b backend][ -T FILE_TYPE ...] INSTANCE_PATH SUFFIX_DN [SUFFIX_DN...]

  The -b option enables you to specify the name of the backend instead of the suffix name. At least one suffix DN or one backend name must be specified.

  The -T option specifies which type of file needs to be repacked. Possible values are entries|indexes|changelog.

  The server instance must be stopped before running this command.

• The Directory Proxy Server part of Directory Enterprise Edition Bundle Patch 6.3.1.1.1 also adds the following new properties:

  monitoring-search-scope

  Dynamic (no restart required)

  Dynamic (no restart required)

  Level: ldap-data-source

  Type: string

  Default : base

  Description : This property specifies the scope (base, subtree, one) used in a search operation. The availability monitor uses the search operation to test a connection to the data source.

  connect-to-parent

  Dynamic (no restart required)

  Level: abstract-data-view

  Type: boolean

  Default: true

  Description: Specifies whether the data view handles searches whose search base is handled by another data view.

  filter-primary-join-rule

  Dynamic (no restart required)

  Level: abstract-data-view

  Type: string (LDAP filter string) Example: objectClass=person

  Default: none

  Description: Controls retrieval of secondary entries; secondary entries are retrieved only if the primary entry matches that filter.

• Native package distributions are not supported for Linux and Windows platforms.

Getting the Software

Directory Server Enterprise Edition Bundle Patch 6.3.1.1.1 is a maintenance release that is applied to an existing installation of Directory Server Enterprise Edition 6.3.1. You cannot apply Directory Server Enterprise Edition Bundle Patch 6.3.1.1.1 to an installation of Directory Server that is not version 6.3.1.

You can download Sun Java System Directory Server Enterprise Edition Bundle Patch 6.3.1.1.1 software from My Oracle Support. My Oracle Support serves as a starting point to direct you to the proper downloads depending upon the distribution type you need to download.

Directory Server Enterprise Edition Bundle Patch 6.3.1.1.1 is available in the following distributions.

• Native package distribution (available for Solaris only)

  Contains native patches to upgrade installed Directory Server Enterprise Edition 6.3.1 native packages.

• Zip distribution (available for Solaris, Linux, HP-UX, and Windows)

  Contains zip-based patches to upgrade Directory Server Enterprise Edition 6.3.1 zip installations, and to upgrade 6.3.1 native installations on Solaris, Linux , HP-UX, and Windows platforms.

Directory Server Enterprise Edition Bundle Patch 6.3.1.1.1 is available through My Oracle Support. For information on patch numbers, see Installation Instructions.

For the detailed information on what you need to install based on your current installation, refer to Installation Instructions.

Hardware Requirements

This section covers hardware requirements for Directory Server Enterprise Edition component products.

• Directory Server Hardware Requirements

• Directory Proxy Server Hardware Requirements

Directory Server Hardware Requirements

Directory Server software requires the following hardware.

Directory Proxy Server Hardware Requirements

Directory Proxy Server software requires the following hardware.

Operating System Requirements

This section covers operating systems, patches and service packs required to support Directory Server Enterprise Edition component products.

Directory Server, Directory Proxy Server, and Directory Server Resource Kit Operating System Requirements

Directory Server, Directory Proxy Server, and Directory Server Resource Kit share the same operating system requirements. The Directory Server Enterprise Edition software has been validated with full installations of the operating systems listed here, not with reduced “base”, “End User”, or “core” installations. Certain operating systems require additional service packs or patches as shown in the following table. For more information, go to My Oracle Support.

For all supported versions of Microsoft Windows, Directory Server and Directory Proxy Server run only in 32–bit mode, and the filesystem type must be NTFS.

To download the patch cluster for your Solaris OS and Java ES versions, go to My Oracle Support.

Note that installations on SuSE Linux Enterprise Server require you to reset several Java environment variables. See Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide for more details.

Software Dependency Requirements

Directory Server relies on the Network Security Services, NSS, layer for cryptographic algorithms. NSS has been validated to work with the Sun cryptographic framework provided on Solaris 10 systems, which supports cryptographic acceleration devices.

On Microsoft Windows systems, Directory Server requires ActivePerl software to use account activation and manual schema replication commands. Directory Server Enterprise Edition does not provide ActivePerl. The dependency concerns the following commands. For detailed command information, see the Sun Java System Directory Server Enterprise Edition 6.3 Man Page Reference.

• ns-accountstatus

• ns-activate

• ns-inactivate

• schema_push

On Microsoft Windows systems, you must disable the pop-up blocker to make Directory Service Control Center work properly.

The Directory Service Control Center supports the following application servers:

• Sun Java System Application Server 8.2.

• Tomcat 5.5.

For more information, see “Installing Directory Service Control Center from Zip Distribution” in the Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide.

Directory Proxy Server will work with any LDAPv3 compliant directory servers, but it is tested only with Sun Java System Directory Server 6.x, Sun Directory Server Enterprise Edition 7.0 , Oracle Directory Server Enterprise Edition 11g R1, and Oracle Unified Directory 11g.

For virtualization, Directory Proxy Server has been validated with the following JDBC data sources, using the drivers mentioned below.

On Microsoft Windows systems, the dsee_deploy command cannot properly register software with the Common Agent Container, cacao, when you run the command from an MKS shell. This can occur when your MKS PATH does not include the system-drive:\system32 folder. Alternatively, run the command on the Microsoft Windows native command line.

On Solaris 10, rc.scripts are deprecated so commands like dsadm autostart are not supported. Instead use Solaris 10 Service Management Facility (SMF) to handle these types of requests. For example, dsadm enable-service. For more information on SMF, see the Solaris operating system documentation.

Identity Synchronization for Windows Requirements in a Firewall Environment

You can run Identity Synchronization for Windows in a firewall environment. The following sections list the server ports that you must expose through the firewall.

Directory Server Plug-in Requirements in a Firewall Environment

Each Directory Server plug-in must be able to reach the Directory Server connector’s server port, which was chosen when the connector was installed. Plug-ins that run in Directory Server Master replicas must be able to connect to Active Directory’s LDAP, port 389, or LDAPS, port 636. The plug-ins that run in other Directory Server replicas must be able to reach the master Directory Server LDAP and LDAPS ports.

Message Queue Requirements

By default, Message Queue uses dynamic ports for all services except for its port mapper. To access the Message Queue broker through a firewall, the broker should use fixed ports for all services.

After installing the core, you must set the imq.<service_name>.<protocol_type>.port broker configuration properties. Specifically, you must set the imq.ssljms.tls.port option. Refer to the Message Queue documentation for more information.

Installer Requirements

The Identity Synchronization for Windows installer must be able to communicate with the Directory Server acting as the configuration directory.

• If you are installing an Active Directory connector, the installer must be able to contact Active Directory’s LDAP port, 389.

• If you are installing a Directory Server connector or a Directory Server plug-in (subcomponent), the installer must be able to contact the Directory Server LDAP port, default 389.

Core Component Requirements

The Message Queue, system manager, and command line interface must be able to reach the Directory Server where the Identity Synchronization for Windows configuration is stored.

Console Requirements

The Identity Synchronization for Windows console must be able to reach the following:

• Active Directory over LDAP, port 389, or LDAPS, port 636

• Active Directory Global Catalog over LDAP, port 3268, or LDAPS, port 3269

• Each Directory Server over LDAP or LDAPS

• Administration Server

• Message Queue

Connector Requirements

All connectors must be able to communicate with Message Queue.

In addition, the following connector requirements must be met.

• The Active Directory connector must be able to access the Active Directory Domain Controller over LDAP, port 389, or LDAPS, port 636.

• The Directory Server connector must be able to access Directory Server instances over LDAP, default port 389, or LDAPS, default port 636.

Supported Browsers for Directory Service Control Center

The following table displays the browsers for each operating system that supports Directory Service Control Center.

Installation Privileges and Credentials

This section covers privileges or credentials required for installation of Directory Server Enterprise Edition component products.

• Directory Server, Directory Proxy Server, Directory Service Control Center, and Directory Server Resource Kit Privileges

Directory Server, Directory Proxy Server, Directory Service Control Center, and Directory Server Resource Kit Privileges

You must have the following privileges when installing Directory Server, Directory Proxy Server, or Directory Service Control Center from the Java Enterprise System native package based distribution.

• On Solaris, you must install as root.

• On Windows systems, you must install as Administrator.

You can install Directory Server, Directory Proxy Server, and Directory Server Resource Kit from the zip distribution without special privileges. See the Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide for details.

Installation Instructions

Directory Server Enterprise Edition Bundle Patch 6.3.1.1.1 delivers bug fixes mainly for Directory Service Control Center, Directory Proxy Server, and Directory Server. Only the upgrade mode is offered within version 6.3.1.1.1 using Native Packages or ZIP distribution.

Upgrade is supported only from Directory Server Enterprise Edition 6.3.1 to Bundle Patch 6.3.1.1.1. If you are using a pre-6.3.1 Directory Server Enterprise Edition version , you must upgrade to Directory Server Enterprise Edition 6.3.1 before you can apply Bundle Patch 6.3.1.1.1.

This section covers the following parts.

• Before You Upgrade

• Upgrading Directory Server Enterprise Edition to 6.3.1.1.1 Using Native Packages

• Upgrading Directory Server Enterprise Edition to 6.3.1.1.1 Using ZIP distribution

• Upgrading Directory Server Enterprise Edition 6.3.1 Native Packages to a 6.3.1.1.1 Zip installation

The following table identifies information for you to use to upgrade Directory Server Enterprise Edition to version 6.3.1.1.1 based on your current installation and the type of distribution you are using.

Table 2-1 Upgrade Paths to Directory Server Enterprise Edition Bundle Patch 6.3.1.1.1

Note - In general, it is a good practice to back up the directory databases regularly and particularly before upgrading the directory server. See the Sun Java System Directory Server Enterprise Edition 6.3 Administration Guide for information about backing up the database.

Before You Upgrade

You must stop all Directory Server and Directory Proxy Server instances before applying Directory Server Enterprise Edition Bundle Patch 6.3.1.1.1.

Native Package-Based Distributions

All Directory Server and Directory Proxy Server instances, including the DSCC registry, must be stopped before Directory Server Enterprise Edition Bundle Patch 6.3.1.1.1 is applied.

To use the localized console, apply the Directory Server Enterprise Edition 6.3.1 localized patch (if it is not already applied) before the Directory Server Enterprise Edition Bundle Patch 6.3.1.1.1. If you apply the Bundle Patch 6.3.1.1.1 before applying the 6.3.1 localization patch, then run the following commands in the specified order.

# dsccsetup console-unreg # dsccsetup console-reg

For more information, see bug 12207124/6583131 in Known Directory Server Issues in Bundle Patch 6.3.1.1.1.

Zip-Based Distributions

All Directory Server and Directory Proxy Server instances must be stopped before the Directory Server Enterprise Edition Bundle Patch 6.3.1.1.1 zip distribution is applied on top the 6.3.1 zip installation.

Note that the patchzip is not applied to the Directory Service Control Center until you undeploy and then redeploy the WAR file. This requirement is related to bug 124/65831311 in Known Directory Server Issues in Bundle Patch 6.3.1.1.1.

Upgrading Directory Server Enterprise Edition to 6.3.1.1.1 Using Native Packages

To Upgrade Shared Components Using Patches

Before You Begin

Before upgrading Directory Server Enterprise Edition to 6.3.1 using native packages, you must upgrade the shared components. On Solaris systems you must be root to perform this procedure.

Using patches, you can upgrade shared components on Solaris. .

Select the platform as per your requirements and install all the patches specified for that platform. If newer patch revisions become available, use the newer ones instead of those shown in the table. Note that DPS631U1 has been upgraded to 6.3.1.1.1 and validated with the level of shared components listed in this table

Choose the right NSS/NSPR/JSS patch for your system by getting the package version of SUNWpr and SUNtls on your system.

# pkginfo -l SUNWpr | grep VERSION
# pkginfo -l SUNWtls | grep VERSION    

Then choose the right patch series from the table below.

1. Shut down any processes using the shared components.
2. If applicable, stop the Common Agent Container and Sun Java Web Console.

   # cacaoadm stop
   # smcswebserver stop

3. Obtain the latest upgrade patches as shown in the tables above.

   For more information on how to obtain the patches, see Getting the Software.

4. Apply the appropriate patches for the shared components.

   Read the README.patchID file for detailed patch installation procedures.

5. Verify that the patch upgrades were successful.

   Read the README.patchID file for verification procedure.

6. If applicable, restart the shared components.

   # cacaoadm start
   # smcswebserver start

7. If your installation uses Identity Synchronization for Windows and you have applied the latest NSS patch 3.12 on your system, set symbolic links to the new libraries delivered in NSS patch 3.12, as shown in the following example. The default value of the SERVER_ROOT path name is /var/mps/serverroot.

   $ cd /var/mps/serverroot/lib
   $ ln -s /usr/lib/mps/secv1/libnssdbm3.so libnssdbm3.so
   $ ln -s /usr/lib/mps/secv1/libnssutil3.so libnssutil3.so
   $ ln -s /usr/lib/mps/secv1/libsqlite3.so libsqlite3.so
   
   $ cd /var/mps/serverroot/lib/sparcv9
   $ ln -s /usr/lib/mps/secv1/sparcv9/libnssdbm3.so libnssdbm3.so
   $ ln -s /usr/lib/mps/secv1/sparcv9/libnssutil3.so libnssutil3.so
   $ ln -s /usr/lib/mps/secv1/sparcv9/libsqlite3.so libsqlite3.so

To Upgrade Directory Server Enterprise Edition Using Native Packages

Before You Begin

Make sure all the shared components are up-to-date. For more information, see To Upgrade Shared Components Using Patches.

If you already have Directory Server Enterprise Edition 6.3.1 installed, upgrade to version 6.3.1.1.1 using the following procedure.

You must be root to perform these steps.

All the Directory Server instances, Directory Proxy Server instances, and configuration information remain unaffected after you complete the Directory Server Enterprise Edition upgrade.

The following table displays the patch numbers that are required to upgrade Directory Server Enterprise Edition on different platforms. If newer patch revisions become available, use the newer ones instead of those shown in the table.

Note - To make the localized Directory Server Enterprise Edition work successfully, install the localized patches before installing the core patches.

Each localization patch contains all the supported languages for the selected platform.

1. Stop the DSCC registry.

   # dsadm stop /var/opt/SUNWdsee/dscc6/dcc/ads

2. Stop any running instances of Directory Server and Directory Proxy Server.
3. Upgrade the shared components. See To Upgrade Shared Components Using Patches.
4. Download Directory Server Enterprise Edition Bundle Patch 6.3.1.1.1.

   See Getting the Software for more details.

5. Change to the directory where you have saved the patch listed in the preceding table.
6. Run the following command to install the patch.

   Before upgrading Directory Server Enterprise Edition, you must install 119254-38 on Solaris 10 SPARC and 119255-38 on Solaris 10 x86. See Getting the Software for information on downloading patches.

   Alternatively, use -G with the patchadd command on Solaris 10 SPARC and Solaris 10 x86 while applying the Directory Server Enterprise Edition upgrade patch. For example:

    # patchadd -G patch-id

   For other versions of Solaris, use the following command:

   # patchadd patch-id

7. Start the Directory Server instances and Directory Proxy Server instances, if any.
8. Start Web Console and Common Agent Container.
9. Restart the DSCC registry.

   # dsadm start /var/opt/SUNWdsee/dscc6/dcc/ads

Upgrading Directory Server Enterprise Edition to 6.3.1.1.1 Using ZIP distribution

To Upgrade Directory Server Enterprise Edition to Bundle Patch 6.3.1.1.1 Using ZIP Distribution

Before You Begin

You can install the zip distribution as a non-root user.

Note - In general, it is a good practice to back up the directory databases regularly, and particularly before upgrading the Directory Server. You cannot restore an earlier Directory Server configuration later. This advice applies to both Zip and Native Packages installations. See the Sun Java System Directory Server Enterprise Edition 6.3 Administration Guide for information about backing up the database.

The dsee_deploy command automatically updates the installation if it finds any previous installation. However, in the case of SuSE Linux 9 and HP-UX, before you upgrade the Directory Server Enterprise Edition installation, you must first upgrade the operating system to SuSE Linux 9 SP4 and HP-UX 11.23 respectively. Then use following procedure to upgrade your Directory Server Enterprise Edition installation to 6.3.1.1.1.

1. Stop CACAO and any running instances of Directory Server and Directory Proxy Server associated with the installation that you intend to patch. Also stop the application server that hosts the WAR file and the DSCC registry.
2. If the system you are upgrading is hosted on SuSE Linux 9 or HP-UX, upgrade your operating system.

   Upgrade SuSE Linux 9 SP3 to SuSE Linux 9 SP4.

   On SuSE 64-bit, .pam-32bit-9-yyyymmddhhmm.rpm is a prerequisite for CACAO to start, and you must install it if it is not already present on your system.

   Refer to the operating system documentation for information about how to upgrade the operating system, how to preserve the partition where Directory Server Enterprise Edition is installed, and where to get the latest patch bundles.

3. Upgrade Directory Server Enterprise Edition to Bundle Patch 6.3.1.1.1
   1. Use the dsee_deploy command from the Directory Server Enterprise Edition Bundle Patch 6.3.1.1.1 zip distribution, with the same installation path and the same CACAO port used in your previous installation of Directory Server Enterprise Edition 6.3.1. The dsee_deploy command will restart CACAO and DSCC registry.
      1. Obtain the zip distribution for this installation.

         Refer to the following table for information about the appropriate zip patch for your system. If newer patch revisions become available, use the newer ones instead of those shown in the table.

         All the multilingual files are included in the above mentioned patches.

         Operating System	Patch number
         Solaris SPARC	126748-06
         Solaris 9 x86	126749-06
         Solaris 10 x86 and AMD x64	126750-06
         Red Hat Linux	126751-06
         SuSE Linux	126751-06
         HP-UX	126752-06
         Windows	126753-06

      2. Install the prerequisite patches or service packs for your platform, as described in Operating System Requirements.
      3. Change to the zip distribution directory that contains the dsee_deploy command.
      4. Upgrade your Directory Server Enterprise Edition installation currently installed at install_path with the dsee_deploy command.

          $ ./dsee_deploy install -i install-path -p cacao-port options

         On Windows installations, browse to the zip distribution folder that contains the dsee_deploy command and run the following command:

         dsee_deploy install -i install-path options

         For example, the following command upgrades your existing Directory Server Enterprise Edition previously installed at /local directory, assuming that you have write access to the directory.

         $ ./dsee_deploy install -i /local

         You can also use the --no-inter option to install in non-interactive mode, accepting the license without confirmation. Non-interactive mode is particularly useful for silent installation.

         During the installation process, a WAR file is saved on your system. The WAR file contains the DSCC web application which when deployed with the application server enables you to access and manage the server instances through web console. The functionality is similar to DSCC in native packages. For more information about the WAR file, see “Installing Directory Service Control Center From Zip Distribution” in the Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide.

         During the installation process, the multilingual packages are also installed.

      5. Deploy the latest dscc.war file in the application server

         For step-by- step information, refer to “Installing Directory Service Control Center From Zip Distribution” in the Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide.

      6. Restart Directory Server and Directory Proxy Server instances and the application server for WAR file.
4. Start daemons only when both operating system and Directory Server Enterprise Edition are upgraded.

Upgrading Directory Server Enterprise Edition 6.3.1 Native Packages to a 6.3.1.1.1 Zip installation

To upgrade Directory Server Enterprise Edition 6.3.1 Linux or Windows native packages to a 6.3.1.1.1 zip installation, you must complete the following procedures:

• To Complete Pre-Upgrade Steps

• To Install Directory Server Enterprise Edition Bundle Patch 6.3.1.1.1

• To Upgrade DSCC

To Complete Pre-Upgrade Steps

Before You Begin

In general, it is a good practice to back up the directory databases regularly, and particularly before upgrading the Directory Server. You cannot restore an earlier Directory Server configuration later. This advice applies to both Zip and Native Packages installations. See the Sun Java System Directory Server Enterprise Edition 6.3 Administration Guide for information about backing up the database.

1. Record Common Agent Container settings.

   # cacaoadm-path list-params

2. Record DSCC registry port numbers.

   # dsadm-path info ads-path

3. Export DSCC registry content.

   • On Linux

     # /opt/sun/ds6/bin/dsconf export -p port cn=dscc /tmp/dscc.ldif

   • On Windows

     # "C:\Program Files\Sun\JavaES5\DSEE\ds6\bin\dsconf.exe" 
     export -p port -e cn=dscc c:\temp\dscc.ldif

4. Stop Directory Server services.

   • Stop all running Directory Servers (including DSCC registry).

     # dsadm-path stop instance-path
     # dsadm-path stop ads-path

   • Stop all running Directory Proxy Servers.

     # dpadm-path stop instance-path

5. Disable features specific to the native packages.
   1. (Linux only) Disable start at boot.

      • For any Directory Server instance registered to start at boot, type the following command:

        # /opt/sun/ds6/bin/dsadm autostart --off instance-path

      • For any Directory Proxy Server instance registered to start at boot, type the following command:

        # /opt/sun/dps6/bin/dpadm autostart --off instance-path

   2. (Windows only) Disable Windows services.

      • For any Directory Server instance registered to start at boot, type the following command:

        # "C:\Program Files\Sun\JavaES5\DSEE\ds6\bin\dsadm.exe" 
        disable-service --type WIN_SERVICE instance-path

      • For any Directory Proxy Server instance registered to start at boot, type the following command:

        # "C:\Program Files\Sun\JavaES5\DSEE\dps6\bin\dpadm.exe" 
        disable-service --type WIN_SERVICE instance-path

6. Unregister the DSCC Agent from the Common Agent Container.

    # dsccsetup-path cacao-unreg

7. If you use the Common Agent Container only for Directory Server Enterprise Edition, then stop the Common Agent Container.

   # cacaoadm-path stop

8. Unregister DSCC application from Java Web Console.

   # dsccsetup-path console-unreg

To Install Directory Server Enterprise Edition Bundle Patch 6.3.1.1.1

Run the following command:

# dsee_deploy install -i install-path options

This command works properly only if a Common Agent Container is not yet running on the default port, 11162. If you don't stop your previous Common Agent Container (step 7 of previous section), specify a different port using the -p option.

# dsee_deploy install -i install-path  -p port options

This command installs a Common Agent Container with the local Directory Service Control Center agent as well, allowing you to use DSCC to create server instances.

To Upgrade DSCC

1. Check Common Agent Container configuration.
   1. If you used the Common Agent Container only for DSEE, check that port numbers are recorded ports.

      # install-path/dsee6/cacao_2/cacao/bin/cacaoadm list-params

      Update if needed:

      # install-path/dsee6/cacao_2/cacao/bin/cacaoadm stop
      # install-path/dsee6/cacao_2/cacao/bin/cacaoadm set-param 
        snmp-adaptor-port=snmp-port
      # install-path/dsee6/cacao_2/cacao/bin/cacaoadm set-param 
        snmp-adaptor-trap-port=snmp-trap-port
      # install-path/dsee6/cacao_2/cacao/bin/cacaoadm set-param 
        jmxmp-connector-port=jmxmp-port
      # install-path/dsee6/cacao_2/cacao/bin/cacaoadm start

   2. If you should keep the native Common Agent Container alive, check that there is no conflict on port numbers with recorded ports.

      # install-path/dsee6/cacao_2/cacao/bin/cacaoadm list-params

      Update if needed:

      # install-path/dsee6/cacao_2/cacao/bin/cacaoadm stop
      # install-path/dsee6/cacao_2/cacao/bin/cacaoadm set-param 
        snmp-adaptor-port=snmp-port
      # install-path/dsee6/cacao_2/cacao/bin/cacaoadm set-param 
        snmp-adaptor-trap-port=snmp-trap-port
      # install-path/dsee6/cacao_2/cacao/bin/cacaoadm set-param 
        jmxmp-connector-port=jmxmp-port
      # install-path/dsee6/cacao_2/cacao/bin/cacaoadm start

2. Configure the DSCC registry.
   1. Create the DSCC registry using recorded ports.

      # install-path/dscc6/bin/dsccsetup ads-create -p port -P secure-port

   2. Import the /tmp/dscc.ldif file.

      • On Linux

        # install-path/ds6/bin/dsconf import -p port /tmp/dscc.ldif cn=dscc

      • On Windows

        # install-path\ds6\bin\dsconf.exe import -p port -e c:\temp\dscc.ldif cn=dscc

   3. If new port numbers are used for Common Agent Container, then:
      1. Unregister all the servers from DSCC registry.

         # install-path/dscc6/bin/dsccreg remove-server instance_path

      2. Register all the servers in DSCC registry.

         # install-path/dscc6/bin/dsccreg add-server instance_path

3. Deploy Directory Service Control Center.

   During the installation process, a WAR file is saved on your system. The WAR file contains the DSCC web application which, when deployed with the application server, enables you to access and manage the server instances through web console.

   • To Deploy the WAR File with Sun Java System Application Server

     1. Create an application server instance.

        $ mkdir /local/domainroot
        $ setenv AS_DOMAINS_ROOT /local/domainroot
        $ cd app-server-install-path/bin
        $ asadmin create-domain --domaindir ${AS_DOMAINS_ROOT} --adminport 3737 \
        --adminuser boss dscc

     2. Edit the server.policy file.

        1. Open the server.policy file.

           $ vi ${AS_DOMAINS_ROOT}/dscc/config/server.policy

        2. Add the following statements to the end of the file:

           // Permissions for Directory Service Control Center
           grant codeBase "file:${com.sun.aas.instanceRoot}/
           applications/j2ee-modules/dscc/-" 
           {
               permission java.security.AllPermission;
           };

           This configures the application server to grant all of the Java permissions to the DSCC application.

     3. Deploy the WAR file in your application server instance.

        $ asadmin start-domain --domaindir ${AS_DOMAINS_ROOT} --user boss dscc 
        $ cp install-path/var/dscc6/dscc.war ${AS_DOMAINS_ROOT}/dscc/autodeploy

        For more information about creating and configuring application server instances and deploying the WAR file, refer to the Sun Java System Application Server Online Help.

     4. Open DSCC.

        Use http://hostname:8080/dscc or https://hostname:8181/dscc based on the configuration of your application server.

        The Directory Service Manager Login page displays.

   • To Deploy the WAR File with Tomcat

     1. Identify your Tomcat installation and instance.

        $ setenv CATALINA_HOME tomcat-install-path
        $ setenv CATALINA_BASE tomcat-instance-path
        $ setenv JAVA_HOME jdk-home-dir

        For installing Tomcat and creating instances, refer to the Tomcat documentation.

     2. Deploy the WAR file.

        1. Create the DSCC directory as shown below:

           $ mkdir ${CATALINA_BASE}/webapps/dscc

        2. Copy the dscc.war file into newly created DSCC folder and unzip the dscc.war file.

           $ unzip -d ${CATALINA_BASE}/webapps/dscc install-path/var/dscc6/dscc.war

        3. Add the emphasized text in the ${CATALINA_BASE}/conf/web.xml file as shown below:

           ...
               <servlet>
                   <servlet-name>jsp</servlet-name>
                   <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
                   <init-param>
                       <param-name>fork</param-name>
                       <param-value>false</param-value>
                   </init-param>
                   <init-param>
                       <param-name>xpoweredBy</param-name>
                       <param-value>false</param-value>
                   </init-param>
               ...
                   <init-param>
                       <param-name>enablePooling</param-name>
                       <param-value>false</param-value>
                   </init-param>
                   <load-on-startup>3</load-on-startup>
               </servlet>
               ....

        4. Verify the permissions of startup.sh (tomcat5.exe on Windows) and run the following command:

           $ ${CATALINA_HOME}/bin/startup.sh

     3. Use http://hostname:8080/dscc to connect to DSCC.

        The Directory Service Manager Login page displays.

Uninstallation Instructions

If you plan to uninstall Directory Server Enterprise Edition 6.0, 6.1, 6.2, or 6.3 please refer to the chapter 3. "Uninstalling Directory Server Enterprise Edition" of Sun Java System Directory Server Enterprise Edition Installation Guide for 6.0, 6.1, 6.2, or 6.3. See the Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide.