Home » Adobe Manuals » Computer Software » Adobe 65015459 » Manual Viewer

Adobe 65015459 Server Guide - Page 30

Click Add on the Web Applications panel.

UPC - 883919159980

Add to My Manuals
Save this manual to your list of manuals

Page 30 highlights

ADOBE CONTRIBUTE CS3 27 User Guide Note: CPS requires that your J2EE application server be running version 1.4 or later of the JVM (Java Virtual Machine). The CPS application must run from an expanded directory structure. J2EE application servers vary in how you deploy the WAR file and create the expanded directory structure. Typically, there are two methods: 1 Deploy the compressed WAR file to a working directory. On some J2EE application servers (such as IBM WebSphere), the deployment process expands the WAR file into a working directory, and from that point forward, the expanded directory is considered to be the application. For these application servers, you deploy the compressed WAR file and work in the resulting directory structure. 2 Expand the WAR file and deploy the expanded structure as the working directory. On other application servers (such as JRun 4, BEA WebLogic, and JBoss), you expand the WAR file manually and then deploy the expanded directory structure, which becomes your working directory. Note: The reason that you must expand the WAR file and then deploy the expanded structure into a working directory on certain Java application servers is to prevent the server from extracting the compressed WAR file to a temporary directory each time the server is started. If this happens, the application data stored in the ckm.xml file is written over each time the server extracts the compressed WAR file to a temporary directory. The deployment method you use depends on your application server; see your Java application server documentation for information on deploying a WAR file. The following procedure demonstrates deploying CPS on a JRun 4 server. Note: The following procedure assumes that you have a preexisting version of JRun 4 installed. To deploy the WAR file on a JRun 4 server: 1 Manually expand the pubserver.war file in the installation folder. a At the command prompt, change to the CPS installation folder. 2 Create your working directory, using the following command: mkdir pubserver-war (UNIX) or md pubserver-war (Windows) a Change to your working directory, using the following command: cd pubserver-war b Expand the WAR file in your working directory, using the following command: java_home/bin/jar -xvf ../pubserver.war where java_home is the root directory of your Java Runtime Environment (JRE). 3 Start the JRun server if it is not already running. 4 Open a web browser, and enter the URL for the JRun Administration Console. Using the default installation location, the URL is: http://localhost:8000. The JRun Administration Console appears in your web browser. 5 Enter the JRun administrator's user name and password. 6 Expand the Default server icon in the left pane, and then click the J2EE Components icon. 7 Click Add on the Web Applications panel.

