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/14.17/admin/scheduler-guide.html)から手動でクローラを開始できます。

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

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

## データストア

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

        // Resource state changed - may need to reconnect
        log.info("Resource change detected for: {}", notification.getResourceName());

        // Schedule reconnection attempt
        scheduleReconnection(getContext().getConfig().getWitnessReconnectDelay());
    }

    /**
     * Handle client move events
     */

        this.cleanupExecutor = Executors.newSingleThreadScheduledExecutor(r -> {
            Thread t = new Thread(r, "LeaseManager-Cleanup");
            t.setDaemon(true);
            return t;
        });

        // Schedule periodic cleanup
        long cleanupInterval = context.getConfig().getLeaseTimeout();
        if (cleanupInterval <= 0) {
            cleanupInterval = DEFAULT_LEASE_CLEANUP_INTERVAL;
        }

replication rules were disabled will be synced to the target cluster. Depending on the number of previously existing objects, the existing objects that are now eligible to be replicated will eventually be synced to the target cluster as the scanner schedules them. This may be slower depending on the load on the cluster, latency and size of the namespace.

In the rare event that target DR site is entirely lost and previously replicated objects to the DR cluster need to be re-replicated, `mc...

        .build(),
    )
    val webSocket = newWebSocket()
    clientListener.assertOpen()
    val server = serverListener.assertOpen()

    // Initiate a close on the client, which will schedule a hard cancel in 500 ms.
    val closeAtNanos = System.nanoTime()
    webSocket.close(1000, "goodbye", 500L)
    serverListener.assertClosing(1000, "goodbye")

    // Confirm that the hard cancel occurred after 500 ms.

    override fun contentType() = delegate.contentType()

    override fun isDuplex() = true

    override fun writeTo(sink: BufferedSink) {
      executorService.schedule({
        try {
          delegate.writeTo(sink)
          sink.close()
        } catch (e: IOException) {
          throw RuntimeException(e)
        }
      }, delayMillis, TimeUnit.MILLISECONDS)
    }

## Metrics Request Handling

Each endpoint can be queried as needed via a scrape configuration in Prometheus or a compatible metrics collection tool. You should schedule scrape operations so a prior scrape completes before the next one begins.

labels.excluded_doc_urls=要從搜尋中排除的URL
labels.user_agent=使用者代理
labels.web_crawling_button_create=建立
labels.web_crawling_button_create_job=建立新作業
labels.crawler_configuration=通用設定
labels.crawler_title_edit=通用設定
labels.schedule=排程
labels.enabled=啟用
labels.day_for_cleanup=刪除以前的文檔
labels.day=天
labels.crawl_button_update=更新
labels.none=無
labels.crawling_thread_count=同時爬蟲設定
labels.incremental_crawling=檢查上次修改時間

labels.user_agent=User Agent
labels.web_crawling_button_create=Создать
labels.web_crawling_button_create_job=Создать новое задание
labels.crawler_configuration=Общая конфигурация
labels.crawler_title_edit=Общая конфигурация
labels.schedule=Расписание
labels.enabled=Включено
labels.day_for_cleanup=Удалить старые документы
labels.day=дней
labels.crawl_button_update=Обновить
labels.none=Нет