Friday, October 12, 2007

Porting Day Communique 4.2 Into Weblogic 9.1

This document will explain the steps that should be followed to configure the Day Communique 4.2 dev. Environment with Weblogic as the app server Instead of the default Servlet engine provided by Communique.

For this paper, I have used the sample application and its domain for porting the Day Communique.

Weblogic domain is a logically related group of WebLogic Server resources. Domains include a special WebLogic Server instance called the Administration Server, which is the central point from which you configure and manage all resources in the domain. Usually, you configure a domain to include additional WebLogic Server instances called Managed Servers. You deploy Web applications, EJBs, and other resources onto the Managed Servers and use the Administration Server for configuration and management purposes only.

Day Communique comes with five war files, they are crxauthor.war,crxpublisher.war,author.war,publish.war and ROOT.war.
  • crxauthor.war: The repository of the authoring environment.
  • crxpublish.war: The repository of the publishing environment.
  • author.war: The Communiqué authoring environment.
  • publish.war: The Communiqué publishing environment.
  • ROOT.war: The Communiqué welcome screen; you do not need this file for Communiqué to run, and it may not be available in custom installations of Communiqué.

Day comes with its own Servlet container which by defaults executes these web applications. When these application runs they lock kind of the \\Day\CQ-4.2\data folder.

So we have to make sure, the default Servlet container is not running, or we can stop these web application from the admin panel of the Day Servlet container.

To stop them log in to the admin panel of the Day Servlet Container.

http://{DAY SERVER}:4402/admin/webapps , with username and password admin/admin, unless u have specified something else while installing Day.


Before you can install the Communiqué Web applications, you need to install the Communiqué libraries on the application server. You can find the libraries in the folder /server/lib/container of your Communiqué program folder. Add the following .jar files (Java archive files) to the libraries of your application server:

  • crx-api-1.3.1.jar
  • jcr-1.0.jar
  • day-commons-naming-1.1.jar

You may copy other libraries also if applicable.

For example for BEA WebLogic 9.1 lib location is :


In our case for the same application domain, the location is \\ bea\weblogic91\samples\domains\wl_server\lib


Now start the weblogic server and also start the admin console.

And perform the following steps

  • Select Deployments.
  • Select Lock & Edit to be able to install new web apps.
  • Click Install.
  • Select the WAR file to deploy, from the \\\Day\CQ-4.2\server\webapps.
  • Select Install this deployment as an application.
  • On the next screen keep the defaults and click Finish.
  • Click on Activate Changes to make your configuration changes persistent.
  • Select the crx application from the deployments list and select Start->Servicing all Requests.
  • Repeat the process for all WAR files.

Look at the weblogic console if any exception is thrown or not.

If every thing is fine, you should be able to access all the web application deployed in weblogic.


If you have deployed the web application but, while accessing them the page shows something like System not ready yet then it means

i) weblogic could not load crxauthor and crxpublish web application due to configuration problems.

ii) Check if you have copied all the required libraries in the correct location inside weblogic.

iii) Check if the data folder of communiqué is locked or not.

iv) Make sure that, these web application instances are not running from the default Servlet container.

1 comment :

  1. Do you have any idea how to stuff CQ with any decent MVC framework? It can be SpringMVC, Struts... Anything that would let me quit writing scriptlets?