To setup the TRUE connector for starting container, execute the following command:
For Linux
sudo ./prepopulate_be_dataapp_data_provider.sh
With this command, you will create external be_dataapp_data_provider volume.
NOTE: Check if script is executable, if not, run the next command:
chmod +x prepopulate_be_dataapp_data_provider.sh
For Windows
In the prepopulate_be_dataapp_data_provider_win.sh change the FULL_PATH with the full path where the TRUE Connector is located:
docker run --rm -v "FULL_PATH/be-dataapp_data_provider:/source_data" -v "be_dataapp_provider_data:/target_data" alpine sh -c "cp -r /source_data/* /target_data/datalake/"
For example:
docker run --rm -v "C:/true-connector/be-dataapp_data_provider:/source_data" -v "be_dataapp_provider_data:/target_data" alpine sh -c "cp -r /source_data/* /target_data/datalake/"
And run the next command:
sh prepopulate_be_dataapp_data_provider_win.sh
For both systems
To start docker container, open terminal and execute following command:
If you are running docker on Linux, you might need administrative rights (sudo)
To check logs, execute following command:
You should see log lines from all 6 docker containers, something like following:
You can also check using docker ps command to verify that containers are up and running:
NOTE: version of docker images might differ.
Once all containers are up and running, TRUE Connector is ready to be used.
This can be also verified with issuing following GET commands:
Provider connector:
https://localhost:8090/about/version
or self description document:
https://localhost:8090/
Consumer connector:
https://localhost:8091/about/version
Ctrl+C is used to exit from log inspection (you will be returned to the terminal).
To stop containers, execute following:
There is also short video, that shows how to use TRUE Connector. Files are located in tutorial folder.
At this point, you should be able to use TRUE Connector and send messages. How to send messages, check following link Send multipart form request
