Revize Installation Guide

INSTALLATION GUIDE

TABLE OF CONTENTS Installation Guide ...... 1

Table of Contents ...... 2

1 Overview...... 5

1.1 Assumptions...... 5

1.2 Typographic Conventions...... 6

2 System Requirements ...... 7

2.1 Server Hardware Requirements...... 7

2.2 Operating System Requirements ...... 8

2.3 Database Requirements...... 9

2.4 Web Server Requirements ...... 9

2.5 Web Browser Requirements ...... 10

3 Stand-Alone installation...... 11

3.1 System Requirements ...... 11

3.2 Installation Steps ...... 11

4 Network Installation ...... 22

4.1 Windows NT 4.0 / 2000 ...... 22

4.2 Redhat Linux / Solaris 8 (Sparc)...... 22

4.2.1 Redhat 6.2/Solaris 8 Installation (GUI).. 23

4.2.2 Solaris 8/Redhat 6.2 Console Installation 24

4.2.3 Redhat Linux 7.2 (and later) Installation 25

5 Installation Verification...... 27

5.1 Administration Center ...... 27

6 External Web server ...... 33

6.1 Resin on IIS ...... 33

6.2 New Install of Revize ...... 33

6.3 Migrating to New Deployment...... 34

6.4 Migrating a Current Deployment to Run Under IIS 38

6.5 Install Resin IIS dll ...... 39

6.7 Web Service Extensions - IIS 6.0...... 46

6.8 Configuring the resin.conf file...... 49

6.9 Editing the Revize.xml File ...... 51

6.10 Create Revize Virtual Directory ...... 51

6.11 Troubleshooting ...... 55

7 External Database...... 58

8 Revize Glossary of Terms ...... 68

1 OVERVIEW

This manual gives the requirements and installation instructions for Revize on all supported operating systems.

1.1 ASSUMPTIONS

In addition to the instructions outlined in this manual, it is assumed that anyone installing Revize should have working knowledge of and/or experience with:

• General installation of software on the target platform • Starting and stopping processes on the target platform • Web servers and their setup, including HTTP protocols, URL’s, port configurations, etc. • Security mechanisms • Backup systems, log file usage and other basic server requirements

1.2 TYPOGRAPHIC CONVENTIONS

Note that Revize documentation uses certain typographic conventions to describe

1. References to a specific location in Revize or the operating system will be indicated in this document either in SMALL CAPS, or as a capitalized word followed by the word “button”. For example:

Click RESOURCES.

Click the New button. 2. Specific words that should be entered into a field will be indicated by bold italics. (Note: Actual entries will not be in bold italics when typed into Revize.) For example: Type John Doe in the First_Name field.

In the Age field, type 52. 3. Fields will be referenced by the name used in Revize, followed by the word “field”. For example: Type a name for your Template in the Label field.

2 SYSTEM REQUIREMENTS

System requirements for Revize are separated into several groups:

• Server Hardware Requirements • Operating System Requirements • Database Requirements • Web Server Requirements • Web Browser Requirements

2.1 SERVER HARDWARE REQUIREMENTS

Intel™-based (or equivalent) server hardware used for Revize should meet the following minimum requirements:

• 256 MB of RAM (512 MB is recommended) • Pentium III 800 MHz or AMD Athlon 800 MHz or greater • 512 MB hard disk space, including 150 MB for the Revize system plus space for Web content

Sparc™ server hardware used for Revize should meet the following minimum requirements:

• 300+ Mhz SPARC processor • 256 MB RAM (512 Recommended) • 512 MB hard disk space, including 150 MB for the Revize system plus space for Web content

2.2 OPERATING SYSTEM REQUIREMENTS

Revize has been tested and is supported on the following operating system platforms.

• All Win32 Platforms. (Complete testing for Windows Server 2003 is in progress.) • Solaris 8 (Sparc) • Red Hat 6.2/6.3 using Linux 2.2.x kernel • Red Hat 7.2 with JDK 1.4.1_02 installed and configuration changes as noted in this guide. • Red Hat 8.0 with JDK 1.4.1_02 installed and configuration changes as noted in this guide.

2.3 DATABASE REQUIREMENTS

The Revize Web Application is shipped with its own database management system (DBMS). However, it is possible to use other database management systems to store Revize data. Connectivity to an external database is supported by a Revize database adaptor. Currently, the following database adaptors are available:

• Oracle 8i • Microsoft SQL Server 7.0, 8.0, & 2000

2.4 WEB SERVER REQUIREMENTS

