eroom 7 server upgrade and configuration guide · eroom 7 server upgrade guide documentum, inc., a...

eRoom 7 Server

Upgrade Guide

Documentum, Inc., a division of EMC6801 Koll Center Parkway, Pleasanton, CA 94566

(925) 600-6800

eRoom 7 Server Upgrade Guide | i

COPYRIGHT

Copyright © 1997-2004

Documentum, Inc., a division of EMC6801 Koll Center Parkway, Pleasanton, CA 94566(925) 600-6800

Trademarks

Documentum® Documentum RightSite®, Documentum Server®, Docbasic®, Documentum DocPage Server®, Now You Know®, Documentum WorkSpace®, Documentum SmartSpace®, Documentum ViewSpace®, AutoRender Pro™, Docbase™, DocInput™, Docobject™, DocPage Builder™, Documentum 4i™, Documentum Administrator™, Documentum CADLink™, Documentum Commerce Server Integrators™, Documentum Application Server Integrators™, Documentum Content Authentication Services™, Documentum Content Personalization Services™, Documentum ContentCaster™, Documentum Corrective Action Manager™, Documentum Desktop Client™, Documentum Developer Studio™, Documentum DocControl Manager™, Documentum DocLoader™, Documentum DocViewer™, Documentum Dynamic Content Assembler™, Documentum eConnector for CAD™, Documentum eConnector™ for IBM WebSphere® (IBM and WebSphere are trademarks of IBM) Documentum eConnector for SAP™ (SAP is a trademark of SAP AG), Documentum eConnector™, Documentum eConnector™ for BEA Weblogic® (BEA is a registered trademark of BEA Systems Inc) Documentum eConnector™ for JDBC, Documentum eConnector™ for ATG Dynamo® (ATG and Dynamo are registered trademarks of Art Technology Group), Documentum eConnector™ for Lotus Notes® (Lotus Notes is a registered trademark of Lotus Development Corporation) Documentum eContent Server™, Documentum Engagement Services™, Document Engagement Server™, Documentum ftpIntegrator™, Documentum Intranet Client™, Documentum iTeam™, Documentum Reporting Gateway™, Documentum Site Delivery Services™, Documentum Web Development Kit™, Documentum Web Gear™, Documentum WebCache™, Documentum WebPublisher™, GMPharma™, GXPharma™, GDPharma™, GSPharma™, Momentum™, Virtual Document Manager™ (VDM), Documentum Selfrepair™, and eRoom are trademarks or registered trademarks of Documentum, Inc. in the United States and throughout the world. All other company and product names are used for identification purposes only and may be trademarks of their respective owners.

eRoom 7 Server Upgrade Guide | 1

Upgrade Overview ................................................................................................... 1

eRoom 6 Background .................................................................................... 1

eRoom 7 Differences .................................................................................... 1

Upgrade Requirements ............................................................................................ 3

eRoom Server Versions .................................................................................. 3

System requirements .................................................................................... 4

Port Requirements ....................................................................................... 5

Additional Requirements for eRoom 7 for Microsoft SQL Server .................................. 5

Additional Requirements for eRoom Enterprise ..................................................... 6

Ensuring Sufficient Disk Space ......................................................................... 7

Upgrade Planning and Preparation ............................................................................ 8

Hardware Configurations ............................................................................... 8

Setting Up An Install Account .......................................................................... 9

Setting Up a File Server Account .....................................................................10

Setting Up a File Server Directory ....................................................................10

Member, Group, and Facility Migration .............................................................10

Server Provisioning (Advanced Installation Only) ..................................................11

Installing the Index Server (Advanced Installations Only) ........................................12

Shutting Down Applications ...........................................................................12

Selecting a Web Site ....................................................................................12

Additional Procedures and Information ..............................................................12

Upgrading to eRoom 7 ............................................................................................ 13

Backing up your data first .............................................................................14

Upgrading from eRoom 6 to eRoom 7 ................................................................14

Upgrading from a Previous Version of eRoom 7 ....................................................16

Additional Procedures for eRoom Enterprise .......................................................16

Getting Started Using eRoom 7 ................................................................................19

For More Information ...................................................................................19

Uninstalling eRoom 7.............................................................................................. 19

Appendix A: Configuring eRoom Inboxes ................................................................... 21

Creating an SMTP Mail Account on a Mail Server for eRoom Usage ............................. 21

Administrative eRoom Inbox Settings................................................................ 21


How do end users direct email to particular inboxes? ............................................21

Conversion of Mail Messages to eRoom Inbox Pages ...............................................22

Appendix B: Upgrade Troubleshooting ......................................................................23

Upgrade Components ...................................................................................23

eRoom and NT Server Default Permissions ..........................................................23

Logs to Gather ...........................................................................................24

Backup of Registry Keys ................................................................................24

Upgrade Testing .........................................................................................24

Contacting Technical Support .........................................................................24

Appendix C: Configuring a Reverse Proxy Server with eRoom 7.................................... 25

Configure the Reverse Proxy Server ................................................................. 25

Configure the eRoom Web Server ....................................................................26

Notes ......................................................................................................26

Appendix D: Troubleshooting Problems with Web Publisher .........................................28


PREFACE

In addition to upgrade instructions, the eRoom 7 Upgrade Guide covers the following topics:

• Upgrade planning and preparation

• Configuring eRoom Enterprise

• Microsoft SQL Server configurations

• Uninstall instructions

• Server components and locations

• Information about default permissions

• Configuring inboxes

• Troubleshooting information

• Configuring a reverse proxy server

Upgrade Overview


Upgrade Overview

eRoom 6 Background

eRoom 6 installations typically included an IIS web server containing the eRoom application and a separate MS SQL database server. Alternatively, in SQL Anywhere installations, databases resided on the web server. File attachments to an eRoom were all stored on the web server (or a SAN storage device connected to the web server). An eRoom configuration might have also included integration with Documentum’s Content Server, Real Time Server, MS Project Viewer, and CAD Viewer.

Members on each eRoom server were typically managed by the eRoom Server Member List (SML), and Facilities provided logical groupings of members and eRooms. A directory listing of eRooms was limited to a specific Facility. Typically, customizations were developed to provide a more comprehensive list of eRooms or facilities for a specific server or across multiple servers.

The SML may have also been connected to an NT Domain or LDAP directory for both authentication and synchronization. In a multi-server eRoom environment, in many cases all eRoom servers were connected to an external LDAP or NT4 directory connection. However, each eRoom server had its own server settings, which were administrated independently of other servers. Administration customizations had to be performed separately on each eRoom server.

With previous versions of eRoom, facility and room creation was server-based. Only eRoom Server Administrators could create facilities. Additionally, facility administrators (or users with create eRoom rights) within a particular facility could create eRooms only within that facility.

eRoom 7 Differences

Overview

In eRoom 7, membership and administration are now centralized within an eRoom site. The eRoom site contains information about one or more servers and the members and eRooms within the site. Multiple eRoom 6 servers can be combined into an eRoom 7 site. Within an eRoom site, communities now provide logical groupings of members and eRooms. A site can have multiple communities, and each community can have its own independent administrator. For administrative purposes, all members must be native to only one community. However, members of a community (or the entire community itself) can be added to another community as guests.

