The Goal

Many users would like to serve the "DAM" folder directly to the user when they call the domain instead of having the user call the URL like

The Solution

Since within the J2EE server "world" each web root is a application the prerequisite is to have the "bluedragon" and the "WEB-INF" folder within the root of the serving folder. Since we want to server the "DAM" folder directly it becomes automatically the root folder for the Web Server, thus we need to have those two folders in the "DAM" folder.

There are two ways to accomplish this, either you copy the "bluedragon" and "WEB-INF" folder into the "DAM" folder or you create a symbolic link (Linux/Unix) or a junction (Windows) to those folders. Actually this is the recommended way, since you will not have to copy folders.

Configure the DAM folder

In the Razuna root folder you will find the "bluedragon", "WEB-INF" and "global" folders. You will need to create a symbolic link to these folders when you want to server the DAM folder on its on.

On Linux/Unix you can issue the following command in the shell (do this within the DAM folder):

Then go on creating the same link for the "WEB-INF" and the "global" folders. Of course, using the correct path, that is! You have to use absolute paths!

For Windows there is no such thing as a symbolic link, but there is Junction. Junction allows you to do the same as symbolic links. You can download and see how to use junction over at

Configure Tomcat

The only thing left to do now is to configure Tomcat to serve your DAM folder directly. For this you will need to stop your Razuna server and open the server.xml file (this can be found within the tomcat/conf folder).

Locate the Host container (all the way to the bottom) and add/edit the Host in question. For our example, our new host entry looks like this:

It's important that the first "Context" contains the line "allowLinking="true"", without it our symbolic links would not work. Also make sure that the second "Context" is pointing to the exact location of your assets.

That's it. Simply startup your Razuna server and you should be able to server your DAM folder directly when you call up your host now.

This does NOT apply to users with the Oracle database!

By default you will find the default folder for storing your assets in the web root of Razuna. That is to say it is NOT in the web root your DAM web application of WEB application. It is located in the root folder of the Razuna application.

For security reasons you might want to move this folder out of your web root or want to locate it on a shared drive, Amazon S3 or network volume. Also, when you use domain locater (DNS record) like to point to your DAM application you will need to create a virtual directory.

Creating a virtual directory within Tomcat (the default standalone web server for Razuna) is easy. First of locate the file "server.xml" in the Tomcat/conf folder. Open it in a text editor.

Then look for the <host> container. If you have not changed the default installation this is the "localhost" entry. In between the <host></host> container add the following;

<Context path="/assets" docBase="absolutepathtodirectory" crossContext="false" debug="0" reloadable="true" />

Where the "docBase" should point to the directory you moved the "assets folder". This is a absolute path, on windows this should be "C:\....." on Linux/MacOS X "/....".

It is quite common, even recommended, that one runs the Razuna application and the Oracle database on two separate machines. Of course this can also be done with Razuna. Following are some things you need to take care off before you will succeed with this setup.

Installation of Razuna, ColdFusion and Oracle

Please follow the Installation Guide and install Razuna and ColdFusion on one machine and the Oracle database and HTTP server on the other machine. Make a note of the URLs and ports you are using. We recommend to have DNS records assigned to each server instead of IP addresses.

Razuna Settings

Since Razuna and the Oracle database transfer files over the HTTP protocol you need to supply the correct URL and if needed the correct port to the Oracle server. These URLs can be set within the General settings and should also have been applied during the initial setup of a host. But if you need to change them afterwards you can do it within the General settings. Caution: Changing any of these settings apply immediately!


By default some accounts are locked and cannot be used within sqlplus. This especially is the case with the ordsys schema. We therefore need to unlock the schema first before we can log in with that schema. Unlocking a account can be done trough the Enterprise Manager. You can access the Enterprise Manager within your browser at http://localhost:1158/em/.

There should be a URL shortcut in your Start Menue in Windows called "Oracle Database - Orcl" which will take you to this URL. Also, make sure that the Enterprise Manager Service is running. If not, go into your "Services" and start up the "OracleDBConsoleORCL" service.

 Log in to the Enterprise Manager with "sys" and your password. Make sure, that you connect as "sysdba".

If this is your first time you login in to the Enterprise Manager you will have to agree to the license information. Else you will see the main page of the Enterprise Manager. 

On top you will see the main navigation. Click on the "Administration" link. You will then get to a list of options.

In the "Users & Privileges" click on "Users". You will then see a list of all the users.

Select the radio button of the user "ORDSYS" and click on "Edit" above the user list. In the detail page you then will be able to modify this user.

Change the password to something secure. Change the status to "Unlocked". If done, click on "Apply" to save the changes.

You can now log out of the Enterprise Manager. Again, to save resources we recommend stopping the Enterprise Manager Service.

Even if you want to keep the password you will need to re-enter here. If you do not change the password and only unlock the user the account will be set to "Expired"!