Installing Directory Service Control Center Using the Zip Distribution

The Directory Server Enterprise Edition zip distribution includes a WAR file (dscc.war) that contains the Directory Service Control Center (DSCC) web application. The WAR file is deployed with the application server, which makes it possible to be out of the Sun Java Web Console and enables you to do the following:

• Connect to DSCC without having an operating system login account on the system hosting DSCC.

• Deploy DSCC without root privileges as the application server enables DSCC.

The WAR file supports the following application servers:

• Sun Java System Application Server 8.2 Enterprise Edition included in Sun Java Enterprise System 5.0

• Tomcat 5.5

  ---

  Note –

  If you deploy the WAR file in Tomcat, make sure that tag pooling is disabled. To disable tag pooling, edit the tomcat-instance-path/conf/web.xml file and add the following text:

  <init-param> <param-name>enablePooling</param-name> <param-value>false</param-value> </init-param>

  ---

You can deploy the WAR file with any of the compliant application servers. The following procedure contains information about deploying the WAR file with Sun Java System Application Server.

To Deploy the WAR File with Sun Java System Application Server

After you install Directory Server Enterprise Edition, the WAR file, dscc.war, is at install path/var/dscc6/.

The steps might differ depending on the application server that you use to deploy the WAR file. For information about deploying the WAR file using other application servers, see the respective server documentation.

1. Initialize the DSCC registry.

   $ install path/dscc6/bin/dsccsetup ads-create Choose password for Directory Service Manager: Confirm password for Directory Service Manager: Creating DSCC registry... DSCC Registry has been created successfully

2. Create an application server instance.

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

3. Edit server.policy file.

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

   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.

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

   $ asadmin start-domain --domaindir ${AS_DOMAINS_ROOT} 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.

5. Open DSCC.

   Depending on the configuration of your application server , use http://localhost:8080 or https://localhost:8181 to connect to DSCC.

   The Directory Service Manager Login page displays.

To Troubleshoot Problems Accessing Directory Service Control Center

Use this procedure on the host where you installed DSCC.

1. Verify that DSCC has been initialized properly.

   $ install-path/dscc6/bin/dsccsetup status *** Sun Java (TM) Web Console is not installed *** DSCC Agent is registered in Cacao Cacao uses a custom port number (11168) *** DSCC Registry has been created Path of DSCC registry is install-path/var/dscc6/dcc/ads Port of DSCC registry is 3998 ***

2. If you see errors that pertain to the DSCC agent, check the status of Common Agent Container.

   The cacaoadm(1M) man page describes the error codes that the command returns. For the exact location of this command on your system, see Command Locations.

   You must run the cacaoadm command as the user who performed the installation. Otherwise, run the command as root.

   After installing Directory Server, the Common Agent Container starts automatically. However, when you reboot, you might have to start the Common Agent Container manually as follows:

   # instance-path/dsee6/cacao_2.0/usr/lib/cacao/bin/cacaoadm status default instance is DISABLED at system startup. Smf monitoring process: 13400 Uptime: 0 day(s), 0:16

   For more information about the Common Agent Container, see Sun Java Enterprise System 5 Monitoring Guide.