The Revize Web Application is shipped with its own Web server. However, it is possible to use Revize with an external Web server. Currently, the following external Web servers are supported:

• Microsoft Internet Information Services (IIS) Web Server

2.5 WEB BROWSER REQUIREMENTS

All interaction with the Revize system uses a standard Web-based interface, operating over a TCP/IP network. Any browser used to access Revize must support JavaScript 1.2 and scripting must not be disabled.

Presently there are two tested and supported web browsers:

• Microsoft Internet Explorer 5.5 or greater • Netscape Communicator 4.76 or greater

Earlier browsers can be used with limitations. Please contact Idetix for further information.

3 STAND-ALONE INSTALLATION

The stand-alone installation of Revize enables development on a single machine, allowing local separate testing of Templates and other resources before they are released into a production system.

3.1 SYSTEM REQUIREMENTS

Because the standard development environment (using Dreamweaver) is Windows-based, the stand-alone installation of Revize has been tested only for Windows 32-bit operating systems. See section 2.1 for hardware requirements.

3.2 INSTALLATION STEPS

1. Installation of Revize is controlled by a set of Java resources accessed via an applet embedded in an HTML document. The applet, installation files and HTML document are available either through a CD-ROM or Web download, depending upon how your organization chose to purchase Revize.

2. If installing via the Web, navigate to the download link provided by Idetix sales / technical support. The Revize startup screen should appear after a few moments, and you can proceed to step 6 below. (Note that the download link used in the following figure is for illustration only. Contact Idetix for specific information regarding Web installation.)

3. If installing from a CD-ROM, insert it into the appropriate drive. If the Revize startup screen appears, skip to step 6 below. Otherwise, you will need to open the startup screen document directly.

4. Use the Windows explorer to navigate the CD- ROM drive

and double-click on INDEX.HTML.

5. Alternatively, click START on the Windows taskbar and select RUN.

Assuming your CD-ROM is drive D, type D:\index.html into the run dialog box and click OK to launch the Revize startup screen. (Substitute the appropriate drive letter, if your CD-ROM drive is not D.)

6. Once the Revize startup screen displays, click the INSTALL button.

7. In the next window, select INSTALL REVIZE. (Installation and use of the Revize Extension to Dreamweaver is described in a separate manual.)

8. If a security warning dialog box appears for the InstallAnywhere applet, click YES to accept the signed security certificate and continue the installation.

9. The InstallAnywhere Web Installer screen should appear, and you can simply click the RECOMMENDED INSTALLATION button to install the version of Revize appropriate for the current platform (in this case, Windows).

10. If the recommended installation button does not appear, simply choose the Windows installer link directly.

11. The installer should indicate that it is down- loading (copying) the Revize Web Application setup program to the indicated location.

12. When the introductory “Thank you” screen appears, click on the Next button to continue.

13. Accept the terms of the license agreement and then choose NEXT.

14. If this is your first time installing Revize on this machine, or you wish to replace a previous installation, select the FIRST INSTALL option.

15. If you are upgrading from a previous installation of Revize choose the UPGRADE AN EXISTING REVIZE INSTALLATION option.

16. Once you have chosen an installation option, click NEXT to continue 17. A prompt will appear asking for the location (folder) into which you would like to install Revize . You may either click CHOOSE… to select a location or simply click NEXT to accept the default location (C:\Revize).

18. A Pre-Installation Summary screen should appear, describing all of the options you have chosen. Click INSTALL to continue the installation with the indicated options.

19. Wait for Revize to load. This process could take several minutes.

20. Follow the remaining prompts until the installation is complete, and you click the DONE button.

21. To start the local Revize server, click START→PROGRAMS→REVIZE→START REVIZE. When the black DOS window appears, minimize but do not close it. For stand-alone installation, this window must remain open while the server is running.

4 NETWORK INSTALLATION

Network installation allows access to Revize across a local network. The network server may use any of the following platforms.

• Windows NT 4.0, Service Pack 5 or greater, • Windows 2000, Service Pack 1 or greater • Solaris 8 (Sparc), 98 • Red Hat 6.2, 7.2, 8.0, 9.0

4.1 WINDOWS NT 4.0 / 2000

Network installation for a Windows NT or Windows 2000 server is exactly like the stand-alone installation discussed earlier in this manual. After finishing the installation, inform each workstation operator of the port used by Revize. By default, this is port:8080.

4.2 REDHAT LINUX / SOLARIS 8 (SPARC)

