Initial setup of the system data

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. 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 user jtel. 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-db1 ~]$ (The system prompt consists of username@hostname current directory)

In principle, the initial setup of the system data can be done from any Linux machine, because every machine has access to the database scripts and has a MySQL client. For performance reasons, however, it is advisable to perform this operation on the primary DATA server, as this way the network load is lowest and the initial setup is quick.


ATTENTION

If this operation is to be performed from another machine, it is essential that the primary DATA server is specified as the target server. The following example assumes that the operation is performed on the primary DATA server, so the target server is localhost.

The initial setup of the database is done with the following commands:

Initial setup of the database
cd /home/jtel/shared/JTELCarrierPortal/DB/mySQL/init
mysql -h localhost -u root -p<password> -vvv -f -n -q -e"source Init.sql"

After the first initialization, some values must still be adapted to the system environment. To simplify this, a special database procedure is called, which makes almost all the necessary adjustments for a standard system. This procedure must be given the following parameters:


ParameterMeaningValue in this example
1_softwareHomeUNC of the directory in which the jtel system stores all data. There you will find e.g. the directories Data, LogFiles and LogFilesCall.'//acd-lb/shared/'
2_dataHomeUNC of the directory in which the jtel system finds all program files. There you will find e.g. the directories JTELCarrierPortal and JTEL.'//acd-lb/shared/'
3_webServerListComma-separated list of all WEB application servers.'acd-jb1,acd-jb2'
4_telServerListComma-separated list of all TEL servers that execute call flow applications.'acd-tel1'
5_daemonServerTEL server on which the management applications are executed.'acd-tel1'
6_loadBalancerName of the server on which the role LB is executed.'acd-lb'
7_httpsTRUE, if the load balancer provides the services via HTTPS, FALSE if notFALSE

ACHTUNG

The following rules apply to UNC or path specifications:

  • The separator is a "/ (slash)" and no "\ (backslash)"
  • The paths must end with /.

The call is made using the following command:

Values to the system environment
mysql -u root -p<password> -v -e "CALL JTELWeb.Hardstyle_ReconfigureFullSystem('//acd-store/shared/','//acd-store/shared/','acd-jb1,acd-jb2','acd-tel1','acd-tel1','acd-lb',FALSE)"

At the end of each installation, the database update scripts should be run once through the database, because the init.sql script does not necessarily contain all the latest routines.

This is done with the following commands, viewed from the STORE role:

Carry out DB and release update
su jtel
cd /home/jtel/shared/JTELCarrierPortal/Update
sudo ./update_release.sh
  • No labels