Configuration

The main way of providing configuration to STAPI is through Java properties.

First, follow basic setup guildlines on copying properties file into the right location.

When properties are in place, configuration can be done.

Configuration specific to Spring itself is described in Spring documentation.

Configuration using profiles

The following profiles can be turned on and off for different effects:

etl - when profile is present, ETL routines will execute the first time application is started. When profile is not present, it is assumed that the database state is right, which might or might not be true.
genderize - whether or not connect to Genderize.io. When profile is present, connection would be made, and gender of real people will be decided upon responses from this API. If it is not gender accuracy that's currently important, it is advised that this profile be not present. Genderize.io offers 1000 free request a day, a number that could be exceeded when multiple tests are run, but a number well bellow what is needed for single datafeed, which required 150 to 200 API requests to Genderize.io.
apiThrottle - whether the API should be throttled. When enabled, throttling is performed according to settings from the throttle configuration. If not enabled, no throttle is performed.

Profile default should always be on.

stapi.datasource.main.url - URL of database, check Spring documentation for details
stapi.datasource.main.username - database username
stapi.datasource.main.password=stapi - database password

source.mediaWiki.memoryAlphaEn.apiUrl - URL of Memory Alpha API, or it's local fork.
source.mediaWiki.memoryBetaEn.apiUrl - URL of Memory Beta API, or it's local fork. For the remaining properties, see common properties section.

All MediaWiki sources share common properties:

source.mediawiki.XXX.minimalInterval - minimal interval of requests. Default to auto. Could be either auto or number of milliseconds. If set to auto, it will be 0 for local fork, and one second for Wikia's wiki.
source.mediaWiki.XXX.logPostpones - should the fact that API request was postponed be logged. Default to false.
source.mediaWiki.XXX.intervalCalculationStrategy - how should the interval between requests be calculated. Possible values are FROM_BEFORE_SEND, and FROM_AFTER_RECEIVED. FROM_BEFORE_SEND means that the interval will be calculated from before the request was send, and another request will be send, for example, 1000 milliseconds after the last one was send. FROM_AFTER_RECEIVED means that the interval will be calculated from after the response was received, and another request will be send, for example, 1000 milliseconds after the last response was received.

Every can be configured in a similar manner. All steps share the same properties:

step.XXX.enabled=true - whether or not this step is turned on. When step is turned off, step reader is provided with an empty list of objects to process, and, as a result, step is marked as completed immediately.
step.XXX.commitInterval=50 - how ofter should the resulting entities be saved. Commit interval 1, when found, should not be changed, because steps that have it were not tested with higher intervals. Steps with commit interval higher than 1 could be tuned.
step.XXX.order=1 - order in which steps are executed. Currently not used, but validated - no duplicated order values are allowed.

throttle.ipAddressHourlyLimit=100 - how much request can an IP do every hour. Default to 100.

cache.cachingStrategyType - default strategy for caching read-only database queries. Possible values are NO_CACHE, CACHE_ALL, and CACHE_FULL_ENTITIES. The first two are self-explanatory. CACHE_FULL_ENTITIES will cache only results of entities retrieved by GUID. This setting will not have any effect if etl profile is enabled.