You are here: Installing a Repository Server

Installing a Repository Server

A Repository Server allows you to maintain a repository of firmware components in a decentralized way.

The (virtual) machine, which is installed using the Repository Server software product, serves as a proxy server for those monitored managed nodes which do not have a connection to the internet.

The download process using the Repository Server is completely independent from the update of the managed nodes.
Administrators may receive email messages about the download progress and error situations.

The managed nodes connect to the Repository Server to receive the necessary updates for their firmware components.

The Repository Server

The Repository Server can also be used to provide the repository for the Update Manager.
In this case the Management Station plays the role of a Managed Node (as shown in the picture above).

Requirements for installation (Linux)

All requirements are checked by the preinstall script.

Installing the Repository Server

Start the installation of the Repository Server with the following command:
rpm -i RepServer-<version>.i686.rpm

By installing the RPM package, the current Linux system becomes a Repository Server.

A new directory /opt/fujitsu/ServerViewSuite/RepServer directory is created during the installation process.
It contains all the executable files and the configuration files needed for the Repository Server.

After the installation process, the following configuration changes are made by the postinstall script:

The first download is scheduled to start at the earliest one hour after installation and is repeated every day at the same time.
The first download may take about 2 hours as the complete repository is loaded.
Subsequent downloads only take an average of 5 minutes as only new and changed versions are loaded.
The required disk space for the local repository in the $RootRepPath directory is 10 GB. ($RootRepPath is defined in the configuration file, see below.)

Configuring the Repository Server

After the installation process is completed, you need to check the installation and to modify the configuration values in the
/opt/fujitsu/ServerViewSuite/RepServer/cfg/RepServer.conf configuration file to your needs.

The configuration file consists of two parts:

The following parameters of the configuration file may be adjusted to the customers needs (see also the explanatory notes in the configuration file):

Values in the expert section of the configuration file should be left unchanged to avoid damage (e.g. the modification of
RootFujitsuRepServer may cause that the firmware download will be initialized!).

You may also modify the cron job in the crontab of root. But this takes only effect for the next start of the download application. To make permanent changes for the cron job, the CronJob parameter in the configuration file must be modified accordingly. The reason is, the download application will always restore the crontab entry from the configuration file upon its next activation.

The configuration file is interpreted every time the download application is activated manually or by the cronjob scheduler.

Updating the Repository Server

The Repository Server functionality is updated with the following command:
rpm -U RepServer-<version>.i686.rpm

The current firmware repository and the former Repository Server configuration remain unchanged during the update.

Uninstalling the Repository Server

The Repository Server functionality is uninstalled by removing the RPM package.

The current firmware repository remains unchanged during remove of the package. Please remove the repository manually if its obsolete.

A reinstall of the Repository Server will restore the link from the Apache web page to the former repository when it is left untouched! Thus an update installation will renew the tools but it will update and provide the repository already present.

Working with the Repository Server

The Repository Server does not have a graphical user interface.
It is started periodically as a cron job by the Crontab Scheduler.

It can also be started manually from the console window using the command line interface:

downloadApplication [-t] [-i]

-t

Trace flag on

-i

Interactive flag on


downloadApplication -h displays the usage message.

The cron job can be called for example as follows:
/usr/bin/downloadApplication.sh -t

After correct installation, the Repository Server does not need any monitoring or maintenance.
Any administrative actions shall be done via the RepServer.conf configuration file and the Linux operating system.
© Fujitsu Technology Solutions ServerView System Monitor Help