Enable WebSockets LAMs
You can configure LAMs to communicate with Moogsoft Enterprise using WebSockets instead of RabbitMQ or Moogsoft Enterprise Bridge.
If you are a SaaS customer and cannot use the UI for integrations with an on-premise data source, you should use WebSockets LAMs.
Moogsoft recommends that you use WebSockets LAMs in non-production environments only, and use Moogsoft Bridge in production environments.
If you use WebSockets LAMs:
You do not have to open a port for local RabbitMQ clusters.
You have an outbound HTTP connection with optional proxy support.
You can enable WebSockets LAMs in any of your environments where you have installed the Moogsoft Enterprise RPM or tarball files.
If you enable WebSockets LAMs in an environment, all LAMs in that environment use WebSockets. You cannot enable multiple communication methods in a single environment.
Before you begin
Before you enable WebSockets LAMs, you must create a WebSockets authentication token.
Create a WebSockets authentication token
You create a WebSockets authentication token to use when enabling either WebSockets LAM or Moogsoft Bridge.
You must have the grazer_login and manage_integrations permissions to create a WebSocket authentication token. The Grazer role has these permissions with a new install of Moogsoft Enterprise.
To create a WebSockets authentication token, run the following:
curl -u <username:password> -X POST 'https://<instance>/integrations/api/v1/auth/integrations'
Substitute the username and password of the user with the Grazer role and manage_integrations permission.
See Role Permissions for more information.
Enable WebSockets LAMs
To enable WebSockets LAMs, edit the integrations configuration file located at $MOOGSOFT_HOME/config/integrations.conf.
Substitute in your base URL and WebSockets authentication token.
{
"controller_url":<Base URL>,
"Websocket_token":<WebSockets authentication token>
}You can optionally configure a proxy object for LAM HTTP communication. The proxy object contains the following parameters:
host: Host of the proxy (mandatory).port: Port of the proxy (mandatory).username: Username of proxy for basic authentication (optional).password: Password for the proxy (mandatory if username is used).
The following example $MOOGSOFT_HOME/config/integrations.conf file contains a proxy object:
{
"controller_url":"https://example.moogsoft.com"
"Websocket_token":"awkdnawdnawidawk123",
"proxy": {
"host" :"host",
"port" :8080,
"username":"user",
"password":"password"
}
}
Restart or start the LAMs to finish enabling the WebSockets LAMs.
Limitations
Please note that LAMs should not be configured with rest_response_mode:event_processed since there is no response when an event is processed by Moogfarmd.