Similar to “SourceInfo”, the framework uses “PublisherInfo”. This holds information that is used to connect to a target repository (URL, username, password etc.) and also controls the framework functionality. For example, if the framework allows for a transformation that a connector does not require, you can disable it. You can extend this, if required.
The framework allows for the following configuration:
When a connection is required
True/false that connections should be pooled
Transform type – none/xml/json + default transform file (to pick out of component)
A set of properties in the publisher controls the DXF in the common app bundle and the options in the framework.
Use these to control the app bundle loaded (via the aspire application), and the configuration of the component “publisher info” (for example, to control whether or not the publisher supports “clear” and “commit” operations)
Control of the common DXF is by way of a new properties file resources/aspire.properties that is added to the component. This file allows you to add properties.
The developer controls the DXF by setting the properties in resources/aspire.properties like in this example:
Installation settings are collected when the component is installed. Required items include location and connection (user/password) details of the target. The intent is that only options that the developer has enabled (in the Developer Settings) will be presented to the user. These settings are collected using DXF. A publisher-specific DXF is merged with a common piece to present the entire set.
The framework collects the following parameters:
The URL for the search engine, etc.
Clear before full crawls
True/False. If true, the publisher will start jobs for full crawls by calling a clear method
Commit after crawls
True/False. If true, the publisher will end jobs for crawls by calling a commit method
Transform data before sending
Transform file name
For cases when transformation is required