test

Sun Java System Directory Server Enterprise Edition 6.2 Installation Guide

Installing Directory Service Control Center From 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 to enable you to do the following tasks:

The WAR file supports the following application servers:

The following two procedures contain information about deploying the WAR file with Sun Java System Application Server and Tomcat respectively.

ProcedureTo 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 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.

  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.

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

    The Directory Service Manager Login page displays.

ProcedureTo Deploy WAR File with Tomcat

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

The dscc.war is installed in the same way as any other web application, except the following settings:

The following example shows how to install DSCC in Tomcat on a Solaris 10 system.

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. 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.

  3. Deploy the WAR file.


    $ mkdir ${CATALINA_BASE}/webapps/dscc
$ unzip -d ${CATALINA_BASE}/webapps/dscc install path/var/dscc6/dscc.war
$ vi ${CATALINA_BASE}/conf/web.xml

    Add the emphasized text in the 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>
    ....
    		 

    $ ${CATALINA_HOME}/bin/startup.sh

    Verify the permissions of startup.sh.

  4. Use http://localhost:8080/dscc to connect to DSCC.

    The Directory Service Manager Login page displays.

ProcedureTo 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 /var/opt/SUNWdsee/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.


    # cacaoadm status
default instance is DISABLED at system startup.
Smf monitoring process:
13400
Uptime: 0 day(s), 0:16

    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:


    # cacaoadm start

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