AMX Application Deployment Options
The output from the Application Metadata Intelligence or GTP Correlation Engine is sent to the AMX application that exports it to the tools in the required formats. AMX application is always deployed in GigaVUE V Series Node. The GigaSMART application sending data to the AMX application is either on hardware or the GigaVUE V Series Node.
Note: For exporting GigaVUE Enriched Metadata for Cloud Workloads, AMI is deployed in GigaVUE V Series Nodes.
Based on where the GigaSMART applications run, you can deploy on:
| Hardware (AMI) |
| Hardware (Control Plane Metadata) |
| Virtual (VMware) |
On-Premises
Hardware (AMI)
In hardware deployments, the Application Metadata Intelligence (AMI) runs on a physical node/cluster, and the AMX application is deployed on a GigaVUE V Series Node running on VMware ESXi. The output from the AMI in CEF format is sent to the AMX application in GigaVUE V Series Node. GigaVUE‑FM manages the performance of the device and the application.
The following devices support the integration of AMX application:
- GigaVUE-HC1
- GigaVUE-HC3
- GigaVUE‑HC1-Plus
Hardware (Control Plane Metadata)
In hardware deployments, the GTP Correlation Engine runs on a physical node/cluster, and the AMX application is deployed on a GigaVUE V Series Node running on VMware ESXi. The output from the GTP Correlation Engine in Flat JSON format is sent to the AMX application in GigaVUE V Series Node. GigaVUE‑FM manages the performance of the device and the application. The GigaVUE-HC3 Gen3 devices support the integration of AMX application.
Private Cloud (VMware)
In the Private Cloud environment, as shown in the diagram, the application is supported only on VMware and deployed in VMware.
Public Cloud
In the Public Cloud environment, the application is supported on AWS and Azure platforms, and deployed as shown in the diagram:
