Dashboard > Hippo CMS > Hippo Community Apps > Community apps CMS configuration (general)
Community apps CMS configuration (general)
Added by Jasha Joachimsthal, last edited by Mathijs Brand on Jul 22, 2008  (view change)
Labels: 


This page describes the minimal setup for your Hippo CMS project. For the various parts of the Hippo Community Apps or the use of other databases than MySQL additional settings may be required.

Hippo Cocoon Plugin version 2.01.00 or higher is required

  1. Create a new eclipse project
  2. Add the editor folder from latest Hippo CMS tag to svn:externals. Name it editor.
  3. Add the folder cms-hcamanager from the latest tag of Hippo Community apps to svn:externals. Name it hcamanager. Note that Oracle users need the Oracle specific tag.
  4. Do an svn update to retrieve the code.
  5. Add a file common-project.xml in your project root with the following structure:
    <project>
      <extend>hcamanager/project.xml</extend>
    </project>
  6. Create a file build.properties in the editor folder and add the following properties
    1. for MySQL:
      hca.jdbc.driverClassName=com.mysql.jdbc.Driver
      hca.jdbc.url=jdbc:mysql://localhost/default
      hca.jdbc.username=username
      hca.jdbc.password=password
    2. For Oracle:
      hca.jdbc.driverClassName = oracle.jdbc.driver.OracleDriver
      hca.jdbc.url = jdbc:oracle:thin:@localhost:1521:TEST
      hca.jdbc.username=USERNAME
      hca.jdbc.password=PASSWORD
      # Schema creation
      hca.jpox.autocreatetables=false
      hca.jpox.autocreateschema=false
      hca.jpox.autocreatecolumns=false
      hca.jpox.autocreateconstraints=false
      # Validataion
      hca.jpox.validateTables=true
      hca.jpox.validateColumns=false
      hca.jpox.validateConstraints=false

      Note: use the oracle.sql file from your release to create the necessary tables.

  7. Override hca.uniquehost in your build.properties file if the result of ${maven.cocoon.site.domain}:${jetty.port} exceeds 32 characters. The default value localhost:50000 is short enough.
    It can have any short value that identifies this installation in a unique way.
  8. Build the CMS from the project root folder with
    maven -d editor cocoon:deploy
  9. Create dashboard configuration
    1. Customize dashboard : follow steps 1-4
    2. Add the following views. 
      <!-- mailing-profiles: newsletter manager and e-Alerts manager -->
      <view src="hcamanager://perspectives/dashboard/views/mailing-profiles/component.xml"/>
      <!-- mailgroups: newsletter manager, added in version 2.01.00 -->
      <view src="hcamanager://perspectives/dashboard/views/mailgroups/component.xml"/>
      <!-- newslettertypes (templates): newsletter manager -->
      <view src="hcamanager://perspectives/dashboard/views/newslettertypes/component.xml"/>
      <!-- mailings: newsletter manager -->
      <view src="hcamanager://perspectives/dashboard/views/mailings/component.xml"/>
      <!-- poll: poll manager, added in version 2.01.00 -->
      <view src="hcamanager://perspectives/dashboard/views/poll/component.xml"/>
      <!-- notifier: e-Alerts manager, added in version 2.02.00 -->
      <view src="hcamanager://perspectives/dashboard/views/notifier/component.xml"/>


      We strongly advise to hide these buttons for most users. Otherwise cms users will be overloaded with buttons they don't understand or use.

    3. When getting an error check: http://<cms>:<port>/workbench/repository-configuration/perspectives/dashboard

Secure connection (https)

If https is used as protocol for Hippo CMS, add an extra RequestHeader to the Apache SSL config:

 RequestHeader add X-Forwarded-Protocol "https"

Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.7 Build:#813 Aug 28, 2007) - Bug/feature request - Contact Administrators