Starting the Coordinator
The executor of the Coordinator is the ms_coordinator, which is stored in {MindIE installation directory}/latest/mindie-service/bin/. When the ms_coordinator is started, the configuration information in the ms_coordinator.json startup configuration file needs to be read, and the .so file in the {MindIE installation directory}/latest/mindie-service/lib/ directory is required for running the ms_coordinator. The .so files include libboundscheck.so, libcrypto.so.3, libhse_cryption.so, libssl.so.3, and libmie_digs.so.
Prerequisites
Before starting the ms_coordinator, configure the following environment variables:
- Set the path of the linked library.
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:${MindIE installation directory}/latest/mindie-service/lib - Set the path of the dependency library for the KMC decryption tool.
export HSECEASY_PATH=${MindIE installation directory}/latest/mindie-service/lib - Set the path of the ms_coordinator.json configuration file.
export MINDIE_MS_COORDINATOR_CONFIG_FILE_PATH=${MindIE installation directory}/latest/mindie-service/conf/ms_coordinator.json
Startup Command
The ms_coordinator can be started in either of the following ways, and the command must be executed in the {MindIE installation directory}/latest/mindie-service/bin/ directory.
- Method 1: Direct start
./ms_coordinator
- Method 2: Start with parameters
./ms_coordinator {predict_ip} {predict_port} {manage_ip} {manage_port}Parameters:
- {predict_ip}: If this parameter is set, it will replace the predict_ip parameter in the ms_coordinator.json startup configuration file.
- {predict_port}: If this parameter is set, it will replace the predict_port parameter in the ms_coordinator.json startup configuration file.
- {manage_ip}: If this parameter is set, it will replace the manage_ip parameter in the ms_coordinator.json startup configuration file.
- {manage_port}: If this parameter is set, it will replace the manage_port parameter in the ms_coordinator.json startup configuration file.