MACROMEDIA CONTRIBUTE 3 - DEPLOYING AND PUBLISHING... User manual

CONTRIBUTE

3
Deploying Contribute and
Contribute Publishing Server

Trademarks
1 Step RoboPDF, ActiveEdit, ActiveTest, Authorware, Blue Sky Software, Blue Sky, Breeze, Breezo, Captivate, Central,
ColdFusion, Contribute, Database Explorer, Director, Dreamweaver, Fireworks, Flash, FlashCast, FlashHelp, Flash Lite,
FlashPaper, Flash Video Encoder, Flex, Flex Builder, Fontographer, FreeHand, Generator, HomeSite, JRun, MacRecorder,
Macromedia, MXML, RoboEngine, RoboHelp, RoboInfo, RoboPDF, Roundtrip, Roundtrip HTML, Shockwave, SoundEdit,
Studio MX, UltraDev, and WebHelp are either registered trademarks or trademarks of Adobe Systems Incorporated and may be
registered in the United States or in other jurisdictions including internationally. Other product names, logos, designs, titles,
words, or phrases mentioned within this publication may be trademarks, service marks, or trade names of Adobe Systems
Incorporated or other entities and may be registered in certain jurisdictions including internationally.
Third-Party Information
This guide contains links to third-party websites that are not under the control of Adobe Systems Incorporated, and Adobe
Systems Incorporated is not responsible for the content on any linked site. If you access a third-party website mentioned in this
guide, then you do so at your own risk. Adobe Systems Incorporated provides these links only as a convenience, and the inclusion
of the link does not imply that Adobe Systems Incorporated endorses or accepts any responsibility for the content on those third-
party sites.
Opera ® browser Copyright © 1995-2002 Opera Software ASA and its suppliers. All rights reserved.
© 2002-2006 Adobe Systems Incorporated. All rights reserved. This manual may not be copied, photocopied,
reproduced, translated, or converted to any electronic or machine-readable form in whole or in part without written
approval from Adobe Systems Incorporated. Notwithstanding the foregoing, the owner or authorized user of a valid copy
of the software with which this manual was provided may print out one copy of this manual from an electronic version of
this manual for the sole purpose of such owner or authorized user learning to use such software, provided that no part of
this manual may be printed out, reproduced, distributed, resold, or transmitted for any other purposes, including,
without limitation, commercial purposes, such as selling copies of this documentation or providing paid-for support
services.
Acknowledgments
Project Management: Jennifer Rowe
Writing: Chris Bedford and Jennifer Rowe
Managing Editor: Rosana Francescato
Editing: Evelyn Eldridge and Lisa Stanziano
Production Management: Adam Barnett
Media Design and Production: Adam Barnett, Aaron Begley, and John Francis
Special thanks to Joel Huff, Vickie Chapman, Sarabjit Singh, and the Contribute engineering and QA teams.
First Edition: March 2006
Adobe Systems Incorporated
601 Townsend St.
San Francisco, CA 94103

3
Contents
Chapter 1: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Chapter 2: Preparing Your Network and Installing Contribute . . 17
Chapter 3: Configuring Contribute and Contribute Publishing
Server to work with your website. . . . . . . . . . . . . . . . . . . . . . . . . . . 41

4Contents

5
CHAPTER 1
Overview
Macromedia Contribute is a website editor that lets people connect to departmental and other
websites so that they can update web page content. Administrative assistants, product managers,
human resource managers, and other people in an organization can use Contribute to update
their team website without having to contact a web team or other departmental resources.
For larger organizations, you can optionally use Macromedia Contribute Publishing Server (CPS)
with Contribute. CPS is a user management and publishing solution that lets Contribute
administrators manage large groups of Contribute users and monitor what those users do on the
website.
This chapter, intended for website administrators and IT professionals, gives you valuable
information you need before you deploy Contribute, and optionally CPS, within an organization.
It explains the Contribute user management models for using Contribute alone or with CPS,
shows scenarios for setting up Contribute in a variety of IT environments, and lists the people
and the various tasks involved in successfully deploying Contribute.
This chapter contains the following sections:
•“Understanding Contribute user management models” on page 5
•“Common website configurations” on page 9
•“Deployment roles and responsibilities” on page 17
•“Deployment tasks checklist” on page 18
Understanding Contribute user management models
User management lets you add and remove user access to websites and create user roles that
restrict editing privileges within a site. User management also provides a mechanism that lets users
easily connect to a website.
Contribute has two user management models: manual site connections using Contribute only
and managed site connections using Contribute plus the CPS User Directory service.
Manual connections let you communicate connection information to users, who then create
their own connections, either by entering connection information in the Connection Wizard or
by importing a connection key file that you give them.

