Using separate ports in Edge Flow Manager

You can make Edge Flow Manager listen to separate ports for UI and C2 type of requests. To do so, you need to uncomment the #efm.server.c2Port= property in the efm.properties file, and set a valid port number as the value of the #efm.server.c2Port= property.

The Edge Flow Manager REST API can be divided into two logical parts. The first group comprises the REST endpoints which are used by the users to create flows, manage credentials, and so on through the UI, called UI endpoints. The second group comprises the REST endpoints which are used by the MiNiFi agent to communicate with Edge Flow Manager, called C2 endpoints. With the default configuration, Edge Flow Manager listens to port configured with the efm.server.port property for all kinds of requests.

There could be cases where distinction between the UI and C2 traffic needs to be made on the network level.

A property is introduced in the efm.properties file to enable separate UI and C2 communication.

#efm.server.c2Port=

By default it is commented out so Edge Flow Manager listens to the port set with the efm.server.port property.

If you want to make Edge Flow Manager listen to separate ports for UI and C2 type of requests, uncomment the efm.server.c2Port property and set a valid port number.

important

If you uncomment the efm.server.c2Port property but do not set a value, Edge Flow Manager startup process fails with the following error message:

Reason: The elements [efm.server.c2port] were left unbound.

If both ports are correctly configured, the following additional log messages should appear when Edge Flow Manager startup process concludes:

>>> Base URL for C2 REST API: http://localhost:10091/efm/api/c2-protocol
>>> Swagger REST API docs for C2: http://localhost:10091/efm/api/swagger