Start/stop RPA service
Start RPA service
It is assumed that RPA Service is installed as ipaadm, Tomcat is installed as ipaadm, MariaDB is installed as ipadb, and the installation folder is /rpa. You must follow the startup sequence to start the service. Follow the steps below to launch Brity RPA v3.0.0. The startup sequence is MariaDB → ActiveMQ → RPA Services → Tomcat, and be sure to follow the startup sequence. If it is to be started for the first time after the complete installation, MariaDB is already started during the installation stage. (recommended to check with ps command) Follow the steps below for operational start-up procedures other than the first complete installation.
First, start MariaDB with the ipadb account as follows.
(If MariaDB is installed with the ipaadm account, proceed su with the ipaadm account)
su ipadb cd /rpa/bin ./mysql-start.sh
The prompt does not automatically drop even if it is completed, so hit enter once to exit and check the process as shown below.
Check the process to see if MariaDB started normally.
ps -ef|grep mariadb
2. Start ActiveMQ with the ipaadm account as follows.
su ipaadm cd /rpa/bin ./activemq-run.sh
Check the process to see if ActiveMQ is displayed normally.
ps -ef|grep activemq
3. Next, start the RPA services as follows with the ipaadm account.
There are two startup shell scripts for RPA service as follows.
N/A
run.sh : Provides Y/N selection through prompt whether to start all services.
Among RPA services, it is possible to start by designating only one specific service as an argument.
Example) ./run.sh core
N/A
run-y.sh : All services are started sequentially immediately after execution without prompt confirmation.
cd /rpa/bin ./run.sh or ./run-y.sh
When all RPA services are started, you can see that 5 Spring Boot loading logos appear in a row in the console window. It does not show a prompt after completion, so please press Enter once
Check the process to see if all RPA services are up normally.
cd /rpa/bin ./ps-rpa.sh
A normal startup is completed if all 8 RPA services are floating as processes, as shown below.
Among RPA services, if you want to check the server.log log file of a specific service with a tail, you can use the log.sh shell script.
Arguments defining each service are as follows.
auth : auth authentication service
core : core service
comm : communication service
gateway : API gateway service
scheduler : scheduler service
tenant : tenant service
textrecognitionServer : OCR service
workflow : workflow service
cd /rpa/bin ./log.sh core
4. Finally, continue with the ipaadm account and start Tomcat, as shown below.
cd /rpa/bin ./tomcat-run.sh
"Tomcat started." is displayed, Tomcat is running. Check out the process as below.
ps -ef|grep tomcat
To check the log tail to see if Tomcat is running normally without errors internally, proceed as follows.
cd /rpa/logs/admin tail -f catalina.out
5. Check if you can access the portal below normally.
Admin Portal: https://Server IP:8080/admin
User Portal: https://Server IP:8080/user
Tenant Portal: https://Server IP:8080/tenant
FindID
RPA Service Interruption
It is assumed that the RPA service is installed as ipaadm, Tomcat is installed as ipaadm, MariaDB is installed as ipadb, and the installation folder is /rpa.
The interrupt sequence proceeds in the reverse order of the start.
Tomcat → RPA service → ActiveMQ → MariaDB proceed in the order, and be sure to follow the startup sequence.First, stop Tomcat with the ipaadm account, as shown below.
su ipaadm cd /rpa/bin ./tomcat-stop.sh
Check the process to see if Tomcat has stopped gracefully.
ps -ef|grep tomcat
If nothing appears in the result of the ps command other than the contents of grep, then it has ended normally.
2. Continue with your ipaadm account and stop all RPA services as shown below.
su ipaadm cd /rpa/bin ./stop.sh
For reference, in the stop.sh shell script, it is possible to stop only that service by specifying one desired RPA service as an argument. (eg ./stop.sh comm)
Check the process to see if the RPA services are stopped normally.
cd /rpa/bin ./ps-rpa.sh
If nothing appears in the result of running ps-rpa.sh, all RPA services are normally stopped.
3. Continue with the ipaadm account and stop ActiveMQ as shown below.
cd /rpa/bin ./activemq-stop.sh
After checking the screen that says ".. TERMINATED", check the process to see if ActiveMQ is normally stopped.
ps -ef|grep activemq
If nothing appears in the result of the ps command other than the contents of grep, it has ended normally.
4. Finally, stop MariaDB with your ipadb account as shown below.
(If MariaDB is installed with the ipaadm account, su to the ipaadm account)
su ipadb cd /rpa/bin ./mysql-stop.sh
Check the process to see if MariaDB has stopped gracefully.
ps -ef|grep mariadb
If nothing appears in the result of the ps command other than the contents of grep, then it has ended normally.
License activation
Access Tenant Portal
Log in to the Tenant Portal (https://server IP:8080/tenant) to register your license. You can log in as admin / superadmin!23 for the first installation. Click the bottom of the page to display the user information window.
Tenant1
Click About to check the server process status in the "About" pop-up window. If you see all versions, it means that the server process is running.
서버 상태 확인
License activation
Click Licenses > Manage Tenant Licenses.
On the "Tenant Licenses Setting" page, click Apply License.
테넌트 라이선스 관리
Register the license by uploading the license file in the "Apply License" pop-up window.
라이선스 적용 팝업
Click Unapplied to change to applied status. A successful license registration will generate license keys for the bot and designer.
If the server MAC address of the issued license is incorrect, it will not be changed to Apply. In this case, you need to check the issued license and the MAC address of the actual device and reissue the license.
Click OK to complete the license application.
A successful license registration will generate license keys for the bot and designer.
Click on the BASE TENANT card to
go to the tenant license setting page.
테넌트 라이선스 관리
Select and add a license to set in BASE TENANT.
라이선스 테넌트라이선스관리 테넌트라이선스설정
Log in to the Admin Portal (https://server IP:8080/admin).
ID: admin
PW: superadmin!23
Go to Menu > System > Group auth. mgmt.
Click the admin group in the user group and change it to 'Y'.
Group Auth.
For information on additional settings for each group, refer to the Administrator's Manual.
Go to Menu > System > License Mgmt. The assigned licenses are displayed in the tenant portal.
라이선스 관리 현황
After installing the bot on your Windows PC for the bot, enter the server IP and license key to activate it.
After installing the designer on your Windows PC for designers, enter the server IP and license key to activate it.
For more information on creating and running processes, refer to the user manual.
SMTP settings
You can set to use e-mail for user registration and password recovery.
The SMTP server must be ready, and port 25 between the RPA server and the SMTP server must be open.
To set up SMTP, follow the steps below.
1. Click Configuration Mgmt. in the Tenant Portal.
SMTP1
2. In the "Configuration Mgmt." page on the left menu, click EMAIL.
SMTP1
3. In the "Configuration Mgmt." pop-up window, enter the SMTP server address to use and click Save.
SMTP2
SMTP3
4. On the "Configurating Mgmt." page, click Email Function test at the top right of the list.
5. In the "Email Function test" pop-up window, enter the email, password, and recipient to test and click Run.
No | Description |
|---|---|
1 | Enter the mail account you want to use. |
2 | Enter the password for the mail account you want to use. |
3 | Enter the mail account to receive the test mail. |
6. If the test is successful, click OK to save the values to be changed. If it fails, adjust the setting value according to the failed message.