
	Core Development Guide

CHAPTER 17 Using Dreamweaver with Director

This chapter describes Director support for Dreamweaver, a third-party editor for creating and managing HTML-based Web sites. Dreamweaver provides a full suite of tools for developing Web pages.

This chapter includes these sections:

This chapter assumes that you have installed Director and either Dreamweaver or Dreamweaver UltraDev.

About Director integration with Dreamweaver

Director integration with Dreamweaver consists of a plug-in extension to Dreamweaver. While using the Dreamweaver work area to edit a Director PID page, you can insert a component by selecting from a list of all components in the portal WAR of a deployed Director application.

For more information For instructions on installing and using the Director extension for Dreamweaver, see Inserting Director component tags in Dreamweaver.

Dreamweaver (like any WebDAV-enabled application) has the ability to access a deployed Director application as a remote site. In other words, the Dreamweaver Site Manager can use WebDAV to connect to the Content Management repository in a deployed Director application. You can then use Dreamweaver to create, edit, upload, download, synchronize, check in, and check out HTML pages.

For more information For instructions on accessing a Director application using WebDAV, see the Site Manager documentation in Dreamweaver and/or the WebDAV chapter in the Director Content Management Guide.

PID pages, however, are not typically stored in the Content Management repository of a Director application; they are stored in a resource set. Thus in order to use the Director plug-in extension for Dreamweaver in combination with WebDAV, you must configure the Director application so that it can fetch and display PID pages from the Content Management repository.

For more information For instructions, see Configuring Director to display PID pages from Content Management.

Inserting Director component tags in Dreamweaver

The Director extension for Dreamweaver provides an interface between the Dreamweaver work area and the component manager of a deployed Director portal application running on an exteNd application server. This extension works with both Dreamweaver and Dreamweaver UltraDev.

This section describes:

Installing the Director extension for Dreamweaver

Procedure To install the Director extension for Dreamweaver:

Unless you have already done so, click here to download and install the Macromedia Extension manager:

The Macromedia Extension manager is a free add-in product from Macromedia that simplifies the process of adding third-party extensions to Dreamweaver, UltraDev, and Fireworks.
Start Dreamweaver and click Commands>Manage Extensions.
Click the icon as shown or click File>Install Extension.
Browse to eXtendDirector\utilities\Dreamweaver.
Select the file Director_Package.mxp.
Click the Install button.
Click Accept to accept the terms of the license agreement.
When you see the completion message, click OK.
Restart Dreamweaver.
Click Commands>Manage Extensions.
Confirm that the Extension Manager shows SilverStream eXtend Director integration as an installed extension.
Close the Extension Manager.

Inserting a component tag into a Dreamweaver page

The Director extension for Dreamweaver allows you to insert component tags into PID pages by selecting from a list of the components in the portal WAR of a deployed application.

Procedure To insert a component tag:

In the Dreamweaver work area, position the cursor where you want to insert a component.
Click Commands>SilverStream Director>Director Insert Component
In the Director Insert Component dialog, specify:
- Hostname/IP :port
  
  The host name (or IP address) of the exteNd Application Server.
- Database:
  
  The name of the Director database on the application server.
- Portal Location(Portal or namespace/Portal)
  
  For example, if the name of the deployed application is TypiCorp, enter TypiCorp/Portal.
Click the Get Component List button.

The Director Insert Component dialog displays a list box that shows all components in the target portal.
Select a component and click Insert Component.

The extension inserts an s3-component tag and a corresponding icon at the specified location.
```
  <s3-component id="PhoneList"  instance="PhoneList1" />
```

Configuring Director to display PID pages from Content Management

By default, the Portal subsystem of a Director application fetches and displays PID pages from resource sets. You can, however, configure the application to fetch and display PID pages from the Content Management repository. This requires modifying the web.xml for your Portal to include the Content Management resource servlet. This servlet allows for URL access to any object in the Content Management system via path or document ID. By adding the initialization parameters shown below, this servlet can also render portal pages (PIDs) stored in the CM system by forwarding the HTML to the Presentation Manager so that any component tags can be processed.

Procedure To configure the Director application:

Before deploying your Director project: add the following lines to the Portal WAR's web.xml file:

  <servlet>
  <servlet-name>cmresources</servlet-name>
  <servlet-class>com.sssw.cm.servlet.EboResourceServlet</servlet-class>
  <init-param>
    <param-name>enable-pid-support</param-name> 
    <param-value>true</param-value> 
  </init-param> 
  <init-param>
    <!--This is the directory in the cm system that stores pids-->
    <param-name>pid-path</param-name> 
    <param-value>/cmpages</param-value> 
  </init-param>
  </servlet>
  <servlet-mapping>
    <servlet-name>cmresources</servlet-name>
    <url-pattern>/cmresources/*</url-pattern>
  </servlet-mapping>

The Content Management resource servlet (EboResourceServlet) has two initialization parameters:

enable-pid-support

If enable-pid-support is true, the resource servlet checks the incoming path of the Content Management document. If it matches the path set under pid-path, the resource servlet assumes that the HTML document is a PID page and sends it to the Presentation Manager for processing, with the MIME type as designated by the Content Management subsystem. Objects in all other path locations are returned as is.
pid-path

The pid-path designates one specific folder in the Content Management repository as storage for PID pages. Restricting PID pages to a single folder is necessary for performance reasons. Content Management folders potentially contain vast numbers of large documents. Scanning every document for s3-component tags would be quite inefficient.

NOTE: Set your Dreamweaver remote site folder to the pid-path folder.

NOTE: Images and other objects used by a PID page also must be stored in the Content Management subsystem. The resource servlet does not modify the relative URLs contained in the page.

Procedure To access PID pages in the Content Management repository through the resource servlet:

Specify the pid-path folder in the URL.

For example, if the servlet name is cmresources and the pid-path folder is cmpages you would specify:
```
  http://localhost/Director/Portal/cmresources/cmpages/test.html
```

To access a PID page in the Content Management repository from another PID page, use the CMPIDReader component. CMPIDReader accepts a single parameter CMPATH that represents the path to the PID page that is being retrieved from the Content Management system. The CMPATH can sent via an s3-component tag or an HTML request. Examples:

  <s3-component ID="CMPIDReader" NAME="CMPIDReader" CMPATH="/cmpages/test.html" />
  
  http://localhost/Director/Portal/main/comp/CMPIDReader?cmpath=%2fcmpages%2ftest.html


	Core Development Guide