data.setAllPageCount(queryResponseList.getAllPageCount());
        data.setExistNextPage(queryResponseList.isExistNextPage());
        data.setExistPrevPage(queryResponseList.isExistPrevPage());
        data.setCurrentStartRecordNumber(queryResponseList.getCurrentStartRecordNumber());
        data.setCurrentEndRecordNumber(queryResponseList.getCurrentEndRecordNumber());
        data.setPageNumberList(queryResponseList.getPageNumberList());

								<group>root</group>
							</mapper>
						</data>
						<!-- Adds systemd file -->
						<data>
							<type>file</type>
							<src>${project.build.directory}/generated-packaging/deb/systemd/fess.service</src>
							<dst>${packaging.fess.systemd.dir}/fess.service</dst>
						</data>
						<!-- Adds systemd/sysctl.d configuration file -->
						<data>
							<type>file</type>

You can register crawling targets in the Admin UI on the (Web, File, Data Store) crawler configuration pages, and then start the Crawler manually on the [Scheduler page](https://fess.codelibs.org/15.3/admin/scheduler-guide.html).

## Migration from another search provider

Please see [MIGRATION.md](MIGRATION.md).

## Data Store

            logger.debug("Unknown hostname.", e);
        }
        return "Unknown";
    }

    /**
     * Sets up administrative HTML data for a given action.
     *
     * @param action  The action to set up data for.
     * @param runtime The action runtime.
     */
    public void setupAdminHtmlData(final TypicalAction action, final ActionRuntime runtime) {

     * Parses mapping rules in the format: input1,input2,... => output
     *
     * @param updater the mapping updater to use for writing changes, or null for read-only reload
     * @param in the input stream to read the mapping data from
     */
    protected void reload(final MappingUpdater updater, final InputStream in) {
        final Pattern parsePattern = Pattern.compile("(.*?)\\s*+=>\\s*+(.*?)\\s*+$");