Using the Alarm Roster Management component in a frontend/backend split

I’ve recently split a production gateway up into frontend / backend gateways, where the frontend only has Vision, Perspective, Tag History (client only), and the Vision web browser modules. The Backend has everything else, including the Alarm Notification module.

I have a Window for alarm roster management that now no longer works because I now no longer have the alarm notification module installed in the frontend and all this configuration is on the backend gateway. Without the module installed, the RosterManagementPanel component doesn’t exist.

How can I get this working again? I don’t really want to install the Alarm Notification module (in trial mode) if it’s not being used in the frontend and even if I did, I’m not sure I would be able to use it anyway. I can’t add the component into the backend project as it doesn’t have Vision. I’m a bit lost…There’s certainly a bit of a learning curve to working with these scale out architectures

1 Like

Some modules just need to be in both.

1 Like