Start Installation
Please note that this installation program needs to correspond toApplication Service Version
We will provide you with a complete module package, which will be installed and deployed to run in your enterprise intranet environment.
The installation process takes approximately 40 to 60 minutes. If you accidentally close the terminal session midway, then re execute the installation command.
danger
If you do not have our product deployment package, you should contact our sales personnel.
Deployment Package Structure
tip
Whether it is a single node deployment or a multi node deployment, you only need to operate on the first machine to complete the installation normally.
If the language displayed during installation is not a commonly used language, you canChange installation display language
Assuming you have downloaded our product deployment package, you will see the following files in the current directory of the server:
xxxxxxxx-pvtadmin.json: (Pre check dependency files (names in each deployment package are inconsistent and end with a JSON suffix)
xxxxxxxx.tar.gz: (Product module package (corresponding to the name of the pre check dependency file, ending with the tar. gz suffix)
30day.lcs: (30 day trial authorization file)
checker-xxxx-xx-xx.tar.gz: (Pre check package, which needs to be associated with pre check dependency files)
caution
Due to the large size of the files, please move them to a directory with larger space, otherwise the installation will not be completed properly.
Due to content requirements, the file name may not match the one you downloaded. In actual deployment, simply change the file name obtained and execute the command.
Pre inspection
Decompression pre check package
tar xvf checker-xxx.tar.gz
tip
If an error is encountered during decompression, it is likely that the package was not fully downloaded. You can try downloading again
Installing the Python environment
tip
Bash install.sh [args]
Args:
--force : Optional Parameter, clear the previous python environment
bash install.sh
tip
If the result of executing the above command is inconsistent with the figure above, it indicates that there may be residual Python 3 environment in your environment
In order to complete the installation normally, it is recommended that you re execute the command and add the -- force Parameter to clear the previous python environment
Perform pre check
If the deployment language is not your common language, you can Change deployment language For your commonly used language. Unfortunately, currently only Simplified Chinese and English are supported
tip
**/ Usr/local/python-3.7.6/bin/python3 run.py -- check pre check dependency files**
Args:
前置检查依赖文件 : The pre examination dependency file mentioned in the front facial deployment package
/usr/local/python-3.7.6/bin/python3 run.py --check /root/79e698f55-pvtadmin.json
::: Info
Fill in key points
- Language version refers to language version information such as subsequent logos, login pages, etc
- If deployed on a single node and accessed only through an intranet IP, the load balancing IP is the server IP
- If a single node deployment requires public IP access, the server IP is the internal IP, and the load balancing IP is the public IP
- Multi node deployment requires filling in all node information. Load balancing IP is the actual lb IP
- If the login method of the client server is to log in with a private key, the absolute path of the private key needs to be filled in the password. For example:
/root/.ssh/id_rsa - The deployment directory is important, and all services will be installed in that directory. It is strongly recommended to set it as a separate folder. For example:
/data/laiye
:::
caution
Pre inspection will check if your server meets the deployment conditions. If it does not meet the requirements, it cannot be deployed normally
Of course, if the hardware difference is not significant. You can select forced deployment and add the -- force Parameter
If you encounter difficulties during the installation process, you can refer toInstallation troubleshooting
Installing Docker Environment
/usr/local/python-3.7.6/bin/python3 run.py --gen /root/79e698f55-pvtadmin.json
Run Installation
tip
This step takes a long time to install, please be patient and wait (About 40 minutes)
The path of the module package must be written as an absolute path, not as a relative path
If the pre check fails, you need to add the -- force Parameter to force deployment
If you encounter errors during the installation process, you can follow theTroubleshooting installation anomalies
/usr/local/python-3.7.6/bin/laipvt install -f /root/79e698f55.tar.gz
:::
Some services require the execution of compatible commands for
/usr/local/python-3.7.6/bin/laipvt -f /root/79e698f55.tar.gz
During installation, all logs will be output to the console, so this article only captures the starting and ending images 
info
Congratulations, if you see the above log output, it means that your service has basically been installed. Next, let's access it through the webpage.
Verify installation (product is WEP)
Based on the results returned in the above figure, use a webpage to access the corresponding service URL. The load balancing address of this instance is 192.168.10.54, and the personal deployment is changed according to the actual situation
info
| Platform Address | Login address | Default username/password | Remarks |
|---|---|---|---|
| Authorization Platform | http://192.168.10.54:8084/license -Manager/# | Admin/Acc123456 | Upload authorization file |
| Work Execution Platform | http://192.168.10.54:8084/portal/# | Admin/Acc123456 | Work Execution Platform |
| Unified management backend | http://192.168.10.54:8084/management/# | Admin/Acc123456 | Member management, role management, product management |
| Operations Management Platform | http://192.168.10.54:8084/admin -Console/#/tenat | Admin/Acc123456 | Organization management, tenant management, tenant allocation authorization |
Verify installation (when the products are IDP2.8 and Chatbot, as well as RPA products)
Based on the results returned in the above figure, use a webpage to access the corresponding service URL. The load balancing address of this instance is 192.168.10.54, and the personal deployment is changed according to the actual situation
info
| Platform Address | Login address | Default username/password | Remarks |
|---|---|---|---|
| Authorization Platform | http://192.168.10.54:8084/license-manager/# | Admin/Acc123456 | Upload authorization file |
| Personal Center | http://192.168.10.54:8084/identity/view/#/usercenter# | Admin/Acc123456 | Personal Center |
| Unified management backend | http://192.168.10.54:8084/identity/view/# | Admin/Acc123456 | Member management, role management, product management |
| Operations Management Platform | http://192.168.10.54:8084/view/tenant/ | Admin/Acc123456 | Organization management, tenant management, tenant allocation authorization |
Sample Page Image (WEP)
Work Execution Platform
Operations Management Platform
Unified management backend
Sample Page Image (RPA)
Laiye Automation Commander Page
If you are unable to access the webpage after the installation is completed, you can use theRunning troubleshooting
At this point, our installation work is complete