Testing Wanaku Start Local

Build for distribution:

mvn -DskipTests -Pdist clean package

Run the CLI with local distributions:

./tests/wanaku-start-local-test.sh

Then, access http://localhost:8080/admin. Wanaku should be available at that address. No authentication should be required.

Testing with the Camel Integration Capability

Build the Camel Integration Capability JAR, then use --local-dist to supply it alongside the wanaku distributions.

With route files:

version=$(cat core/core-util/target/classes/version.txt)
java -jar apps/wanaku-cli/target/quarkus-app/quarkus-run.jar start local \
  --local-dist apps/wanaku-router-backend/target/distributions/wanaku-router-backend-${version}.zip \
  --local-dist apps/wanaku-tool-service-http/target/distributions/wanaku-tool-service-http-${version}.zip \
  --local-dist /path/to/camel-integration-capability-main-0.2.0-SNAPSHOT-jar-with-dependencies.jar \
  --camel-routes file:///path/to/routes.camel.yaml \
  --camel-rules file:///path/to/rules.yaml

With a service catalog:

version=$(cat core/core-util/target/classes/version.txt)
java -jar apps/wanaku-cli/target/quarkus-app/quarkus-run.jar start local \
  --local-dist apps/wanaku-router-backend/target/distributions/wanaku-router-backend-${version}.zip \
  --local-dist /path/to/camel-integration-capability-main-0.2.0-SNAPSHOT-jar-with-dependencies.jar \
  --service-catalog my-catalog \
  --service-catalog-system ftp

The camel-integration service is automatically added when any CIC option is provided.

Stopping the router

The router must be stopped gently. Do not kill the process with signal -9 because it leaves dangling processes.

Use the stop script to gracefully shut down the router and all capability services:

./tests/wanaku-start-local-stop.sh

If you captured the PID at startup, you can pass it directly:

WANAKU_PID=<pid> ./tests/wanaku-start-local-stop.sh

The script sends SIGTERM first and waits for processes to exit. SIGKILL is only used as a last resort if processes do not respond.