The Manager is an optional component that automatically handles the following tasks:
If the application uses a dynamic approach for the RoutingManagement it is recommended to use the function Ucs_Rm_SetRouteActive() together with Manager component.
Enable the Manager in the initialization structure.
Do not access the following functions if the Manager is enabled:
The following callback functions will not work if the Manager is enabled:
See also API Reference, section Manager. |
The application must define a set of structures that are required as input for the Manager. Basically the application must provide a list of nodes and a list of routes.
node_address
attribute must be set to the value as set in the "identification string" of the respective node (INIC). Each node must be configured with a unique node_address
. Other values inside the identification string are not evaluated by the Manager.The code below shows a setup of two nodes and one route for synchronous streaming. Since the route is initialized as "active" it is automatically created as soon as both nodes are available. The application does not need to activate this route at a certain time.
The code below shows a possible initialization sequence of the Application Message Service.
See also Getting Started, section Initialization. |
If the application logic requires information about the availability of nodes, it is possible to register an optional callback function mgr.report_fptr. See also the initialization code above. The following code shows an implementation of this function.