Click on the icon below to watch a graphical installation demo (steps 1 to 3).

To install DBPrism CMS run the install.sh script on the server machine if you are using Oracle on Unix, or install.bat script for Win32, logged as Oracle database owner (oracle unix user). Before runs this install script check enviroment settings such as JAVA_HOME, ORACLE_HOME, CMS_HOME, SYS_PASSWORD and so on, for example:

	if [ "$CMS_REPOSITORY" = "" ] ; then CMS_REPOSITORY=cms;export CMS_REPOSITORY fi SYS_PASSWORD="sys/change_on_install@$CMS_REPOSITORY as sysdba";export SYS_PASSWORD CMS_USER_SEC=cms_user_sec;export CMS_USER_SEC CMS_USER_SEC_PWD=cms_user_sec;export CMS_USER_SEC_PWD CMS_OWNER=cms_owner;export CMS_OWNER CMS_OWNER_PWD=cms_owner;export CMS_OWNER_PWD # Where Cocoon is running, edit them acording to your need CACHEHOST=cachehost;export CACHEHOST CACHEPORT=8888;export CACHEPORT

Normally your unique change will be the setting for CMS_REPOSITORY and SYS_PASSWORD values, look at the Script Detailed document for more information.
Run it using a command sequence like this:

	# cd $HOME/cms/scripts # ./install.sh

Tip: the script assumes a database instance named "cms", to quickly customized this setting add a new entry into your $ORACLE_HOME/network/admin/tnsnames.ora file according to your needs. Also you will need to change this value into the file $CMS_HOME/dbprism/xdocs/setupcms.xml

This script assume CMS_OWNER as the schema where the source code and test tables are created. CMS_USER_SEC schema is used for storing procedures and packages used by the Virtual Private Database security layer, look at the Workshop pages for more detail on the security layer implementation.

If you change CACHEHOST, CACHEPORT values into install.sh script, set the same values into enable-cache-sync.sh and disable-cache-sync.shscripts. Look at the Cocoon External Cache Invalidator Server section for more details.

DBPrism CMS 2.0.1 provides a separate schema for your assets, so you can share the Source code of the CMS and VPD implementation packages with multiple repositories. This three-schema configuration setup provides many benefits for administration tasks such as exporting and importing operations, CMS code upgrade an so on.

Then the next step into the database server side is to create the repository for the content assets. This step is made executing the script create-rep.[sh|bat]

Like the step 1, these scripts requires checking on some enviroment setting such as CMS_REPOSITORY, SYS_PASSWORD, and so on.

The script requires two arguments, the database username and password for the target schema. This database user is a new database to be created, if this user exist the script will fail at many points and the repository will be unestable. Example:

	# cd $HOME/cms/scripts # ./create-rep.sh demo_rep demo_rep

In the step 2 we created an database user which will content the CMS assets. We can populate this content with some default values at this point. These default values includes, definitions for RSS Channels, Categories for the MoreOver News feed and Questions and Answers for the FAQ List.

To upload these initials values excecute:

	# cd $HOME/cms/scripts # ./upload-test.sh demo_rep demo_rep

Also we need to upload almost a home page for the web site and the administrative pages, for doing it execute:

	# cd $HOME/cms/scripts # ./upload-demo-site.sh

The above script uses a pre-configured demo web site with only one public page, the Home Page, you can add then sections and sub-sections to this web site using the administrative pages. The content for the demo web site is located into the directory $CMS_HOME/demo, you need to set the same username and password for the database repository as the used in the step 2 into the configuration file $CMS_HOME/demo/xdocs/setupcms.xml.

upload-demo-site.[sh|bat] script uses the Upload Utility click on the link to see more information.

This CMS works with Cocoon 2 architecture, Cocoon 2 uses sitemap.map file for configuring presentation concerns, here a setup code used in the root sitemap file of Cocoon2.

	<?xml version="1.0"?> <map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0"> <!-- =========================== Components ================================ --> <map:pipelines> ..... <!-- sub-sitemap example pipeline --> <map:pipeline> <!-- ================ DBPrism 2.0.1-production begin here =========================== --> <map:match pattern="doc/**"> <map:mount uri-prefix="doc" src="cms/" check-reload="yes"/> </map:match> <map:match pattern="ldoc/**"> <map:mount uri-prefix="ldoc" src="lcms/" check-reload="yes"/> </map:match> <map:match pattern="xmlj/**"> <map:mount uri-prefix="xmlj" src="xmlj/" check-reload="yes"/> </map:match> <map:match pattern="x-dbprism-cache-invalidate"> <map:generate type="serverpages" src="invalidate.xsp"/> <map:serialize/> </map:match> <map:match pattern="dist/*.*"> <map:read src="dist/{1}.{2}" mime-type="application/octect-stream"/> </map:match> <!-- ================ DBPrism 2.0.1-production end here =========================== --> <map:match pattern="sub/**"> .... </map:pipelines> </map:sitemap> <!-- end of file -->

The above section means that DBPrism CMS will use two sub sitemaps located into the directories cms and lcms. Each sub sitemaps defines DBPrismGenerator as default Generator for Cocoon and several pipelines used into the CMS, directories starting at doc are for the production web site, and the other (ldoc) for the internal website (site used by the Content Authors). Finaly DBPrism / Cocoon2 CMS is preconfigured for a mount point /dbprism, for Apache + Tomcat it requires to edit mod_jk.conf file with this line:

	JkMount /dbprism/* ajp12

For Apache+Jserv on jserv.conf file:

	ApJServMount /dbprism /root

For Apache+OC4J on oc4j.conf file (through mod_proxy):

	ProxyPass /dbprism/ http://localhost:8888/dbprism/ ProxyPassReverse /dbprism/ http://localhost:8888/dbprism/

Look for the respective install instructions on each case ( Apache/Jserv, Apache/Tomcat, Apache/Oracle9iAS Container for J2EE).

If you are using Oracle JDeveloper 9.0.3+ DS, you can quickly make the web server deployment into an OC4J using the deployment tool. First open de project file CMS.prj located into the CMS_HOME directory, then navigate to the Deployment tree and execute the deployment profile named webapp.deploy