### How to get the DSEE 6.3 Zip/Compressed Archive Distribution installed properly on Windows 2003

The Zip/Compressed Archive version of the DSEE 6.3 product is not the same as the JES 5u2 or Native DSEE 6.3 installation. You need to pay attention to your "Distribution Type" that you download, there is a big difference in the delivery of the product between the "Native / Package" version and the "Zip / Compressed archive" version of the product. Currently we do not have the 6.3 native (JES) version of the product available for download on Windows. This guide is meant as a "get 6.3 zip distribution deployed quickly" guide.

In this article we will be focusing on installing on windows 2003

To follow along in the 6.3 install guide, you would follow these steps as laid out here:

http://docs.sun.com/app/docs/doc/820-2761/install-bits-zip?a=view

really, simplified, here are the steps I performed to get my configuration running, and starting up properly after a system reboot.

cd into the DSEE.6.3-Windows-x86\\DSEE_ZIP_Distribution directory and run your

.....dsee_deploy install -i c:\\path\\to\\wherever-u-want-it-installed

where c:\\path\\to\\wherever-u-want-it-installed is whatever path you want the DS installed to
after the install completes, you need to set up the DSCC Registry

.....cd c:\\{install path}\\dscc6\\bin

A few of these next steps seem to be "missing" from the install, I'm reviewing if they are covered somewhere else.

.....cd c:\\{install-path}\\ds6\\bin\\

Once the DSCC registry is set up you are ready to install the Java Development Kit and Sun Java Application Server 9.1 to run the DSCC web application.