Revize can be installed on a Linux or Solaris platform via a graphical user interface or through a console.

The steps for installation of Revize on a Linux or Solaris server are similar to those for Windows, as the installer is Java-based and performs the same tasks on all operating systems. However, there ate a few key differences in the preparation for install and a few post- install procedures that must be followed on these Unix- family platforms. Those differences are noted in this section.

4.2.1 Redhat 6.2/Solaris 8 Installation (GUI)

Installation files can be obtained via download from the web or from a CD provided by Idetix. See Section 3.2 for details.

1. If installing from the Web, follow the appropriate links to initiate the installer. If installing from a CD, insert the CD, mount the drive and run the file setup.bin from the CD drive. 2. Follow the on-screen prompts to complete the installation. See Section 3.2 for details. 3. When the prompt Where Would You Like to Install displays, browse for the desired location or click the NEXT button for the default location (/opt/revize). 4. Use any text editor to open the file /resin/conf/revize.xml (where is the Revize installation directory). Search or scroll down to the line: localhost Change the web server name to the actual name of your server machine.

5. If necessary, in the same file (revize.xml), just below the web server name attribute you may change the port of the web server that Revize uses (for example from the Revize default value of 8080 to the standard Web port of 80): 8080 Note: It is not necessary to change the value of the port used by Revize, but access to the Revize server must be through the port specified by this value, e.g., http://localhost:8080. 6. For Redhat Linux, use any text editor to open the file /resin/conf/resin.conf (where is the Revize installation directory). In the first few lines of this file, you should see a comment and a reference to the jikes compiler. Remove this reference before attempting to start Revize. (Jikes is used to compile jsp pages in Windows and some Unix environments but not in Linux) 7. To run Revize, browse to the directory where Revize is installed and click START_REVIZE.

4.2.2 Solaris 8/Redhat 6.2 Console Installation

Installation from a console environment assumes that the setup.bin file is available, either from the CD (located in the /INSTDATA/UNIX/LINUX directory) or downloaded from the Web.

Note: Unlike other Revize installation procedures, console installation does not provide an opportunity to choose an installation location. It automatically installs

into the default installation directory, which is /opt/revize. One way to address this issue is to create a /opt partition (if one does not already exist) and then create a soft link using the ln command to redirect the installation location. (For example ln -s /home/revize /opt/revize would allow console installation into the /home/revize directory.)

1. Browse to the directory where the setup.bin is located. (If installing from a CD, the setup file may need to be copied to a location where its properties can be updated.) 2. Make the setup.bin file executable by typing chmod a+x ./setup.bin 3. From the directory where the setup file is located, type ./setup.bin –i console to begin console installation. 4. After several minutes, the script output should indicate that installation is complete. 5. To run Revize as a background process, browse to the installation directory and type ./Start_Revize & at the command line.

4.2.3 Redhat Linux 7.2 (and later) Installation

To install Revize on Red Hat Linux 7.2 (and later), you may need to install a compatible Java Virtual Machine before installing Revize.

1. Download and install the updated Java Virtual Machine from the Web at:

java.sun.com/j2se/1.4.1/download.html

This JVM works with the new kernel in Redhat 7.2 (and later). Make sure to download the SDK version for Linux.

2. Set the PATH environment variable to point to the new installation of the JVM. This can be done by opening up the file /etc/profile and adding the following two lines to the top after the first set of comments. (Change the example path to the JVM binary to match the actual location, if you install Java in another directory.)

PATH=$PATH:/usr/java/jdk1.4.1_02/bin export PATH It should look something like the example below.

3. Set the LD_ASSUME_KERNEL variable. • Open a console window

• Type “LD_ASSUME_KERNEL=2.2.5” and hit Enter

4. You are now ready to begin the normal install process as described in Section 4.2.1.

5 INSTALLATION VERIFICATION

The installation of Revize can be verified by accessing the Administration Center and adding a resource.

This procedure is predicated upon several assumptions.

1. The Revize server has been configured as required using the Revize Administration Guide as a reference. 2. Your web browser meets the minimum browser requirements. 3. The Revize server is already running. 4. Revize security is turned off. This is the default setting in the Revize configuration. See the Revize Administration Guide for more information.

5.1 ADMINISTRATION CENTER

To make sure that the Admin Center is in proper communication with the Revize server, display the Admin Center and create a Resource.

1. Click START/PROGRAMS/REVIZE/ADMIN CENTER on a Windows machine, or type http://localhost:8080/revize/admincenter

