Communication Agent
23.2 Updated Communication Agent
In order to reduce memory usage, the singular Communication Agent is now split into three separate service agents:
-
AIM: Provides a method to automate app processing by scheduling sessions to run at designated times, allowing flexibility to meet business needs.
-
Thick Client: The Mobile Client program is hosted on a terminal server where sessions are served to emulation clients connected to the server. These sessions connect on the full-client listening thread. All sessions connect to the same IP address. Because of this, the Windows logon to the terminal server emulation session is used as the device ID.
-
Web Socket: Web socket supports HTTP requests as an open interface option to Mobile Enterprise Platform.
Though each of the service agents above are now independent, you still access each of the service agents through the Communication Agent option in the Agent Settings list. This enables your current settings to automatically carry over into the new architecture, as well as giving you a single point of entry to make future changes. The process to make changes to your services has not changed.
For this new functionality to work properly, you must create a connection string to your Redis server.
Finally, rather than restarting an agent in order to address performance issues, you can now simply clear sessions.
Loading...
There was a problem loading this topic