6Overview
This user model works best for smaller workgroups and organizations. It allows you to quickly set
up Contribute, create a connection to your website, define the necessary user roles, generate
connection information for the website connection/user role, and send it to users in the form of a
connection key file.
Managed connections lets you use CPS to integrate Contribute with your organization’s LDAP
or Active Directory services, giving you the ability to add and remove user access to a website and
modify user roles without having to resend connection key files to users. You can also create a file-
based database, using an XML file to manually enter user names and passwords.
CPS is intended for larger organizations that have several Contribute users to manage. CPS lets
you add and remove users from websites and roles without having to resend connection
information. When you create a connection to a website that uses CPS, you simply add users to a
list that grants access to a given website and user role. When users access the website, CPS
prompts them for a user name and password. After entering their user name and password, they
are granted access to the website and the role you’ve assigned to them.
To use CPS, you must have a J2EE application server such as Macromedia JRun installed. To
learn about other CPS functionality, see “Using Contribute Publishing Server with Contribute”
on page 6. For more information about getting CPS for your organization, see the CPS website at
www.macromedia.com/go/cps.
Using Contribute Publishing Server with Contribute
Using Contribute Publishing Server (CPS) with Contribute creates a powerful solution for
managing and maintaining your website.
CPS is a J2EE-based server application that lets you centrally manage large groups of Contribute
users. CPS includes of the following services:
User Directory service is a user management solution that lets you integrate Contribute with
your organization’s user directory to easily manage and authenticate users.
E-mail Notification service lets you automatically notify users about changes to web pages
within the draft review process.
Log service lets you monitor website activity so that you can easily troubleshoot problems.
CPS also has two other services that you can extend to meet your needs or use as they are:
Simple File Deployment service enables you to easily move files from a staging or testing
server to a live server
RSS Activity Feed service produces a syndication feed that lists changes that occur in any
folder on your website.
The biggest advantage to using CPS is the ability to integrate your organization’s user directory
services (such as LDAP or Active Directory) with Contribute. This gives you individual control
over which user is granted access to a particular website and the role to which they are assigned.

Understanding Contribute user management models 7
Consider a large organization with several decentralized websites. In addition to a public facing
site that provides information about the organization, there are several internal sites in use by
individual departments and workgroups. The organization uses LDAP as both a directory service
that lets users look up other employees as well as an authentication service through which
administrators set permissions limiting users’ access to file-sharing servers and other network
resources.
Unlike sites that don’t use CPS to manage users, when a user logs in to a CPS website, the User
Directory service retrieves the connection information associated with that user, and provides
access to the sites the administrator has assigned. By maintaining site connection information
within the User Directory, administrators can add or remove access to websites without having to
resend connection information.
This example provides a partial listing of employees from an organization’s user directory. The
employees, their workgroup affiliations, and the sites they can access are listed in the following
table:
Although this user list is oversimplified, it demonstrates one possible scenario for the way that
users within an organization might be assigned access to websites. This scenario divides users
according to their role within the organization, and assumes that they have full editing and
publishing privileges within their respective sites. Certain users have access to all the sites. For
example, the product managers, John Lydon and Malcolm McClaren, work with all the teams in
developing and launching products, and need to contribute to all the sites.
User Workgroup Websites
John Lydon Product Management Sales, Production, Marketing
Malcolm McClaren Product Management Sales, Production, Marketing
Martin Atkins Marketing Marketing
Keith Levine Sales Sales
John Savage Production Production
Laura Logic Web Design Sales, Production, Marketing
Jah Wobble Contribute Administrator Sales, Production, Marketing