into a browser window. (Replace localhost with the actual name of the server machine, and note that the http:// is not generally optional.)

2. Verify that the Revize login screen displays.

3. Log in using the default values login: root password: revize and click ENTER.

4. Choose the REVIZE WebSpace from the dropdown menu and click ENTER.

5. Once the list of Revize webSpaces appears, click RESOURCES on the top menu.

6. From the Resources interface, click CHANNELS on the side menu.

7. A list of available Channels should appear. This list may be empty.

8. Click the New button in the upper right corner of the Channels listing section. The Edit Screen for creating a new Channel displays.

9. Type test in the Channel Name, Description, and Location fields. (The values do not matter, since you will be deleting the Channel when you are finished.)

10. Click the Create button (you may have to scroll down to see it), which will write the Channel definition to the database. When the database is successfully updated, the list of Channels again displays indicating the Channel you just created.

11. Click the Delete button next to the Channel you just created. When you are asked if you are sure you want to delete the Channel, click OK. The list page redisplays without your Channel.

If all the above steps complete successfully, Revize is configured and operating correctly.

6 EXTERNAL WEB SERVER

Revize™ is an Out-of-the-Box solution for content management; however, it can be configured to use an external Web Server or Database. In this section we demonstrate the steps necessary to install Resin (the Revize Application Server) as a JSP/Servlet container for use by Microsoft IIS Web Server. Note - additional license fees may apply in this configuration.

6.1 RESIN ON IIS

In releases of Revize prior to 4.3, the IIS installation instructions required several folders to be moved under the IIS document root folder. This is no longer the recommended deployment of Revize to run under IIS. We now recommend you perform a Revize install and then create a virtual directory to the Revize web application.

6.2 NEW INSTALL OF REVIZE

If you are installing Revize for the first time please perform the following steps:

1. Install Revize Perform a normal Revize install.

2. Continue Configuration Please continue on to section 6.5.

6.3 MIGRATING TO NEW DEPLOYMENT

If Revize has been running under IIS utilizing the prior deployment recommendation of moving folders under the IIS document root AND you wish to preserve prior content, the following steps should be done after installing the new version of Revize:

1. Install Revize Perform a normal install, not an IIS install. There is an IIS upgrade to allow for existing users who do not wish to migrate to the new recommended deployment.

2. Stop the current Revize The next several steps require copying files to the new version of Revize. Stopping the current Revize ensures that the files will be copied safely.

3. Copy the current database from under the IIS document root to the new version of Revize In Windows Explorer open the directory

install>1\db\pointbase. Delete all the files in the directory - they will be replaced with your current Pointbase database files. In Windows Explorer open the directory C:\Inetpub\wwwroot\db\pointbase. Copy the “.wal” and “.dbn” files. Paste them into \db\pointbase directory.

4. Copy your WebSpace folders from under the IIS document root to the new version of Revize The webspace folders contain the Revize published pages, published reference files, and custom edit forms. In Windows Explorer open the C:\Inetpub\wwwroot\revize directory. For each WebSpace you have created in Revize there should be a corresponding directory. If, for example, you created a WebSpace with a label of “companyintranet” there will be a corresponding directory named “companyintranet” in the C:\Inetpub\wwwroot\revize directory. Copy all the WebSpace folders. You do not have to copy any folders or files other than the webspace folders (e.g. do not copy admincenter). Paste them into \www\revize.

5. Copy your repository files from under the IIS document root to the new version of Revize Whenever a file is uploaded to Revize the file is saved into folder in the web application named “repository”. Each WebSpace will have a folder under “repository” that contains all the reference

1 Replace with the directory you installed Revize in.

files in that WebSpace. The Repository is located at C:\Inetpub\wwwroot\revize\repository. Similar to what was described in step 2, there will be a folder under repository with the name of a corresponding WebSpace. In Windows Explorer open the C:\Inetpub\wwwroot\revize\repository directory. Copy all the WebSpace folders. Paste them into the \www\revize\repository folder.

6. Configure resin.conf The resin.conf should be configured after install to accept requests from IIS, but we will check to be sure. Open \resin\conf\resin.conf in a text editor such as notepad. Look for the following element:

If the element exists, Resin is configured correctly. If it does not, locate the following element:

On the next line, insert the “cluster” element. Resin may also be configured to listen to a port in order to handle http requests. Look for the following element:

If you find the element, it can be safely deleted. You don’t have to delete it. If you leave it, Resin will handle both http requests at the specified port and requests from IIS.

versions of Revize may introduce new elements in revize.xml it requires a manual migration of your settings from your current revize.xml under IIS to the new version of Revize. There are two ways to migrate revize.xml to the latest version. The first is to open the both versions of revize.xml and use copy and paste to move your settings into the new revize.xml. The second way would be to again open both versions of revize.xml, only in this case you would find any added elements to the new revize.xml and copy them into your current revize.xml. It should be noted that once you are running under the new deployment all future upgrades will migrate revize.xml automatically.

8. Copy isapi_srun.dll to scripts directory. The new version of Revize may contain a new version of Resin as well. To ensure the ISAPI mapping will function properly copy isapi_srun.dll from \resin\libexec to the Scripts directory under Inetpub. This requires IIS to be stopped. Do not restart IIS until step 9 is complete.

9. Configure resin.ini Depending on the version of Revize from which you are migrating, you may have to reconfigure resin.ini. Open the resin.ini file located in the Inetpub\Scripts directory. The file should contain the following:

ResinConfigServer localhost 6804 IISPriority high

If it doesn’t, replace all the existing lines with the lines above. Restart IIS.

10. Start Revize You can now start the new version of Revize. Please proceed to section 6.10.

11. Adjust channels to reflect new deployment Under the prior deployment, local Channel locations were typically pointing to “../revize/”. When migrating to the new deployment the local Channel locations need to be changed to “../www/revize/”. Making this change will cause a channel publish.

6.4 MIGRATING A CURRENT DEPLOYMENT TO RUN UNDER IIS

If you have been using Resin as the Revize Web Server and wish to utilize IIS as the web server please perform the following steps:

1. Upgrade Revize If necessary, upgrade Revize using the normal upgrade, not the IIS upgrade. There is an IIS upgrade to allow for existing users who do not wish to migrate to the new recommended deployment.

2. Configure resin.conf The resin.conf should be configured after the upgrade to accept requests from IIS, but we will check to be sure. Open \resin\conf\resin.conf in a text editor such as notepad. Look for the following element:

If the element exists, Resin is configured correctly. If it does not, locate the following element:

On the next line, insert the “cluster” element. Resin may also be configured to listen to a port in order to handle http requests. Look for the following element:

If you find the element, it can be safely deleted. You don’t have to delete it. If you leave it, Resin will handle both http requests at the specified port and requests from IIS.

6.5 INSTALL RESIN IIS DLL

1. If there is not a directory called scripts under C:\Inetpub create it.

2. There must be a virtual /scripts directory under your web site that points to C:\inetpub\scripts. If one does not exist create it.

3. Locate \resin\libexec\isapi_srun.dll and copy it into C:\inetpub\scripts

Copying isapi_srun.dll to inetpub/scripts directory is relatively straightforward. If you're upgrading to a new version of Resin, you may need to stop and start IIS (control panel/services) to get permission to overwrite isapi_srun.dll.

4. Create a resin.ini in C:\inetpub\scripts with the following content:

ResinConfigServer localhost 6804 IISPriority high

If you are overwriting an existing resin.ini file, you will need to stop and start IIS to be sure the updated configuration information will be used by IIS.

5. Open Internet Information Services from the Administrative Tools menu inside the windows control panel.

6. Right click on the folder called “scripts” under the Default Web Site. Then select properties; next select Scripts and Executables from the Execute Permissions drop down list. (see figure below)

7. Make sure the Resin application server works. Start Revize by opening Windows Explorer and navigating to \Revize and double clicking on “Start Revize”. You should see the following in the console:

Can't load JNI VFS library. java.lang.UnsatisfiedLinkError: no resin in java.library.path

#008999 -- 1 Resin server licensed to Idetix, Inc

Starting Resin on Tue, 01 Jun 2004 07:02:52 -0400 (EDT)

Revize by Idetix Software Systems, Version 4.2.4 (Build 88)

Workflow Services Enabled

8. Make sure the isapi_srun.dll is properly installed • Open browser and enter the following url: http://localhost/scripts/isapi_srun.dll/caucho-status

A window like the following should appear: Connect Live Dead Host Timeout Time Time 1. localhost:6804 (ok) 2 10 120 Host url-pattern * /resin/web-inf/* * /revize/*/ftpoperationservlet • • • * /revize/workflowwebservlet * /revize/web-inf/*

* *.jsp * *.xtp * /servlet/* * /web-inf/*

If you get an 404 error (page not found), either the DLL is not installed or the virtual directory is not configured correctly (scripts and execute permissions are required)

6.6 SET ISAPI FILTER VIA IIS MANAGER

1. Open up Internet Information Services from the Administrative Tools menu inside the windows control panel.

2. Highlight the Default Web Site or the one that equates to your Web Site and right-click it. Select Properties from the menu that pops up.

3. Start by selecting the ISAPI Filters tab and click the add button. Name the filter appropriately (e.g. Revize-Resin) and point it to the isapi_srun.dll file that was placed in the /scripts directory. Click the Apply button then click the OK button. (see screen shot figure 2.2.a below for reference)

Figure 2.2.a

4. While we are our viewing our Default Website Properties, we also want to take the time to set up the IIS server to recognize .jsp pages and allow them to run. To set this up follow the steps below:

a. Click on the Home Directory Tab (Shown in figure 2.2.a above)

b. Click on Configuration

c. On the screen that follows make sure that you are on the “Add Mappings” tab, and click on add. Add a mapping for .jsp files by clicking on Browse and going to C:\Inetpub\scripts\isapi_srun.dll. This directory script should show in the Executable area of the screen.

d. Attach the .jsp extension to this mapping by adding .jsp in the Extension area of the screen.

e. Select the Limit to: radio button under Verbs and add the following verbs: GET,HEAD,POST,TRACE

f. Click OK and OK again to get back to the Web Site Properties screen

5. The last item we want to address while in the Default Web Site Properties area is allowing other files to be used for a homepage other then default.htm, as IIS uses this for the default home page. Specifically we to be able to use index.html and index.jsp. To set this up follow the steps below.

a. While on the Default Web Site Properties area, click on the Documents tab and then add in index.jsp, and index.html file names to the list by clicking Add.

6. Test the IIS Filter:

Open web browser to following URL:

http:///script/caucho-status

Where is the IP or domain of the web site

12. A window like the following should appear: Connect Live Dead Host Timeout Time Time localhost:6804 (ok) 2 10 120 Host url-pattern * /resin/web-inf/* * /revize/*/ftpoperationservlet • • • * /revize/workflowwebservlet * /revize/web-inf/* * *.jsp * *.xtp * /servlet/* * /web-inf/*

6.7 WEB SERVICE EXTENSIONS - IIS 6.0

When using IIS 6.0 (windows 2003) a new Web Service extension for jsp pages needs to be added. Click on Web Service Extensions.

On the right-hand pane click on Add a new Web service extension…

Set Extension name to jsp, add isapi_srun.dll to Required files, and check Set extension status to Allowed as shown below:

Click OK. You should see the following in the right-hand pane:

6.8 CONFIGURING THE RESIN.CONF FILE

1. The resin.conf is located in \resin\conf. It should be configured after install to work properly with IIS. There are a couple of things to note in the file. Open the file in a text editor. It should look like the following:

index.html,index.htm,index.jsp

Of particular note are the following sections:

and

The “http” element configures Resin to accept http requests at the specified port. Because you are installing Revize to run under IIS you can safely remove that element.

The “cluster” element configures Resin to communicate with the dll you installed in a previous step. You’ll notice the port set in the “srun” element matches the port you set in the resin.ini file.

6.9 EDITING THE REVIZE.XML FILE

Because we have made some changes to the directory structure that is part of the normal installation of Revize, we need to update those changes in the revize.xml file that controls many of the components in Revize. The instructions below tell you what you will need to change. Some of these options are optional.

1. Scroll down till you see: localhost here you may need to change the server name to the actual server name of your machine 2. Next, just below the web server name attribute you will find the port of the web server that Revize uses: 8080. Here you want to change the port number from 8080 to the port that IIS is using - in this case 80.

6.10 CREATE REVIZE VIRTUAL DIRECTORY

In order for IIS to handle requests to the Revize web application a virtual directory needs to be created in IIS pointing to the revize directory. Perform the following steps:

1. Open IIS Administration. 2. Right click on the web site that will be using Revize.

3. Select New -> Virtual Directory.

4. Set the alias to revize.

5. Select the \www\revize directory.

6. Select the appropriate permissions.

Revize should now be configured to run under IIS.

6.11 TROUBLESHOOTING

The following troubleshooting information is from the Resin™ website on configuring Resin™ on IIS. You can find this information on the web at http://www.caucho.com/products/resin/ref/cse- iis.xtp#Configuring_IIS/PWS

1. First, check your configuration with the standalone httpd.sh. In other words, add a block and browse http://localhost:8080.

2. Check http://localhost/caucho-status. That will tell if the ISAPI filter/extension is properly installed. 3. Each srun host should be green and the mappings should match your resin.conf. 4. If caucho-status fails entirely, the problem is in the isapi_srun installation. Try http://localhost/scripts/isapi_srun.dll/caucho- status directly (bypassing the filter). If this fails, IIS can't find isapi_srun.dll. o Check that isapi_srun.dll is in c:\inetpub\scripts. o Make sure that your IIS host has a mapping from /scripts to c:\inetpub\scripts and that the /scripts has execute permissions. 5. If you've created a new IIS web site, you need to create a virtual directory /scripts pointing to the c:\inetpub\scripts directory. 6. If caucho-status shows the wrong mappings, there's something wrong with the resin.conf. 7. If caucho-status shows a red servlet runner, then httpd.exe hasn't properly started. 8. If you get a "cannot connect to servlet engine", caucho-status will show red, and httpd.exe hasn't started properly. 9. If httpd.exe doesn't start properly, you should look at the logs in resin/log. You should start httpd.exe -verbose to get more information. 10. If you get Resin's file not found, the IIS configuration is good but the resin.conf probably points to the wrong directories. The caucho-status screen should look like the figure below if everything is set up correctly. (The localhost part may be the name of your server and that would be OK.) If the screen

below looks like your screen then you are ready to go. If not, you will need to review the above steps in the troubleshooting section and double- check your configuration. If there are additional issues, please call Idetix Software Systems Technical Support.

7 EXTERNAL DATABASE

Revize™ is an Out-of-the-Box solution for content management, however, it can be configured to use an external Web Server or Database.

Connecting to Oracle

In this section we demonstrate the steps necessary to use Oracle as an external database.

1) Create a new database in Oracle

2) Create a new tablespace. The sql command to create a tablespace is

“create tablespace datafile ‘’ size ” example: create tablespace idetix datafile ‘revize’ size 100M;

3) create a user in the same name as the name of the tablespace that was created in step 2.

The sql command to create a user

create user identified by default tablespace temporary tablespace temp example: create user idetix identified by idetix default tablespace idetix temporary tablespace idetix;

4) Grant necessary permission to the newly crated user. The typical sql command to grant permissions are grant create table to grant create sequence to grant create view to grant create session to

5) In \resin\conf\revize.xml file, under db section, comment out pointbase and uncomment Oracle section

6) In revize.xml, under Oracle section, put the proper database url,user name and password. The user name and password should be same as created in steps 3.

7) Save the revize.xml file

8) Under /bin directory, run the resetdb batch/shell script. This will create all the necessary tables for Revize

9) Start Revize Server.

Connecting to Microsoft SQL Server

In this section we demonstrate the steps necessary to use Microsoft SQL server as an external database.

1) In \resin\conf\revize.xml file, under db section, comment out pointbase and uncomment MS-SQL section

2) In revize.xml, under MS-SQL->version section, put the proper version (the default is set to 2000, currently both 7.0 and 2000 are supported).

3) In revize.xml, under MS-SQL->url section, change "INNOVATION" to

4) Go to Program Files\Microsoft SQL Server\Enterprise Manager

Go to "Databases" under the MS-SQL Server Name and right click and click on "New Database" Name the new database whatever you want (eg named REVIZE)

5) Go to "Security" under the MS-SQL Server Name and create a login named “revize” with password (e.g., “root”)

Click on "Server Roles" and check "System Administrators".

6) Go to "Databases" and click on the new database that was created. Right click on the users and click on "New Database User". In the dropdown choose the login that you created and check "Public" under "Database Role Membership". Please see the screen shot

MS-SQL Setup should be fully configured now.

The database now needs to be initialized for use with Revize. A tool in the bin directory of the Revize installation directory will create the necessary tables and records. If you are utilizing a web server other than resin, any changes made to the revize.xml file need to be reflected in the /resin/conf/revize.xml file in the revize installation directory.

Run resetdb command from bin directory

Then start REVIZE and it should be ready to run

8 REVIZE GLOSSARY OF TERMS

Admin Center: A set of web pages, viewable in a web browser, which provide ability to interface with the Revize Web Application.

Administrator: The manager of Revize Resources with the ability to grant access permissions.

API (Application Program Interface): The language of communication between an operating system or control program and an application program.

ASP (Application Service Provider): An organization that provides access to software applications, housed within its own facilities by way of the Internet or private phone lines.

Authenticate: Verify the identity of a computer user by validating username or username and password.

Channel: The path that defines how and where Revize- managed pages are published. This could be a file system, FTP, etc.

Concurrency: The Revize safeguard that does not allow two Users to update the same Record at the same time. Administrators or Superusers can unlock this feature.

Content Editor: See Editor

Developer: The individual who designs the Templates that determine how a web page or a web site will look and function (also a web developer or web designer).

Developer’s Tool: License for a single-user, single- machine use of the Revize Web Application, along with an application that allows Developers to build, test, and package Revize WebSpaces and components such as Modules, Templates, and Channels all on one machine. These WebSpaces, or any of the individual Resources, can then be exported.

Dynamic Web Pages: Web pages that must be processed by a web server every time they are requested for viewing.

Editable Content: Web page information entries that can be changed or updated. With Revize, this information is represented by Records and structured by Revize Modules.

Editor: A person authorized to change or update content on a web site using Revize Template Edit Pages that have previously been formatted by a Revize Developer. The Editor could also be called a “Business Content Expert” because the Editor is a person with pertinent information who can, through Revize, publish that information on a web site (sometimes referred to as a content editor).

Field: An area in a Record that is always used to record the same type of data (i.e. name, amount, price, etc.) A collection of fields is organized together to make up a Record, and a group of Records combine to form a Module.

Group-Level Permissions: Access to read or write within a system only when proper authentication is given (i.e. password and log-in information). Usually, an entire group of people has access to the same data. Access is denied if any part of the authentication process is incorrect.

ISP (Internet Service Provider): An organization providing Internet access.

JavaScript: A standard scripting language typically used to validate form input on web-based clients. JavaScript can also be used to produce dynamic web content from a web server in a Java Server Page, or JSP. The Revize Admin Center was developed using JSP.

JDBC (Java Data Base Connectivity): A programming interface that allows Java applications access to a database via SQL language.

JNDI (Java Naming Directory Interface): A programming interface (API) for connecting Java programs to naming and directory services such as DNS, LDAP and NDS. The application is written to the JNDI API, and the directory drivers are written to the JNDI SPI (Service Provider Interface).

Link: An indicator programmed into a record that enables easy location of and access to data in another record.

LDAP (Lightweight Directory Access Protocol): A set of definitions of users and organizational units, with the attributes of each. These definitions are based on company or industry-produced standards.

Module: The collection of Records into units for use in web information, acting much like a table in a database. In Revize, these Modules are created by Developers or Administrators, and can hold any set of information (i.e. names, telephone numbers, departmental data, etc.).

Profiling: A type of analysis, particularly applied to a Template and the information that Template references in the Revize system. This allows for data storage to be referenced later.

Publish: Combining of a Template (as designed by a Developer) and content (as edited by an Editor) into a final web page. Revize does the work of synthesizing the two.

Publishing Engine: Revize’s sub-system that “Publishes” pages as they are updated.

Record: A collection of fields. By organizing these fields into a group (Record), they are ready for use on a web site.

Reference File: Any image, PDF file, Word document, or other file that can be utilized by Revize.

Re-purposed: A web site that has been updated to allow the Revize system to manage the content.

Resources: Objects or data that can be accessed or changed by a Developer or Administrator.

Snippet: Advanced JSP or Java code that can be cut and pasted into a web page.

SNMP (Simple Network Management Protocol): A method for a system to send a status report to an Administrator, and for that Administrator to control and make changes in the system based on a set of company standards.

Static Web Pages: Web pages that a web server can process immediately when requested. See also Dynamic Web Pages.

Superuser: The installer of Revize software onto the company network. The Superuser is usually a member of the corporate IT department.

Tag Library: A collection of tags (similar to HTML tags) that allow access to editable content in Revize Templates, allowing for the editing of the static portions of a web page.

Template: The Resource that sets up and controls how a web page will look once the content has been edited and added.

URI: (Uniform Resource Identifier)

URL: (Uniform Resource Locator) A complete description of an item, containing the location of the item (often entered in the address bar of a web server).

Username: The name or identification of a system user that allows the system to give or deny access.

Web Application Installation: A fully licensed installation for running Revize.

WebSpace: A collection of all of the Revize Resources for a particular web site.

Workflow: A system of checks and balances. The Superuser appoints a Workflow Developer who sets up the list of Users content must flow through before being published to the finished web page.

Workflow Developer: The person responsible for setting the Workflow structure.

XML (eXtensible Markup Language): A standards- based, flexible text based language. Revize uses XML for its network communications (such that external systems may control Revize) and in some configurations.