• Multi-lingual backend now includes Spanish, French, German and Conversational Chinese translations.
  
• Red-lining : “what’s changed” tracks additions, deletions before publishing.
  
• Lucene/Nutch based site search.  The new site search can index many different file types such as HTML, XML, ZIP, OpenDocument, Microsoft Office (Word, Excel, Powerpoint), PDF, JavaScript, RSS, RTF, MP3 (ID3 tags).  Additionally, we have created an admin tool to allow a site administrator to build new indexes on a scheduled basis.
  
• New I/O friendly disk cache implementation speeds page delivery and overall throughput.
  
• JSP/Velocity integration tool eases legacy/enterprise system integration by allowing JSPs to be wrapped by velocity templates and content.
  
• Improved starter site ships with Events calendar, more demonstrations, Google Maps and Google Analytics.
  
• Multi-host sites will exclude system content by default, more cleanly separating content that lives on specific hosts.
  
• Multi-host sites log you into the host that you are viewing by default.
  
• Community contributed JSON Tool – server side JSON handling that allows you to consume and reuse JSON from remote systems – thanks Michael Fienen (@fienen)!
  
• Community contributed email Tool – scripting friendly tool allows email communication from within Velocity – thanks Chris Falzone (@chris_falzone)!
  
• A number of minor bug fixes and improvements.

UUJYVUC5N3XA

Upgrading dotCMS

1. Backup your dotCMS directory and database. (I’ve had several upgrades fail and ruin a db, please make sure and back everything up)

2. Download the latest dotCMS and unzip it. (I experienced better results from using the latest “trunk” in svn and compiling then I did with releases zip from their site)

3. Copy your older dotCMS/assets directory to the newer dotCMS-Root /dotCMS/
Note: If you have changed where your assets live use your altered assets directory.

4. If you have changed velocity files or jsps on the filesystem you will also need to move them.  If you don’t
know what these are then you probably haven’t.

