...
On request of the users an additional, combined adapter has been added, the WandaAdapter which performs both the pre-and post processing tasks and also executes the Wanda Model. Using this combined adapter is more efficient because instead of 3 separate execute activities the General Adapter only needs to execute one and as a result the Wanda Java API used by the adapter only needs to load the Wanda Model schematization once, providing considerable performance improvement, especially for a large model. The configuration example given on this page therefore all assume that the combined WandaAdapter is used.
Exception handling
Some of the exceptions that may occur during transformations are logged as warnings in the configured diagnostics file without aborting the adapter processing.:
- location Id's for which a matching Wanda component cannot be found
- parameter Id's for which a matching Wanda property cannot be found for the selected Wanda Component
- time series that cannot be loaded for a selected component and property because the property has no defined series in the wanda model
For other types of exception, the exception is logged and an exception i thrown so the adapter processing is aborted and the general real adapter will also log the error in the FEWS log.
Wanda adapter binary folder
The following files are part of the binary folder for the Wanda adapter and are provided in the fews-wanda-adapter-bin.<version>.zip artifact of the "install adapters" teamcity builds:
...
- command - className: this contains the full class name of the combined WandaAdapter
- binDir: this contains the path where the adapter binaries are stored.
- arguments: a single argument needs to be specified providing the full path to the runInfo file (as specified in exportActivities section).
- logFile: this (optional) settikng setting can be configure configured to scan the Wanda ouput logs for error messages.
...