# Starting and stopping containers 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: ``` docker-compose up & ``` If you are running docker on Linux, you might need administrative rights (sudo) To check logs, execute following command: ``` docker-compose logs -f ``` You should see log lines from all 6 docker containers, something like following: ``` uc-dataapp-consumer | 2022-09-16 16:01:50.496 INFO 1 --- [ main] o.s.b.a.e.w.EndpointLinksResolver : Exposing 0 endpoint(s) beneath base path '/actuator' uc-dataapp-provider | 2022-09-16 16:01:50.690 INFO 1 --- [ main] o.s.b.a.e.w.EndpointLinksResolver : Exposing 0 endpoint(s) beneath base path '/actuator' uc-dataapp-consumer | 2022-09-16 16:01:51.062 INFO 1 --- [ main] o.s.b.w.e.t.TomcatWebServer : Tomcat started on port(s): 8080 (http) with context path '/platoontec/PlatoonDataUsage/1.0' uc-dataapp-provider | 2022-09-16 16:01:51.128 INFO 1 --- [ main] o.s.b.w.e.t.TomcatWebServer : Tomcat started on port(s): 8080 (http) with context path '/platoontec/PlatoonDataUsage/1.0' uc-dataapp-consumer | 2022-09-16 16:01:51.155 INFO 1 --- [ main] c.t.d.Swagger2SpringBoot : Started Swagger2SpringBoot in 53.078 seconds (JVM running for 60.067) uc-dataapp-provider | 2022-09-16 16:01:51.203 INFO 1 --- [ main] c.t.d.Swagger2SpringBoot : Started Swagger2SpringBoot in 53.952 seconds (JVM running for 60.42) be-dataapp-consumer | Sep 16, 2022 4:01:51 PM org.apache.catalina.core.ApplicationContext log be-dataapp-consumer | INFO: Initializing Spring DispatcherServlet 'dispatcherServlet' be-dataapp-provider | Sep 16, 2022 4:01:52 PM org.apache.catalina.core.ApplicationContext log be-dataapp-provider | INFO: Initializing Spring DispatcherServlet 'dispatcherServlet' ecc-provider | Sep 16, 2022 4:02:00 PM org.apache.coyote.AbstractProtocol start ecc-provider | INFO: Starting ProtocolHandler ["https-jsse-nio-8449"] ecc-provider | Sep 16, 2022 4:02:00 PM org.apache.coyote.AbstractProtocol start ecc-provider | INFO: Starting ProtocolHandler ["http-nio-8081"] ecc-provider | 16-09-2022 16:02:00.776 [restartedMain] INFO it.eng.idsa.businesslogic.Application.logStarted - Started Application in 66.089 seconds (JVM running for 69.121) ecc-consumer | Sep 16, 2022 4:02:00 PM org.apache.coyote.AbstractProtocol start ecc-consumer | INFO: Starting ProtocolHandler ["https-jsse-nio-8449"] ecc-provider | Sep 16, 2022 4:02:01 PM org.apache.catalina.core.ApplicationContext log ecc-provider | INFO: Initializing Spring DispatcherServlet 'dispatcherServlet' ecc-consumer | Sep 16, 2022 4:02:01 PM org.apache.coyote.AbstractProtocol start ecc-consumer | INFO: Starting ProtocolHandler ["http-nio-8081"] ecc-consumer | 16-09-2022 16:02:01.131 [restartedMain] INFO it.eng.idsa.businesslogic.Application.logStarted - Started Application in 65.977 seconds (JVM running for 69.317) ecc-consumer | Sep 16, 2022 4:02:01 PM org.apache.catalina.core.ApplicationContext log ecc-consumer | INFO: Initializing Spring DispatcherServlet 'dispatcherServlet' ``` You can also check using *docker ps* command to verify that containers are up and running: ``` CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES bc693e1fdb90 rdlabengpa/ids_execution_core_container:1.14.8 "/bin/sh -c 'java -j…" 3 hours ago Up 3 hours (healthy) 0.0.0.0:8087->8086/tcp, :::8087->8086/tcp, 0.0.0.0:8091->8449/tcp, :::8091->8449/tcp, 0.0.0.0:8890->8889/tcp, :::8890->8889/tcp ecc-consumer 28dc87213f68 rdlabengpa/ids_be_data_app:0.3.8 "/bin/sh -c 'java -j…" 3 hours ago Up 3 hours (healthy) 0.0.0.0:8184->8183/tcp, :::8184->8183/tcp, 0.0.0.0:9001->9000/tcp, :::9001->9000/tcp be-dataapp-consumer 9eb157ceb37b rdlabengpa/ids_be_data_app:0.3.8 "/bin/sh -c 'java -j…" 3 hours ago Up 3 hours (healthy) 0.0.0.0:8183->8183/tcp, :::8183->8183/tcp, 0.0.0.0:9000->9000/tcp, :::9000->9000/tcp be-dataapp-provider 44bc21187460 rdlabengpa/ids_execution_core_container:1.14.8 "/bin/sh -c 'java -j…" 3 hours ago Up 3 hours (healthy) 0.0.0.0:8086->8086/tcp, :::8086->8086/tcp, 0.0.0.0:8889->8889/tcp, :::8889->8889/tcp, 0.0.0.0:8090->8449/tcp, :::8090->8449/tcp ecc-provider b3f4cdb77ed6 rdlabengpa/ids_uc_data_app_platoon:1.7.9 "/bin/sh -c 'java -j…" 3 hours ago Up 3 hours (healthy) 8080/tcp uc-dataapp-consumer a36748901ce1 rdlabengpa/ids_uc_data_app_platoon_pip:v1.0.0 "java -jar pip.jar" 3 hours ago Up 3 hours 0/tcp uc-dataapp-pip-provider d6f77ad9762d rdlabengpa/ids_uc_data_app_platoon:1.7.9 "/bin/sh -c 'java -j…" 3 hours ago Up 3 hours (healthy) 8080/tcp uc-dataapp-provider bb0bb9668931 rdlabengpa/ids_uc_data_app_platoon_pip:v1.0.0 "java -jar pip.jar" 3 hours ago Up 3 hours 0/tcp uc-dataapp-pip-consumer ``` 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: ** or self description document:\ \&#xNAN;*https\://localhost:8090/* Consumer connector: ** Ctrl+C is used to exit from log inspection (you will be returned to the terminal). To stop containers, execute following: ``` docker-compose down -v ``` There is also short video, that shows how to use TRUE Connector. Files are located in [tutorial](https://github.com/Engineering-Research-and-Development/true-connector/blob/main/doc/tutorial/README.md) 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](/true-connector/exchange-data.md) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://engineering-ing-inf-rd.gitbook.io/true-connector/readme/start-stop.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.