You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Installation of required additional software

Note: for redundant systems, do this on BOTH storage nodes.

Additional software must be installed to provide and update the jtel software repository. Since this can not only be obtained from the official CentOS package sources, other software sources must be configured:

Install additional software sources - MySQL 8.x.
yum -y install https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm
Install additional software sources - MySQL 5.6
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.

Install and configure GIT
yum -y install git2u mysql-community-client
su jtel
cd
git config --global user.name "jtel Support"
git config --global user.email "support@jtel.de"


If you need a proxy for GIT:

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 nodes.

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:

Change user context
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:

New Repository Locations

Attention: new repository URLs - see here: New Repository Locations

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


In the event that specific adaptations or extensions have been programmed for the customer, the customer-specific software repository must also be downloaded. This is done exemplarily by a command which is structured as follows:

Download a custom repository
cd /srv/jtel/shared
git clone https://bitbucket.org/jtelgmbh/cacme/software.git acme

Both the source URL and the target directory are customer-specific in this case and differ from case to case.

In the downloaded software repositories, the software release to be installed at the customer must now be selected. In this case it is release 3.14:

Select the desired release
cd /srv/jtel/shared/JTELCarrierPortal
git checkout release/stable-3.18
cd /srv/jtel/shared/JTEL
git checkout release/stable-3.18
cd /srv/jtel/shared


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

Prepare data directories
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.

Cleaner processes in /etc/cron.daily
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
  • No labels