Tips for Editing an Adapter

FlexNet Manager Suite 2022 R1 (On-Premises)

The following principles are helpful when you are developing and testing your inventory adapter. If you need information about the fields in the editing pane and the permitted values, see Edit panel.

Minimize processing times

During development, use the setting to limit the number of computers for test imports. This will potentially save hours of processing while testing your adapter. The control applies a filter to the number of computers that the adapter reads from the source database, allowing validation of your work without requiring that all the data is read and processed.

Start with a template

Start with one of the supplied templates and customize it to suit your data source. Focus on the areas needing change:

• In the Step Explorer, each step that requires editing is shown in bold text. The bold is automatically removed when all areas requiring change have been modified.
• When you have selected a step so that its details are shown in the edit panel, the individual edits required are shown within curly braces, underlined, and in red.
• Every step that needs editing has extensive comments on the data structures and requirements provided in the step details. Following these guidelines will provide the quickest path to a working adapter.

Test each SQL step

As you modify each step, you can test the SQL and inspect the data set it produces, by highlighting the section of your SQL to test, and clicking the Run current script button. The result is shown in the Result tab below.

Tip: The Run current script button will run the entire step if there is no selection in the SQL script.

Note: If the selection (or, when there is no selection, the step) includes any red, underlined text that still requires customization, this produces a syntax error when run.

Figure: This step still requires customization, but the customizable text is not included in the selection, which can safely be run to inspect the results of the individual statement.

Test progressively

As you complete each step, click the Run from beginning button. This executes all the steps in the adapter from the start up to and including the one currently being edited. Errors are shown in the Log Message tab. In the Step Explorer, steps which succeed are marked with a check mark (tick) and those that fail show a red warning symbol.

Tip: The adapter is executed in the appropriate mode. For example, when you are developing the adapter on an inventory beacon, it must run in disconnected mode, meaning that all Target to Source steps are skipped, and all steps with the Disconnected check box set are exercised.

Note: If any steps between the start and your present position are still bold (require editing to customize them), they will produce a syntax error on execution.

For repeated testing of an adapter collecting differential inventory, keep in mind that second and subsequent passes will not collect any results until there is a new inventory collected on a later date for some machine(s). In other words, as you continue testing on any given day, you can expect diminishing returns on any differential inventory collections.

Final test

Finally, when you are ready to run an end-to-end test of your adapter, use the Full Import toolbar button.

When you are working on an inventory beacon (disconnected mode), in the Run Full Import dialog, the Run readers check box is set, and the Run writers check box is cleared, and both are disabled. This indicates that your full import gathers the data from your source databases to the intermediate package; but that the stage of writing data to the operations database is completely asynchronous, and cannot be controlled from the beacon. As long as the connection for this adapter is in test mode, the inventory data it gathers is never visible in the FlexNet Manager Suite compliance console.

Working on your application server gives you the option of executing the writers as well as the readers in the Compliance Importer. When the writers are run successfully, you can look for imported data in the FlexNet Manager Suite console. (You cannot, however, see the impact on compliance of this latest inventory until the next compliance calculation is run.)

Tip: While the adapter is marked as a test adapter, only the writers for this individual adapter are run. This provides much faster validation of your work than when you edit a production connector: production connectors require that all writers system-wide are exercised together.