Site Server 3.0 Content Deployment with UNIX Readme

August 1999

Microsoft Corporation

Introduction

Content Deployment with UNIX, included in the Site Server 3.0 Commerce Edition Resource Kit, stages and deploys Web pages and other file-based information between directories, among local servers, or across geographically remote, secured networks to multiple destination servers.

UNIX servers are viable end-point servers for and that can receive content from Microsoft® Windows NT® staging servers. Microsoft® Site Server 3.0 Commerce Edition includes Content Deployment binaries for UNIX SUN Solaris, version 2.5 and version 2.5.1 platforms. To enable porting to other UNIX platforms, the source code for UNIX end-point servers is included when you download and install the Resource Kit. Follow the instructions in this document to transfer and customize the source code located in \SS3RK\ResKit\Code\cdx\.

This Readme provides installation instructions and the directory structure for Content Deployment with UNIX.

! WARNING   Do not expose these UNIX end-point servers directly to the Internet. Although Content Deployment with UNIX uses an algorithm to encrypt the passwords being passed from Windows NT to UNIX, we recommend that you do not deploy content from Windows NT to UNIX over an unsecured network.

Installing Content Deployment with UNIX

When installing Content Deployment with UNIX, you must use ftp to transfer the archive file to your UNIX server. Once the file is on your UNIX server, you can then uncompress the archive and build the binary files. To do this:

  1. Use ftp to transfer the archive file \SS3RK\ResKit\Code\cdx\cd_unix.tar.gz in binary mode to your UNIX server.

  2. Uncompress the file cd_unix.tar.gz. For example, enter the following at the command line: # gunzip cd_unix.tar.gz | tar xvf cd_unix.tar.

  3. Modify the makefiles in the /bin directory for your UNIX platform.

  4. Build the executable files (binaries) for the Content Deployment with UNIX end-point server. For example, make -f bin/makefile.

  5. Modify the installation script in the /install directory for your UNIX platform, if necessary.

  6. Run the shell script /install.sh to install Content Deployment.

  7. Refer to the documentation (man pages in the /man directory) for details about running Content Deployment with UNIX. (You need to add yourself to the cdxadmin group on the UNIX computer.)

! WARNING   Do not expose these UNIX end-point servers directly to the Internet. Although Content Deployment with UNIX uses an algorithm to encrypt the passwords being passed from Windows NT to UNIX, we recommend that you do not deploy content from Windows NT to UNIX over an unsecured network.

Content Deployment with UNIX Directory Structure

Content Deployment with UNIX has the following directory structure:

Directory   Files Contents
/cdx      
  /bin Contains all of the files necessary for building Content Deployment.
  /crssetup File used to convert files with a DOS extended-character set to corresponding ISO standard characters. You should not need to do this because cd_unix.tar.gz has already converted the files. Use this file only if you need to edit the text files on a DOS console and ftp them to the UNIX computer.
/crsunix.mk List of source files to build and the corresponding object files to produce.
/makefile Makefile used to build the source files.
/mkrel Controls the building of the files.
/rmsemshm Controls the removal of semaphores and shared memory when sscdx stop is run.
/sscdx Controls the startup/stop for Content Deployment.
/vars.mk Environment file used to set up the correct variables used during building.
/version Version file.
/config   Contains the configuration parameters used by Content Deployment.
  /cdx Parameters used by Content Deployment.
/readme Contains important, late-breaking information about Content Deployment Unix (CDX). For additional late-breaking information and instructions on contacting Microsoft for product support, and for information about Microsoft Site Server 3.0 Commerce Edition documentation, see readme_siteserver.htm for Site Server 3.0 Commerce Edition.

Note   For optimal results, the file system where the CRSTemp directory resides should never become full. Reporting of this condition by CDX varies, depending upon the state of the replication and when the file system becomes full. Under some conditions the replicated content could be removed from the destination. To recover, free space on the file system and rerun the replication.
/install   Contains the UNIX shell script for installing Content Deployment.
  /install.scr Installs Content Deployment on the UNIX platform.
/install.sh Determines what operating system to install on.
/license   Contains the license source files.
  /license Contains the following license files:

/license.cpp

/license.h

/lics.app

/lics111.cpp

/lics111.h
  /unix Contains the license files for Content Deployment with UNIX.
/man   Contains the man page for Content Deployment.
  /cdx.1 Contains documentation about Content Deployment that can be viewed through man commands.
/server   Contains all of the source code used to generate the service that you run on UNIX machines.
  /bldver.h

/cdxcat.log

/check.cpp

/check.h

/clog.cpp

/clog.h

/cmap.cpp

/cmap.h

/coblock.cpp

/coblock.h

/common.h

/crc32.h

/crsapi.h

/crscntrs.h

/crscntrs.ini

/crsdll.def

/crsdll.mak

/crsdll2.rc

/crsmsg.mc

/crsmsgx.h

/cserve.cpp

/cserve.h

/csock.cpp

/csock.h

/debug

/dirscan.cpp

/dirscan.h

/filemap.cpp

/filemap.h

/filepars.cpp

/filepars.h

/glblcfg.cpp

/glblcfg.h

/global.cpp

/global.h

/log.h

/mailsupp.cpp

/mailsupp.h

/md5.h

/md5c.cpp

/msghdr.h

/ntcode.cpp

/ntcode.h

/package.cpp

/package.h

/pathname.cpp

/pathname.h

/perf.cpp

/perf.h

/perflib.cpp

/perflib.h

/priv.cpp

/priv.h

/projcfg.cpp

/projcfg.h

/project.cpp

/project.h

/queue.cpp

/queue.h

/repl.cpp

/repl.h

/resource.h

/route.cpp

/route.h

/secret.cpp

/server.dsp

/server.dsw

/server.opt

/simple.cpp

/simple.h

/stypes.h

/transact.cpp

/transact.h

/uxconfig.cpp

/uxconfig.h

  

Information in this document, including URL and other Internet web site references, is subject to change without notice.  The entire risk of the use or the results of the use of this resource kit remains with the user.  This resource kit is not supported and is provided as is without warranty of any kind, either express or implied.  The example companies, organizations, products, people and events depicted herein are fictitious.  No association with any real company, organization, product, person or event is intended or should be inferred.  Complying with all applicable copyright laws is the responsibility of the user.  Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document.  Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 1999-2000 Microsoft Corporation.  All rights reserved.

Microsoft, Windows and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries/regions.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.