eXperDB

Full usage is available on https://marketplace-logo-inzent.s3.ap-northeast-2.amazonaws.com/eXperDB-v15.4+user-guide.docx 

1. Fundamentals eXperDB-v15.4 is postgresql-v15.4, same database. This product has eXperDB-v15.4, eXperDB-Management, eXperDB-Management-Agent, eXperDB-Monitoring installed. eXperDB packages is installed. Server user(experdb) already exists. Product use-case is DB Server and Management Server.

2. AWS Create EC2-Instance 2-1.Select the instance type for which SQL commands are available. 2-2.AWS key-pair create or select. 2-3.Select network auto public IP check or set the private IP to be accessible to user. 2-4.Set security group. 2-5.Set instance volume(default: 50GB). 2-6.Wait for the health check of the created instance to complete.

3. eXperDB Start(DB and Management) 3-1.Access Server with SSH(port 22) key-pair and user ec2-user(pw ec2-user) 3-2.sudo su - experdb command change user ec2-user - experdb. All task execute(chapter 3~6) commands with the experdb account. 3-3.Set the postgresql.conf for server CPU and Memory (default 4core 16GB) 3-4.start eXperDB(command: pg_ctl start) 3-5.Check eXperDB Status(command:pg_ctl status) Result is pg_ctl: server is running (PID: 00000), it is normal. If result is pg_ctl: no server running, it is abnormal.

4. MGMT-WebConsole Start(Management Server) 4-1. All task execute(chapter 3~6) commands with the experdb account. Management Server eXperDB is running(executed Chapter3). MGMT is short for Management 4-2.cd /experdb/app/eXperDB-Management/eXperDB-Management-WebConsole/bin After sh startup.sh this command is start WebConsole. 4-3.Check WebConsole status(command: ps -ef | grep WebConsole) Result is apache.catalina.startup.Bootstrap start process exists, it is normal. Result is no process exists, it is abnormal. 4-4.Web http://(managment server IP):8880/ access it, you will see a login page. First login, you will change PW popup, Retry log in after change PW. Default ID/PW: admin/experdb12#

5. Monitoring Start(Management Server) 5-1. All task execute commands with the experdb account. Management Server eXperDB is running. MGMT is short for Managment 5-2.cd/experdb/app/eXperDB-Monitoring/eXperDB_Server/ After sh experdbmon.sh start this command is start Monitoring-Server. 5-3.Check Monitoring status(command: sh experdbmon.sh now) Result is two monitoring process exists, it is normal. 5-4.After Monitoring Client install, install file is here(eXperDB github: https://github.com/experdb/eXperDB-Monitoring ) 5-5.When running the Monitoring client, IP and DB port settings are required. 5-6.First login, you will change PW popup, Retry log in after change PW. 5-7.Please refer to the Monitoring guide for functions such as instance registration.

6. Management-Agent Start(DB-server) 6-1. All task execute(chapter 3~6) commands with the experdb account. Management Server eXperDB is running(executed Chapter3). 6-2.cd /experdb/app/eXperDB-Management/eXperDB-Management-Agent/bin sh startup.sh command start eXperDB-Management-Agent 6-3.Check Agent status(command: sh status.sh) Result is Program : "eXperDB-Management-Agent .. status : running", it is normal. Result is Program : "eXperDB-Management-Agent .. status : stop", it is abnormal. 6-4.client start, First login, you will change PW popup, Retry log in after change PW. (default: admin/experdb12#) 6-5.Login WebConsole top menu admin > DBMS registration > registration 6-6.Please refer to the solution guide for detailed features