8Overview
Likewise, web designer Laura Logic and Contribute administrator Jah Wobble have access to all
sites. As the web designer, Laura provides templates that are easy to add content to and that fit the
needs of users collaborating internally. The templates she maintains include those for taking
meeting minutes, for scheduling, and for providing product specifications, marketing launch
plans, and sales projections, to name a few. Laura also collaborates with Jah Wobble, the
Contribute administrator, to help determine the editing and publishing privileges for individual
users and roles.
User list input from directory
service (LDAP, Active Directory)
Sales Marketing Manufacturing
User Directory manages users
and their connections
PUBLISHING SERVICE
SERVER
Users... John Lydon, Martin
Atkins, Keith Levine, Laura...
DIRECTORY SERVICE

Common website configurations 9
CPS integrates with the organization’s LDAP service, which authenticates user access to various
network resources. In this case, the LDAP authentication is the first step in granting access to
websites hosted on various servers within the organization. The Contribute roles further define
user privileges within a website, determining the degree to which users can modify pages within
the site.
Common website configurations
Before you deploy Contribute, you should consider various scenarios for setting up Contribute
for large or multi-team organizations.
This section describes three primary configurations for you to consider as you set up a Contribute
site.
Single website on one webserver Typically, this is a website where users have read access to
the root of the site and read/write access to specific folders in the site as controlled by the file
server or network permissions. There is a single root folder and all users access the site using
the same Contribute connection. If this applies to your site, see “Deploying Contribute for a
single website with one webserver” on page 10.
Multiple websites on one webserver In this structure there is a single root folder. The root
folder contains folders for each section or organizational function within the website.
Contribute roles are used to control user access to particular folders on the site and to assign a
subset of the common templates used on the site. Although not required, file server
permissions are usually used in addition to Contribute roles to restrict user access to sections of
a site. If this applies to your site, see “Deploying Contribute for multiple websites on one
webserver” on page 12.
Website on a staging server and a live server Many websites use a staging web server with
their production web server. Staging servers let you create and test web content without
making it live on your public facing website. Only when content has been approved are web
pages and their associated files copied from the staging to the production web server. When
used with Contribute, a staging server adds an extra measure of security because you can
configure your staging server so that Contribute specific files (such as administrative folders,
rollback files, and interim drafts) are not copied to the publicly accessible website outside your
network firewall. For more information, see “Deploying Contribute to a staging server and a
live server” on page 14.
Depending on how your website is structured, you need to use separate strategies to successfully
set up Contribute for multiple users and groups. Specifically, you’ll need to think about where to
store the Contribute shared settings file, how to prevent overlapping connection paths, and how
you’ll send connections to users.
Deploying Contribute for a single website with one webserver
In this example, Contribute is deployed to a simple intranet consisting of a single web server
hosting a departmental website. The website has a single, common root folder with subfolders for
individual departments. The site uses Dreamweaver templates and CSS styles to enforce the look
and feel of the website and SSIs to maintain page elements such as navigation menus, headers,
and footers.

10 Overview
The key to this arrangement is that all users have the same Contribute site connection. In other
words, there is a single connection point for all users that controls the behavior of Contribute
when editing the website. If you want to restrict users to editing content in their workgroup’s
folder, you would need to create a role that limits access to a specific folder.
An advantage to this type of Contribute deployment is that users in all departments can
collaborate by sending pages for review to one another. If separate connections had been created
for each department (as in the example “Deploying Contribute for multiple websites on one
webserver” on page 12), then only the users with access to that folder could receive and edit drafts
sent to them for review.
It is important that the Templates folder, which is located at the same level as the Contribute
shared settings folder (_mm), is accessible by all users, and the site’s CSS (CSS folder), and server
side includes (SSI folder) are protected by role settings that restrict access to those folders. Web
pages and associated files stored in these folders cannot be edited using Contribute, preventing
them from being inadvertently modified or damaged. If you want to restrict users to editing
content in their workgroup’s folder, you need to create a role that limits access to a specific folder.
Team Sites _mm(Shared settings) TemplatesSSICSS
WEB SERVER HOSTING
INTERNAL SITES
Sales Manufacturing Marketing