This chapter provides information on the following deployment scenarios:

Deploying in RAD Environment

To deploy DMS applications in the Infinity Process Platform Rapid Application Development environment, a Jackrabbit facet is provided, which can be added to your dynamic Web project.

Please refer to the chapter Creating a Dynamic Web Project in Eclipse of the Rapid Application Development guide for detailed information on how to create a dynamic Web project, add Process Manager facets and deploy your applications in this environment.

The Process Manager Jackrabbit Facet

The Jackrabbit facet can be selected in the project facets part of the dynamic Web project. Stop your server if running and select one of the Process Manager Jackrabbit facets to deploy Jackrabbit with your application:

Creating a Web Project with Jackrabbit Facet.
Figure: Creating a Web Project with Jackrabbit Facet.

Setting the Repository Path

The repository location must be specified in the repositoryHome parameter of the bean jackrabbitRepositoryStartupBean in the jackrabbit-jcr-context.xml file, which resides in the carnot-jackrabbit/WEB-INF/config/ipp/spring folder of your Web application. There is a default value, set to the path c:/tmp/repository. To use Jackrabbit this path must point to an empty folder or an existing Jackrabbit repository.

   <bean id="carnotJackrabbitRepository" class="org.eclipse.stardust.vfs.jcr.spring.JackrabbitRepositoryStartupBean">
      <property name="jndiName" value="jcr/ContentRepository" />
      <property name="repositoryConfig" value="/WEB-INF/jackrabbit/repository.xml" />
      <property name="repositoryHome" value="c:/tmp/repository" />

In case the default value has not been changed, an appropriate warning message will appear during the Jackrabbit facet creation, to inform where to configure the repository path:

Repository Path Warning
Figure: Repository Path Warning

In some cases, e.g. after a non graceful shutdown, it might occur that your Jackrabbit repository content is corrupt. If it does not contain important content to be lost, remove the complete repository to make it created newly.

Setting up additional Jackrabbit VFS Repositories

Infinity allows to instantiate an arbitrary number of document repositories as described in chapter Federated Document Repositories in the Concepts part.

To set up additional Jackrabbit VFS repositories, add an additional bean besides the existing one in your jackrabbit-jcr-context.xml file pointing to a different repository home and JNDI name, e.g:

 <bean id="jackrabbitRepositoryStartupBean2" class="org.eclipse.stardust.vfs.jcr.spring.JackrabbitRepositoryStartupBean">
      <property name="jndiName" value="jackrabbit.repository2" />
      <property name="repositoryConfig" value="/WEB-INF/jackrabbit/repository.xml" />
      <property name="repositoryHome" value="c:/tmp/repository2" />

Standalone Deployment

Preparing Jackrabbit Deployment

To make deployment possible with Jackrabbit, you have to create the following property files and add them to your classpath:

In the file, add default entries, which can be one or more users as keys and their passwords as values:


You can leave the file, which is a container for users as keys and a comma-separated list of their roles as values, empty.

The default values set in the file, can be overwritten in the file by setting the following properties:

which have the values <ipp-jcr-user> and <ipp-jcr-password> respectively per default.

Application Server specific Requirements

The necessary steps that have to be performed to make a Jackrabbit deployment possible for specific application servers are described in detail in the Deployment Guide in the according application server chapters. Please refer to: