This new release of DBPrism CMS includes a graphical installer based on Jetty web server, Ant and few of Cocoon XSP pages. Why the installer uses XSP?
Because the CMS is not installed yet, so the XSP page works as a wrapper for the Ant's task used for the different installation process. To launch the installer go to the CMS distribution sources and execute Ant in the directory of the demo web site them, use your favorite browser at with this location http://localhost:8888/ldoc/install.xhtml:

cd sites/www.mycompany.com/
ant run

Here a sample screen of the installer form:

Before this step you have to configure some basic things such as the environment variable JAVA_HOME, ORACLE_HOME, and database users used for installing the code (CMS_CODE) and the tables (CMS_DATA). You can see this common parameters at the left side of the Web Installer as is depicted in the following picture. Also you can configure in advance the target database into the common.xml file used by the Front End Application at the post installations steps.

The important parameters at the common.xml file are database, log, user/ pass (only for testing database connectivity), db.[ host| port| sid] and jdbc.string.

You must have to check the basic database connectivity using the SQLPlus or tnsping command line utility to the database defined into the common.xml file, Also a FTP/WebDAV connectivity using defaults ports 2100/8080 and the availability of the DBMS_SMTP package are required.

A fresh database install do not have these ports and packaged enabled, you can configure them executing these commands logged as SYS with the SQLPlus at the server side:

SQL> exec dbms_xdb.setFtpPort(2100);
SQL> exec dbms_xdb.setHttpPort(8080);
SQL> @?/rdbms/admin/utlmail.sql
SQL> @?/rdbms/admin/prvtmail.plb
SQL> alter system set smtp_out_server='smtp.yourdomain.com' scope=both;

You can test the connectivity at the Web Installer too, here a sample output of this option:

This step is required to be executed only once time because it only installs some common components for the DBPrism CMS at the SYS's schema such as the Jxtp toolkit and the common libraries Log4J, JUnit and JAXB.

The installer screen requires some database parameters for this step, they are SYS's user name and password, a valid SQLNet connect string and database host name used to connect by FTP, you can override the common.xml parameters with this values.

Here an example of the Web Installer output after running the Pre-Installation option:

This is the mainly step of DBPrism CMS 2.1.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.

The parameters required for this step are the same the previous one, here the output of this option:

After the main CMS step is done you have to create a minimum of one CMS user, there is an option at the CMS Installer to create CMS users. For this step you need to provide more parameters than the previous one steps. Here an screen capture of the Add user install form:

The list of the input parameters is depicted in the table below:

The installer provides you a link to connect to the CMS an start using it. The link is http://localhost:8888/ldoc/index.xhtml, once you click on it an authorization request will prompt you for the user name and password used on latest install step (Add CMS Users) here, by default the CMS Install script creates two sample pages once for the home in English and once for Spanish. The CMS Front End look like this:

Note that in the above screen capture the menu are localized to English if you change the browser preferences to Spanish as default language this menu and the Front End forms will automatically localized to Spanish. You can find more information about the options and forms at the Front End application section.

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.

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.

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!!!.

<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>