Download the current j2sdk (i used the JDK 6 Update 6 from http://java.sun.com/javase/downloads/?intcmp=1281 ), and the sun application server 9.1 (from http://www.sun.com/download/index.jsp?cat=Application%20%26%20Integration%20Services&tab=3&subcat=Application%20Servers ) run the j2sdk installer first, and then the application server installer. Keep track of the passwords you set. Accept the defaults for both installers, pay attention and add the application server as a service when asked by checking the option (not a default). Also, as the application server installer asks, tell it to start the server.

You need to follow the instructions laid out in step 3.b the 6.3 install guide for the manual edit of the server.policy file as detailed here: http://docs.sun.com/app/docs/doc/820-2761/install-dscc-zip?a=view

In my installation the file was in the path

c:\\appserver91\\domains\\domain1\\config\\server.policy

I copied/pasted the example text of step 3.b from the link above.

--snip

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

-- snip

Stop and start the application server from the windows Start>>Programs>>Sun Microsystems>>Application Server 9.1>> menu for the edit of the server.policy file to take
You will connect to the application server administration port with a web browser to deploy the DSCC web application through the GUI rather than the command line steps given in the DSEE 6.3 install guide. Connect to http://localhost:4848 and you will see the application server management console (after logging in). Click on "web applications" on the left side, on the right side of the screen click on the "Deploy.." button

Select the "Local Packaged file or directory..." option, and click on the "browse files" button. You will want to select the dscc.war file which will be located in the path c:\\{install root}\\var\\dscc6\\dscc.war where {install root} is where you set with your -i switch to the dsee_deploy command.

Once you have selected the dscc.war, and return to the application server deploy screen, make sure "application name" and "context root" on the form are set to dscc, you can add a note to the "description" field like "directory 6.3 zip distribution DSCC" to identify the install. Click OK to submit the form and deploy the DSCC web application.

You can "launch" the web application from the application server admin. You can also connect to http://[hostname]:8080/dscc to use the dscc web application to create your first DS instance and get started using the console to manage the DS.

\* note that you can substitute "localhost" in the above URL's to the FQDN of the host you are running the DS/application server on.

You need to add the following steps to have the CACAO service properly start up on reboot. It is important you understand how the CACAO works on windows.

The CACAO service should not be started/stopped through the windows service controls manager console. The only proper way to start the CACAO service is when the system is booting up.

The registration of the CACAO service is not complete until you perform a set of manual steps to "enable" the service at system reboot, as well as getting windows to grant the account the CACAO is running as the "logon as a service" privilege.

To configure the CACAO service properly you will need to do the following

.....cd c:\\{install-path}\\dsee6\\cacao_2\\bin\\
.....edit pswd.txt

(you will create a one line file that has the password of the user the DS will run as - administrator in my test)

.....cacaoadm status (note the DISABLED state returned)
.....cacaoadm start (wait about 10 seconds or so for the service to start)
.....cacaoadm status (you should now see its "Enabled")

There is one final step left, which is to go into the windows services control manager select the "Common Agent Container" (Start >> Administrative Tools >> Services >> "Common Agent Container...". You will right click on it and select "properties". In the Properites dialog, there is a "logon" tab. You need to re-enter the password for the account you are running the services as (Administrator in my test case) entering the password here will trigger the system setting the "logon as a service" permission for this account, which is needed for the CACAO service to start at boot time.

As you apply/close you will see a dialog notifying you that the "logon as a service" has been granted.

Keep in mind that if you are going to use a port for the Directory service under 1024 (the defaults are 389 and 686), that you must install the DS with an account that is "privelidged"... that is part of the local administrators group (by direct membership).

hi Sir thanks alot i followed each and every step and i was able to install DSEE 6.3 on windows server 2003 THANKS A ZILLIONN THANK U THANK U GOD BLESS U

Posted by NOOR RAZA CHEEMA on April 26, 2010 at 02:10 PM PDT #

Can u plz tell me what should be my next steps i should proly craete a new directory server ? so that i can view the directory server console:S???

Posted by NOOR RAZA CHEEMA on April 26, 2010 at 06:46 PM PDT #

You should take the time to read through the deployment guide, given the differences in the 6.x DSEE. The DSCC is the "console" for the 6.x and 7.x DSEE.

Also, for any kind of procedural activities are presented in the administration guide. You can completely manage the DS instances from the command line as well as the DSCC. The DSCC offers nice features like server groups, cloning server configurations,etc.

You'll save yourself considerable confusion (and time trying to fix things) with a simple investment up front in the overviews provided in the deployment guide for the DSCC.

The DSEE installation documentation goes on to discuss setup/use of the DSCC, as well as creating your fist instance from the command line.

To follow the documenation you have to understand the distribution type (ZIP or Package/JES). Depending on what distribution type you will either install an app server to deploy the WAR file for the DSCC, or have the DSCC running in the JES installed SMC Webserver. Please see my other blog post "http://blogs.sun.com/DSHelpDesk/entry/understanding_the_directory_server_distributions" ) to review and clarify for yourself what distribution type you are using.

The 6.3 documentation collection can be reviewed as a set here:

http://docs.sun.com/app/docs/coll/1224.4?l=en

Posted by Todd Grayson on April 26, 2010 at 11:36 PM PDT #

You should take the time to read through the deployment guide, given the differences in the 6.x DSEE. The DSCC is the "console" for the 6.x and 7.x DSEE.

Also, for any kind of procedural activities are presented in the administration guide. You can completely manage the DS instances from the command line as well as the DSCC. The DSCC offers nice features like server groups, cloning server configurations,etc.

You'll save yourself considerable confusion (and time trying to fix things) with a simple investment up front in the overviews provided in the deployment guide for the DSCC.

The DSEE installation documentation goes on to discuss setup/use of the DSCC, as well as creating your fist instance from the command line.

To follow the documentation you have to understand the distribution type (ZIP or Package/JES). Depending on what distribution type you will either install an app server to deploy the WAR file for the DSCC, or have the DSCC running in the JES installed SMC Webserver. Please see my other blog post "http://blogs.sun.com/DSHelpDesk/entry/understanding_the_directory_server_distributions" ) to review and clarify for yourself what distribution type you are using.

The 6.3 documentation collection can be reviewed as a set here:

http://docs.sun.com/app/docs/coll/1224.4?l=en

Posted by Todd Grayson on April 26, 2010 at 11:37 PM PDT #

• HTML Syntax: NOT allowed