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 token provided via email):
sudo
zypper addrepo https:
//repo
.apiomat.com
/yambas/rest/web/Repo/LIVE/suse
?token=***********
"ApiOmat"
add php7 repository - if you want to use php5, you don't need this step, but then you have to use the apiomat-dashboard.suse.php5 package
#for openSUSE:
sudo
zypper addrepo http:
//download
.opensuse.org
/repositories/devel
:languages:php
/openSUSE_Leap_42
.3
/devel
:languages:php.repo
#for SUSE SLE
sudo
zypper addrepo http:
//download
.opensuse.org
/repositories/devel
:languages:php
/SLE_12/devel
:languages:php.repo
# add php7.0 repo
zypper addrepo --no-gpgcheck http:
//download
.opensuse.org
/repositories/devel
:
/languages
:
/php
:
/php70/openSUSE_Leap_42
.3
/devel
:languages:php:php70.repo
zypper refresh
# add libmcrypt for php-mcrypt module
wget http:
//download
.opensuse.org
/repositories/home
:
/AndnoVember
:
/test/openSUSE_Leap_15
.0
/x86_64/libmcrypt-2
.5.8-lp150.1.1.x86_64.rpm
rpm -Vp libmcrypt-2.5.8-lp150.1.1.x86_64.rpm
rpm -ivh libmcrypt-2.5.8-lp150.1.1.x86_64.rpm
Now, run
sudo
zypper refresh
sudo
zypper --no-gpg-checks --non-interactive
install
apiomat-yambas
sudo
zypper --no-gpg-checks --non-interactive
install
apiomat-dashboard.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-dashboard.suse-xxx.rpm
With Suse 15 some PHP dependencies have changed, so you also have to install the php-json package:
# only for Suse 15!
zypper -y
install
php-json
sudo
service apache2 restart
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.
Next steps
-
Change SuperAdmin password in apiomat.yaml
-
Change Default Organization password in apidocs and apiomat.yaml
-
Obtain a license key
-
Run the graphical installer
Installing Monitoring Service (optional)
ApiOmat microservices require a Java 8 runtime to be installed. If Java 8 was not installed before (YAMBAS includes an installation) it has to be installed manually: AdoptOpenJDK Installation
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.