DBPrism - 2.1.0 - Install Instructions ::-

Requeriments to install DBPrism / Cocoon CMS 2.1

DBPrism CMS 2.1 is very straigforwd installation because they use Ant for all the installation and configuration steps

Here the list of required/tested software

Build tool - Apache Ant 1.6.2+ with FTP extension required libraries
Oracle Client RSF files, minimum release tested 9.2.0.3+.
Oracle Database 10g with patchset to 10.1.0.3+ or 10.2.0.1+.
DBPrism CMS Cocoon 2.0 libraries.
DBPrism 2.1 CMS .
Oracle Application Server Containers for J2EE (Pure Java) or Tomcat 5 , but it will work with any container where Cocoon 2.0 run.
Sun JDK 1.4.2+

Database Server Installation - Pre-Install setup (run only once)

This step is required to be executed only once time. It install DBPrism Toolkit for Java and JTidy library required for DBPrism CMS.

To perform this step change to DBPrism CMS 2.1 distribution directory and execute:

ant pre-install

The script will install on SYS schema DBPrism Java Toolkit and JTidy library and granting execute privilege to PUBLIC, to perform this operation Ant will use dba_user and dba_pass constants of common.xml file.

Database Server Installation - Initial Setup

This is the mainly step of DBPrism CMS 2.1 installation. It will create two database users, once is used for storing the CMS code (Java and PLSQL) the other one is used for the CMS Tables and triggers.

Execute ant with this argument to perform this step:

ant install-cms

The database user created at this point is cms.owner.user and cms.admin.user, see common.xml file for more details, and check these parameters after the install step running ant without arguments.

Before installing the CMS please check that the database is listening on port 2100 (ftp), If not execute logged as SYS this command dbms_xdb.setFtpPort(2100) and dbms_xdb.setHttpPort(8080).

Database Server Installation - Create CMS Users for your Web Site.

This step could be either upload DBPrism Project Web Site or upload a Demo Web Site

You can check the directory sites/ into DBPrism CMS distribution to check the content to be uploaded

Since DBPrism CMS 2.1, the content of the Web Site could be uploaded using FTP or WebDAV protocols, the Ant install Script will use FTP.

You can check sites/[www.dbprism.com.ar|www.my.company.com]/cms directory to see the complete list of files to be uploaded, also you can see the build.xml files located into each sites directories for the targets: dbprism-web-install and demo-web-install

Excecute these steps:

cd sites/www.dbprism.com.ar/
ant add-cms-user
ant dbprism-web-install

or:

cd sites/www.mycompany.com/
ant add-cms-user
ant demo-web-install

This task also will populate some tables of DBPrism CMS, adding RSS Channels and MoreOver ^TM News test channels.

Also will start two DBMS Scheduler Jobs which download the content of the RSS and MoreOver default channels. This content is downloaded directly from the web using HTTP.

Last operation of this task is update-webdav-metadata , this task provide an useful operation for creating jump start web sites from XML files stored on disk, it use document/header/title values for updating WebDAV DisplayName property of the CMS Pages, and document/header/title value of the index.xml file located on the directories for updating DisplayName properties of the CMS directories.

Web Server Deployment

Finally this step will create and deploy DBPrism CMS application files. Execute:

ant deploy-app
ant deploy-web

for deploying into an OC4J running according to the parameters of common.xml (Container settings OC4J).

For Tomcat or any other Web Server distributions you can execute:

ant cms-ear

A dbprism or demo ear/war files will be created into deploy/ directory, so you can manually copy these ready to use files to the webapp directory of Tomcat. Before this step check for the values of build.xml, such as project.[web|app], project.base.[web|live] and project.site because they affect prism.xconf, cocoon.xconf, web.xml and other related files.

You can test the above step trying this url: http://server:port/dbprism/status or http://server:port/demo/status

Once the application is deployed into the specific container, you need to put the public and live directories of DBPrism CMS. Public directory means a directory for read only pages. In the other hand Live directory is used by the content authors or webmasters to create/delete/update pages/directories publish the content and so on. Execute this Ant task to create these Web Server resources directories:

cd sites/www.dbprism.com.ar/
ant dbprism-doc-ldoc-app
cd $J2EE_HOME/applications/dbprism/dbprism
unzip $CMS_HOME/deploy/dbprism-doc-app.zip
unzip $CMS_HOME/deploy/dbprism-ldoc-app.zip

or:

cd sites/www.mycompany.com/
ant demo-doc-app
cd $J2EE_HOME/applications/demo/demo
unzip $CMS_HOME/deploy/demo-doc-app.zip

The above steps will create into deploy/ directory files with .zip extension including all the Web Server resources ready to copy into application deployment directory. The unzip steps are examples of OC4J applications server deployment task for the doc|ldoc directories.

Cocoon support sub sitemap extensions, then you only need to deploy one time the war/ear file, the other sub sequent task will be unzip sub directories directly into the deployment directory, for example: applications/dbprism/dbprism directory in case of you are installing DBPrism CMS on an OC4J container.

If the above steps are correctly performed you will get your DBPrism CMS up and running on the urls: http://server:port/[dbprism|demo]/[doc|ldoc] for the public and live areas. Enjoy DBPrism CMS!!!.

Usually DBPrism CMS is deployed using Apache mod_proxy functionality. It means that you will configure mod_proxy using something like this:

<VirtualHost *>
    ServerAdmin webmaster@dbprism.com.ar
    ServerName demo.dbprism.com.ar
    ErrorLog logs/demo.dbprism.com.ar_error_log
    CustomLog logs/demo.dbprism.com.ar_log combined
    <IfModule mod_proxy.c>
      ProxyRequests Off
      ProxyPreserveHost On
      ProxyPass         / http://localhost:8888/demo/doc/
      ProxyPassReverse  / http://localhost:8888/demo/doc/
    </IfModule>
</VirtualHost>

This mod_proxy directive combined with virtual host support will route every request like this http://demo.dbprism.com.ar/ to the webserver deployment site demo and the sub sitemap doc.

This work is licensed under a Creative Commons License .