Members can be added to the eRoom 7 community member list (as a “local member”), or they can authenticate/synchronize to an external directory, such as LDAP or an NT4 domain. The concept of a facility still exists in eRoom 7, but facilities reside within an individual community. Each facility maintains its own settings page for database templates, inboxes, custom fields, and custom icons only. However, facility administration and membership/synchronization rules that applied in eRoom 6 are no longer relevant in eRoom 7. New eRoom provisioning functionality will determine which server machine and community an eRoom is created in. The following illustration depicts the structure of an eRoom 7 site:

Upgrade Overview

2 | eRoom 7 Server Upgrade Guide

There are several important eRoom 7 differences you can see in this illustration. In particular:

• A site can include multiple communities, which in turn can include multiple facilities.

• Although sites and communities can contain multiple facilities, a facility still represents a distinct database file. However, the eRoom 7 site database now contains information on servers, communities, facilities, membership, and licensing across the entire eRoom 7 site.

• Facilities must be created within a particular community, and eRooms must be created within a particular facility.

Other important differences not depicted in the illustration include the following:

• Membership is now administered at the community level rather than at the facility or server level.

• The only member synchronization that now occurs is between the eRoom site and its communities, (which in turn synchronize with an external directory, if applicable). There is no longer any member synchronization between SMLs and facility member lists.

• When adding members to an eRoom, room coordinators can search for any member of the community, regardless of what facility the eRoom resides on.

• There are no longer any facility administrators in eRoom 7; they have been replaced by community administrators.

• There are still facility settings pages in eRoom 7, but they now only control facility-level inbox functionality, custom icons, custom fields, and database templates.

eRoom 7 and directory connections

eRoom 6 supported the use of external directory connections at the server and the Facility level. eRoom 7 associates Windows NT Domain or LDAP connections with communities only. An eRoom 7 directory connection is added to a community, and the directory members automatically become members of a group within the community. This directory group cannot be deleted unless the directory connection is deleted from the community.

eRoom 7 Site

community A

facility A1eRoom A1

member listmember A1

community B

member A2

member A3

eRoom A2

eRoom A3

facility A2eRoom A4

eRoom A5

eRoom A6

facility B1eRoom B1

member listmember B1

member B2

Guest A1

eRoom B2

eRoom B3

Upgrade Requirements


Prior to upgrading to eRoom 7, identify where the current eRoom 6 directory connections are located (SML or FML based). Then identify the eRoom 7 community these directory connections should reside in. If your eRoom 6 directory connection is connected to your eRoom 6 SML, the eRoom 7 upgrade will translate directory connections to the community that contains your SML. Most likely the “Main” community of members will contain all members from all server member lists for the purpose of the eRoom 7 upgrade. By default, the upgrade will create a group (of the same name as the directory connection) within the community containing all members from the external directory connection. After the upgrade, you can later add new communities and move directory connections to new communities as desired.


eRoom Server Versions

Requirements for eRoom 7 vary depending on the type of eRoom 7 installation and the type of database you use. eRoom 7 is available in two different installations:

Standard installation

The Standard installation is limited in the number of servers that can be used. Typically, the eRoom 7 server and file server reside on the same machine, although the file server directory can be placed on a separate machine from the eRoom 7 server. And if you have the SQL Server version of the Standard installation, the database server can also reside on a different machine.

The Standard installation is available in two different database versions:

• One provides an embedded SQL Anywhere database

• The other lets you use Microsoft’s SQL Server, which includes support for SQL Server 2000. This version can be installed in an environment that uses Microsoft Windows Clus-tering Services. (Configuring eRoom 7 to take advantage of this service requires some extra Windows environment procedures.)

Advanced installation

With the Advanced installation, the web server, indexing server, database server, and file server can reside on different machines, and there can be multiple web and database servers. The Advanced installation can only be used with SQL Server. It can also be installed in an environment that uses Microsoft Windows Cluster Services. (Configuring eRoom 7 to take advantage of this service requires some extra Windows environment procedures.)



System requirements

Client Server(s)

Hardware For browser-only access (“thin client”), system requirements are that of the browser itself.

For browser access with the plug-in (“rich client”):

• 300 MHz Pentium

• 128 MB RAM

• 50 MB free disk space

• 900 MHz single processor

• 512 MB RAM

• 512 MB free disk space (for eRoom server). File server disk space requirement depends on usage. Index server requirement is approximately 50% of total file usage.

Note: in the Standard installation, your database and index server are on the same machine as your eRoom server, requiring more disk space.

Software The following can be used with either the thin-client or the optional plugin:

• Microsoft Windows 2000


• Microsoft Windows XP®

• Microsoft Windows NT® 4.0 (with Service Pack 6a)


• Microsoft Windows ME

The following can be used with the thin-client only:

• Microsoft® Windows® 95 (with Service Pack 1)

• Macintosh OS 8.5 or 9.x

• Macintosh OS X

• Sun Solaris 2.7 or higher

• HP-UX 10.20 or higher

• Linux RedHat 7.x or higher

• Windows 2000 Server (with Service Pack 2 or later)

• Windows 2000 Advanced Server (with Service Pack 2 or later)

• Windows Server 2003 Standard

• Windows Server 2003 Enterprise

The following can be used for non-production (evaluation) use only:

• Windows 2000 Professional

• Windows XP Professional

Supported browsers:

• Microsoft Internet Explorer® 5.0.1 or higher

• Netscape Navigator® 4.7 and higher. (Note: Navigator® 4.7 and 6.0 provide browser-only access.)

• Netscape 7.0 or higher or Mozilla 1.0 or higher can be used with the rich client, but Internet Explorer 5.0.1 must be installed on the machine.

Supported database platforms:

• Embedded SQL Anywhere database

