Sv translation | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Installation of required additional softwareInstall GITGit is required, to checkout the software and the default mysql-client is required (for running the update scripts).
Configure GIT proxy server (optional)If you need a proxy for GIT:
Downloading the jtel software for the first timeNote: for redundant systems, do this on the ACTIVE storage node. Change to jtel UserThe 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:
Clone jtel SoftwareNext, the jtel Software is cloned. This will be done in 2 steps, as a user name and password is required for each one.
Clone Customer SoftwareIf 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:
Change to required Software ReleaseIn the downloaded software repositories, the software release to be used must now be selected. In this case it is release 3.20:
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 DirectoriesThe last step is to create the directories for central logging, standard data import and the main data directory:
Cleaner processesA CRON job is used to clean up the directories of the portal. With redundancy, configure this on both STORE. Since the directory is only mounted on one, but we don't know which one is active, the command must be executed on both. Note: execute as ROOT.
|
...