Testing and Diagnosis for Your Business Adapter

In connected mode, before running any import (even to a test database, let alone a production environment), you can run a simulation that will show the projected results of the Business Importer running your new adapter.

In connected mode, you will also want to create log files for your imports, and possibly run tracing. All these topics are included in this section.

Testing and diagnosis options are limited for business adapters running in disconnected mode on your inventory beacon. After running the adapter against the source database, you can inspect the archive package that will be uploaded to the central application server. This package is saved in Program Data\Flexera Software\Beacon\IntermediateData\, and is a zip archive containing the following:

• A file DDI.xml that represents the business adapter (without its connection strings), so that you can see the steps than run in your adapter
• A manifest that includes a result code from running your adapter, and any error messages
• An XML file of the collected data.

On the inventory beacon, you may also examine the log file for the beacon engine, which includes results of uploading the intermediate package. This is saved in %ProgramData%\Flexera Software\Compliance\BeaconEngine. You may search in the log file for the name of your business adapter to find steps relating to it.

Note: There is no specific presentation in the compliance console (the web interface) of the results of importing your business adapter data. Look for collected information displayed in appropriate lists after the import is completed. Of course, the impact on your compliance position that results from this imported business information is shown only after the next inventory import and reconciliation.