Acumem Freja has been tested and verified to work on the following Linux distributions:
Red Hat Enterprise Linux 4.7
Red Hat Enterprise Linux 5.2
Ubuntu 6.06 LTS
Ubuntu 8.04 LTS
However, note that sampling 32-bit applications on 64-bit Ubuntu 6.06 may fail due to bugs in the 64-bit Ubuntu Linux kernel.
Acumem Freja should work on any Linux installation that fulfills the following requirements:
80486 or newer x86/x86-64 architecture processor
2GB RAM
At least 40MB of permanent storage
Linux kernel 2.6.0 or later
glibc 2.3.3 or later, with NPTL threads
GTK 2.4 or later is required for the graphical user interface
A graphical web browser to view reports
The following Windows versions are supported:
Windows XP sp2, sp3 (32-bit)
Windows XP Professional x64 sp2 (64-bit)
Windows Server 2003 sp1, sp2, r2, r2 sp2 (32-bit, 64-bit)
Vista sp0, sp1, sp2 (32-bit, 64-bit)
Windows Server 2008 sp1, sp2 (32-bit, 64-bit)
Windows 7 (32-bit, 64-bit)
Windows Server 2008 R2 (64-bit)
Other general system requirements:
80486 or newer x86/x86-64 architecture processor
2GB RAM
At least 40MB of permanent storage
A graphical web browser to view reports
On 32-bit versions of Vista, Windows Server 2008 and Windows 7, a driver is installed along with the binaries.
Acumem Freja supports both 32-bit and 64-bit Linux installations. Users running a 32-bit installation should use packages with the i486 architecture tag, users of 64-bit distributions should use the 64-bit packages with the x86_64 architecture tag. Using the 32-bit binaries on a 64-bit system may, depending on available system libraries, work, but limits data acquisition to 32-bit applications.
Users who are unsure of whether their installation is a 64-bit or 32-bit may issue the following command to determine that:
$ uname -m
The installation supports 64-bit applications if the output of the command is x86_64.
Acumem Freja supports several different installation methods on Linux. Choose the one that is most suitable for your system.
Users of systems using the RPM package manager should follow the instructions in Section 2.1.3.1, “Distributions with RPM Support”. These include, among others, the following distributions:
Red Hat Enterprise Linux
Fedora
CentOS
SUSE
Users of Debian, or distributions derived from Debian, should follow the instructions in Section 2.1.3.2, “Distributions with DEB Support”. The following distributions, among others, use the DEB packaging format:
Debian
Ubuntu
Users of other distributions, or users who wish to install Acumem Freja
in custom locations, may use the .tar.gz
packages described in Section 2.1.3.3, “Other Linux Distributions”.
Installing the RPM packages normally requires root access on
the target system. If you do not have root access on the
target system, you may still install Acumem Freja in your
home directory using the .tar.gz
packages described in Section 2.1.3.3, “Other Linux Distributions”.
Acumem Freja ships as two separate RPM packages, one for
the core product
(acumem-freja-
)
and an optional package containing the graphical user
interface
(version
.architecture
.rpmacumem-freja-gui-
). The
graphical user interface depends on the core product and can
not be installed separately.
version
.architecture
.rpm
The packages may be installed either by opening them from a graphical file manager and using the default package manager, or by issuing the following command as root:
$ rpm -Uvh acumem-freja-version
.architecture
.rpm \
acumem-freja-gui-version
.architecture
.rpm
The product is installed in
/opt/acumem/freja/bin
by default,
and a Gnome/KDE menu entry is installed for the GUI under
the "Programming" category.
Note that the installation package will not add
Acumem Freja to the default PATH
environment variable.
If you wish to uninstall Acumem Freja, issue the following command as root:
$ rpm -e acumem-freja-gui acumem-freja
Installing the DEB packages normally requires root access on
the target system. If you do not have root access on the
target system, you may still install Acumem Freja in your
home directory using the .tar.gz
packages described in Section 2.1.3.3, “Other Linux Distributions”.
Acumem Freja ships as two separate DEB packages, one for
the core product
(acumem-freja_
)
and an optional package containing the graphical user
interface
(version
.architecture
.debacumem-freja-gui_
). The
graphical user interface depends on the core product and can
not be installed separately.
version
.architecture
.deb
The packages may be installed either by opening them from a graphical file manager and using the default package manager, or by issuing the following command as root:
$ dpkg -i acumem-freja_version
.architecture
.deb \
acumem-freja-gui_version
.architecture
.deb
Ubuntu users don't normally have a separate root user, but may prefix commands with sudo to execute them as root, or run sudo -s to start a root shell. Execution of commands as root still requires the user to be "privileged", i.e. a member of the admin group.
The product is installed in
/opt/acumem/freja/bin
by default,
and a Gnome/KDE menu entry is installed for the GUI under
the "Programming" category.
Note that the installation package will not add
Acumem Freja to the default PATH
environment variable.
If you wish to uninstall Acumem Freja, issue the following command as root:
$ dpkg -r acumem-freja-gui acumem-freja
Users wishing to install Acumem Freja on a system without native RPM
or DEB support, or without root access, may use
the .tar.gz
packages instead of the other
packages. These packages lack desktop integration, which requires
files to be installed in system directories.u79
To install the software, simply decompress the package
(acumem-freja-
)
using the default graphical compression utility by double
clicking on the file, or by issuing the following commands:
version
.architecture
.tar.gz
$ tar -zxf acumem-freja-version
.architecture
.tar.gz
The command above decompresses Acumem Freja into the
directory
acumem-freja-
in the current working directory.
version
To uninstall the product, simply remove the directory containing the decompressed files.
Acumem Freja requires a valid license to run. There are two kinds of licenses, individual licenses, which are installed locally, and license server based licenses.
If a network based license server is used, each user must set up Acumem Freja to use the correct server. The easiest way is to use the license tool like this:
/opt/acumem/freja/bin/license --server acumem://host:port
Host should be the hostname or IP address of the machine running the license server, and port should be the TCP port the license server is using. This information should be provided by your system administrator.
This will remove any locally installed license file and set up a reference to the license server.
An alternative way to specify a license server without removing
local license files is to set the environment
variable ACUMEM_LICENSE_FILE
to the point to the
license server:
export ACUMEM_LICENSE_FILE=acumem://host:port
The normal way to specify environment variables is to put commands
in your
file. This file gets invoked for login shells, and also by common
window environments such as Gnome and KDE. Other systems may use
other files.
$HOME
/.bash_profile
You will get a
license file named license.dat
or
license.txt
from Rogue Wave Software. To use the
license you have to install it using the
license command from the Acumem Freja
package, usually installed as
/opt/acumem/freja/bin/license:
$ license license.dat
You have to accept the license agreement to install the
license. When the installation is finished the license is
installed
as
and the $HOME
/.acumem/licenselicense.dat
file is no longer
needed.
Acumem Freja will search for a license in the following locations in order of preference:
The license file or license server pointed to by
the ACUMEM_LICENSE_FILE
environment variable
$HOME
/.acumem/license
/etc/acumem/license