All the parameters affecting the server work are set during the build process. However, after build and deployment there is still a possibility to change some of their values. The core component responsible for administration of the server settings is org.alembik.Configurator, which serves as a paramaters repository for all other modules. Configurator exposes the current values through the HTML administration console, where user may adjust them during the server runtime.

Administration console

The Alembik's administration console is a web application bundled with the server engine, which is accessible at the following URL:

web administration console

     http://[host:port]/alembik/        
 

The console displays the current service state as well as gives access to an HTML form of server parameters. The form page is password-protected - the actual credentials are set during the build process and stored in web.xml of the application's WAR file.

Once changed and confirmed at the form page the server settings are stored in alembikConfiguration.properties file at the container's working directory. These parameter values will then take precedence over the ones from the initial release configuration after subsequent Alembik restart.

A logged administrator is also given a possibility of reloading WURFL repository definitions without restarting the service. Please look for the [reload wurfl] menu entry at the left panel.

Mind that [browse] button provided for user convenience (beside file selection boxes) can be used only when configuring Alembik directly at its installation machine (otherwise you are browsing the file system of your local machine!).

Configurator parameters

The Configurator class maintains the values of server parameters under the keys provided by a Property enumeration. Each module may access those values at runtime using an appropriate enum key through a dedicated API.

All the parameter values come from alembikConfiguration.properties file, which is initially located inside the Alembik distribution archive. However, at any moment the file may be replaced by another version in the container's working directory (see above), whose values can be freely edited.

org.alembik.Configurator
public static enum Property
{
   IMAGE_PROCESSOR_CLASS ("image.processor.class"),
   AUDIO_PROCESSOR_CLASS ("audio.processor.class"),
   VIDEO_PROCESSOR_CLASS ("video.processor.class"),
   TEXT_PROCESSOR_CLASS ("text.processor.class"),

   FFMPEG_COMMAND ("ffmpeg.command"),
   FFMPEG_VERSION ("ffmpeg.version"),
   FFMPEG_IMLIB2_LOCATION ("ffmpeg.imlib2.location"),
   IMAGEMAGICK_COMMAND ("imagemagick.command"),
   MP4BOX_COMMAND ("mp4box.command"),

   STORAGE_ROOT_DIRECTORY ("storage.root.dir"),
   STORAGE_URL_PATH ("storage.url.path"),

   STREAMING_URL_PATH ("streaming.url.path"),
   SERVLETS_URL_PATH ("transcoding.servlets.url.path"),

   WEBRENDERING_ERROR_PAGE ("webrendering.error.page"),
   GENERAL_ERROR_PAGE ("general.error.page"),
   GENERAL_STATUS_PAGE ("general.status.page"),
   ERROR_IMAGE_PATH ("image.error.path"),

   WURFL_FILE_PATH ("wurfl.file.path");
}

public String getProperty (Property property) {}

public String getProperty (Property property, String defaultValue) {}

For the details on each particular parameter please refer to the building chapter.

Miscellaneous configuration

If Alembik server is to be deployed in the Intranet environment with a proxy connection to Internet, there can be specified two Java VM parameters with approriate proxy parameters: alembik.proxyHost and alembik.proxyPort. Then all the original media content will be fetched using the connection set with these values.

application server's start-up command line

   java ... -Dalembik.proxyHost=[host_name] -Dalembik.proxyPort=[port-number]