Note: If you have changed any language properties copy the file under /common/ext-ejb/content/*

Note: From a version prior to 1.7a you need to move your reports directory also.
5. Change new instance database settings.
Uncomment the database you are using in the config (/dotcms/tomcat/conf/Catalina/localhost/ROOT.xml).

You will need to update the last part of the URL to your database name along with username:password.
The following is an example of a postgres config pointing to a database named dotcms

<!– POSTGRESQL –>
<Resource name=”jdbc/dotCMSPool” auth=”Container”
type=”javax.sql.DataSource” driverClassName=”org.postgresql.Driver”
url=”jdbc:postgresql://127.0.0.1/dotcms”
username=”postgres” password=”xxxxx” maxActive=”50″ maxIdle=”10″ maxWait=”-1″
removeAbandoned=”true” removeAbandonedTimeout=”60″ logAbandoned=”true”/>

6. Check your setting in conf/server.xml are correct.
This file is all new. Make sure that ip, ports, settings and ssl are all configured
correctly (configuring Tomcat is outside the scope of this document).
By default dotCMS will automatically run on localhost. If you need
the dotCMS to run on a particular IP address, edit the ./conf/server.xml file and search
the connector and server tags and add the address property on both. E.G.

<Server address=”208.250.1.102″ port=”8005″ shutdown=”SHUTDOWN” debug=”0″>
…
<Resource name=”jdbc/dotCMSPool” auth=”Container”
type=”javax.sql.DataSource” driverClassName=”org.postgresql.Driver”
url=”jdbc:postgresql://localhost/dotcms”
username=”postgres” password=”xxxxx” maxActive=”60″ maxIdle=”10″ maxWait=”60000″
removeAbandoned=”true” removeAbandonedTimeout=”60″ logAbandoned=”true”
testOnBorrow=”true” validationQuery=”SELECT 1″/>

7. If you are on a UNIX box, change the /bin scripts permissions,
add execution permission to *.sh in the bin dir.
> cd /wwwroot/test.dotcms.org/bin
> chmod 755 *.sh

8. Start your dotCMS using bin/startup.bat or bin/startup.sh depending on whether on UNIX or Windows.

9. Log into the dotCMS as an admin and goto CMS Maintenance usually under CMS Admin tab and do the following.
1. Execute Fix Asset Inconsistencies
2. Reindex all structures (very important, if you do not, then don’t be surprised if your hosts POOF disappear!)

Conclusion

All in all the process is pretty simple.  If you’re paying for a non CE version of DotCMS then they can simply upgrade you with a WAR file which in essence is just the new compile sources and once ran by your container (tomcat, GlassFish, etc) then it will perform upgrade tasks to the db and else where.  It’s fairly straight forward, but for those of you trying to save some dough this manual process is all you have at your disposal.

Server Packages & Setup

• Ubuntu 9.0.4 x86_64
• dotCMS 1.9
• java jdk 5 (1.5.0) (dotCMS doesn’t work with 1.6.0 which is jdk 6)
• MySQL 5.0 (dotCMS Support MySQL, MS SQL, Postgres and Oracle)

Step 1) Setup Server

For me, like stated, I am using Storm On Demand servers, thus I basically login to my control panel and I create a new instance. This server takes just a couple minutes to build and then I’m ready to go.  The password is set to the account strong password used when creating your control panel login.  So you can ssh into your machine using that password and the root username.

The first thing I always like to do with a new instance is run a full system update using APT.

apt-get update

Step 1-a) Java JDK

Then once everything is update install the 1.5 jdk (now all number is single, so look for JDK for J2SE 5, instead of 1.5, which is need for dotCMS to run (not compatible with 1.6).  You can use the IBM, Sun or openJDK version.  Doesn’t make a difference, but Ubuntu allows you to use openJDK and Sun’s JDK right from APT.

apt-get install sun-java5-jdk

Once the jdk is installed you’re almost ready to go.

Now make sure that the JAVA_HOME path is set.  You can try the command “export $JAVA_HOME” and if nothing comes out, then you’ll need to set it.

Next, save the file and in some cases you might have to restart your sshd daemon.

/etc/init.d/sshd restart

Step 1-b) MySQL

Make sure MySQL is installed.  You can simple try “/etc/init.d/mysql restart” to see if the server exists.. Yes yes I know some of you are already yelling at me to just use the version check command.. But, sometimes, this command just slips off of the fingers quicker haha.  I do a lot of restarting of daemons, it’s like second nature, and besides this is a new server install, there isn’t anything live using MySQL yet.  If this server wasn’t a new instance, please be aware this is dumb, and shouldn’t be used.

Just in case you don’t have MySQL installed, you can use the follow APT command

apt-get install mysql-server

After you have ensured that MySQL is running we need to change 1 setting in the my.cnf file.

vim /etc/mysql/my.cnf

Add “lower_case_table_names=1″ excluding the quotes to the my.cnf file and then run the MySQL restart command again and MySQL is ready to go.  We do not need to run any install scripts on MySQL because the dotCMS package is set to install it’s data into the database when it’s ran for the first time.

Lastly, lets create a database and user for dotcms.  So lets login to MySQL.

mysql --user=username -p

mysql> create database dotcms; (now hit enter)

mysq> use dotcms; (hit enter)

mysql> create user 'dotcms'@'localhost' IDENTIFIED BY 'somePassWord' (hit enter)

mysql> GRANT ALL PRIVILEGES ON *.* TO 'dotcms''@'localhost' (hit enter)

optionally if you would like to access the db outside of the localhost using the same user you can interchange ‘localhost’ with ‘%’.

Now you have created a new user, and granted it permissions on the dotcms database. MySQL is ready to rock baby!

Step 2) Get dotCMS 1.9

I learned the hard way but as tantalizing as the full fledged release version of dotCMS 1.9 is, please use the latest trunk from svn.  There are a HUGE number of bug fixes, and I underestimated just how many.  I previously installed 1.9 from the version 1.9b3, and there were some CRUCIAL bugs still now fixed like the ability to add multiple hosts, and copy hosts.. This a HUGE issue.  However, the latest trunk is all good to go.

Step 2 a) Download dotCMS 1.9 from SVN

No matter what SVN client you use there are many out there. No matter which client you use get the latest version from http://svn.dotcms.org/trunk

Step 2 b) compile dotCMS using ant

Once the source has downloaded you’ll have to compile it, and it will created all of the necessary SQL files and trust me it’s not hard..  Just 1 command, your grandmother could do this

The command you need to run (windows or ssh) is going to be from the root of the project and is:

ant deploy

I know, confusing huh? At any rate this will setup the entire directory, files, etc to be installed.

Step 2 b) Place files in location for instance

Now, you can technically run the instance from where ever you would like but I like to keep things tight in Ubuntu.  I suggest putting the files into a directory called “dotCMS”, or perhaps “dotCMS19″ and that directory should be located in /user/local and some like to use /opt/ in Ubuntu.. Doesn’t matter much to me but I don’t like to run these things from my user or root home folders.

Step 3 a) Configure dotCMS

We have a couple things we need to take care of.  First we need to edit /conf/Catalina/localhost/ROOT.xml file. Make sure and change the database name in the URL, the username and password for the database server and make sure that only ONE database config is uncommented at a  time.. Trust me, people forget about this all the time.

From the root directory, (dotCMS/) run the following command:

chmod -R 755 *.sh

This will ensure that all sh scripts have the correct permission both in dotCMS and tomcat to run properly.

Step 4) Start the dotCMS instance

Go into your dotCMS installation directory.. dotCMS/bin/ and run the following to start the installed and cause dotCMS to install the default database scripts.

sh ./startup.sh

Step 5) Login and Enjoy

You’re all set, now just login to http://localhost/c/

I have compile a list of my top 10 favorite dotCMS features in 1.9, enjoy, and feel free to share you’re in the comments.

1) Brand New UI –  This might not seem like a new “feature” but trust me it is.  The old UI, was a bit clunky and unfamiliar, however, the new interface is very intuitive and easy to use.  Also, the inline editor makes best use of the power presented with dotCMS, I couldn’t be happier with the new UI, and I definitely think the designers should get some props!  The new layout uses Dojo AJAX Toolkit for almost everything.

2)  Multi-Site/Tenant Management – This feature speaks for it’s self, but until you really see the interface and see the power it’s hard to see the benefit.  I have attached a small screencast below to show you the power in the multi-site management system.

In the words of dotCMS them selves:
With dotCMS 1.9 multi-tenant capabilities, whole sites can be quickly created, shared and even be copied from existing web properties to help speed your “time to live”.  With our new host manager, administrators can provision hosts globally, changing permissions, themes, analytic code, able to make host-wide changes from a single friendly interface.

3) WebServices and JSON API – This feature is huge for all of your developers out there who need to built onto dotCMS and make a more robust and custom solution.  This will allow you to access data from the site, manipulate your data and create your own tooling.  Need to create your own iPhone or Android app to interface with a site built on dotCMS 1.9?  If so, this feature is perfect for getting and passing data back and forth.

4) Internationalization – dotCMS 1.9 is now fully nationalized.  The product takes use of best practices and even allows localization of the administration panel.  dotCMS 1.9 will ship with English, Spanish, Romanian and German translations, but more will be coming soon and you can also create your own if need be.

5) Integrated Form Builder – This is another huge feature that frankly I’m surprised to see in this release.  With the amount of new features slated to be released in the new 1.9 version, it’s hard to believe that they found the time to integrate a new form builder product.  The Form Builder, does precisely what it sounds like; allows you to create your own forms using a GUI interface in the admin panel and then stores and reports the data back to you, the user.  This is very useful for large data collection projects, or anyone who ever uses forms.. Ever.. For any reason!  I’ve used Form Builders with previous CMS’ like Joomla but this implementation blows them all away.

6)  SUDO Logon Power – If you’re hosting multiple websites on this system, and for multiple owners/users this feature is a must.  I’m excited to get this feature in place, but basically this will allow you, the admin, to login as if you’re the other user.  You’ll see what they see, get restricted to what ever they’re restricted to, and you’ll really get a good feel for what your client is seeing.  Before, working in such environments you were forced to memorize or collect passwords while you were testing and tinkering around, but fumble with passwords no more, this feature will grow on you.

7) PHP – Ruby – Python – Groovy Plugin – Given the wide range of developers who use dotCMS I’m inclined to believe that this new plugin will be very popular.  This plugin will allow a developer to create code in PHP, Ruby, Python, or Groovy and integrate it into content.  This works similar to integrating JavaScript into HTML.