• Microsoft SQL 2000 (Service Pack 1; Service Pack 2 recommended



Note: The above requirements are minimums for production environments. In some cases, requirements are lower for evaluation or other non-production purposes.

Port Requirements

If you are using eRoom 7 with a separate file server that resides behind a firewall, or if you are using eRoom 7 for SQL Server and the SQL server resides behind a firewall, there are a few unique firewall port requirements you should be aware of:

• For eRoom 7 for SQL Server, the use of Microsoft Distributed Transaction Coordinator (DTC) is required. DTC ensures transactional integrity when eRoom 7 writes to both the site database and to an eRoom database. DTC requires the following open ports:

- 135 RPC EPM (End Point Mapper)

- 1433 TDS SQL (for TCP/IP traffic)

- 1434 SQL 2000 (for Integrated Security)

- 5100-5200 MSDTC (Dynamically assigned)

• If your site uses a separate file server that resides behind the firewall, then the follow-ing open ports are required:

- 137 NETBIOS Name Service (for browsing requests of NetBIOS over TCP/IP)

- 138 NETBIOS Datagram Service (for Browsing datagram responses of NetBIOS over TCP/IP)

- 139 NETBIOS Session Service. (For file sharing and print sharing)

- 445 Common Internet File Systsem (CIFS)

Additional Requirements for eRoom 7 for Microsoft SQL Server

System requirements

If you are going to use the eRoom 7 for Microsoft SQL Server database version, the following requirements also apply:

• Although eRoom can log in using an existing account, we recommend creating a new SQL Server account specifically for eRoom to use. The account must use SQL Server authen-tication, not Windows NT authentication, and must at least have dbcreator rights to install.

• For performance reasons, we recommend installing Microsoft SQL Server and eRoom 7 for SQL Server on different machines on the same NT network and same domain, or any fully-trusted domain.

• If you decide to install SQL Server on a separate server, you must install some additional items on the eRoom 7 server machine. In particular, you must install the Client Connec-tivity option found on the Microsoft SQL Server installation CD. For Microsoft SQL 2000, you must also install the Management Tools option. Reboot the web server after install-ing the SQL Client software.

• SQL Server defaults to port 1433 but this port can be changed, if appropriate.

• If your SQL server resides behind the firewall, you must use Microsoft Distributed Trans-action Coordinator (DTC) to ensure transactional integrity. (See the Port Requirements section for additional details.)



• For optimal eRoom performance, set the SQL Server to communicate with client appli-cations using TCP/IP. To confirm this setting, choose from the Start menu Programs > Microsoft SQL Server 7.0 > Client Network Utility, and then set the Default Network Library to “TCP/IP”. To do this, make sure only the TCP/IP protocol is enabled in the General tab of the SQL Server Client Network Utility.

• You should stop the Microsoft SQL Server services and apply all required service packs. You can download the service packs from the location http://www.microsoft.com/download.

• Microsoft SQL Server must be installed with the following Microsoft defaults:

- Character Set: 437 U.S. English

- Sort Order: 1252 ISO character set, 52 nocase_iso Dictionary order, case-insensitive. (Other sort orders like binary are not supported. To verify SQL Server sort order, from the MS SQL Query Analyzer run the SQL Statement sp_helpsort.)

- Unicode Collation: 1033 General Unicode

- Unicode Style: Case-Insensitive

• On the same web server where the eRoom Server software will be installed, install (from the Microsoft SQL Server installation CD) the SQL Server Client Network Utility and, for Microsoft SQL Server 2000, management tools.

Information you should collect

The eRoom 7 installation asks for three things related to your Microsoft SQL Server:

• Server Name - Choose or type the name of the machine on which Microsoft SQL Server is running.

• User Name - Enter the login ID for the Micrsoft SQL Server account you want eRoom to use.

• Password - Enter the password for the above login ID.

Additional Requirements for eRoom Enterprise

If you are going to use eRoom Enterprise (an integrated environment consisting of eRoom 7 and Documentum’s Content Server ECM system), the following requirements also apply:

http://www.microsoft.com/download

http://www.microsoft.com/download



• You must use version 7.2 of eRoom.

• If you use eRoom for SQL Server, and you already have a SQL server set up for use by Documentum, you must create a new instance of the SQL server for use by eRoom. This is necessary because Documentum requires a case-sensitive sort order, while eRoom requires a case-insensitive sort order.

• Documentum Foundation Classes (DFC) version 5.1 or greater must be installed on each machine where the eRoom 7 server software is installed. A DFC installer is available for download with eRoom 7.

• In order to use eRoom 7 with Documentum Web Publisher, you must install a copy of Web Publisher version 5.2 or later on the eRoom server. eRoom 7 only needs to access Web Publisher files; Web Publisher does not need to run on the eRoom server.

• If you want to make Documentum templates available for users who publish eRoom 7 files to Documentum, you will need to create dedicated template folders within the Documentum Docbases eRoom 7 will use.

• You must create a dedicated Documentum account with superuser privileges for each Docbase that will be used by eRoom 7.

• The Documentum Connector must be enabled on the eRoom 7 Site Settings page, as well as the Community Settings page for any community that will use eRoom Enterprise.

• You must increase the DFC resources used for connecting the eRoom 7 server and the Documentum server by editing the dmcl.ini file within DFC.

• If you are going to use Documentum’s Webtop interface, and you are running Webtop 5.1, you must also install the Webtop patch provided on the Documentum site along with the eRoom 7 and DFC downloads. (Webtop requires an Internet Explorer 5.5 or later browser.)

• If you need Thumbnail or Rendition support, Documentum Media Services version 5.1 or greater must be installed an configured to work with Content Server.

• If you want to display within eRoom the properties of eRoom items that are linked to Documentum’s Content Server, you must install the eRoom WDK Component. This is not strictly required for using eRoom Enterprise, but it is necessary if you want to access the properties of linked items from within eRoom.

For additional information on these requirements and on configuring eRoom 7 to work with Content Server, refer to the section Additional Procedures for eRoom Enterprise, on page 16 in this guide.

Ensuring Sufficient Disk Space

It is important to ensure that your eRoom installation (including the file server, index server, and server data) has room to grow. The files and directories that will grow in size depend on whether you have the Standard installation of eRoom 7 or the Advanced installation.

Upgrade Planning and Preparation


When you upgrade from eRoom 6 to eRoom 7, files will be moved from their eRoom 6 locations to the new eRoom 7 locations you specify during the install process.


Performing an upgrade requires considerable preparation and planning. Before you launch the installation process, you must make sure you know which servers you will use for various functions (web server, database server, file storage, etc.) In addition, you must set up several accounts and directories that you will be asked to specify by the installation and upgrade programs.

Finally, you must carefully decide and plan how you would like to bring your existing eRoom 6 facilities and rooms into an eRoom 7 site, as there are different ways this can be done, with advantages and disadvantages to each way. Please read this section carefully and plan accordingly before you begin the upgrade process.

Hardware Configurations

The following table shows typical ways you might distribute eRoom 7 site components among various server machines. With the Advanced installation, in addition to the possibilities depicted in the table, you could also use more than four servers and have multiple instances of various site components (MS SQL database, Web server, file server, etc.).

Version Disk partition recommendations

Standard Installation, SQL Anywhere

Use separate partitions for the following and make sure they have sufficient room to grow:

• the File Server directory you specify

• the eRoom Data directory (on SQL Anywhere, this includes the site and facility databases, the full-text search databases, and the optional log files)

Standard Installation, SQL Server



• the site and facility databases

• the eRoom Data directory (on SQL Server, this includes the full-text search databases and the optional log files)

Advanced Installation, SQL Server



• the eRoom Data directory (in this version, this includes only the optional log files, which are not very large, and--if you are using eRoom Enterprise--a Documentum Foundation Classes working directory.)



Setting Up An Install Account

All installations

For both Standard and Advanced installations of eRoom 7, the Windows account used to install the eRoom software must have administrative rights for the server and must also have “Act as part of the operating system” rights. If this right is not set, the eRoom install will set it and prompt you to log out then log in again.

Advanced installations only

Because an eRoom 7 Advanced installation spans multiple servers connected to a single site, we recommend that you set up a dedicated Windows account for installing and administering eRoom 7.

This account should be a domain-level account that is added to the local administrator’s group on the server(s). By making this a domain-level account, you ensure that the login is common across multiple servers and the user credentials will be identical. In the case of servers located within a DMZ (not on a domain), create a local account and use a standard naming convention for install accounts across all servers.

Number of Servers Server eRoom 7 Site Components

Standard Advanced

One Server Server 1 All components on the same server.

All components on the same server.(This Advanced install configuration for testing only.)

Two Servers Server 1 Web serverSQLA databaseIndexing server

Web Server

Server 2 eRoom file server MS SQL databaseIndexing servereRoom file server

Three Servers Server 1 Web serverIndexing servereRoom file server

Web server

Server 2 MS SQL database eRoom file server

Server 3 (Not applicable) MS SQL database

Four Servers Server 1 Web server Web server

Server 2 eRoom file server MS SQL database

Server 3 MS SQL database eRoom file server

Server 4 (Not Applicable) Indexing server



Setting Up a File Server Account

Standard installations only

If you intend to store files uploaded to eRoom 7 in a directory on the eRoom 7 server itself, then you do not need to set up a File Server account for the Standard Installation. However, if you intend to store your File Server share on a different machine than eRoom 7, you must set up an account (either domain or local) for access to the File Server. The account does not need any special Windows rights (administrative rights, for example).

Advanced installations only

For all Advanced installations, you must create a Windows account for eRoom 7 to use to access the File Server share (the location where eRoom 7 files are uploaded and stored). The account should be a domain account, unless you are installing eRoom 7 within a DMZ. The account does not need any special Windows rights (administrative rights, for example).

Setting Up a File Server Directory

All installations

All eRoom 7 installations require a File Server directory to contain uploaded files. Because the Site Creation wizard will prompt you for this directory after you install eRoom 7, you should create this directory before launching the install.

In addition, you must also share the file server directory via Windows file sharing (unless you are both placing the File Server directory on the same machine as eRoom 7 and performing a Standard installation). The only account that needs share access to the File Server directory is the File Server account discussed in the previous section.

Note: If you create the File Server directory on a shared drive on a cluster configuration, then you must also create a clustered file share resource for this shared drive in the Cluster Group. This resource will need the permissions set up for the File Server account to access the data files. Otherwise, the shared drive will not be available after a failover.

Member, Group, and Facility Migration

Members

The Migration wizard will ask you whether you want to create a new community to serve as the main community for site members, or whether you want to add members to an existing community. If you have already defined a community to serve as your primary member community, you would want to choose it here, rather than create a new community. Also, you can create new communities later if necessary, via the Site Settings page.

In addition to the main community (which is named after the original site name), the Migration wizard will automatically create a satellite community for each of the following:

• each eRoom 6 facility that was not linked to the Server Member List (SML).

• each eRoom 6 facility that was linked to the SML, but also contained non-SML members.

• each SML group that was specifically linked to by at least one eRoom 6 facility. (All eRoom 6 facilities that pointed to the same SML group and had no non-SML members are consolidated into the main community.)



All members of these satellite communities will remain native to the main community, and be assigned as guest members to their satellite communities. This ensures convenience of administration, while preserving the eRoom 6 member divisions in case you need them. If you like, you can later eliminate the satellite communities to further consolidate membership. You can also create additional communities later.

The following are some circumstances in which you might choose to keep groups and facilities in separate communities rather than consolidating them into the main community.

• You might want communities to strictly observe organizational political boundaries. For example, a specific web server might be delegated solely for accessing eRooms and data belonging to a particular subsidiary or department.

• You might want to create a separate community for administrative purposes. For exam-ple, if different administrators currently manage different eRoom 6 communities, you might want to preserve this practice in eRoom 7.

• You might want to impose more restrictive access for particular projects. For example, you might want to create an executive community or a merger-related community.

Facilities and groups

The Migration wizard also asks you where you want to move your existing eRoom 6 facilities and local groups. The default option is to move them all into the main community. Depending on your needs, a centralized main community containing all the facilities and groups may be more easy to administer than keeping facilities and groups in separate communities. In addition, end users will not need to be concerned about what server or facility an eRoom resides on.

Alternatively, you can choose to keep your facilities and groups in their separate satellite communities, reflecting their eRoom 6 organization. This option allows you to delegate facility and group management to the community administrators of the satellite communities.

Server Provisioning (Advanced Installation Only)

Among the new administrative features in eRoom 7 Advanced installation is server provisioning. This involves determining which servers new eRooms are created on in order to ensure that the load shared by different servers is balanced. You can either establish your own preferences for a provisioning policy, or choose to have eRoom 7 make provisioning decisions automatically (based on the relative capacity of the available servers of each type).

You can also establish provisioning groups, which allow servers to be chosen based on the type of eRoom involved. Provisioning groups are often created based on geographical or organizational criteria—for example, you might want to reserve one set of servers for North American clients, another for European clients, and so on. When a “North America” eRoom is created, eRoom chooses the appropriate servers from those assigned to the “North America” provisioning group. If that group designates multiple servers of a particular type (web, database, file, full text index), then eRoom uses relative capacity logic to choose the best server of each type from the set available to “North America.”

When you migrate a facility from Room 6 to eRoom 7 (after you have created an initial site), and if you have defined provisioning groups or specified multiple options for various server types, you will be asked to choose server assignments for the migration. If necessary, administrators can re-provision at any time after the migration.



Multiple eRoom 6 servers can be added to an existing eRoom 7 site, by joining that site. Consequently, not all eRoom 6 servers need to be upgraded at once. When joining an existing site, it is important to identify which database server, file server, and index server will contain the data prior to upgrading.

Installing the Index Server (Advanced Installations Only)

If you intend to perform an Advanced installation, you should prepare for this installation by downloading and running the index server setup program on the machine you would like to use as an index server. (This setup file is listed as the eRoom 7 Search Engine Installation and is located with the eRoom 7 files on the Documentum download site.) When you create an eRoom 7 site, you will be asked for the name of the index server. You can then enter the name of the machine on which you installed the index server.

If you install the index server after creating the eRoom 7 site, or if you do not enter the name of the index server when you create the eRoom 7 site, then you will need to add the index server (once installed) to the eRoom site by means of the eRoom 7 Admin utility.

Shutting Down Applications

To install the eRoom Server, close all applications temporarily. Disable virus scanners during the installation. Restart applications after installation and re-enable virus scanners.

Selecting a Web Site

When you install the eRoom 7 Server, you are prompted for a web site on which to install eRoom. You can use the default web site, or you can use an additional web site that you created within IIS. Refer to IIS online documentation for information about how to set up IIS with multiple web sites. eRoom recommends testing an additional web site configuration before installing the eRoom software.

Additional Procedures and Information

If in addition to upgrading from eRoom 6 you are also reconfiguring your installation, you may need to meet additional requirements and perform additional procedures than the ones described in this manual. Among the procedures not covered in this manual are the following:

• Failover clustering setup

• Network security environment setup

• Inbox configuration

For information on these procedures, refer to the eRoom 7 Installation and Configuration Guide and related technical notes, both available from the Documentum Support site.

If you have made API customizations in eRoom 6, refer to the API Help for information on whether you need to update those customizations for eRoom 7. If you have created eRoom XML Query Language applications or queries, see the XML Help for information on changes to the XML schemas and to query targeting. Both the API Help and the XML Help are available from within the eRoom 7 Help environment, or as an independent help file from the Documentum Support site.

Upgrading to eRoom 7


Finally, you must evaluate and revise your eRoom 6 backup procedures so that they are effective for eRoom 7, since the basic structure and organization of eRoom 7 differs from that of eRoom 6 in important respects.


This section explains how to upgrade to eRoom 7 from a previous eRoom installation (or from a previous version of eRoom 7). Once the eRoom 7 files are installed, the install program will lead you through the steps to create or join an eRoom site. It will then lead you through the steps to migrate the data from an eRoom 6 facility-based setup to an eRoom 7 site.

An eRoom 7 site consists of one or more servers that support a population of eRooms and users. All servers in a site share a common membership pool. Consequently, members can log into the site and then do not need to log in again during the same session--even if they go to different eRooms and servers. A site can be as small as a single server, but can have many servers. The site can be split into multiple communities.

Upgrading to eRoom 7 involves most or all of the following procedures:

• Running the Setup program to install the software

• Running the Site Setup program to set up or join an eRoom 7 site

• Database conversion (only if you are upgrading from SQL Anywhere to SQL Server)

• Migration (if you have multiple eRoom 6 servers that you want to combine into a single eRoom 7 site). Combining multiple eRoom 6 servers into a single eRoom 7 site is gener-ally recommended since it simplifies eRoom 7 administration.

• Index Installation (eRoom Advanced installations only). This is performed automatically.

• Specifying Site Settings

The following table shows the supported direct upgrades from eRoom 6 to eRoom 7:

Note: While it may not be possible to upgrade directly from one particular version to another particular version, it may be possible to upgrade by means of an interim step. For example, you cannot directly upgrade from eRoom 6 for SQL Anywhere to eRoom 7 for SQL Server (either Standard or Advanced); however, you can first upgrade to eRoom 6 for SQL Server and then upgrade from there to eRoom 7 for SQL Server.

To:

From: V7 StandardSQL Anywhere

V7 StandardSQL Server

V7 AdvancedSQL Server

V6 SQL Anywhere Supported Not supported Not supported

V6 SQL Server Not supported Supported Supported

V7 Standard SQL Anywhere Point release Supported Supported

V7 Standard SQL Server Not supported Point release Supported

V7 Advanced SQL Server Not supported Not supported Point release



Backing up your data first

In preparation for your upgrade, back up all your current eRoom data (all the data users have added into eRoom) and eRoom SQL databases first.

Note: The following procedure provides a general outline of your backup routine. If you are using eRoom for SQL Server, the databases on the Microsoft SQL Server must be backed up as a separate process.

To back up your eRoom data:

1. Stop all IIS and eRoom services (eRoom Scheduler, IIS Admin, WWW). This closes the open database and log files in your data directory so that they can be copied.

2. From your eRoom 6 ServerData directory (typically in C:\Program Files\eRoom Server\ServerData), copy all your eRoom data to a safe, neutral location where you can easily access it in the future if necessary.

3. Confirm that your backup program backed up any open eRoom files.

See also: For more detailed information on backing up your data, you can download Backup and Restore Guidelines from the Documentum Support site.

Upgrading from eRoom 6 to eRoom 7

The following figure shows the supported upgrade paths from eRoom 6 to eRoom 7.

Although there are several different upgrade paths, there are only two basic procedures for upgrading: one for upgrading to eRoom 7 with the same database you are using in eRoom 6 and one for upgrading from the SQL Anywhere database version of eRoom 6 to the MS SQL Server database version of eRoom 7. Refer to the procedure below that applies to your situation.

eRoom 7

eRoom 6SQL Anywhere

MS SQL

MS SQL

eRoom 7AdvancedMS SQL

eRoom 6Standard

eRoom 7StandardSQL Anywhere

http://support.documentum.com/Support/Start/dmLogin.asp



To upgrade from eRoom 6 to the same database version of eRoom 7:

This procedure is for upgrading either from SQL Anywhere eRoom 6 to SQL Anywhere eRoom 7, or from eRoom 6 for SQL Server to eRoom 7 for SQL Server.

1. Log in to your web server under the administrator account you established in the section Setting Up an Install Account.

2. Download and run the appropriate eRoom 7 installer (SQL Anywhere, SQL Standard installation, or SQL Advanced installation). (For more information on the different ver-sions, see eRoom Server Versions, on page 3.)

When the eRoom 7 install procedure is finished, the Site Creation wizard should launch automatically. If for some reason it does not, launch the ERSAdmin utility that resides in the ...\Program Files\eRoom\eRoom Server directory. Then select the eRoom folder, right click, and choose Create Site.

3. Follow the prompts to create an eRoom 7 site.

When the site creation procedure is finished the Migration wizard should launch automatically. If for some reason it does not, launch the ERMigration utility directly from the ...\Program Files\eRoom\eRoom Server directory.

4. Follow the prompts to migrate your eRoom 6 facilities to the eRoom 7 site you have cre-ated.

For additional information on the choices you will make in this procedure, see Member, Group, and Facility Migration, on page 10 and Server Provisioning (Advanced Installation Only), on page 11.

5. If you have more than one eRoom 6 server and you want to combine your existing facili-ties into a single eRoom 7 site, repeat this entire procedure (steps 1-4) on each server, except when the Site Creation wizard asks you whether you want to create a new site or join an existing site, choose to join an existing site. Then specify the site you created the first time through the procedure.

To upgrade from eRoom 6 for SQL Anywhere to eRoom 7 for SQL Server:

This procedure is for upgrading from eRoom 6 for SQL Anywhere to eRoom 7 for SQL Server (either Standard installation or Advanced installation). To do this, you must first migrate to eRoom 6 for SQL Server and then upgrade to either the Standard or Advanced installation of eRoom 7.


2. Download and run the eRoom 6 for SQL Server installer. Install eRoom 6 for SQL Server on top of eRoom 6 for SQL Anywhere. (Be sure to also download the eRoom 6 Installation and Configuration guide for help with this procedure.)

3. The upgrade utility launches to convert the existing database from SQL Anywhere to SQL Server.



4. After the database conversion is complete, download and run the appropriate eRoom 7 for SQL Server installer (Standard installation or Advanced installation). Install eRoom 7 for SQL Server on top of eRoom 6 for SQL Server. (For more information on the different versions, see eRoom Server Versions, on page 3.)

When the eRoom 7 install procedure is finished, the Site Creation wizard should launch automatically. If for some reason it does not, launch the ERSAdmin utility that resides in the ...\Program Files\eRoom\eRoom Server directory. Then select the eRoom folder, right click, and choose Create Site.

5. Follow the prompts to create an eRoom 7 site.

When the site creation procedure is finished the Migration wizard should launch automatically. If for some reason it does not, launch the ERMigration utility directly from the ...\Program Files\eRoom\eRoom Server directory.

6. Follow the prompts to migrate your eRoom 6 facilities to the eRoom 7 site you have cre-ated.

For additional information on the choices you will make in this procedure, see Member, Group, and Facility Migration, on page 10 and Server Provisioning (Advanced Installation Only), on page 11.

7. If you have more than one eRoom 6 server and you want to combine your existing facili-ties into a single eRoom 7 site, repeat this entire procedure (steps 1-6) on each server, except when the Site Creation wizard asks you whether you want to create a new site or join an existing site, choose to join an existing site. Then specify the site you created the first time through the procedure.

Upgrading from a Previous Version of eRoom 7

To ugrade to eRoom 7.2 from a previous version of eRoom 7


2. Download and run the appropriate eRoom 7.2 installer (SQL Anywhere, SQL Standard installation, or SQL Advanced installation). Install eRoom 7.2 on top of the previous ver-sion of eRoom 7.

3. eRoom 7.2 no longer supports POP3-based inboxes, and attempts to reconfigure existing inboxes. For instructions on configuring SMTP-based inboxes manually, see Appendix A: Configuring eRoom Inboxes, on page 21.

Additional Procedures for eRoom Enterprise

If you are planning to use eRoom Enterprise, which combines eRoom 7 with Documentum Content Server, you must also complete the procedures in this section.

Installing DFC on the eRoom 7 server

Documentum Foundation Classes (DFC) must be installed on the same server(s) as eRoom 7. A DFC installer is available for download with eRoom 7.



1. Log in to your web server as administrator.

2. Download and launch the DFC installer.

3. Follow the instructions in the Setup program until the installation completes.

4. After the Setup program is finished, you must re-boot.

5. Edit the dmcl.ini file for DFC to increase the resources used for connecting the eRoom 7 server and the Documentum server.

The dmcl.ini file resides in the \WINNT directory of the machine on which you are installing DFC. Edit it by adding the following lines:

[DMAPI_CONFIGURATION]cache_queries = Tclient_codepage=UTF-8client_cache_size=1000connect_pooling_enabled=Tmax_session_count=100max_collection_count=100

(You can also find a copy of these lines in the ...eRoomServer\dmcl_settings.txt file of your installed copy of eRoom 7.) These settings are the recommended minimums.

6. If you are installing the DFC after installing eRoom 7, you must run the eRoom Checker to configure the correct permissions on Documentum-related files and folders. Locate the ERChecker executable in the ...\documentum\eRoom7 directory and specify a check for General Site Consistency and All File Permissions.

Creating a dedicated eRoom 7 template folder

If you want eRoom 7 users to be able to choose Documentum template files when publishing a file to Documentum, you must create a folder for the template files within each Docbase that will be used by eRoom 7. The folder(s) must meet the following criteria:

• They must be named eRoom Templates and placed within the /System cabinet of the Docbase.

• They must have world write access.

Creating dedicated content server accounts

You must create a dedicated Content Server account with superuser privileges for use by eRoom 7. The account must be created for each Docbase that eRoom 7 will access, and the account login name and password must be the same for each Docbase. (eRoom accepts only one login and password for Documentum access.)

Be sure to make a note of the login name and password for the account(s) you create, so that you can enter them on the eRoom 7 Server Settings page.

The two most convenient ways to add a single user to a Docbase are to use either the Documentum Administrator utility or the Webtop utility (if available at your site). For information on adding a user account with Documentum Administrator, refer to the Documentum Content Server Administrator’s Guide. For information on adding a user account with Webtop, refer to the Documentum Using Webtop manual.



Enabling use of content server by eRoom 7

Once both eRoom 7 and DFC are installed on the server and you have created a dedicated Documentum Administration account, you must enable use of eRoom 7 with Content Server on the eRoom Site Settings page.

You can get to the Site Settings page in one of two ways:

• remotely, by entering in your browser the URL servername.com/eRoom, then go to Site Settings.

• locally, by using the Microsoft Management Console (MMC)—choose Start > Programs > eRoom Administration > eRoom Server Administration

1. On the eRoom 7 Site Settings page, click the General tab, then scroll down to the Docu-mentum section.

2. Make sure the Enable Documentum Connector checkbox is selected.

3. Enter the Login name and Password for the dedicated Content Server account you cre-ated for your Docbase(s).

4. Specify any other options you prefer for the remaining Documentum settings. (For example, if you are going to use Documentum’s Webtop interface, enter the Webtop URL.)

5. Scroll to the top of the Site Settings page and click the Apply button.

6. Scroll down to the Documentum section.

A Test button is now available.

7. Click the Test button to verify that the Login name and Password you have provided afford access to Documentum.

For details about all Documentum server settings, see the eRoom Administration section of the eRoom 7 online Help.

Installing Web Publisher on the eRoom server

Web Publisher is an easy-to-use, browser-based interface that enables non-technical users to easily create, manage, and publish content for multiple, multilingual Web sites. If you are planning to use eRoom 7 with Documentum Web Publisher, you must also complete the procedures in this section. In order for the eRoom server to communicate with application servers running Web Publisher, a copy of Web Publisher must be installed on the eRoom server. If a supported application server is not already installed on the eRoom server, then an application server must first be installed before installing Web Publisher.

1. Install a supported application server (for example, BEA WebLogic or Apache Tomcat) on the eRoom server.

2. Install Web Publisher (Web_Publisher_5.2.x_windows.exe) on the eRoom server.

Note: You do not need to run either the application server or Web Publisher on the eRoom server; you only need to install it there.

If you receive errors when attempting to work with Web Publisher files, or if you are unable to see Web Publisher files or folders, please see Appendix D: Troubleshooting Problems with Web Publisher, on page 28.

Getting Started Using eRoom 7


Configuring Web Publisher servers for use with eRoom

In order for “Go to Content Server...” command in eRoom to work correctly with Web Publisher servers, you must perform the following procedure on each Web Publisher server that eRoom will connect to.

1. Locate the XML file wp\config\app\contextsensitive_view_config.xml.

2. Open the file, and under the <actions_list> tag enclosed within the <component> tag, add the following line:

<an_action_name=”search” valid_by_default=’true’/>

3. Log into Web Publisher as a user with administrative privileges.

4. Press the Ctrl key while clicking the Documentum icon in the top-right corner of the page.

5. Click the Configuration button.

6. Click the “Rec-configure View Sensitive Action” link.

7. Wait until the process finishes, then close the popup window.

Getting Started Using eRoom 7

To learn more about beginning to configure and use eRoom sites and rooms, see the Welcome to eRoom topic in the eRoom 7 online Help. To open this topic, choose Start> Programs> eRoom Server> Getting Started with eRoom.

For More Information

Refer to the eRoom 7 online Help for product documentation (for administrators as well as

end users). To open the Help, click “ ” in the control bar at the top of an eRoom page.

• For information about new features in eRoom 7, see the What’s new in eRoom 7 topic.

• For details about the user interface, see the Guided tour in the Working in your eRoom topic (Basics section).

• For information about coordinating an eRoom, see the section Coordinating an eRoom.

• For server and facility administration details, see the Administration section.

• For information on managing eRoom membership (including the use of NT domain and LDAP directories), see the Membership section.

See also: Visit the Documentum Support site for additional Support Note information.

Uninstalling eRoom 7

Use the following procedure to remove everything associated with an install of eRoom 7.

Note: Do not perform this procedure if you still have eRoom data you want to save or recover.


Uninstalling eRoom 7


1. Shut down the eRoom Monitor (if you installed the eRoom client on the same machine as the eRoom Server).

2. Use the eRoom Server Administration MMC console to delete the site. (Select the eRoom folder, right click, and choose All Tasks > Delete Site).

3. Uninstall the eRoom Server by opening the Control Panel and double-clicking "Add/Remove" Programs. Choose eRoom Server and click "Remove". If prompted to remove files no longer in use, you can select “Yes” at your discretion.

4. After removing eRoom 7 and re-booting, verify the following:

- If your ...\eRoom Data directory (or whatever else you named it during install) has been removed. If not, remove it (provided a backup isn't needed or doesn't currently exist).

If you are using Microsoft SQL 2000, then also ensure the eRoom databases within Microsoft SQL Enterprise Manager have been removed. If not, delete them.

Verify that registry entries have been removed.

- Run Registry Editor. (Start > Run > Regedit)

- Select - HKEY_LOCAL_MACHINE\SOFTWARE\

- Find and open the eRoom key under the software key.

- Verify that the eRoom Server key is removed. If not, delete the HKLM\Software\eRoom\eRoom Server key. Do not do this if you still want to keep eRoom data.

Verify that the eRoom Server files have been removed.

- Go to the following directories and delete the following files if they exist (these are defaults -- installation locations may vary):

/inetpub/eRoom - remove eRoom directory

Verify that all virtual roots have been removed from IIS:

- Open the Internet Service Manager to check all "eroom" roots.

- If any still exist, right-click and delete all the "eRoom" virtual directories/applications.

Make sure that IIS Services are started and that you can access the IIS default home page. Then you can re-install eRoom if needed.

Appendix A: Configuring eRoom Inboxes



An eRoom inbox is a special folder that can receive and store email messages (and their attachments). By cc'ing email messages about your project to your eRoom, you can create an automatic archive of project correspondence. To retrieve email messages, eRoom logs into an SMTP account on a mail server, just as if it were a mail client like Outlook Express or Eudora.

Creating an SMTP Mail Account on a Mail Server for eRoom Usage

Establishing an SMTP service and domain

1. In the IIS Admin Console on the eRoom server that will host the SMTP service, make sure the SMTP service is installed.

2. Make sure there is a virtual SMTP domain configured within the IIS Admin Console.

3. In the Incoming section of the Email page of the eRoom Site Settings, enter the name of the SMTP domain from the previous step into the “Email address domain” field.

Creating the inbox

1. In an eRoom, click create and choose the Inbox item. Provide a name and description for the inbox.

2. Complete the inbox address by filling in the Address field in front of the domain name.

3. Click OK to create the inbox.

Each inbox you create follows the same process. Multiple inboxes can reside in a single eRoom. All inboxes must have unique email addresses. eRoom will enforce this by changing email addresses for inboxes that are copied.

Administrative eRoom Inbox Settings

The eRoom Scheduler Service accesses the SMTP accounts to retrieve mail for all eRoom inboxes. You can disable the inbox functionality within the eRoom Site Settings page by clearing the “Check for email sent to inboxes” checkbox under the Scheduler section.

When inboxes are enabled, you can use the eRoom Server Tuning dialog box to set the interval at which the eRoom Scheduler checks for new mail delivered to the SMTP service. The default setting checks every five minutes.

How do end users direct email to particular inboxes?

eRoom delivers mail to the inboxes based on their addresses. The Scheduler checks for mail in the drop directory specified in the SMTP service (IIS Manager). For single-server sites, mail is delivered to the appropriate inboxes. For multi-server sites, mail on servers other than the one with the SMTP service is temporarily stored in the ~Mail Drop folder on the main file server. When the Scheduler runs on other servers, it looks for mail in this folder and directs it to the appropriate inboxes.



Conversion of Mail Messages to eRoom Inbox Pages

eRoom converts each email message sent to an inbox to an eRoom page as follows:

• The subject line becomes the title of the page.

• The page itself contains an email icon ( ) for replying to the sender and the text of the message.

• File attachments are created as attachments to the new eRoom item. If eRoom cannot determine the type of attachment (because it is using a non-standard MIME type), eRoom creates a file attachment as a text file called “Attachment N.txt” where N is a number greater than zero. Users can rename this file if they like.

HTML email messages:

The inbox feature supports HTML email messages. eRoom restricts the HTML content of eRoom items so that they can be edited with our rich text editor. Incoming email messages in HTML format will have all non-supported HTML stripped from them, including style sheets, script (VBScript and JavaScript), and other non-standard tags. It is important to note that all script is removed, which prevents potential security problems caused by malicious script. Inline images are retained, and can be edited in the rich text editor.

Appendix B: Upgrade Troubleshooting



This section contains information on troubleshooting potential problems with the eRoom 7 upgrade process. If you encounter difficulties, read this section and try to isolate where the problem occurs, which will suggest possible solutions.

Upgrade Components

Broadly speaking, the upgrade process consists of three main subcomponents:

Program file installation - If the upgrade fails during program file installation, the problem is most likely related to permissions. Check to see if strict Windows Domain Group policies might be preventing you from installing the application. Also make sure that you have created an install account (as described in the Setting Up An Install Account section) and logged in with that account when you started the installation (as directed in the Upgrading from eRoom 6 to eRoom 7 section).

For additional information on eRoom 7 and permissions, see the section eRoom and NT Server Default Permissions below.

Site Creation - If the upgrade fails during site creation, the problem may be related to database connectivity or Windows permissions. Again, check to see if strict Windows Domain Group policies might be preventing you from setting up a site.

Facility Migration - If the upgrade process fails during facility migration, the problem is most likely related to SQL connectivity or to a data issue specific to an individual facility database.

eRoom and NT Server Default Permissions

Note: There are default permissions set up for an eRoom installation. Organizational stan-dards may vary from enterprise to enterprise. These permissions can be changed to “harden” the security of the server. Follow the Microsoft Windows recommendations for hardening NT or 2000 IIS security. However, any configuration changes should be sufficiently tested prior to installing eRoom.

eRoom 7 Rights and NTFS Rights

Access rights set in the eRoom application are not passed down as NTFS rights to the operating system (NT/2000). Conversely, general NTFS permissions for each NT user on the server do not apply to eRoom objects or files. The eRoom application user rights will determine access control to the application (communities and eRooms) and rights to eRoom-specific objects. Windows NTFS permissions that are important are the IUSR Account (anonymous access account) used by IIS and the eRoom Server user account created by the eRoom application. Both accounts are used to access server resources. However, the IUSR account access is limited in scope.

Checking eRoom Permissions

eRoom provides a utility called the eRoom Checker that does a deep permissions check on the eRoom web server. It checks and lists a detailed permission checklist for the entire server, including registry and directories for the IUSR and System NT Accounts. In addition, it checks the integrity of database objects and can make permissions repairs and add missing facilities and erooms to the site database.



You run eRoom Checker from the eRoom Server Administration MMC console. Please contact Documentum Technical Support for assistance with running this utility.

See also: For more information about the eRoom Checker utility, see the eRoom Diagnostic and troubleshooting tools section of the System Administration section of online Help.

For more information on Windows NT permissions and security, see the following web resources:

http://www.microsoft.com/technet/iis/permmaze.asp

http://www.microsoft.com/technet/security/iis5chk.asp

Logs to Gather

It is important to gather the following logs if your upgrade fails. They will be helpful if you need to contact technical support:

• ERSSvrInstallLog.txt, located in the c:\Winnt directory.

• eRoomerrors.log, located in the eRoom Data directory you specified during program file installation.

• Migration log, located in the ...\Program Files\eRoom\eRoom Server directory with the name Migration Log<data>.txt

Backup of Registry Keys

Note that the upgrade process backs up your eRoom 6 registry keys (hklm\software\eroom and hklm\software\odbc). These are backed up in the …\Program Files\eRoom\eRoom Server directory. These may be required for a restore back to eRoom 6 or request by technical support.

Upgrade Testing

It is important to test your upgrade in a separate environment prior to converting your production eRoom servers. Become familiar with eRoom 7 functionality, data storage, and the entire eRoom upgrade process. Proper planning can help ensure a successful migration.

Contacting Technical Support

Before contacting technical support, please gather the above-mentioned logs and if possible take screen shots of any error messages you encounter.

http://www.microsoft.com/technet/iis/permmaze.asp

http://www.microsoft.com/technet/security/iis5chk.asp

Appendix C: Configuring a Reverse Proxy Server with eRoom 7



Follow these steps to configure eRoom 7 with a reverse proxy (RP) server. This configuration ensures that eRoom requests are properly redirected through the reverse proxy to the eRoom web server. First you configure the reverse proxy, and then the eRoom 7 web server.

Important: Verify that the reverse proxy server you are using is fully supported to work with eRoom 7. If you’re not sure, contact Documentum Technical Support.

For this example, assume that:

• End users want to access eRoom by using eroom.company.com.

• There are two servers, as follows:

Configure the Reverse Proxy Server

1. Configure the public DNS server to resolve eroom.company.com to the reverse proxy server IP (192.168.1.99).

Note: In some configurations, two IP addresses might be required for the reverse proxy server (one or two NIC cards)—one IP for external (Internet) use, and one for internal net-work use. In this configuration, DNS should resolve to the external (Internet) IP. TCP/IP set-tings can be set in Windows Control Panel / Network Settings. Consult with a qualified network IT person to make sure the reverse proxy network settings are correctly configured before testing with eRoom Server.

2. Configure the reverse proxy to redirect client requests to the eRoom Server:

3. Configure the reverse proxy server to redirect to the eRoom server, using its fully-quali-fied domain name.

Example - From: https://proxy.company.comTo: https://app1.company.com

4. Test accessing the default home page (of the eRoom web server) from a client worksta-tion. For testing purposes, the host file on a client workstation can be configured to resolve eroom.company.com to the external IP of the reverse proxy (if you skipped step 1 for DNS setup).

5. Configure the RP to redirect all the /eRoomXXX virtual roots on the reverse proxy server to forward to the eRoom server. These include

/eRoom/eRoomASP/eRoomData

Server Description Fully Qualified Domain Name IP Address

app1 eRoom Server app1.company.com 192.168.1.100

proxy reverse proxy Server proxy.company.com 192.168.1.99



/eRoomExtpages/eRoomHelp/eRoomReq/eRoomSetup/eRoomXML

Example - From: https://proxy.company.com/eRoomaspTo: https://app1.company.com/eRoomasp

Note: If you want to disable the reverse proxy server for users inside the firewall, you can do so on the Edit eRoom Server dialog, accessible through the eRoom Server Administration utility. (This requires that internal users can resolve the reverse proxy DNS name.)

Configure the eRoom Web Server

1. On the eRoom server, the fully qualified domain name eroom.company.com should be mapped to the true eRoom server (192.168.1.100). You can do this by modifying the HOSTS file with an entry that resolves eroom.company.com to 192.168.1.100 (the IP of the eRoom server itself).

2. Choose Start > Programs > eRoom Administration > eRoom Server Administration to Open the eRoom Server Administration utility.

3. Right-click on the eRoom server and choose “Edit Server”.

4. In the Full Servername field, enter the RP server name.

5. In the Reverse Proxy Server section, check the “This eRoom server is being used through a reverse proxy server” checkbox.

6. Specify any other Reverse Proxy Section settings as necessary.

Notes

On overriding the eRoom web server name in eRoom Server Settings

• When the eRoom server name is overridden, eRoom responds to requests to app1.com-pany.com with its own HTTP redirects (response code 301) to the server name specified in eRoom Server Settings. The preceding procedure (Configure the eRoom Web Server) allows you to override the eRoom server name and ensure that eroom.company.com resolves to the true eRoom server (instead of redirecting and resolving back to the reverse proxy in a loop).

• The override web server name set in eRoom Server Settings must also be used to ensure that URLs in eRoom email notifications and invites/alerts are sent out using the public name eroom.company.com rather than the internal eRoom server name app1.com-pany.com. This allows end users to click the link in eRoom emails and resolve to the reverse proxy (as long as DNS is correctly set up).

• When accessing eRoom from a browser on the eRoom server itself, eroom.company.com will resolve locally to the eRoom server (vs. back to the RP). IIS will also likely respond to app1.company.com or localhost or to its own IP address (192.168.1.100). However, access to the web server using the true name or IP address of the eRoom server is likely to be unpublicized, and restricted by firewalls.



On securing the configuration

• When securing both the eRoom and proxy servers, use proper care and testing to ensure that the security does not impair functionality of either application.

• SSL can be installed on the reverse proxy to ensure a secure connection with client workstations. This means clients would use “https://” instead of “http://”.

• SSL can also be installed on the eRoom web server to ensure a secure connection between the RP and the eRoom server. However, some proxy servers may not be able to redirect to a web server with “https://”.

• In eRoom 7, an SSL certificate must be installed on the eRoom web server for eRoom to recognize “https://” instead of “http://”. eRoom automatically recognizes that the SSL certificate is installed and required. After applying the SSL certificate to the eRoom server, you need to ensure that users use SSL (users cannot have the choice of whether or not to use https:// in the URL address). Otherwise, the URL addresses in the notifica-tions, alerts, and invitations will be incorrect. For instructions on how to force the use of SSL for connected users, refer to the Documentum Support Notes on the Documentum Support site for additional information.

• If an SSL certificate cannot be installed on the eRoom web server, an alias might be cre-ated so that “http://” requests get translated to “https://” automatically.



Appendix D: Troubleshooting Problems with Web Publisher


Appendix D: Troubleshooting Problems with Web Publisher

Problem Troubleshooting Steps

When attempting to import a file from Content Server into eRoom, Web Publisher files and folders fail to appear.

Verify that you have correctly installed eRoom Version 7.2. Versions prior to 7.2 do not display Web Publisher files and folders.

When attempting to check out a Web Publisher file from eRoom, you receive the error, “Web Publisher is not installed on the eRoom Server”.

Verify that Web Publisher has been installed on the eRoom server. Note: Web Publisher does not need to be running on the eRoom server.

Verify that the Class Path system environment variable contains the fully qualified path and filename for wcm.jar (typically located in ...\program files\documentum\shared).

When attempting to check out a Web Publisher file from eRoom, you receive the error “The eRoom-to-WCM connector service is not installed”.

Verify that there is a copy of the file eroom.jar located in the eRoom 7 installation directory (typically ...\program files\eRoom Server 7).

Verify that the Class Path system environment variable contains the fully qualified path and filename for wcm.jar (typically located in c:\program files\documentum\shared).

Verify that the Class Path system environment variable contains the fully-qualified path and filename for eroom.jar

When right-clicking on an eRoom item linked to a Web Publisher file and choosing “Go to Content Server...”, an error dialog appears with an error similar to this: “JumpOperation: failed to intialize form: InvokeMethod() failed while calling: onInit This startupAction:search is not properly defined. Cannot execute.

Verify that you have correctly completed the instructions in this manual for setting up eRoom Enterprise to work with Web Publisher.

© 2011 - 2013 EMC Corporation. All Rights Reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change

without

notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO

REPRESENTATIONS OR

WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND

SPECIFICALLY

DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United State and other

countries.

All other trademarks used herein are the property of their respective owners.

eroom 7 server upgrade and configuration guide · eroom 7 server upgrade guide documentum, inc., a...

Documents