The Web Panel Receiver

Overview

Web Panel Receivers communicate with the web server embedded into the executable model and host Web Panels.

Editing a Web Panel should only be performed whilst the Web Panel Receiver is connected to the running executable model to ensure that the designer has up to date information on available instance information.

The Web Panel receiver may be started/stopped using the context menu of a Web Panel model element. That same menu also provides helpers to open the hosted web page(s) and export a Web Panel Bundle.

The Web Panel communicates with the embedded web server in the generated executable model. To commence a design or simply use the panel, both the Web Panel receiver and the executable model must both be running although they may be started in either order. The design web page includes indicators that show if:

· The hosted web page is connected to the receiver.

· The receiver is connected to the executable model.

Standalone Receiver

The receiver can run without Rhapsody using the provided JAR, for example:

java -jar WebPanelReceiver.jar --tcp-port 6424 --http-port 8080 --panel-dir . --debug false

Argument	Default	Description
--tcp-port	6424	Port for the C++ executable to connect on
--http-port	8080	Port for the HTTP/SSE server
--panel-dir	panel	Directory to serve static files from
--debug	false	Write detailed logs to `<panel-dir>/receiver-debug.log`

Web Panel Receiver API

The auto-generated Web Panel Views make standard REST GET and POST requests to the Web Panel receiver which then translates those into calls into the embedded web server.

Users are not restricted to using the auto-generated web panels and may use their own utilising REST. See the Web Panel Receiver API.

Using that API, you may design web panels using any libraries you wish, for example: