DBPrism Servlet Engine
Config file used by Ant Scripts during the installation off DBPrism CMS

The XML code below shows common.xml file of DBPrism CMS distribution. This file is used during the installation steps of DBPrism CMS. It defines several constants for creating databases users, choosing the target database, and so on. These constants will be showed in detail below.

<?xml version="1.0" encoding="iso-8859-1"?>

    <!-- $Id: CMS-Config.xml,v 1.1 2005/11/23 10:24:06 mochoa Exp $ -->
    <!--
      Database setting.
      Check it, if you want to use Ant's task for uploading database
      resources such as Toolkits, Demos and so on.
    -->
    <!-- SQLNet connect string of the target database used during
         the installation steps 
         -->
    <property name="database" value="devel"/>
    
    <!-- Directory for logging during the installation steps
         and for DBPrism log -->
    <property name="log" value="/tmp"/>

    <!-- Database DBA username and password -->
    <property name="dba_user" value="sys"/>
    <property name="dba_pass" value="change_install"/>

    <!-- Database username and password used with DBPrism/Cocoon demos -->
    <property name="user" value="scott"/>
    <property name="pass" value="tiger"/>

    <!-- Database Schema used for storing CMS code -->
    <property name="cms.owner.user" value="CMS_CODE"/>
    <property name="cms.owner.pass" value="CMS_CODE"/>

    <!-- Database Schema used for CMS primary user (owner of the cms_docs table) -->
    <property name="cms.admin.user" value="CMS_DATA"/>
    <property name="cms.admin.pass" value="CMS_DATA"/>

    <!-- Database username and password used to create extra CMS user
         change it and execute ant add-cms-user for adding new user to the CMS -->
    <property name="cms.rep.user" value="DBRPISM_ADMIN"/>
    <property name="cms.rep.pass" value="DBPRISM_ADMIN"/>

    <!-- Set it with your proxy values, if you don't have proxy set it to null -->
    <property name="proxy.host" value="null" />
    <property name="proxy.port" value="null" />

    <!-- 
        information used during the deployment time (war/ear) packaging) 
        -->

    <!-- Host,port,SID of the target database used at runtime -->
    <property name="db.host"  value="reptil"/>
    <property name="db.port"  value="1521"/>
    <property name="db.sid"   value="devel"/>
    
    <property name="thin_string" value="${db.host}:${db.port}:${db.sid}"/>
    <property name="jdbc_string" value="jdbc:oracle:thin:@${thin_string}"/>

    <!-- Database username and password used to connect from DBPrism/Cocoon war -->
    <property name="cms.web.user" value="DBPRISM_ADMIN"/>
    <property name="cms.web.pass" value="DBPRISM_ADMIN"/>

    <!-- username and password using to validate ESI invalidation messages -->
    <property name="cms.esi.user" value="invalidator"/>
    <property name="cms.esi.pass" value="invalidator"/>

    <!--
      Container settings (WebServer).
      Check it, if you want to upload DBPrism / Cocoon2 CMS zone into OC4J.
    -->
    <property name="web.host" value="coral"/>
    <property name="web.port" value="8888"/>
    <property name="admin.port" value="23791"/>
    <property name="admin.user" value="admin"/>
    <property name="admin.pass" value="admin"/>

    <!-- Values used for configuring war/ear files -->
    <property name="project.web" value="dbprism" />
    <property name="project.app" value="dbprism" />
    
    <!-- absolute urls used in your web site, if you are behind a mod_proxy
         change it the absolute url published through mod_proxy -->
    <property name="project.base.web" value="/" />
    <property name="project.base.live" value="/" />
    
    <!-- Directory with resources includes into the WAR file -->
    <property name="frontend.dir" value="sites/frontend/web" />
    <property name="resource.dir" value="sites/www.dbprism.com.ar/web" />

    <!--
      Environment setting (Paths).
      Check it, if you want to compile DBPrism code.
    -->
    <property name="env" environment="env" value="env"/>
    <!-- Where OC4J is installed (oc4j.jar file location) -->
    <property name="J2EE_HOME" value="C:\Archivos de programa\JDev10g\j2ee\home"/>
    <!-- Java 1.2+ installation directory resolved by environment setting -->
    <property name="JAVA_HOME" value="${env.JAVA_HOME}"/>
    <!-- ORACLE_HOME resolved by environment setting -->
    <property name="ORACLE_HOME" value="${env.ORACLE_HOME}"/>
    <property name="COCOON_WEBAPP" value="./dbprism"/>

    <!--
      Project setting. Do not edit this, only for DBPrism CMS developers.
    -->
    <property name="project.name" value="cms" />
    <property name="project.version" value="2.1.0-production" />
    <property name="project.dist" value="${project.name}-${project.version}" />
    <property name="project.package.prefix" value="com.prism.cms" />
    <property name="project.package.dir" value="com/prism/cms" />

    <!--
      Developer's user id, used to access to the CVS at SourceForge.
    -->
    <property name="project.dev" value="mochoa" />

    <target name="message">
          <echo message="BuildName: ${project.dist}" />
          <echo message="BuildHome: ${basedir}" />
          <echo message="BuildFile: ${ant.file}" />
          <echo message="BuildJVM: ${ant.java.version}" />
    </target>


    <!-- system properties -->
    <property name="slash" value="${file.separator}" />

    <!-- Path to Secure Shell (/usr/bin/ssh|C:\cygwin\bin\ssh.exe) -->
    <property name="ssh" value="/usr/bin/ssh" />
