Installation requires Maven, with some additional plugins. We will assume that MAV_HOME is the directory that contains the maven installationd and the plugins subdirectory and MAVEN_REPO contains the Maven repository, usually $HOME/.maven/repository on Unix machines.
maven -DartifactId=maven-torque-plugin -DgroupId=torque -Dversion=3.1.1-dev plugin:download(on one line) to install the torque plugin.
Blogentis needs a database, and it comes configured to use HSQL, an embedded database written in Java. Using HSQL is not recommended for production use, but it is very easy to set up.
To use HSQLDB, modify
to the correct path of your blogentis installation.
Blogentis will need a database, either PostgreSQL or MySQL is fine. You will need to create the database so that tomcat has full permissions on that database, and you will need to note the database name, user and password for later use.
Specifically, you will need to edit the following files, and replace some values by the user that will access the database,
the password that identifies the user, the JDBC Driver, which is
org.postgres.Driver for postgres and
com.mysql.Driver for MySQL, the JDBC Connection URL, whic
torque.database.blogentis.adapterto the save value as above, and set all properties under
torque.dsfactory.blogentis.connectionto their apropriate values.
torque.databaseto their appropriate values, with buildUrl and createUrl set to the JDBC Connection string. Also set
torque.databaseto postgres or mysql depending on your database server.
The Slide WebDAV server will need to be configured and point to a directory on the filesystem where the
user Tomcat is running as has write access. You will need to change the
workpath of the stores (XPath /slide/namespace/definition/store/(nodestore|contentstore)/parameter)
to point (using absolute pathnames) to that directory.
Blogentis can be set up so that it pulls user account information from an LDAP directory. This is useful if you already use LDAP for user authentication and wish to give the users access to blogentis. Please note that at the tme of writing, this options incurs a slight performance penalty; it also is not recommended for security-concious servers, as the same password for user authentication is used to authenticate with Basic HTTP authentication, which isn't secure.
To enable LDAP access, edit the
WEB-INF/conf/TurbineResources.properties file and locate the
properties and modify them according to the comments of the file. Also change all
services.SecurityService.ldap.user to values that reflect your LDAP schema;
the defaults have been set for UNIX accounts, they may or may not work with your schema.
You will need to set
services.SecurityService.ldap.admin to an bindable object on your server,
but it need not be the admin account. If it is not the admin account, the users wiil not be able to store
personal preferences on the LDAP server.