Architecture and components of the activity app

Edit online

The Activity app in Aspera on Cloud (AoC) shows app events and the performance, history, and usage for file transfers. Activity's responsive engine streams log data to the web application, generating interactive visualizations of real-time and historical data.

Architecture and components

  1. Each time a user performs an action on the transfer service*, such as logging in, sending a file, or creating a user, the service produces a corresponding event.
  2. The secure event gateway authenticates each activity message, adds the message to a queue, and then routes the message to the analytics engine.
  3. The analytics engine receives the event message in the database for real-time data, then sends the events to the database for historical data.
  4. Using the Activity API, the Activity app requests both real-time and historical data to display in the Activity app UI. Alternatively, an external application uses the Activity API to request real-time and historical data.
Note: The version of an Aspera High-Speed Transfer Server must be v. 3.9.3 or later. IBM Aspera recommends that you always use the latest version server software.