Skip to main content
Version: 2.9.0

Overview

The EWB Network Server provides API access for operating on an EWB Network.

This document describes how to configure and run the EWB Network Server


Command Line Options

Configuration options for the EWB Network Server are provided as command line arguments.

UsageDescriptionRequiredDefault
-auth, --patch-auth-header <AUTH_HEADER>the HTTP auth header to use with the patch serverNoNone
-c, --current-date <DATE>the date to use as the current dateNoCurrent Date
-cors, --cors <CORS_DEFINITION>set the cors definitionNo0
-d, --days-to-search <NUM_DAYS>the number of days to search for a network database in the EWB data rootNo0
-debug, --debug-routing <FILE>enable route debugging. Request bodies will be saved to the specified fileNoNone
-e, --ewb-data-root <DIRECTORY>the directory of the EWB data rootYes
-ga, --grpc-auth <CLIENT_AUTH> <TRUST_PATH>CLIENT_AUTH controls the client authentication requirements (OPTIONAL/REQUIRE). TRUST_PATH specifies the path to the trusted certificate for verifying the remote endpoint's certificateNoNone
-gp, --grpc-port <PORT>The port number for the gRPC serverYes
-gt, --grpc-tls <CERT_PATH> <KEY_PATH>CERT_PATH specifies the path to the certificate to use, and KEY_PATH specifies the path to the private key for the certificate.NoNone
-h, --helpshows the help messageNo
-o, --output <FILE>the network build status file (including path)Noewb-network-server-status.json
-p, --port <PORT>the port number the REST API will listen on.Yes
-pa, --patch-api <API_ENDPOINT>the patch server end point (including server, port and url)NoNone
-s3, --s3-bucket <BUCKET>the AWS S3 bucket name to create the output in. If specified, the default S3 connection will be usedNoNone
-t, --timeout <SECONDS>the timeout (in seconds) for receiving data from the patch API. Zero to disableNo60
-cpi, --connection-point-identifier <IDENTIFIER>specifies the connection point identifier to useNoNMI