Deployment
All deploying files at inlong-dataproxy
directory.
Configuration
Configure Message Queue
- If you use InLong TubeMQ,
tubemq_master_list
is the rpc address of TubeMQ Master.
$ sed -i 's/TUBE_LIST/tubemq_master_list/g' conf/flume.conf
- If you use Apache Pulsar, replace
pulsar_server_url_list
inconf/flume-mulit-pulsar-demo.conf
and overwriteconf/flume.conf
.
notice that conf/flume.conf FLUME_HOME is proxy the directory for proxy inner data
Environment Preparation
sh prepare_env.sh
Configure InLong-Manager URL
configuration file: conf/common.properties
:
# manager web
manager_hosts=ip:port
run
sh bin/dataproxy-start.sh
check
telnet 127.0.0.1 46801
Add DataProxy configuration to InLong-Manager
After installing the DataProxy, you need to insert the IP and port of the DataProxy service is located into the backend database of InLong-Manager.
For the background database address of InLong-Manager, please refer to the deployment document of the InLong-Manager module.
The insert SQL statement is:
-- name is the name of the DataProxy, which can be customized
-- address is the IP of the DataProxy service is located
-- port is the port of the DataProxy service, default is 46801
insert into data_proxy_cluster (name, address, port, status, is_deleted, creator, create_time, modify_time)
values ("data_proxy_name", "data_proxy_ip", 46801, 0, 0, "admin", now(), now());