Database constants

This table summarize the constants of common.xml file used to define the target database of the installation script. Also will affect some SQL Scripts which are automatically changed according to your installation setup, for example your proxy host/port will be inserted as rows of the CMS defaults table.

database constants
NameExample valueExplanation
databasedevelSQLNet connect string used by SQLPlus or loadjava operations during the installation steps
dba_user/dba_passsys/change_on_installDatabase user with DBA privileges used to create CMS users for example
user/passscott/tigerDatabase username and password for DBPrism/Cocoon demos
cms.owner.user/cms.owner.passCMS_CODE/CMS_CODEDatabase username and password who is the owner of the CMS code.
cms.admin.user/cms.admin.passCMS_DATA/CMS_DATADatabase user who is the owner of the cms_docs table (see CMS Tables for more details)
cms.rep.user/cms.rep.passDBPRISM_ADMIN/DBPRISM_ADMINUsername and password used to create a new CMS user by the Ant task add-cms-user, see Ant Scripts page for more detail.
proxy.host/proxy.portproxy/8080Host/Port used by the CMS to query the web. Remember to use dbms_java.grant_permission (connect,resource) to cms_code/cms_data to this host due its necessary for executing UploadNews and UploadRss jobs.
The above database users must be in upper case since they are used in some path information that are case sensitive
Container specific constants

These values are using when you make the WAR/EAR files, so they will be using at the runtime, many of these constants affects configurations files which are automatically edited by Ant, for example cms.web.[user/pass] will be stored in prism.xconf file and used when DBPrism connects to the database.

Constant used during deployment activities
NameExample valueExplanation
db.host/db.port/db.sidreptil/1521/develTarget Database where DBPrism CMS is running, these values are used to create a JDBC thin connection string.
cms.web.user/cms.web.passCMS_DATA/CMS_DATADatabase username and password used by the container where the CMS is running to execute the code, this username and password do not necessary be equal to the CMS Admin User because it only needs permissions to see /public/CMS_DATA WebDAV folder and execute some stored procedures such as CMSj.sitemap, CMSj.header and so on.
cms.esi.user/cms.esi.passinvalidator/invalidatorUsername and password used by invalidate.xsp page to authorize ESI invalidation messages.
For security reason on productions web sites this username and password must be changed to other values and re-execute cache-sync and deploy-app Ant tasks to update with a secure value.
web.host/web.portlocalhost/8888Hostname and port where Cocoon is running.
admin.port/admin.user/admin.pass23791/admin/adminFor OC4J only, these values are used by oc4j Ant task to deploy EAR/WAR files.
project.web/project.appdbprism/dbprismValues used by the deploy tool to create the EAR file (${project.app}.ear) and publish this application on the web (http://${web.host}:${web.port}/${project.web}/)
project.base.web/project.base.live"/dbprism/doc/" "/dbprism/ldoc/"Absolute path for accessing to the web resources, such as images, static html, and so on. If you are using DNS with mod_proxy to publish DBPrism CMS public and live sites, these values will be "/", then a .js file will be retrieved as http://www.mydomain.com/js/tree.js on the public web site, and http://live.mydomain.com/js/tree.js on the Content Authors web site.
frontend.dirsites/frontend/webDirectory which contains static resources of DBPrism CMS FrontEnd application, unless you have a new FrontEnd application this constant will never change.
resource.dirsites/www.dbprism.com.ar/webDirectory with static resources of your web site, this constant is useful for building customized war/ear bundles with the static resources (images, static html files, stylesheets, etc.) that your web site needs.
Enviroment settings

Constants used to locate executable files such as SQLPlus for example.

These values defines some path to downloaded software
NameExample valueExplanation
J2EE_HOME/usr/local/JDev10g/j2ee/homeDirectory where OC4J is unpacked, if you are using OC4J distribution embebed into Oracle JDeveloper 10g it is under the directory j2ee/home of your JDeveloper Home. This directory must be contain admin.jar file which is used by the Ant task oc4j-deploy. For building dbprism.war file, this constant its not required.
JAVA_HOME${env.JAVA_HOME}This constant usually is resolved using the environment setting JAVA_HOME, if this variable is not properly configured change the value here.
ORACLE_HOME${env.ORACLE_HOME}Oracle Home with an Oracle Client Required Support Files (RSF), DBPrism CMS 2.1 was successful tested with Oracle 9.2+ clients files (SQLPlus, loadjava, etc.) either in Linux, Solaris and Windows. Be sure that your ORACLE_HOME environment variable is properly configured because it affects not only DBPrism installation script, it will be used also to locate your tnsnames.ora file for example.
This will not be equals to the target database that must be 10.1.0.3+
This work is licensed under a Creative Commons License . Creative Commons License
(C) 1999-2008 - DBPrism ~ DBPrism CMS | Marcelo F. Ochoa | TANDIL ~ Argentina | 2008-10-07T20:16:52
DBPrism at SourceForgeBuilt with Cocoon2