Document Actions
2.
Installation Instructions
Up one level
The OpenEngagement DMS server has an installer for Windows platforms, which may be downloaded at any time from the OpenEngagement web site, http://www.openengagement.com. Look under Products, DMS, Downloads.
The installation process first installs Zope and Plone (web application platforms on which the CMS runs) and will then install the OpenEngagement CMS, which will include the DMS and KMS.
IIS
It is not recommended that IIS run on the same server as the OpenEngagement DMS. Most Windows operating systems do not include IIS and those that do generally do not enable IIS by default. However, users should check that IIS is not installed and should remove it if necessary, using the Control Panel’s Add or Remove Programs. In this dialog, users may select the Add/Remove Windows Components button, and then remove Internet Information Services. If users do wish to run IIS and the OpenEngagement DMS on the same server, they must configure one to use a different port, as both use port 80 by default.
Port 80
As well as IIS, the server should have no other applications using port 8080 or 80, the ports used by default for Zope and HTTP respectively. To determine there are no other applications using these ports, a useful utility is TCPView, which is a freeware application available at www.sysinternals.com.
Restarting Windows
The installation process must restart Windows. Once restarted, the CMS server will be running and users can launch a web browser to access it.
Launching the OpenEngagement CMS
The OpenEngagement CMS is installed as a Windows service and should be running whenever the computer on which it is installed is running unless it is specifically stopped. To check the service is running, you may go to the Control Panel, Administrative Tools, Services, and check the status of the Zope service, and start it if necessary.
Accessing the OpenEngagement CMS Through a Web Browser
The OpenEngagement CMS may be accessed through a web browser, through the Quick Upload or through the Go-between. The URL will be: http://localhost/CMS. The DMS often takes a couple minutes to start up. You may wish to save this URL in your favourites. To use a web browser on the same computer on which the OpenEngagement is installed, you may always use this URL. To access it from other computers, you must specify the name of the computer in the URL. For example, if the computer is named Jupiter, you would specify: http://Jupiter/CMS.
Accessing the OpenEngagement CMS Through the Go-Between
The Go-Between is very tightly integrated with Working Papers, and will actually run inside your Working Papers application window, appearing as a series of menu items. The first steps are to install the Go-Between and then to configure Working Papers to work with the OpenEngagement DMS (The Go-Between does not interact with the KMS). This is generally a one-time operation, though users may change the settings for the OpenEngagement CMS from time to time. Configuration is done by going to Tools | Options | DMS and specifying OpenEngagement CMS as the current CMS, then hitting the Configure button. This brings up the configuration dialog where users specify the settings of OpenEngagement CMS. Unless you've changed the settings of the OpenEngagement CMS you should be able to use the default settings of 80 and blank for the Port and Path fields respectively. For the Server, you should set this to the same path as you use in a web browser, omitting the http:// portion. Once this is done, you will be able to access the Go-between through the Open from OpenEngagement and Save to OpenEngagement menu items.
Usernames and Passwords
Once your OpenEngagement server instance has been installed, likely your first task will be to create user accounts for the initial users of the system; later, additional users may be added or deleted as necessary at any time. You may assign some users site-wide roles, but most will likely be given only the Member role and assigned further roles locally.
The same set of usernames and passwords are used in the web browser interface, Quick Upload, and Go-between.
The installer will create two user accounts, one with user id admin and password admin, the other with user id script and password script. The admin user account should be used to create additional user accounts. Once these additional accounts are tested, the password for the admin account should be changed. The password for the script user account should also be changed. Doing this is described later in this documentation.
Setting Up Your OpenEngagement CMS Instance
Once the initial set of users is created, you will then create one or more Areas, as well as Entities and possibly Sections to organize your site. These tasks cannot be done through the Go-Between and must be done through a web browser or through Quick Upload. Within Areas you may create Entities and, optionally, sub-Areas or Sections. Within Entities, you may create Sections and, optionally, sub-Entities. Within Sections, you may create Engagement, Page, File, Link and Image objects. Engagement objects are intended to store compressed CaseWare client files. Once the general structure of your site has been created, and the initial content has been created, you should assign users local roles, so they may begin using the system and/or themselves assigning further users additional local roles. Firms may define the set of Sections that are created automatically within each Entity. Assuming a firm wishes to have the same set of Sections in each Entity, users should never need to explicitly create or delete Sections.
Email Server
Likely the most difficult step related to installing the OpenEngagement DMS is configuring the email server. This is done under Mail Settings, which is accessible from the Preferences link or using the URL, http://localhost/CMS/prefs_mailhost_form. Users should also define the site administrator email. This is done in the Portal Settings page, also accessible from the Preferences link, in the Site 'From' Address field. This may be tested by navigating to the contact page and sending an email. Ensure that the site administrator does receive this email.
For all sites, the following information must be provided before mailing will work:
- Portal Settings must contain a valid "From:" email address
- Mail Settings must contain the correct mail server and port.
- Any users wishing to contact the site must also have a valid e-mail addresses. Note, the admin user account does not have an associated email account, and so cannot send or receive email.
Firms may install an SMTP (email) server on the same computer where the DMS is installed, or may specify an already existing SMTP server elsewhere on the network.
Scheduled Tasks
The OpenEngagement DMS uses a number of scheduled tasks, which will be set up by the installer. To check these are created properly, users can go to the Scheduled Tasks dialog in the Control Panel. There should be four scheduled tasks installed by OpenEngagement. These should each run every day overnight and should create a log file in the bin directory called script.log.