Deployment

Environment Requirements

  • Install and start MySQL 5.7+

  • initialize database there is sql/apache_inlong_manager.sql in inlong-manager directory, load this file through the following command to complete the initialization of the table structure and basic data

    1. # initialize database：
    2. mysql -uDB_USER -pDB_PASSWD < sql/apache_inlong_manager.sql

Dependencies

  • If the backend database is MySQL, please download mysql-connector-java-8.0.27.jar and put it into lib/ directory.
  • If the backend database is PostgreSQL, there’s no need for additional dependencies.

Configuration

Go to the decompressed inlong-manager directory and modify the conf/application.properties file:

  1. # manager service port number
  2. server.port=8083
  4. # The configuration file used is dev
  5. spring.profiles.active=dev

The dev configuration is specified above, then modify the conf/application-dev.properties file:

  1. spring.datasource.druid.url=jdbc:mysql://127.0.0.1:3306/apache_inlong_manager?useSSL=false&allowPublicKeyRetrieval=true&characterEncoding=UTF-8&nullCatalogMeansCurrent=true&serverTimezone=GMT%2b8
  2. spring.datasource.druid.username=root
  3. spring.datasource.druid.password=inlong

InLong support to start a Sort task by Manager, you need to configure a Flink environment in the plugins/flink-sort-plugin.properties.

  1. # Flink host split by coma if more than one host, such as 'host1,host2'
  2. flink.rest.address=127.0.0.1
  3. # Flink port
  4. flink.rest.port=8081
  5. # Flink jobmanager port
  6. flink.jobmanager.port=6123
  7. # InLong Audit Proxy Address
  8. metrics.audit.proxy.hosts=127.0.0.1:10081

Start

  1. bash +x bin/startup.sh

Register Message Queue

  • If using InLong TubeMQ, the register command is:
  1. curl --header "Content-Type: application/json" --request POST http://localhost:8083/api/inlong/manager/openapi/cluster/save --data '
  2. {
  3.         "name": "tube_cluster",
  4.         "type": "TUBE",
  5.         "mqSetName": "default_set_name",
  6.         "extParams": "{\"cluster_tube_manager\": \"127.0.0.1:8080\", \"tube_masterUrl\": \"127.0.0.1:8715\", \"cluster_tube_clusterId\": \"1\"}",
  7.         "inCharges": "admin"
  8. }'
  • extParams: the other info of your cluster. It is described in JSON format, for example:
  1. {
  2.   "cluster_tube_manager": "http://127.0.0.1:8081",
  3.   "tube_masterUrl": "127.0.0.1:8715",
  4.   "cluster_tube_clusterId": "1"
  5. }
  • If using Pulsar, the register command is:
  1. curl --header "Content-Type: application/json" --request POST http://localhost:8083/api/inlong/manager/openapi/cluster/save --data '
  2. {
  3.         "name": "pulsar_cluster",
  4.         "type": "PULSAR",
  5.         "url": "pulsar://pulsar:6650",
  6.         "token": "null",
  7.         "mqSetName": "default_set_name",
  8.         "extParams": "{\"pulsar_adminUrl\": \"http://pulsar:8080\"}",
  9.         "inCharges": "admin",
  10.         "creator": "admin"
  11. }'
  • url: the address of your Pulsar cluster, such as pulsar://127.0.0.1:6650,127.0.0.1:6650,127.0.0.1:6650
  • pulsar_adminUrl: the other info of your cluster