Give it a try

You can give easily a try of Silverpeas by signing up in our demonstration platform Enjoy Silverpeas!

Download the production-ready distribution

The above solutions are obviously limited in functionalities as Silverpeas requires additional external tools and services to perform some of its advanced features and those services aren't packaged with them (in order to keep them simple and light for a testing purpose).

To fetch directly the last stable version, production-ready, of Silverpeas, please use the links below to download both the distribution of Wildfly required by Silverpeas and the current distribution of Silverpeas:

• Wildfly 26
• silverpeas-6.4.1-wildfly26.zip (the GPG signature of the distribution)

You can also fetch the last release candidate of the next major version of Silverpeas by downloading both the distribution of Wildfly required by it and its current distribution.

For those wishing to upgrade their Silverpeas distribution to the latest release candidate, you have to know latter has an impacting change on its implementation of the JCR that requires a migration of it. See below on how to install Silverpeas for more explanations.

• Wildfly 26
• silverpeas-6.5-build241125-wildfly26.zip (the GPG signature of the distribution)

Don't forget to read the instructions below about how to install Silverpeas from these two distributions.

Pre-requisite

Silverpeas 6 can be automatically deployed on the JEE application server Wildfly >= 10.1.0. Nevertheless, we strongly recommend to deploy it on Wildfly 26.1.3 as this version was tested by ourselves with the current version of Silverpeas.

Silverpeas 6 depends on external tools/services to run or to offer a better user experience. Please find below a list of the tools and services you will need to install.

Installation

You will get better performance with GNU/Linux (or *BSD) systems.

gpg --keyserver hkp://pgp.mit.edu --recv-keys 3DF442B6
gpg --verify silverpeas-6.4.1-wildfly26.zip.asc

Proxy configuration

The installation process starts by downloading from our Nexus Repository Manager the different software components that made up Silverpeas. Hence, an access to the Internet is required, so if you are behind a proxy, you have to define correctly its properties for the installer.

Because the Silverpeas build life-cycle is managed with Maven (Nexus is a repository of Maven artifacts, id est software bundles), the installation program accesses the repository through an embedded Maven library (unlike Silverpeas 5, it doesn't require Apache Maven to be installed). So, the proxy configuration can be done with the usual user Maven settings. Please edit or create the file .m2/settings.xml in the home directory of the user that is responsible of the Silverpeas installation with the following instructions:

<settings>
  ...
  <proxies>
   <proxy>
      <active>true</active>
      <protocol>http</protocol>
      <host>proxy.somewhere.com</host>
      <port>8080</port>
      <username>proxyuser</username>
      <password>somepassword</password>
      <nonProxyHosts>www.google.com|*.somewhere.com</nonProxyHosts>
    </proxy>
  </proxies>
  ...
</settings>

For a complete configuration description, see this Maven documentation page. For a complete description of each parameter see Maven Settings.xml configuration page.

Configuration

The configuration of Silverpeas is split into two main folders in the directory SILVERPEAS_HOME/configuration:

• jboss with JBoss CLI scripts for configuring Wildfly in order to run Silverpeas,
• silverpeas with Groovy and XML scripts for configuring the Silverpeas application itself.

Usually you don't have to touch the content of these folders unless for some specific settings of your own. The only file to adapt to your need is the SILVERPEAS_HOME/configuration/config.properties global configuration file that can be created from the template SILVERPEAS_HOME/configuration/sample_config.properties. All the commented parameters declared in the global configuration file are set with their default value. To set some parameters with a different value, then just uncomment them and set the correct value. This file is used by the configuration process to set up both the Wildfly server and Silverpeas.

Usually, the properties of the database to be used by Silverpeas have to be set explicitly into this configuration file. So, if it doesn't already exist, creates it from the template SILVERPEAS_HOME/configuration/sample_config.properties in the same directory and set the following properties with the parameters of the database. Example of such a SILVERPEAS_HOME/configuration/config.properties file:

DB_SERVERTYPE = the database type (POSTGRESQL, MSSQL, or ORACLE)
DB_SERVER = the IP address or the DNS name of the database server
DB_USER = the login of the user with the administrative rights on the database
DB_PASSWORD = the password associated with the login above
DB_NAME = the name of the database if otherwise than Silverpeas

Beside the global configuration file, the behaviour of some of the Silverpeas functionalities are parameterized through properties files in the directory SILVERPEAS_HOME/properties that is generated during the installation process. This setting can be refined either through a Groovy script or an XML script in SILVERPEAS_HOME/configuration/silverpeas. In the case of an XML script, as in Silverpeas 5, it is usually named CustomerSettings.xml. When you name your own scripts to configure some parts of Silverpeas, don't forget the scripts are loaded by the configuration process by their name and the 00-SilverpeasSettings.xml script must be the first one to be executed. Below an example of such a SILVERPEAS_HOME/configuration/silverpeas/CustomerSettings.xml file:

<?xml version="1.0" encoding="UTF-8"?>
<silverpeas-settings product="Custom">
  <fileset root="${SILVERPEAS_HOME}/properties/org/silverpeas">

    <configfile name="calendar/settings/calendar.properties">
      <parameter key="calendar.import.ics.file.replace.before.process"><![CDATA[CREATED:0000/CREATED:1970]]></parameter>
    </configfile>

    <configfile name="general.properties">
      <parameter key="web.request.domain.allowed">*</parameter>
    </configfile>

    <configfile name="util/uploads/uploadSettings.properties">
      <parameter key="MaximumFileSize">1610612736</parameter>
    </configfile>
  </fileset>
</silverpeas-settings>

Installing Silverpeas

The installation program is built upon the build automation system Gradle. You don't have to install it as the program will download it the first time you run it.

For an upgrade, if the use of a new Silverpeas distribution isn't required, you just have to change the version variable in the SILVERPEAS_HOME/bin/silverpeas.gradle file with the new version of Silverpeas 6.

To install or upgrade Silverpeas, that is to say to download Silverpeas, to configure it and then to deploy it into Wildfly, you just have to type, in the SILVERPEAS_HOME/bin directory:

silverpeas clean install

with:

• clean: this command instructs to clean up any previous installation of Silverpeas; this command is required for an upgrade to force the installation process to rebuild and to configure Silverpeas. For a fresh installation, this command isn't required.
• install: this command starts the installation process that follows then the following execution path:
  1. if the Gradle's cache is empty, the software components that made up Silverpeas are then downloaded from our Nexus Repository and pushed in the cache, otherwise the version in the cache is used,
  2. the Silverpeas Web application is built,
  3. Wildfly/JBoss is configured to run the Silverpeas Web application,
  4. Silverpeas is configured,
  5. the database used by Silverpeas is either built (in the case of a fresh installation) or updated (in the case of an upgrade).

Once the installation or upgrade process done, you will find the bundles deployed in Wildfly/JBoss in the SILVERPEAS_HOME/deployments/ directory.

If you need only to reconfigure Silverpeas, you just have to type, in the SILVERPEAS_HOME/bin directory:

silverpeas configure

To know if the process has succeeded or what failed, you can consult the build log file in the SILVERPEAS_HOME/log directory whose the name starts with build and ends with the timestamp of the process.

Launching Silverpeas

To start Silverpeas, in the SILVERPEAS_HOME/bin directory:

silverpeas start

To stop Silverpeas, in the SILVERPEAS_HOME/bin directory:

silverpeas stop

To get the status of Silverpeas, in the SILVERPEAS_HOME/bin directory:

silverpeas status

Once started, you can access Silverpeas through the following url: http://localhost:8000/silverpeas and by using the default credentials SilverAdmin/SilverAdmin.