. . .

Suse package installation

This guide will lead you through the installation of the ApiOmat .rpm package for Suse linux. The package is supported for the OS versions defined in Infrastructure Requirements.

Installing MongoDB

ApiOmat is based on MongoDb database. MongoDB can be also installed via yum:

Installing ApiOmat

Installation from Yum repository

If your installation machine has internet access, add the ApiOmat Yum repository to your system ( replace **** with the password provided via email):

sudo zypper addrepo ftp://f00c6540:****@apiomat.com/suse "ApiOmat"

Now, run

sudo zypper refresh
sudo zypper --no-gpg-checks --non-interactive install apiomat-yambas
sudo zypper --no-gpg-checks --non-interactive install apiomat-dashboard2.suse

Installation with rpm files

If you obtained the installation files manually, copy the .rpm packages of YAMBAS and Dashboard to the application server(s) and enter:

sudo zypper install apiomat-yambas-xxx.rpm
sudo zypper install apiomat-dashboard2.suse-xxx.rpm

After Dashboard installation, you will be asked to open http://localhost/dashboard/install in your browser. Follow the steps in this installer tool to configure ApiOmat automatically.

Reboot afterwards to start all services automatically.

Beta - Installing Dashboard 3

sudo zypper --no-gpg-checks --non-interactive install apiomat-dashboard.suse
#or with rpm-file
sudo zypper install apiomat-dashboard3.suse-xxx.x86_64.rpm

The installation path is /opt/aom-dashboard3.

If you are installing dashboard 3 besides dashboard 2, then you have to configure the alias of both dashboards in its vhost files (/etc/apiomat/apiomat-dashboardX.conf) in this way:

Alias /d2 "/opt/aom-dashboard/site/apiomat/"
<Directory "/opt/aom-dashboard/site/apiomat">
AllowOverride All
...
Alias /d3 "/opt/aom-dashboard3/site/apiomat/"
<Directory "/opt/aom-dashboard3/site/apiomat">
AllowOverride All
...

After editing the .conf-files the apache service needs to be restarted.

With this configuration the 2 versions of dashboard would be accessible on localhost/d2 and localhost/d3.

Next steps

Installing Monitoring Service (optional)

ApiOmat microservices require a Java8 runtime to be installed. If Java8 was not installed before (YAMBAS includes an installation) it has to be installed manually (please use the newest patch provided by Oracle):

wget --header 'Cookie: oraclelicense=accept-securebackup-cookie' http://download.oracle.com/otn-pub/java/jdk/8u102-b14/jdk-8u102-linux-x64.rpm
sudo zypper --non-interactive in jdk-8u102-linux-x64.rpm

ApiOmat is able to monitor server data like CPU load or disk space. To enable this feature, a central service registry has to be installed on one node in the cluster:

sudo zypper --no-gpg-checks --non-interactive install apiomat-serviceregistry

Additionally, a monitoring service has to be installed on each node (app and database) which should be monitored:

sudo zypper --no-gpg-checks --non-interactive install apiomat-monitoringservice

By default, the services are not added to any runlevel. To automatically start the services after reboot, execute the following commands:

sudo chkconfig --level 345 apiomat-serviceregistry
sudo chkconfig --level 345 apiomat-monitoring

In the next step, you have to check the Java version: Oracle Java 8 is required (do not use OpenJDK).

Finally, start the services and make sure the service registry is fully started (http://localhost:8761/ is reachable) before you start the monitoring service:

sudo /etc/init.d/apiomat-serviceregistry start
sudo /etc/init.d/apiomat-monitoringservice start

Checks

YAMBAS

  • Logs: /var/log/tomcat/catalina.out

  • http test: http://<HOSTNAME>:8080/yambas/rest - should print the version number

Dashboard

  • Logs: /var/log/apache

  • http test: http://<HOSTNAME>/dashboard

Monitoring Services

  • Logs:

    • /var/log/apiomat-monitoringservice.log

    • /var/log/apiomat-serviceregistry.log

Please visit the FAQ section for questions and solutions.

* link only available in Enterprise Documentation