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

Deploy manager

manager is a background service that interacts with the front-end page.

Modify 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) Modify the database URL, username and password:

  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

2) Configure the Message Queue Service, you could choose InLong TubeMQ or Apache Pulsar:

  • Configuration TubeMQ cluster information if using TubeMQ

    1. # Manager address of TubeMQ cluster, used to create Topic
    2. cluster.tube.manager=http://127.0.0.1:8081
    3. # Broker used to manage TubeMQ
    4. cluster.tube.master=127.0.0.1:8000,127.0.0.1:8010
    5. # TubeMQ cluster ID
    6. cluster.tube.clusterId=1

  • Configuration Pulsar cluster information if using Pulsar

    1. # Pulsar admin URL
    2. pulsar.adminUrl=http://127.0.0.1:8080,127.0.0.2:8080,127.0.0.3:8080
    3. # Pulsar broker address
    4. pulsar.serviceUrl=pulsar://127.0.0.1:6650,127.0.0.1:6650,127.0.0.1:6650
    5. # Default tenant of Pulsar
    6. pulsar.defaultTenant=public

3) Configure ZooKeeper clusters information:

  1. # ZK cluster, used to push the configuration of Sort
  2. cluster.zk.url=127.0.0.1:2181
  3. cluster.zk.root=inlong_hive
  4. # application name, that is the cluster-id parameter of InLong Sort
  5. sort.appName=inlong_app

Start the service

Enter the decompressed directory, execute sh bin/startup.sh to start the service, and check the log tailf log/manager-web.log. If a log similar to the following appears, the service has started successfully:

  1. Started InLongWebApplication in 6.795 seconds (JVM running for 7.565)