BroadVision One-To-One Content 7.0. Installation Guide. UNIX and Windows XAS. 585 Broadway Redwood City, CA

Transcription

1 BroadVision One-To-One Content 7.0 Installation Guide UNIX and Windows XAS 585 Broadway Redwood City, CA

2 Installation Guide Copyright BroadVision, Inc. All rights reserved. 585 Broadway, Redwood City, California U.S.A. Printed in the United States of America This manual and the software described in it are copyrighted. Under the copyright laws, this manual or the software may not be copied, in whole or in part, without prior written consent of BroadVision, Inc., or its assignees, except for purposes of internal use by licensed customers of BroadVision, Inc. This manual and the software described in it are provided under the terms of a license between BroadVision and the recipient, and their use is subject to the terms of that license. RESTRICTED RIGHTS LEGEND: Terms and Conditions Applicable to Federal Governmental End Users. BroadVision licenses products for ultimate end use by federal government agencies and other federal government customers ("federal government customers") only under the following conditions. Software and technical data rights in these products include only those rights customarily provided to end use customers of Software as defined in the BroadVision Master Software License and Services Agreement and any exhibit thereto. This customary commercial license in technical data and software is provided in accordance with FAR (Technical Data) and (Computer Software) and, for Department of Defense purchases, DFAR (Technical Data - Commercial Items) and DFAR (Rights in Commercial Computer Software or Computer Software Documentation). If a federal government or other public sector customer has a need for rights not conveyed under these terms, it must negotiate with BroadVision to determine if there are acceptable terms for transferring such rights, and a mutually acceptable written agreement specifically conveying such rights must be executed by both parties. The product described in this manual may be protected by one or more U.S. and International patents. Certain applications of BroadVision One-To-One software are covered by U.S. patent 5,710,887. DISCLAIMER: BroadVision, Inc., makes no representations or warranties with respect to the contents or use of this publication. Further, BroadVision, Inc., reserves the right to revise this publication and to make changes in its contents at any time, without obligation to notify any person or entity of such revisions or changes. TRADEMARKS: BroadVision and BroadVision One-To-One are registered trademarks of BroadVision, Inc., in the United States and the European Community, and are trademarks of BroadVision, Inc., in other countries. The BroadVision logo, BroadVision One-To-One Content, BroadVision One-To-One Enterprise, BroadVision Content Catalyst, WorldView, and BroadVision QuickSilver are trademarks of BroadVision, Inc., in the United States and other countries. Acrobat and the Acrobat logo are trademarks of Adobe Systems Incorporated. Epic is a trademark of Arbortext, Inc. FAST Data Search for is a trademark of Fast Search & Transfer, Inc. Java and all Java-based trademarks (including Java, JavaServer Pages, Javadoc, JavaMail, and JavaBeans) are logos and trademarks or registered trademarks of Sun Microsystems, Inc., in the U.S. and other countries, and are used under license. This product includes software developed by the Apache Software Foundation ( All other trademarks, service marks, and trade names belong to their respective owners. BroadVision, Inc., disclaims any proprietary interest in the marks and names of others. 2 BroadVision, Inc

3 Contents Preface 5 Technical support...6 Support for third-party software products...6 Typographical conventions Installation overview 9 Server and client applications...10 Server applications...10 Client applications...10 System requirements...11 Disk space requirements...11 Server disk space requirements...11 Client disk space requirements...11 Hardware requirements...12 Server hardware requirements...12 Client hardware recommendations...12 Software requirements...13 Server software requirements...13 Client software requirements...16 Installation configuration and sequence...17 Installing BroadVision One-To-One Content server applications 19 Installing server applications on Windows...19 Content Server...19 Prerequisites...19 Upgrading to Content Server 7.0 on Windows...20 Installing Content Server on Windows...23 Installing FAST Data Search for BroadVision on Windows...23 Post-installation tasks...24 Additional setup...25 Modifying or removing Content Server on Windows...25 Removing FAST Data Search for BroadVision Version 2.0 on Windows...26 Troubleshooting...27 One-To-One Content mod_dav_rm module for Apache on Windows (optional)...27 About the mod_dav_rm module...27 Prerequisites...28 Configuring WebDav for use with Content Server...28 Configuration files...29 httpd.conf...29 Creating a mod_dav_rm configuration in httpd.conf...29 Sample configuration file...32 One-To-One Content Installation Guide 3

4 Contents Creating users configuration files...32 Providing user authentication...33 Sample user configuration files...35 WebDAV proxy support...38 Troubleshooting...38 Content Catalyst Web on Windows Content Catalyst Web...39 Prerequisites...39 Upgrading from Content Catalyst Web 6.0 on Windows Installing Content Catalyst Web 7.0 on Windows Content Catalyst Web 7.0 on Windows 2000 setup...41 Configuring Content Catalyst Web 7.0 on Windows Configuring the upload gateway...47 Multiple host installations...48 Post-installation steps for Content Catalyst Web 7.0 on Windows Removing Content Catalyst Web 7.0 on Windows Installing server applications on UNIX...53 Content Server...53 Prerequisites...53 Upgrading to Content Server 7.0 on UNIX...53 Installing Content Server on UNIX...57 Example environment variable files...58 Installing FAST Data Search for BroadVision on UNIX...61 Post-installation tasks...64 Additional setup...66 Removing Content Server on UNIX...67 Troubleshooting...67 One-To-One Content mod_dav_rm module for Apache on UNIX (optional)...69 About the mod_dav_rm module...69 Prerequisites...69 Content Catalyst Web on UNIX...70 Content Catalyst Web...70 Prerequisites...70 Upgrading from Content Catalyst Web 6.0 on UNIX...71 Installing Content Catalyst Web 7.0 on UNIX...73 Content Catalyst Web 7.0 UNIX setup...74 Configuring Content Catalyst Web on UNIX...77 Configuring the upload gateway...80 Multiple host installations...82 Post-installation steps for Content Catalyst Web 7.0 on UNIX...82 Removing Content Catalyst Web 7.0 on UNIX Installing BroadVision One-To-One Content client applications 87 Installing the One-To-One client applications...87 Prerequisites...87 Upgrading client applications to version Installing the One-To-One Content client applications...89 Post-installation tasks...90 Content Administrator...90 Content Creator...90 Modifying your installation...91 Glossary 93 Index BroadVision, Inc

5 Preface BroadVision One-To-One Content is an application for designing, creating, and managing content for deployment to a website. This guide provides instructions and other information to help you get One-To-One Content server and client software up and running: Chapter 1, "Installation overview briefly describes available components, lists system requirements, explains possible system configurations, and summarizes the steps used to install each component. Chapter 2, "Installing BroadVision One-To-One Content server applications provides detailed installation instructions for each server component. Chapter 3, "Installing BroadVision One-To-One Content client applications provides detailed installation instructions for each client component. The Glossary defines terms related to One-To-One Content. The Index helps you find information in this guide. One-To-One Content Installation Guide 5

6 Preface Technical support Technical support Technical Support services are provided on an annual basis to BroadVision customers. If you experience problems in using any of BroadVision s software products, contact BroadVision s World-wide Customer Support Organization for assistance. Registered customers who have a login name and password can report problems via BroadVision s website Logins to the website allow access to customer-specific support information plus the ability to log and track Service Requests. If you do not have a login, contact your BroadVision Account Representative or logins@broadvision.com to request a login name and password. The website is the preferred method of reporting problems; however, if necessary, you can report problems via to support@broadvision.com. Please be sure to include the service request number when communicating via . Information on how to contact Customer Support offices by telephone can be found on the BroadVision website. Support for third-party software products To allow for complete testing, BroadVision certifies our product releases against the versions of third-party products that are released and available sufficiently in advance of our product release date. This often means that third-party vendors release new versions of their products prior to the next release of the BroadVision software. While BroadVision would prefer that customers use the tested and certified software versions, we also understand that customers will occasionally want or need to use these new versions of third-party products. As long as the vendor guarantees forward compatibility, our products should work with these new versions. BroadVision will usually test and certify newer versions of third-party products in our next product release. This can be a good indicator that the newer versions will work with the previous release. In exceptional cases BroadVision may determine that the newer version of a third-party product cannot be used because it fails in some way during the testing cycle. In this case we will continue to certify the older version. BroadVision will support customers who use newer versions of third-party products by working with the customer to resolve compatibility problems with the third-party vendor. BroadVision will also consider, at our option, developing and releasing minor fixes for our products in order to resolve problems with new versions of third-party products. In exceptional cases, if BroadVision finds that a major architectural change is required to work with the newer version of the third-party product, even though the vendor had guaranteed backward compatibility, the issue may be resolved only after the new version is certified. 6 BroadVision, Inc

7 Preface Typographical conventions Typographical conventions To distinguish sample code, commands, file names, directory names, and keywords and syntax from text, this manual uses the monospace font. In command-line examples, the monospace italic font indicates sample text that you must replace with a specific value. For example, in the following command line, you must supply a value to replace the sample variable setenv IT_DAEMON_PORT 1230 Note that system, subsystem, class, and member names are not called out in a different font. The italic face is used for emphasis and to call out new terminology. One-To-One Content Installation Guide 7

8 Preface Typographical conventions 8 BroadVision, Inc

9 1 Installation overview This chapter describes the BroadVision One-To-One Content server and client applications, general system requirements for installation, and a summary of the installation sequence. The information is arranged as follows: Server and client applications System requirements Installation configuration and sequence One-To-One Content Installation Guide 9

10 Chapter 1 Installation overview Server and client applications Server and client applications One-To-One Content is a multi-user authoring and content management system that combines the flexibility of XML with state-of-the-art database and workflow technologies for designing, creating, and managing your documents and other files. It consists of several server and client applications. Server applications One-To-One Content includes the following server applications: Content Server Use Content Server to create and customize content management repositories for storing DTDs, XML files, XSL files, and other files, such as graphics. Content Server includes publishing and workflow capabilities. Workflow helps you track and manage document authoring, editing, and production tasks. Publishing enables you to produce high quality printed output from complex XML, and to publish to PDF, HTML, WML, PostScript, RTF, QuickSilver, and WorldView formats. BroadVision Content Catalyst Web Use Content Catalyst Web to create, access, and manage data stored in the repository in a thinclient, browser-based environment. Content Catalyst Web server components are scalable and can be customized. Client applications One-To-One Content includes the following client applications: Windows client applications Web client applications Content Administrator Use Content Administrator to manage DTDs, XML files, XSL files, and other files, such as graphics that are stored in your content management repository. The Content Administrator client includes Workflow Designer and Workflow Manager applications to help you track and manage document authoring, editing, and production tasks. Use Content Administrator s publishing features to produce high quality printed output from complex XML, and to publish to PDF, HTML, WML, PostScript, RTF, QuickSilver, and WorldView formats. BroadVision Content Catalyst for Windows Use Content Catalyst for Windows to create, access, and manage data stored in the repository, as well as to perform configuration and administrative functions. Content Creator Use Content Creator to create and manage content based on familiar software editing tools, such as Microsoft Word. Content Catalyst Web Use Content Catalyst Web to create, access, and manage data stored in the repository in a thinclient, browser-based environment. The Content Catalyst Web client is a thin-client application that runs in a web browser. 10 BroadVision, Inc

11 Chapter 1 Installation overview System requirements System requirements This section lists general hardware and software requirements for all One-To-One Content server and client applications. See the appropriate section of this guide for a list of specific software requirements for each component. Disk space requirements Server disk space requirements One-To-One Content has the following disk space requirements for servers. These numbers do not include space for Oracle8i or the repository. On Windows disk drives with FAT file systems, the installation size depends on the cluster size of the drive. Your installation size could be larger than the size displayed in the installation dialog box. Server component Windows Solaris HP-UX AIX Content Server 190 MB 250 MB 280 MB 320 MB Content Catalyst Web 17 MB 19 MB 17 MB 19 MB On Windows, the drive containing the system TEMP directory also requires a minimum of 22 MB free disk space. One Solaris, HP-UX, and AIX, you must have 20 MB of free disk space available in the /tmp partition. Client disk space requirements One-To-One Content has the following disk space requirements for clients. Client component Content Administrator Content Creator Content Catalyst for Windows Windows 49 MB 39 MB 31 MB In addition, the drive containing the system TEMP directory requires a minimum of 10 MB free disk space. One-To-One Content Installation Guide 11

12 Chapter 1 Installation overview System requirements Hardware requirements The requirements listed here are intended only as guidelines, representing the hardware used for testing the One-To-One Content server and client applications. You should work with your BroadVision consultant to determine the optimum hardware configuration for your system. Server hardware requirements Server component Content Server Content Catalyst Web Windows Solaris HP-UX AIX Intel Pentium II with two processors or 100% compatible with the following minimum configuration: 733 MHz 1 GB RAM virtual memory two times the size of the physical memory Intel Pentium II with the following minimum configuration: 450 MHz 1 GB RAM Solaris server class machine with two processors and 1GB RAM Solaris server class machine with four processors and 1GB RAM. Note: Content Catalyst Web has the same requirements as One-To-One Enterprise on Solaris. HP 9000/800 Series server machine with two processors and 1 GB RAM HP 9000/800 Series server machine with two processors and 1 GB RAM Note: Content Catalyst Web has the same requirements as One-To-One Enterprise on HP- UX. An IBM pseries (RS/6000) server with 32-bit PowerPC architecture, and 1 GB of RAM. An IBM pseries (RS/6000) server with 32-bit PowerPC architecture, and 1 GB of RAM. Note: Content Catalyst Web has the same requirements as One-To-One Enterprise on AIX. If you use separate machines for Content Server and the Oracle server, you need a second server machine that meets the Oracle 8i configuration requirements. Consult your Oracle documentation for system requirements. Multiple disks are recommended to improve overall system performance for Oracle. Client hardware recommendations Content Catalyst Web runs on any hardware that supports the browsers listed in Web client applications on page 16. An Intel Pentium III or 100% compatible machine running at 400 MHz with 256 MB RAM is recommended for all other One-To-One Content client applications. Content Catalyst Web and Content Catalyst for Windows both require a graphics adapter configured to display at 800 x 600 resolution or higher, using 256 or more colors. 12 BroadVision, Inc

13 Chapter 1 Installation overview System requirements Software requirements This software listed here was used for testing the One-To-One Content server and client applications. Server software requirements This section lists the software required for One-To-One Content Server and One-To-One Content Catalyst Web server. Content Server Windows On Windows, One-To-One Content Server requires the following software: Windows 2000 Server with Service Pack 1 Microsoft Virtual Machine for Java, version or later Microsoft Internet Explorer, version 5.5, with Service Pack 2 TCP/IP Network Protocol Solaris On Solaris, One-To-One Content Server requires the following software: Solaris 2.7 or Solaris 2.8 In addition to the basic operating system, be sure to install the latest patches recommended for that system. Additionally, the following table lists patches that this version of Content Server was tested with for supported operating systems. The patches in the following table can be downloaded from the website or obtained from your Sun service provider. The two-digit number following the dash in each patch ID is the revision of that patch. The table lists minimum patch revisions that this version of Content Server was tested with. Later revisions (a higher dash number) are acceptable. Solaris Patch ID Description version bit shared library patch for 64-bit C bit shared library patch for C Kernel update patch /usr/lib/fs/ufs/fsck patch Linker patch libthread patch , 2 Kernel update patch 1 Patch required for FAST Data Search for BroadVision. 2 Patch requires other patches. See One-To-One Content Installation Guide 13

14 Chapter 1 Installation overview System requirements HP-UX On HP-UX, One-To-One Content Server requires the following software: HP 11.0 or HP 11i In addition to the basic operating system, be sure to install the latest patches recommended for that system. Additionally, the following table lists patches that this version of Content Server was tested with for supported operating systems. The patches in the following table can be downloaded from the website or obtained from your Hewlett Packard service provider. The table lists minimum patch revisions that this version of Content Server was tested with. Later revisions are acceptable. AIX Content Catalyst Web HP-UX Patch ID Description version 11.0 QPK B Quality Pack for HP-UX XSWGR1100 B HP-UX General Release Patches, March XSWHWCR1100 B HP-UX Hardware Enablement and Critical Patches, March i BUNDLE11i B Required Patch Bundle for HP-UX 11i, February i GOLDBASE11i B Gold Base Patches for HP-UX 11i, June i GOLDAPPS11i B Gold Applications Patches for HP_UX 11i, June Patch required for FAST Data Search for BroadVision. On AIX, One-To-One Content Server requires either one of the following tested and certified environments: AIX (maintenance package ) with fixes for IBM 1.3 JVM. AIX 5L, also known as AIX 5.1 (maintenance package ). In addition to the basic AIX operating system, install the latest patches that IBM recommends for that system. All platforms On all platforms, One-To-One Content Server requires Oracle Each Content Server installation requires at least one Oracle server license and one Oracle client license. On all platforms, install the following software for One-To-One Content Server as needed: Adobe Acrobat Distiller, version 4.0, if you plan to publish content to PDF. FAST Data Search for BroadVision, Version 1.0 or Version 2.0, if you want full-text search capability. (FAST Data Search for BroadVision is an optional product that you must purchase if you want to use it with One-To-One Content.) One-To-One Content Catalyst Web requires the following software on Solaris systems: 14 BroadVision, Inc

15 Chapter 1 Installation overview System requirements BroadVision One-To-One Enterprise 6.0 AH ORACLE database One-To-One Content Server 7.0 Java Virtual Machine 1.3 One-To-One Content Installation Guide 15

16 Chapter 1 Installation overview System requirements Client software requirements Windows client applications All One-To-One Content client applications for Windows require the following software: One of the following operating systems: Windows 2000 Professional with Service Pack 1 Microsoft Windows NT 4.0 Workstation with Service Pack 6a Later versions of the Service Pack may work but have not been qualified. Windows 98 Second Edition Windows XP TCP/IP Network Protocol Microsoft Internet Explorer, version 5.5, with Service Pack 2 For Content Administrator, the Microsoft Virtual Machine for Java, which is installed with Microsoft Internet Explorer, must be at version level or later. Additional software is required for certain client applications, as shown in the following table. Client component Windows Content Administrator Arbortext Epic version 4 (required only if you want to use Epic as your XML editor) Content Creator Microsoft Word 2000 or Microsoft Word 97 If you plan to set up Content Creator as your preferred XML editor in Content Administrator, you cannot use Word 97. You must use Word Web client applications Content Catalyst Web requires one of the following web browsers: Netscape Navigator Microsoft Internet Explorer, version 5.5, with Service Pack 2 16 BroadVision, Inc

17 Chapter 1 Installation overview Installation configuration and sequence Installation configuration and sequence Content Server/Oracle configuration Installation sequence You can use either of the following Content Server/Oracle configurations: Use the same machine for Content Server and the Oracle server. If you choose this configuration, you must install Content Server and the Oracle server software on the same machine. Installing the Oracle server software simultaneously installs the Oracle client software on the same machine. Use separate machines for Content Server and the Oracle server. If you choose this configuration, you must install the Oracle server software on the Oracle server machine and a separate installation of the Oracle client software on the Content Server machine. Install One-To-One Content applications and prerequisite software in the following order: 1. Install the Oracle server software on the machine that you want to use as your Oracle server. Before creating an Oracle database, see Chapter 2 of the One-To-One Content Administrator Guide for details about Content Server/Oracle database requirements. When you install the Oracle server software, the Oracle client software is simultaneously installed on the same machine. If you plan to install One-To-One Content Server on a different machine, the Content Server machine requires a separate installation of the Oracle client software. 2. Install the Oracle client software on the machine on which you plan to install Content Server, if the Content Server machine will be separate from the Oracle server machine. 3. If you need to publish content to PDF format, install Adobe Acrobat Distiller. 4. Install Content Server. Depending on your planned content management configuration, install Content Server either on the machine on which you installed the Oracle server software or on the machine on which you separately installed the Oracle client software. When you install Content Server on Windows, the One-To-One Content Administrator client is simultaneously installed on the same machine. 5. To use full-text indexing and search with One-To-One Content, install and configure a supported third-party search engine. 6. If you plan to use Content Catalyst Web, install it on the same machine on which BroadVision One-To-One Enterprise is installed and configured. It can be installed before or after the client applications. 7. If you plan to use Arbortext Epic as your XML editor, install it on the machine(s) on which you plan to install the One-To-One Content client component(s). If you install it later, you will need to manually update some environment variables. See the information on APTCATPATH in Appendix B of the One-To-One Content Administrator Guide for details. 8. Install the One-To-One Content client applications you want to use. Clients can be installed on the same machine as Content Server or on remote machines. One-To-One Content Installation Guide 17

18 Chapter 1 Installation overview Installation configuration and sequence 18 BroadVision, Inc

19 2 Installing BroadVision One-To-One Content server applications This chapter provides detailed instructions for installing One-To-One Content server software, as follows: Installing server applications on Windows Installing server applications on UNIX Installing server applications on Windows Content Server When you install Content Server on Windows, the One-To-One Content Administrator client is simultaneously installed on the same machine. Prerequisites Hardware Ensure that your system complies with all disk space and hardware requirements listed under System requirements on page 11. Software Install Oracle software as follows: If you plan to use the same machine for Content Server and the Oracle server, install the Oracle server software on that machine. This simultaneously installs the Oracle client software on the same machine. If you plan to use separate machines for Content Server and the Oracle server, install the Oracle server software on the Oracle server machine and a separate installation of the Oracle client software on the Content Server machine. Before creating your Oracle database, refer to Chapter 2 of the One-To-One Content Administrator Guide for Content Server/Oracle database requirements. The following software must be installed on the machine on which you plan to install Content Server: Windows 2000 Server with Service Pack 1 Microsoft Virtual Machine for Java, version or later Microsoft Internet Explorer, version 5.5, with Service Pack 2 or version 6.0 TCP/IP Network Protocol One-To-One Content Installation Guide 19

20 Chapter 2 Installing BroadVision One-To-One Content server applications Installing server applications on Windows Adobe Acrobat Distiller, version 4.0 (if you plan to publish content to PDF) When you install Adobe Acrobat Distiller version 4.0, be sure to include Adobe Acrobat Reader so that you can view the published PDF documents. See your Adobe documentation for installation instructions. Upgrading to Content Server 7.0 on Windows Upgrading from previous versions of Content Server involves saving certain files from your existing content management installation, removing and reinstalling your program files, upgrading the content management repository, and, if desired, updating or recreating your full-text index. Upgrading the software To upgrade from Content Server 6.0 to Content Server 7.0 on Windows 1. On the machine on which Content Server is installed, make sure no applications are running. 2. Log on to the Content Server machine as a user with local administration privileges. 3. Stop the publishing server by selecting Start > Programs > BroadVision One-To-One Content > Stop Publishing Server. 4. Use the Services applet to stop the services named BR Fulltext Service and BR Application Manager. 5. Copy the file default.dom to a safe location. This file is located in the %IMCONFIGHOME% directory. Unless you specified a different location when you installed Content Server, this file is located in drive:\bv1to1cm\cm\imconfighome. 6. Make a backup copy of catalog files, templates, and DTDs that have been added or changed since you installed Content Server version Use Add/Remove Programs to remove the Content Server version 6.0 server software and, if installed, the One-To-One Content client software, version Remove all directories and remaining contents from %IMHOME%. 9. Reboot your system. 10. Log on as a user with local administration privileges. 11. Insert the One-To-One Content product CD and browse to the ContentServerWin directory. 12. Double-click the Setup.exe file located in the ContentServerWin directory. The setup program for Content Server starts. 13. Follow the instructions on your screen. 14. Click Finish when the installation completes. 15. Reboot the system. 16. Copy the default.dom file that you saved during Step 5 to the Content Server version 7.0 imconfighome directory. Unless you specified a different directory during installation, this directory is located in drive:\bv1to1cm\cm\imconfighome. 20 BroadVision, Inc

21 Chapter 2 Installing BroadVision One-To-One Content server applications Installing server applications on Windows Upgrading the repository To upgrade a 6.0 repository to a 7.0 repository on Windows 1. Make a full backup copy of the Oracle database that contains the content management repository you are upgrading. See your Oracle documentation for instructions. 2. Be sure you have enough free space to extend the tablespace. The amount of free space required can vary depending on your system configuration and the size of the repository. IMPORTANT: You must be a brdba user to perform the upgrade procedure. Do not start Oracle SQL*Plus as a user other than brdba when you run the commands in step At an MS-DOS prompt, start Oracle SQL*Plus as the Oracle user brdba, run the appropriate upgrade script or scripts, and save the output to log files. If you are currently using 6.0 AC. Type the following command at the MS-DOS prompt: sqlplus > upgrade.log If you are currently using 6.0 AB. Type the following command at the MS-DOS prompt: sqlplus > upgrade.log If you are currently using 6.0 or 6.0 AA with a 6.0 or 6.0 AA repository. Type the following command at the MS-DOS prompt: sqlplus > upgrade.log If you are currently using 6.0 or 6.0 AA with a repository. You need to upgrade your repository to the 6.0 level and then upgrade it to the 7.0 level by running the following two scripts at the MS-DOS prompt: sqlplus > upgrade.log Check the log file to verify the upgrade was successful and then run the second script: sqlplus > upgrade.log brdba_password is the password for the brdba user; by default, the password is dba. repository_name is the repository name. %IMHOME is the path where Content Server is installed. upgrade.log is the name of the output log file for this command. 4. Check the log file to be sure the upgrade was successful. IMPORTANT: If you are using Content Catalyst Windows or Content Catalyst Web with Content Server, and you are upgrading from 6.0, 6.0 AA, or 6.0 AB, you must perform the some additional configuration steps. See Appendix B in the The Content Catalyst Widows/Web Administrator Guide for more information. If you are upgrading from 6.0 AC, no further steps are required. One-To-One Content Installation Guide 21

22 Chapter 2 Installing BroadVision One-To-One Content server applications Installing server applications on Windows To upgrade a repository to a 7.0 repository on Windows 1. Make a full backup copy of the Oracle database that contains the content management repository you are upgrading. See your Oracle documentation for instructions. 2. Be sure you have enough free space to extend the tablespace. The amount of free space required can vary depending on your system configuration and the size of the repository. IMPORTANT: You must be a brdba user to perform the upgrade procedure. Do not start Oracle SQL*Plus as a user other than brdba when you run the command in steps 3 and At an MS-DOS prompt, start Oracle SQL*Plus as the Oracle user brdba, run the imupgrade_551_60.sql script, and save the output to a log file. To do this, type the following command at the MS-DOS prompt: sqlplus > upgrade.log brdba_password is the password for the brdba user. By default, the password is dba. repository_name is the repository name. %IMHOME is the path where Content Server is installed. upgrade.log is the name of the output log file for this command. 4. Check the log file to be sure the upgrade was successful. 5. At the MS-DOS prompt, run the imupgrade_60_70.sql script, and again, save the output to a log file. To do this, type the following command at the MS-DOS prompt: sqlplus > upgrade.log 6. Check the log file to be sure the second upgrade was successful. IMPORTANT: If you are using Content Catalyst Windows or Content Catalyst Web with Content Server, you must perform some additional configuration steps. See Appendix B in the Content Catalyst for Windows/Web Administrator Guide for more information. Upgrading the full-text index To update the full-text index for a content management repository that has been upgraded from version 6.0 to version 7.0, you must do one of the following: If you are currently using FAST Data Search for BroadVision, Version 1.0, you need to upgrade to Version 2.0. For information on configuring your system to use FAST Data Search for BroadVision, see Upgrading FAST Data Search for BroadVision in Chapter 8 of the One-To- One Content Administrator Guide. If you are using a different search engine and you now want to use FAST Data Search for BroadVision, Version 2.0 (which is available as a separate add-on product), you must install FAST Data Search for BroadVision, Version 2.0 and reindex your repository using FAST Data Search for BroadVision, Version 2.0. For details about upgrading a full-text index, see Reindexing an upgraded repository for FAST Data Search for BroadVision in Chapter 8 of the One-To-One Content Administrator Guide. 22 BroadVision, Inc

23 Chapter 2 Installing BroadVision One-To-One Content server applications Installing server applications on Windows Installing Content Server on Windows Use the following procedure to install Content Server on machines on which it is not already installed. When you install Content Server, the Content Administrator client is automatically installed. Machines with a previous version of Information Manager (now called Content Server) installed must be upgraded. Instead of performing this installation procedure, perform the procedure Upgrading to Content Server 7.0 on Windows on page 20. To install Content Server on Windows 1. Close all applications running on the machine on which you plan to install Content Server. 2. Log on as a user with local administration privileges. 3. Insert the One-To-One Content product CD. 4. Browse to the ContentServerWin directory on the CD. 5. Double-click the Setup.exe file located in the ContentServerWin directory. The setup program for Content Server starts. 6. Follow the instructions on your screen. 7. Click Finish when the installation completes. Reboot the system. Installing FAST Data Search for BroadVision on Windows To use FAST Data Search for BroadVision, Version 2.0 for full-text indexing and search with your repository, you must install and configure it for use with One-To-One Content. This section details the procedure for installing FAST Data Search for BroadVision, Version 2.0 for the first time with One-To-One Content. For configuration information, see Chapter 8, Configuring full-text indexing and search, in the One-To-One Content Administrator Guide. NOTE: FAST Data Search for BroadVision is available as a separate add-on product. If you are currently using FAST Data Search for BroadVision, Version 1.0, you need to upgrade to Version 2.0. For information, see Upgrading FAST Data Search for BroadVision in Chapter 8 of the One-To-One Content Administrator Guide. If you are using a different search engine and you now want to use FAST Data Search for BroadVision (which is available as a separate add-on product), you must install FAST Data Search for BroadVision, Version 2.0 and reindex your repository using FAST Data Search for BroadVision. To install FAST Data Search for BroadVision 1. On the machine on which Content Server is installed, make sure no applications are running. 2. Insert the FAST Data Search for BroadVision product CD. 3. Double-click the setup.exe file located in the FastSearch directory. One-To-One Content Installation Guide 23

24 Chapter 2 Installing BroadVision One-To-One Content server applications Installing server applications on Windows The second Installanywhere window displays the following statement: This software installation contains the FastSearch version 2.0 for BroadVision One-To-One Enterprise Version Specify an installation directory. The default is c:\datasearch. 5. Fast Search 2.0 is selected for installation. Click Next to finish the installation. 6. An Explorer window opens, displaying the contents of the FastSearch menu. Close this window, because it hides the InstallShield Setup Status and InstallShield Wizard Complete windows, preventing you from seeing the status of the installation process. 7. Register FAST Data Search for BroadVision as a Windows service by selecting Programs > FastSearch > Register RTSearch from the Windows Start menu. This creates a Windows service named FAST Real-Time Search, with its startup type set to manual. To avoid having to restart the service every time you reboot the machine, you can use the Windows Services applet to change the startup type for the service from manual to automatic. 8. Follow the instructions in Chapter 8 of the One-To-One Content Administrator Guide to configure FAST Data Search for BroadVision for Content Server. Post-installation tasks Set the temporary file transfer directory location Content Server requires a temporary file transfer directory for checkin, checkout, and other processes. By default, Content Server creates a directory called ftrbasedir in drive:\temp or drive:\tmp, whichever it encounters first. If you do not want to use the default, you can define a directory name as a value for the ftr_base_directory variable in %IMHOME%\lib\rm.ini file. To set the temporary file transfer directory 1. Open the rm.ini file in the directory %IMHOME%\lib. 2. Uncomment the following line by removing the # character: #ftr_base_directory=<directoryname> 3. Type the directory name you want in place of <directoryname>. 4. Save and close the rm.ini file. If you do not set the ftr_base_directory environment variable, Content Server creates a directory called ftrbasedir in a location it determines through the following process: 1. Content Server searches for the value of the Temp system or user environment variable. 2. If Temp is not defined, Content Server searches for the value of TMP. 3. If both Temp and TMP are not defined, Content Server searches for the directories c:\temp and c:\tmp, in that order, and uses the first one that exists. If Content Server cannot find a directory in which to create ftrbasedir, an error displays. 24 BroadVision, Inc

25 Chapter 2 Installing BroadVision One-To-One Content server applications Installing server applications on Windows Start the Application Manager and the full-text indexing service After you install Content Server and reboot your machine, the Application Manager and the fulltext indexing service start automatically each time you start a Windows session.the service names are BR Application Manager and BR Fulltext Service, respectively. Start the publishing server You can start and stop the publishing server manually, as described below, or set it up as a Windows service. For instructions on setting it up as a service, see Setting up the publishing server to run automatically on Windows in the One-To-One Content Administrator Guide. To start the publishing server 1. Select Start > Programs > BroadVision > One-To-One Content > Start Publishing Server. You must start the publishing server each time you restart a Windows session. To stop the publishing server 1. Select Start > Programs > BroadVision > One-To-One Content > Stop Publishing Server. Additional setup One instance of the Content Administrator client is installed when you install Content Server. To allow additional users to access Content Server functions and the content management repository, you must install one or more additional One-To-One Content client applications. See Chapter 3, Installing BroadVision One-To-One Content client applications. You must also create a content management repository (unless you upgraded an existing one), add projects and users, and perform other setup. The procedures for completing these setup tasks are described in detail in the One-To-One Content Administrator Guide. Modifying or removing Content Server on Windows You can use the setup program to repair or remove your installation. The setup program automatically opens in One-To-One Content Server Modification mode when Content Server is installed. The One-To-One Content Server Modification mode provides the following choices: Repair Reinstall your current Content Server installation. This option reinstalls the files in all of the Content Server directories and resets all registry entries, including environment variables. Remove Remove your current Content Server installation. To repair your Content Server installation 1. Log on as a user with local administration privileges. 2. Insert the One-To-One Content product CD. 3. Double-click Setup.exe in the ContentServerWin folder of the CD. or In the Windows Add/Remove Programs utility, select BroadVision One-To-One Content 7.0 Server and click Change/Remove. The One-To-One Content Server Modification window opens. One-To-One Content Installation Guide 25

26 Chapter 2 Installing BroadVision One-To-One Content server applications Installing server applications on Windows 4. Select Repair in the One-To-One Content Server Modification window and click Next. To remove your Content Server installation 1. On the machine on which Content Server is installed, make sure no applications are running. 2. Log on as a user with local administration privileges. 3. In the Windows Add/Remove Programs utility, select BroadVision One-To-One Content 7.0 Server and click Change/Remove. 4. The One-To-One Content Server Modification window opens. 5. Select Remove in the One-To-One Content Server Modification window and click Next. 6. Click OK to confirm removal of One-To-One Content Server. Removing FAST Data Search for BroadVision Version 2.0 on Windows Use the following procedure to completely remove FAST Data Search for BroadVision Version 2.0 from Windows. Before removing FAST Data Search for BroadVision Version 2.0 The removal procedure deletes the FAST Data Search for BroadVision Version 2.0 software as well as all user indexes and configuration files. If you want to save either the indexes, the configuration files, or both, do the following before removing the software: Move the index directories $FASTSEARCH/data_index and $FASTSEARCH/data_fixml to a safe location. Move the configuration files $FASTSEARCH/etc/rtsearchrc.xml and $FASTSEARCH/etc/indexConfig.xml to a safe location. These files should only be used for future reference concerning configuration settings. Do not reuse these files. To remove FAST Data Search for BroadVision Version 2.0 on Windows 1. Select Start > Programs > Administrative Tools > Services. 2. In the Services dialog box, right-click on FAST Real-Time Search, and select Stop from the popup menu. 3. Close the Services dialog box. 4. In the Windows Add/Remove Programs utility, selects FastSearch, and click Change/Remove. The InstallShield Wizard modification window opens. 5. Select Remove, and click Next. The confirmation window is displayed. 6. If the confirmation information is correct, click Finish. The software and all associated files are removed. 26 BroadVision, Inc

27 Chapter 2 Installing BroadVision One-To-One Content server applications Installing server applications on Windows Troubleshooting Port in Use Error Content Server applications use port number 1963 as a default port for client/server communications. If port number 1963 is already in use by another application, an error message on the server indicates that the port address is already in use. You may also receive a message stating that Application Manager cannot be started. To correct this problem, you must change the default port number 1963 to another available port number by changing the value of the IM_RPC_PORTNAME system variable. To change the default port number on a Windows server or client machine 1. In the Windows Control Panel, double-click the System icon to open the System Properties window. 2. On Windows NT version 4 systems, select the Environment tab in the System Properties window. On Windows 2000 systems, select the Advanced tab and click Environment Variables. 3. Scroll down the list of System Variables and click IM_RPC_PORTNAME. On Windows NT version 4 systems, the value for this variable is displayed in the Value field in the lower portion of the window. On Windows 2000 systems, click Edit to display the value. 4. Change the port number from 1963 to another available port number. 5. On Windows NT version 4 systems, click Set. On Windows 2000 systems, click OK. 6. Click OK again. For client applications, repeat steps 1 through 6 on each client machine. One-To-One Content mod_dav_rm module for Apache on Windows (optional) This section describes how to install the One-To-One Content mod_dav_rm module. The mod_dav_rm module allows a Content Server repository to be accessed through a WebDAVenabled Apache 2.0 web server by WebDAV clients such as Microsoft Word, Microsoft Web Folders, and Windows Explorer. For information about WebDav as it relates to Content Server, see the One- To-One Content Developer Guide. For general information about the WebDAV standard, see About the mod_dav_rm module The One-To-One Content mod_dav_rm module is compatible with the following Apache 2.0 platform configurations: Windows NT, Windows 2000, Solaris, HP-UX, and AIX. If you are using the mod_dav_rm module on UNIX, see One-To-One Content mod_dav_rm module for Apache on UNIX (optional) on page 69 for UNIX installation instructions. The mod_dav_rm module file is named mod_dav_rm.so. This file is used for all of the supported Apache platforms. The file is copied to <drive>:\bv1to1cm\cm\lib\dav\win during the One- To-One Content install process. One-To-One Content Installation Guide 27

28 Chapter 2 Installing BroadVision One-To-One Content server applications Installing server applications on Windows Prerequisites Before installing the One-To-One Content mod_dav_rm module, ensure that: Apache 2.0 is installed and configured. Apache must be built with Dynamic Shared Object Support (DSO). For information about DSO, see The Apache mod_dav module is installed and configured. The Apache mod_dav module enables WebDAV functionality for Apache 2.0 web servers. For information on the Apache mod_dav module, see One-To-One Content Server 7.0 is installed and configured, and accessible to the Apache web server machine. To install the mod_dav_rm module 1. Copy the file <drive>:\bv1to1cm\cm\lib\dav\win\mod_dav_rm.so into the <Apache_root>/modules directory. 2. Go to Configuring WebDav for use with Content Server, next. Configuring WebDav for use with Content Server This section details the procedures necessary to enable WebDAV between a One-To-One Content Server and Apache 2.0 server. The information applies to both Windows and UNIX Apache installations. Apache compatibility The mod_dav_rm.so module for Apache was tested with Apache version On Solaris: Apache was built with GNU C compiler v On HP-UX: Apache was built with HP ANSI C compiler with the PHSS_26262 ld(1) and linker tools cumulative patch installed. On AIX: Apache was built with VisualAge C for AIX Compiler, Version 5. On Windows: Apache was built with Microsoft 32-bit C/C++ Optimizing Compiler Version for 80x86. The mod_dav_rm.so module has not been tested with any of the pre-compiled versions of Apache WebDav server modules To make Content Server repositories accessible to WebDAV clients, you must configure the Apache mod_dav module and the One-To-One Content mod_dav_rm module for Apache. The mod_dav module is a standard Apache server module distributed with Apache 2.0. This module provides class 1 and class 2 WebDAV ('Web-based Distributed Authoring and Versioning') functionality for Apache. WebDAV is an extension to the HTTP protocol that allows creating, moving, copying, and deleting resources and collections on a remote web server. For more information about the Apache mod_dav module, see 2.0/mod/mod_dav.html. The One-To-One Content mod_dav_rm module for Apache enables a WebDAV-enabled Apache 2.0 web server to access Content Server repositories. 28 BroadVision, Inc