{{Obsolete}}
WARNING End Of Life Alfresco 5.0. Alfresco 5.0. does not support JCR in any way.
Basic Configuration Details
Configuring the JCR-RMI extension is performed by the modification of a simple properties file (jcr-rmi.properties). The file is located in the source code tree at /extention/config/alfresco/extension/jcr-rmi.properties
# ##################### #
# RMI JCR Configuration #
# ##################### #
rmi.jcr.binding.servername=localhost
rmi.jcr.binding.port=1099
rmi.jcr.binding.name=javaContentRepository
Overriding Default Configuration
The best way to override the JCR-RMI configuration is to put a properties file in the classpath before the jar which loads the extention /alfresco/extension/jcr-rmi.properties.
This avoids the need to recompile the extention or the webclient package. This also ensure that the configuration alterations will persist between deployments.
Modification of war files either through explosion or recompiling for a given target is practiced by many but is inconsistent with the initial design goals of the technology. Overriding the configuration at the server is the best practice.
tomcat
In tomcat this can be accomplished by putting the file (and folders) in the common/classes folder.
RMI Registry Setup
Tomcat does not provide the required infrastructure for running the JCR RMI extention. You must start an instance of the RMI Registry.
The RMI Registry is started on port 1099 by default. It should be run as a daemon (background process).
This can be done in unix with the following command:
nohup rmiregistry &
This can be done in windows by
Install RMI Registry as a windows service with SrvAny.Exe (part of the Windows resource kit, which has to be purchased)
jboss
In tomcat this can be accomplished by putting the file (and folders) in the conf folder.
RMI Registry Setup
By Default The JBoss Application Server provides RMI insfrastructure. JBoss can be configured to run either RMI/JNP or RMI/IIOP.
JBoss runs the RMI registry on port 4444
