JCMS FAQs - Installation and configuration

See the article JCMS 5.5: Configuring Apache, mod_jk and Tomcat (in french).

To install JCMS rapidly on Windows with Tomcat, see the article Getting Started with JCMS.

For more installation details see Operating and Installation Manual (in french).

See the article Configuring JCMS with OpenLDAP (LDAP/LDAPS) (in french).

See the article JCMS 5: Developing specific authentications with AuthenticationManager.

Severals SSO plugins are available for download.

A reverse proxy is an HTTP(S) server that receives requests and distributes them to other HTTP servers. This type of architecture makes it possible to hide the true servers from HTTP clients which know only the reverse proxy. Reverse proxy architectures are typically used to enhance the security of a cluster of HTTP servers, to supply a homogeneous access URL for heterogeneous HTTP services or for load balancing purposes.

JCMS must be explicitly configured to operate behind a reverse proxy, since it must produce hypertext links and HTTP redirections for the reverse proxy URL instead of the URL for its own HTTP server.

Use the Properties Editor to set the following parameters (Admin Area > Configuration):

• Site tab:
  • Site URL: URL of the Reverse Proxy (e.g. http://www.mysite.com/)
• Proxy tab (Reverse Proxy section):
  • Enabled: check 'Yes';
  • Address: the Reverse Proxy IP address (only requests coming from this address will be handled in Reverse Proxy mode);
  • Context Path: access path of the webapp in the base URL ("/" in this example).

Some JCMS functions, such as the RSS portlet, perform HTTP requests which may have to be sent by the enterprise's proxy server. Use the Properties Editor to set the forward proxy parameters (Admin Area>Configuration>Proxy tab>Forward Proxy section):

• Host: indicates the address of the outgoing proxy server to use;
• Port: indicates the port number of the proxy server;
• Not for: requests indicated by these addresses will be direct and will not pass via the proxy;
• Login: identifier of an account on the proxy server;
• Password: account password.

If you have set up a JSync cluster, don't forget to fill the Not for property in order to avoid JSync requests to be sent to the proxy.

In several cases (types generation, upload, deployment, etc.) JCMS creates temporary files using the <code>File.createTempFile()</code> method. By default, this method uses the temporary directory of the hosting platform (e.g. the /tmp folder under Unix). To change this, you must modify the system property java.io.tmpdir. This is done in the application server start script by setting the property at the startup of the JVM via the -D option:

-Djava.io.tmpdir=/my/temporary/directory/

Attention: if your application server starts in secure mode, you must add a read/write permission on this property.

See the article Implementing a high-availability JCMS site with the JSync replication protocol (in french).

See the article [JCMS 5.7 : Mise en œuvre de l’Import/Export (in french).

JCMS is by default case-sensitive to the identifier used for authentication, but some LDAP directories are not. If a person authenticates a first time by entering his login in lower-case then a second time in upper-case, JCMS will create two distinct accounts. To avoid this, use the Properties Editor (Admin Area>Properties Editor>Access tab) to set the Case-sensitive option to No.

JCMS is configured to recognize the most popular formats (doc, xls, ppt, pdf, jpg, gif, etc.) but it is possible to add formats not supported natively by JCMS. This is declared in the properties. For example, if you want to add support for Flash Video files (extension .flv), proceed as follows:

1. Edit the file WEB-INF/data/webapp.prop to add the following lines:

file-document.ext.flv:                   video/x-flv
file-document.icon.video/x-flv:          images/custom/files/flv.gif
en.file-document.typeinfo.video/x-flv:   Flash Video File
fr.file-document.typeinfo.video/x-flv:   Fichier Flash Video

2. Next, place the icon corresponding to this file type (flv.gif) in the folder images/custom/files/ (16x16 pixels dimension).

3. Finally, don't forget to configure your application server to ensure it returns the right MIME-type for this file type. The configuration is specific to each application server. For example, in Tomcat, in the file TOMCAT_DIR/conf/web.xml you must declare:

<mime-mapping>
  <extension>flv</extension>
  <mime-type>video/x-flv</mime-type>
</mime-mapping>

If the browser proposes to save the document rather than display it, the problem is almost certainly due to the configuration of the application server or web server. You must add the corresponding file extension / MIME type association to the server's configuration.

For example, Tomcat 4.1.30 is delivered without support for PowerPoint documents. To be able to handle these files, just add the file extension / MIME type association to the file TOMCAT_DIR/conf/web.xml:

<mime-mapping>
    <extension>ppt</extension>
    <mime-type>application/vnd.ms-powerpoint</mime-type>
</mime-mapping>

To determine the MIME type of a document just consult the "Content Type" field of the JCMS document.

Consultez l'article JCMS 5.5 : Accès WebDAV.

Un add-pack permet de définir les limites de JCMS (espaces, membres, langues, ...). Il peut aussi contenir une date d'expiration.

Pour obtenir un add-pack, il vous suffit d'appeler votre contact commercial chez Jalios en lui indiquant votre besoin. Précisez :

• Votre add-pack actuel (le cas échéant)
• Votre version de JCMS
• Le nom du site (celui défini par la propriété channel.name)
• Le nombre d'espaces de travail souhaité
• Le nombre d'espaces collaboratif souhaité
• Le nombre de membres souhaité
• Le nombre de membres en base de données souhaité
• Le nombre de documents en base de données souhaité
• Le nombre de langues souhaité

En retour nous vous fournirons une clé d'activation se présentant sous la forme d'une propriété (channel.add-pack) à ajouter dans le fichier WEB-INF/data/custom.prop de votre application JCMS.

Utiliser le plugin d'eclipse QuantumDB.

Installation :
http://quantum.sourceforge.net/how_to_install.html

Configuration (valable pour Derby) :

• Dans Eclipse, passer dans la vue Quantum DB
• Dans la fenête Database Bookmarks, cliquer sur l’icône +
• Cliquer sur Add driver
• Cliquer sur Add external Jar : sélectionner MyJcmsSite/WEB-INF/lib/derbyclient.jar
• En face de Class Name, cliquer sur Browse et sélectionner org.apache.derby.jdbc.ClientDriver
• Type : choisir Generic JDBC
• Cliquer sur Finish
• Sélectionner dans la liste le driver que vous venez de créer et cliquer sur Next
• Remplir les champs :
  • UserId : user
    
  • PassWord : user
    
  • JDBC URL : jdbc:derby://localhost:1527/jcmsdb;create=true;
    
  • Puis Finish
    
• Modifier dans custom.prop : derby.port: 1527
• Redémarrer

Utilisation :

• Dans la fenêtre Database Bookmarks, double cliquer sur votre nouvelle base
• Aller dans APP --> Table : ce sont les tables de JCMS.
• Double cliquer sur une table pour visualiser son contenu