Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

BaSyx / Documentation / Components / Context

< BaSyx ‎ | Documentation ‎ | Components
Revision as of 11:30, 7 October 2020 by Unnamed Poltroon (Talk) (Initial version)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Context Configuration

By default, each Java component starts an HTTP server providing its functionality. The configuration for the servlet can be modified within its context.properties file. Here is an example showing the default configuration for the registry component:

contextPath=/registry
contextHostname=localhost
contextPort=4000

With this configuration, the component can be accessed at:

http://localhost:4000/registry/

For docker components, the context.properties file can be mounted inside of the container using a volume during container startup. E.g., to run the registry component with custom context configuration, use

docker run --name=registry -p 8082:4000 -v C:/tmp:/usr/share/config eclipsebasyx/aas-registry:latest

The context.properties file has to be located in C:/tmp in this example.

In order to change the context configuration when directly starting the component from a component's Java executable, you can specifiy the configuration file path via the BASYX_CONTEXT parameter. See the following example with the registry:

java -jar -DBASYX_CONTEXT="C:/tmp/context.properties" registry.jar

Note that for docker components, the context port is the container's internal port. A set container port can be mapped to any host port. In the example above, the default port 4000 is mapped to the host port 8082. Therefore on the host machine, the registry will be accessible at:

http://localhost:8082/registry/

Back to the top