@Resource
    protected FileConfigService fileConfigService;

    /** Helper for managing crawler processes */
    @Resource
    protected ProcessHelper processHelper;

    /** Service for managing scheduled jobs */
    @Resource
    protected ScheduledJobService scheduledJobService;

    // ===================================================================================

        // future `thread == currentThread()` calls from this thread don't incorrectly queue instead
        // of executing. Don't null out the latestTaskQueue field, because the work done here
        // may have scheduled more operations on another thread, and if those operations then
        // trigger reentrant calls that thread will have updated the latestTaskQueue field, and
        // we'd be interfering with their operation.

import org.codelibs.fess.app.web.admin.reqheader.AdminReqheaderAction;
import org.codelibs.fess.app.web.admin.role.AdminRoleAction;
import org.codelibs.fess.app.web.admin.scheduler.AdminSchedulerAction;
import org.codelibs.fess.app.web.admin.searchlog.AdminSearchlogAction;
import org.codelibs.fess.app.web.admin.sereq.AdminSereqAction;
import org.codelibs.fess.app.web.admin.storage.AdminStorageAction;

![Admin UI](https://fess.codelibs.org/_images/fess_admin_dashboard.png)

管理者UIでは、（Web、ファイル、データストア）クローラの設定ページでクロール対象を登録し、[スケジューラページ](https://fess.codelibs.org/15.3/admin/scheduler-guide.html)から手動でクローラを開始できます。

## 他の検索プロバイダーからの移行

[MIGRATION.md](MIGRATION.md)を参照してください。

## データストア

現在、Fessは以下の[ストレージロケーションとAPI](https://fess.codelibs.org/15.3/admin/dataconfig-guide.html)のクロールをサポートしています：

* If ExperimentalCriticalPodAnnotation=True flag gate is set, kubelet will ensure that pods with `scheduler.alpha.kubernetes.io/critical-pod` annotation will be admitted even under resource pressure, will not be evicted, and are reasonably protected from system OOMs. ([#41052](https://github.com/kubernetes/kubernetes/pull/41052), [@vishh](https://github.com/vishh))...

        // future `thread == currentThread()` calls from this thread don't incorrectly queue instead
        // of executing. Don't null out the latestTaskQueue field, because the work done here
        // may have scheduled more operations on another thread, and if those operations then
        // trigger reentrant calls that thread will have updated the latestTaskQueue field, and
        // we'd be interfering with their operation.

  }

  /**
   * Starts a {@link ClosingFuture} pipeline by submitting a callable block to an executor.
   *
   * @throws java.util.concurrent.RejectedExecutionException if the task cannot be scheduled for
   *     execution
   */
  public static <V extends @Nullable Object> ClosingFuture<V> submit(
      ClosingCallable<V> callable, Executor executor) {
    checkNotNull(callable);

     */
    public void reloadConfiguration() {
        reloadConfiguration(true);
    }

    /**
     * Reloads the application configuration.
     *
     * @param resetJobs true to reset scheduled jobs.
     */
    public void reloadConfiguration(final boolean resetJobs) {
        ComponentUtil.getSearchEngineClient().refresh();

        ComponentUtil.getSuggestHelper().init();

    // ============================================================
    // Job and Process Constants
    // ============================================================

    /** Scheduled job identifier. */
    public static final String SCHEDULED_JOB = "scheduledJob";

    /** Default job target value (all configurations). */
    public static final String DEFAULT_JOB_TARGET = "all";

		<dependency>
			<groupId>org.apache.commons</groupId>
			<artifactId>commons-fileupload2-jakarta-servlet6</artifactId>
			<version>${commons.fileupload.version}</version>
		</dependency>

		<!-- scheduler -->
		<dependency>
			<groupId>org.lastaflute.job</groupId>
			<artifactId>lasta-job</artifactId>
			<version>${lasta.job.version}</version>
		</dependency>

		<!-- mail -->
		<dependency>