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:
|
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)
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 |
The initial setup of the database is done with the following commands:
|
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:
Parameter | Meaning | Value in this example | |
---|---|---|---|
1 | _softwareHome | UNC 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 | _dataHome | UNC 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 | _webServerList | Comma-separated list of all WEB application servers. | 'acd-jb1,acd-jb2' |
4 | _telServerList | Comma-separated list of all TEL servers that execute call flow applications. | 'acd-tel1' |
5 | _daemonServer | TEL server on which the management applications are executed. | 'acd-tel1' |
6 | _loadBalancer | Name of the server on which the role LB is executed. | 'acd-lb' |
7 | _https | TRUE , if the load balancer provides the services via HTTPS, FALSE if not | FALSE |
The following rules apply to UNC or path specifications:
|
The call is made using the following command:
|
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:
|