Standalone

Environment Requirements

• MySQL 5.7+
• Flink 1.13.5
• Docker 19.03.1+

Prepare Message Queue

InLong Support the following Message Queue services now, you can choose one of them.

• InLong TubeMQ
• Apache Pulsar 2.8.x

Download the Binary Package

You can get binary package from Download Page ,or you can build the InLong refer to How to Build.

Extract apache-inlong-[version]-bin.tar.gz and apache-inlong-[version]-sort-connectors.tar.gz, and make sure the inlong-sort/connectors/ directory contains sort-connector-[type]-[version].jar.

DB Dependencies

• If the backend database is MySQL, please download mysql-connector-java-8.0.27.jar and put it into the following directories:

inlong-agent/lib/
inlong-audit/lib/
inlong-manager/lib/
inlong-tubemq-manager/lib/

• If the backend database is PostgreSQL, there’s no need for additional dependencies.

Configure

In conf/inlong.conf, configure the parameters according to the actual situation, mainly include:

# local IP
local_ip=
# Configure MySQL
spring_datasource_hostname=
spring_datasource_port=3306
spring_datasource_username=root
spring_datasource_password=inlong
# Configure Pulsar or TubeMQ Address
# the REST server address for Flink
flink_rest_address=
# the REST server Port for Flink
flink_rest_port=8081

Start

bin/inlong-daemon start standalone

Register Message Queue

You can register message queue for Manger according to Register MQ Cluster.

Check

After all component run successfully, you can access http://localhost with default account:

user: admin
password: inlong