Architecture of FlexNet Manager for SAP Applications

FlexNet Manager Suite 2024 R1 (On-Premises)

Components of a typical FlexNet Manager for SAP Applications installation:

1. FlexNet Manager Platform provides the basis for using FlexNet Manager for SAP Applications. The required hardware is a Windows server. The database server can be a separate server or the same physical server as the FlexNet Manager Platform server.
2. The SAP Admin module of FlexNet Manager for SAP Applications requires an SAP system with release 7.00 or later (minimum Basis support package 14).
3. The Satellite transport of FlexNet Manager for SAP Applications is an optional component. Release 4.6C or later is required; no sizing is necessary. The Satellite transport must be installed if any of the following statements are true:
   • You want to collect SAP package data and run activity checks and you do not want to execute the USMM to collect user data and license data
   • You do not want to use the RFC function RFC_READ_TABLE or its corresponding authorization, SDTX
   • You want to collect activity check data for a system that runs an SAP Basis release older than 7.0
   • You use a CUA central system that is not installed on the same system as the SAP Admin module
   • You want to retrieve the module hierarchy from an independent SAP system. The module hierarchy is used to provide information on modules and sub-modules in the Module Usage report. The data from the Module Usage report can be used to create transaction profiles.
   If any of the above statements apply to you, the Satellite transport must be installed on all SAP systems with SAP packages, to enable the optimization of the relevant package licenses and execution of activity checks. If the Satellite transport is not used, the USMM must be executed to collect license data and user data.