Debian-based online installation

Online installation

If the system has access to the internet it is recommended to use the apt repositories provided by ITEG.

Prequisites

First make sure all the installation tools and helpers are installed:

sudo apt install wget apt-transport-https ca-certificates unzip

Most systems will just tell you that those are already installed, that's fine.

Repository signing keys

To trust the signing keys used by ITEG's repositories the respective keyrings need to be installed:

cd /tmp
wget https://deb.clazzes.org/clazzes.org-archives-keyring.deb https://deb.iteg.at/iteg-archives-keyring.deb
sudo dpkg -i clazzes.org-archives-keyring.deb iteg-archives-keyring.deb
rm -v clazzes.org-archives-keyring.deb iteg-archives-keyring.deb

INFO

The core svc-runner is open source with everything beeing freely available on deb.clazzes.org, but most applications are closed source and are provided on deb.iteg.at.

Apt sources *.sources

To make the apt repositories for svc-runner and several ITEG-provided requirements known to the system we need to put some .sources files in the /etc/apt/sources.list.d directory:

sudo wget --directory-prefix=/etc/apt/sources.list.d \
    https://deb.clazzes.org/any/sources.list.d/any/any-clazzesorg-1.sources \
    https://deb.clazzes.org/any/sources.list.d/any/any-jmod-1.sources \
    https://deb.clazzes.org/any/sources.list.d/any/any-svcrunner-1.sources \

INFO

Most applications will require additional apt sources, i.e. additional .sources. The URLs of those can be found in the application specific documentation.

Details

The starting point for svc-runner-based ITEG products are:

  https://deb.iteg.at/any/sources.list.d/any/any-itegizer-1.sources \
  https://deb.iteg.at/any/sources.list.d/any/any-svcutil-1.sources \

Further candidates for bomtools integration are:

   https://deb.clazzes.org/any/sources.list.d/any/any-bomtools-1.0.sources \
   https://deb.clazzes.org/any/sources.list.d/any/any-jartools-1.0.sources \
   https://deb.clazzes.org/any/sources.list.d/any/any-pytools-1.sources \
   https://deb.clazzes.org/any/sources.list.d/any/any-xpkg-1.sources \
   https://deb.clazzes.org/debian/sources.list.d/bookworm/bookworm-xpkg-1.sources \
   https://deb.clazzes.org/debian/sources.list.d/bookworm/trixie-xpkg-1.sources \

Installing SVC-Runner

To install the basic svc-runner perform this:

sudo apt update

sudo apt install --no-install-recommends \
      clazzes.org-archives-keyring \
      jmod-aop-util \
      jmod-clazzes-aopalliance \
      jmod-clazzes-deps-bc \
      jmod-clazzes-deps-core \
      jmod-clazzes-deps-jdbc \
      jmod-clazzes-deps-http \
      jmod-clazzes-deps-mail \
      jmod-clazzes-persistence \
      jmod-clazzes-transaction \
      jmod-clazzes-util \
      jmod-fancymail \
      jmod-htpasswd-jaas \
      jmod-http-util \
      jmod-jackson-rpc2 \
      jmod-jbo-login \
      jmod-jdbc2xml \
      jmod-login \
      jmod-sched-util \
      jmod-sql-util \
      openjdk-21-jre-headless \
      svc-api \
      svc-runner-docker \
      svc-runner-jdbc \
      svc-runner-jetty \
      svc-runner-mariadb \
      svc-runner-monitoring \
      svc-runner-mssql \
      svc-runner-oracle \
      svc-runner-postgres \
      svc-runner-server \
      svc-runner-sshd

# feel free to add further recommended tools:
sudo apt install --no-install-recommends \
      curl \
      fping \
      iputils-ping \
      less \
      lsof \
      nano \
      net-tools \
      screen \
      tmux \
      nvi

WARNING

Access to some directories on deb.iteg.at is restricted. Customers need either a fixed range of IP addresses (that we have allowed access from on request) or to use a user and password (which we have configured and provided on request).

Configuration

When installing svc-runner for the first time then configuration work is required, i.e. editing and eventually creating files in subdirectories of /etc/svc-runner/.

For basic configuration information see SVC-Runner Configuration Basics.

For application specific configuration details please look at the application documentation.