Section	Page
Contents	3
Chapter 1: Overview	4
Understanding Contribute user management models	4
Using Contribute Publishing Server with Contribute	5
Common website configurations	7
Deploying Contribute for a single website with one web server	7
Deploying Contribute for multiple websites on one web server	8
Deploying Contribute to a staging server and a live server	9
Deployment roles and responsibilities	11
Deployment tasks checklist	12
Chapter 2: Setting up your Contribute Server Environment	14
Preparing your web server before you deploy	14
Understanding network and server permissions	14
Understanding server access for connecting to CPS-managed websites	15
Restricting access to administrative folders and special file types	15
Apache web servers	15
Microsoft IIS web servers	16
Other web servers	16
Special files created by the draft review process	16
Planning your Contribute site structure and connection path	18
Understanding Contribute connection paths	18
Understanding subsites and overlapping website connections	19
Understanding Contribute network connection types	21
Network paths and web addresses (URLs)	24
Installing Contribute and creating an administrative connection	24
Preparing to connect to a website	24
Creating a Contribute website connection	25
Installing Contribute Publishing Server (Optional)	26
Software requirements	26
Installing Contribute Publishing Server using the Simple Installation	26
Installing Contribute Publishing Server by using the WAR File Installation	28
Chapter 3: Configuring Contribute	34
Configuring Contribute	34
About Contribute administrative settings	34
Configuring Contribute administrative settings	35
About Contribute user roles and settings	36
Creating Contribute roles	38
Configuring Contribute Publishing Server (CPS only)	40
Understanding Contribute user authentication models	40
About Contribute and LDAP or Active Directory	41
Authentication workflow	42
Configuring CPS User Directory and other services	43
Enabling Contribute websites to work with CPS (CPS only)	45
Adding users to your website (CPS only)	47
Deploying Contribute and website connections	49
Sending connection keys for websites	50
Sending connections for CPS managed sites	52
Deploying Contribute across an organization	52
Deploying Contribute CS3 by using Microsoft Systems Management Server	52
Uninstalling Contribute CS3	56
Index	57
A	57
about CPS 2	57
Add Users dialog box 45	57
Administer Website dialog box 43, 44	57
administration	57
settings, about 31	57
sitewide settings 32	57
administrator, responsibilities 8	57
C	57
child website 16	57
compressed WAR archive 27	57
connecting to a website that CPS manages 47, 49	57
connection key, sending 47	57
Connection Wizard 21	57
connections	57
about 18	57
child websites 16	57
creating a website 21	57
network path 22	57
overlapping 16	57
SFTP 19	57
URL 22	57
WebDAV 20	57
Contribute 45	57
Administer Website dialog box 43, 44	57
Enable Publishing Server dialog box 43	57
Log service 2	57
Publishing Server, enabling 42	57
User Directory, enabling 43	57
Contribute Publishing Server	57
about 2	57
case study 2	57
Simple Installation 23	57
using secure LDAP with User Directory 42	57
WAR File Installation 23, 25	57
CPS	57
about 2	57
Simple Installation 23	57
using secure LDAP with User Directory 42	57
WAR File Installation 23, 25	57
D	57
deploying	57
responsibilities 8	57
tasks 9	57
E	57
E-mail Notification, about 2	57
Enable Publishing Server dialog box 43	57
expanded WAR archive 27	57
F	57
FTP, connection information 22	57
I	57
installing	57
Contribute Publishing Server, Simple Installation 23	57
Contribute Publishing Server, WAR File Installation 23, 25	57
L	57
LDAP, using secure LDAP with User Directory 42	57
Log service, about 2	57
N	57
network	57
about 11	57
connection types, about 18	57
path and web addresses 21	57
O	57
overlapping, website connections 16	57
P	57
parent website 16	57
permissions, about 11	57
Publishing Server	57
enabling with Contribute 42	57
Publishing Server Console 40	57
Simple Installation 23	57
system requirements 23	57
using secure LDAP with User Directory 42	57
WAR File Installation 23, 25	57
web address 43	57
R	57
roles	57
about 33	57
Administrator 33	57
default 33	57
example of 34	57
Publisher 33	57
Writer 33	57
S	57
secure LDAP, using with User Directory 42	57
server permissions 11	57
services	57
E-mail Notification 2	57
Log 2	57
User Directory 2	57
SFTP connection information 19, 22	57
Simple Installation, Contribute Publishing Server 23	57
Sitewide Settings dialog box 32	57
staging servers, case study 6	57
system requirements 23	57
U	57
User Directory	57
about 2	57
enable 43	57
User Directory service, using secure LDAP (LDAPS) 42	57
user management	57
about 1	57
Contribute Publishing Server 1	57
manual connections 1	57
users, connecting to a website that CPS manages 47, 49	57
W	57
WAR	57
compressed archive 27	57
expanded archive 27	57
WAR File Installation, Contribute Publishing Server 23, 25	57
Web Application Archive, see WAR.	57
WebDAV connection information 20	58
website connections	58
child websites 16	58
creating 21, 22	58
overlapping 16	58
website, address (URL) 22	58

Match case Limit results 1 per page

ADOBE CONTRIBUTE CS3

User Guide

Note:

CPS requires that your J2EE application server be running version 1.4 or later of the JVM (Java Virtual Machine).

The CPS application must run from an expanded directory structure. J2EE application servers vary in how you

deploy the WAR file and create the expanded directory structure. Typically, there are two methods:

Deploy the compressed WAR file to a working directory.

On some J2EE application servers (such as IBM WebSphere), the deployment process expands the WAR file into a

working directory, and from that point forward, the expanded directory is considered to be the application. For these

application servers, you deploy the compressed WAR file and work in the resulting directory structure.

Expand the WAR file and deploy the expanded structure as the working directory.

On other application servers (such as JRun 4, BEA WebLogic, and JBoss), you expand the WAR file manually and

then deploy the expanded directory structure, which becomes your working directory.

Note:

The reason that you must expand the WAR file and then deploy the expanded structure into a working directory

on certain Java application servers is to prevent the server from extracting the compressed WAR file to a temporary

directory each time the server is started. If this happens, the application data stored in the ckm.xml file is written over

each time the server extracts the compressed WAR file to a temporary directory.

The deployment method you use depends on your application server; see your Java application server documen-

tation for information on deploying a WAR file. The following procedure demonstrates deploying CPS on a JRun 4

server.

Note:

The following procedure assumes that you have a preexisting version of JRun 4 installed.

To deploy the WAR file on a JRun 4 server:

Manually expand the pubserver.war file in the installation folder.

At the command prompt, change to the CPS installation folder.

Create your working directory, using the following command:

mkdir pubserver-war

(UNIX)

md pubserver-war

(Windows)

Change to your working directory, using the following command:

cd pubserver-war

Expand the WAR file in your working directory, using the following command:

java_home/bin/jar -xvf ../pubserver.war

where

java_home

is the root directory of your Java Runtime Environment (JRE).

Start the JRun server if it is not already running.

Open a web browser, and enter the URL for the JRun Administration Console.

Using the default installation location, the URL is: http://localhost:8000.

The JRun Administration Console appears in your web browser.

Enter the JRun administrator’s user name and password.

Expand the Default server icon in the left pane, and then click the J2EE Components icon.

Click Add on the Web Applications panel.