yumdnf -y install https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm

yum -y install http://dev.mysql.com/get/mysql-community-release-el6-5.noarch.rpm

The required software can then be installed and configured. The configuration is done under the user jtel.

yum -y install git2u mysql-community-clientgit
su jtel
cd
git config --global user.name "jtel Support"
git config --global user.email "support@jtel.de"

Configure GIT proxy server (optional)

If you need a proxy for GIT:

git config --global http.proxy http://<proxy_server>:<port>

Downloading the jtel software for the first time

Note: for redundant systems, do this on the ACTIVE storage nodesnode.

Change to jtel User

The following operations are no longer performed in the context of the root user but must be performed in the context of the jtel user. To do this, you can either log in as user jtel in a separate SSH session or, if you are already logged in as user root, you can switch to the context of the jtel user. This is done with the following command:

su jtel
cd

After entering these commands you can recognize the user change at the system prompt, which is now [jtel@acd-lb ~]$ (the system prompt consists of username@hostname current directory) The next step is to download the two software repositories with the jtel standard software.

This is done by entering the following commands:

Clone jtel Software

cd /srv/jtel/shared
git clone https://bitbucket.org/jtelgmbh/jtel.git JTEL
git clone https://bitbucket.org/jtelgmbh/jtelcarrierportal.git JTELCarrierPortal

Clone Customer Software

If specific software has been programmed for the customer, the customer-specific software repository must also be downloaded. This is done

by a command which is structured as follows, for the example customer acme:

cd /srv/jtel/shared
git clone https://bitbucket.org/jtelgmbh/cacme/-software.git acme

Change to required Software Release

In the downloaded software repositories, the software release to be

used must now be selected. In this case it is release 3.

20:

cd /srv/jtel/shared/JTELCarrierPortal
git checkout release/stable-3.1820
cd /srv/jtel/shared/JTEL
git checkout release/stable-3.1820
# For customer specific software only
# cd /srv/jtel/shared/acme
# git checkout develop
cd /srv/jtel/shared

Note, that the customer specific release is usually develop, as customer releases are not branched or tagged when the jtel Software is branched or tagged.

Create Required Directories

The last step is to create the directories for central logging, standard data import and the central main data directory:

cd /srv/jtel/shared
mkdir -p LogFiles LogFilesCall Import/{Clients,ServiceNumbers}/{Done,In,Problems}
cp -a JTELCarrierPortal/Data .
cp -a JTEL/Data/system/gui Data/system
cd /srv/jtel/shared/JTELCarrierPortal/Update
bash ./get_binaries.sh

Cleaner processes

A CRON job is required to clean up the directories of the portal. 

With redundancy, on both STORE. Since the directory is only mounted on one, but we don't know which one, the command must be executed on both.

Caution: as ROOT.

cat <<EOFF > /etc/cron.daily/jtel_portal_cleaner.sh
find /srv/jtel/shared/Data/clients/*/reports -type f -mtime +2 -delete
EOFF
chmod +x /etc/cron.daily/jtel_portal_cleaner.sh

...