VMware preinstallation planning

Review deployment profiles and other analytics settings that must be decided before installation.

Deployment profile

The first decision that you must make is which deployment-profile you want to use. The available deployment profiles for analytics are: n1xc2.m16, n1xc4.m32, n1xc6.m48, n3xc4.m16, n3xc4.m32, n3xc6.m48, n3xc8.m64. For more information about deployment profiles, see Deployment profiles.

For a typical production deployment, choose a three replica profile. A one replica profile is only sufficient if you expect a low API transaction rate and do not plan to retain much analytics data.

Storage space

Based on your expected API transaction rate, you can estimate how much storage space your analytics subsystem requires. See Estimating storage requirements.

Firewall requirements

The analytics firewall requirements are documented here: Firewall requirments.

Inter-subsystem communication security

If your network infrastructure requires that load-balancers implement TLS termination, then mTLS between API Connect subsystems can be disabled and JSON Web Token (JWT) security can be used instead.

Note: Although mTLS is disabled, the network communication is still secured with standard TLS, which does not require passthrough to be enabled on load-balancers.

For more information about configuring JWT for network security, see: Enable JWT security.

Disabling internal storage

If you are offloading your analytics data to a third-party system, you can choose to not store your API event data in your API Connect analytics subsystem by disabling local analytics storage. With local storage disabled, the CPU, memory, and storage requirements of your analytics subsystem are greatly reduced, but you lose the ability to view your analytics data in the Analytics UIs.

Important: It is not possible to enable or disable local storage after installation.