Architecture and Operations

FlexNet Manager Suite 2021 R1 (On-Premises)

To facilitate the two-way exchange of data between FlexNet Manager Suite and BMC Atrium, components already supplied with both systems are used, and additional elements are supplied with the downloaded adapter.

The following diagram combines the positioning of these elements on different servers, with the data flows for both export and import (as defined in BMC Atrium and Remedy Integration). There are two determining factors in this structural arrangement:
  • The schedule for triggering both exports and imports is configured within Atrium, and the Atrium Integrator needs to invoke the data export utility and the FlexNet Business Importer. For this reason, all three components (Atrium Integrator, export utility, and Business Importer) are located on the same server.
  • For performance, it is preferable that the intermediate database be on the same database server as your compliance database for FlexNet Manager Suite. (Where you choose a different location, ensure there is a high-speed network connection between the two servers, and a trust relationship for the accounts used during operations.)
The combination of these two determinants produces the following physical architecture. Net data flows are shown here, with each process also shown separately below.

Once the adapter components are installed and all systems are configured (as described in the chapter Installing the Adapter), operation is fully automatic, triggered by schedules you set during configuration. The two directions of data exchange function independently, and are summarized below.

Export of Computers and Products

In summary, the process for exporting computer and product information from FlexNet Manager Suite to BMC Atrium (shown below in blue arrows) is as follows:

  1. The schedule for export fires in Atrium, and the Atrium Integrator calls the data export tool (installed as part of the adapter).
  2. The data export tool reads content from the compliance database for FlexNet Manager Suite, and writes the data into the intermediate database. (It also creates entries in the log file, and sends alert emails if there any errors.)
  3. On success, the Atrium Integrator reads the data from the intermediate database, maps it using the defined data transforms to the fields required in Atrium
  4. The Atrium Integrator writes the results into the CMDB.

Import of Assets

In summary, the process for importing assets (and their ownership) from BMC Atrium into FlexNet Manager Suite (shown below in green arrows) is as follows:

  1. The schedule for import fires in Atrium.
  2. The Atrium Integrator reads data from both the Remedy database and the CMDB, and writes the results into the Intermediate database. (It also sends alert emails if there are any errors.)
  3. On success, the Atrium Integrator calls the FlexNet Business Importer.
  4. The Business Importer reads the data from the intermediate database, transforms it as required, and writes the results into the compliance database of FlexNet Manager Suite.

FlexNet Manager Suite (On-Premises)

2021 R1