Setting up a Linux server for exporting recordings

About this task

To enable the recording export function on an Remote Control Linux server, complete the following steps.

Starting from version 10.1.0 FP 5 the Remote Control Server uses FFmpeg (https://ffmpeg.org) to convert the recording files. To enable the recording export function on an Remote Control Windows server, complete the following steps:
  1. Download and install FFmpeg from the following repository: https://github.com/BtbN/FFmpeg-Builds/releases.
  2. Select a build that includes the libx264 encoder (typically the "GPL" builds). If a version of FFmpeg is already installed on the OS, it is highly recommended to replace it with a build from the link above to ensure the libx264 library is available for high-quality H.264 encoding. The check can be performed with the following command:

    ffmpeg -encoders

  3. Stop the Remote Control server service by using the following command:

    /etc/init.d/trcserver stop

  4. Add the ffmpeg command to the PATH system variable.
  5. Start the Remote Control server service by using the following command

    /etc/init.d/trcserver start

    Important: If the server is not installed in the default folder, the video.properties and the encode.cmd files need to be changed after the server update.

Please note that the following instructions only apply to Remote Control Server version 10.1.0.0442 and lower.

Procedure

  1. Download and run the Java Media Framework (JMF) Performance Pack for Linux installer from the following site
    http://java.sun.com/javase/technologies/desktop/media/jmf/2.1.1/download.html
  2. Download and install MPlayer with support for the XviD codec.
    Depending on the Linux® distribution,you are using, you might be able to install this by using the regular package repositories if you are using SuSe Linux®. If you are using RedHat Linux®, go to http://www.mplayerhq.hu/design7/news.html.
  3. Edit the video.properties file to ensure that the full path to the encode.sh file is set up correctly.
    This file is in the WEB-INF/rc/encode.sh directory. You must expand the relative path to an absolute path where the application was deployed by WebSphere Application Server. 
    for example :
 /opt/IBM/WebSphere/AppServer61/profiles/installedApplications
     /trc.ear/trc.war/WEB-INF/rc/encode.sh.
  4. Stop the BigFix® Remote Control Server service by using the following command

    /etc/init.d/trcserver stop

  5. Copy the file jmf.jar from the JMF installation directory to the WEB-INF/lib directory within the BigFix® Remote Control Server installation directory
  6. Start the BigFix® Remote Control Server service by using the following command

    /etc/init.d/trcserver start

Results

Note: It is important to note that the jmf.jar file must be copied again into the WEB-INF/lib directory, whenever the BigFix® Remote Control Server is updated otherwise the exporting function is disabled.