/** The path of the HTML: /admin/scheduler/admin_scheduler.jsp */
    HtmlNext path_AdminScheduler_AdminSchedulerJsp = new HtmlNext("/admin/scheduler/admin_scheduler.jsp");

    /** The path of the HTML: /admin/scheduler/admin_scheduler_details.jsp */
    HtmlNext path_AdminScheduler_AdminSchedulerDetailsJsp = new HtmlNext("/admin/scheduler/admin_scheduler_details.jsp");

Sie können in der Administrationsoberfläche (Web, Datei, Datenspeicher) Crawling-Ziele in den Crawler-Konfigurationsseiten registrieren und den Crawler manuell auf der [Scheduler-Seite](https://fess.codelibs.org/14.17/admin/scheduler-guide.html) starten.

## Migration von einem anderen Suchanbieter

Bitte lesen Sie [MIGRATION.md](MIGRATION.md).

## Datenspeicher

                                <c:if test="${fe:permission('admin-scheduler')}">
                                    <la:link styleClass="btn btn-success"
                                             href="/admin/scheduler/createnewjob/data_crawling/${f:u(id)}/${fe:base64(name)}">
                                        <em class="fa fa-plus-circle">

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.0/admin/scheduler-guide.html).

## Migration from another search provider

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

## Data Store

            totalCalls.incrementAndGet();
            // Make sure that no other tasks are scheduled to run while this is running.
            assertFalse(fakePool.hasNext());
          }
        };

    assertFalse(fakePool.hasNext());
    e.execute(intCounter);
    // A task should have been scheduled
    assertTrue(fakePool.hasNext());
    e.execute(intCounter);
    // Our executor hasn't run any tasks yet.

                                <c:if test="${fe:permission('admin-scheduler')}">
                                    <la:link styleClass="btn btn-success"
                                             href="/admin/scheduler/createnewjob/file_crawling/${f:u(id)}/${fe:base64(name)}">
                                        <em class="fa fa-plus-circle">

        String message = "Test scheduled job error";
        ScheduledJobException exception = new ScheduledJobException(message);

        assertEquals(message, exception.getMessage());
        assertNull(exception.getCause());
    }

    public void test_constructorWithMessageAndCause() {
        // Test constructor with message and cause
        String message = "Test scheduled job error with cause";

    private final AtomicInteger globalAttemptsInCurrentWindow = new AtomicInteger(0);
    private final AtomicLong currentWindowStart = new AtomicLong(System.currentTimeMillis());

    // Cleanup scheduler
    private final ScheduledExecutorService cleanupScheduler;
    private final AtomicBoolean closed = new AtomicBoolean(false);

    // Statistics
    private final AtomicLong totalAttemptsBlocked = new AtomicLong(0);

							<p><la:message key="labels.menu_crawl_config" /></p>
						</a>
					</li>
					</c:if>
					<c:if test="${fe:permission('admin-scheduler-view')}">
					<li class="nav-item">
						<a href="${fe:url('/admin/scheduler/')}" class="nav-link <c:if test="${param.menuType=='scheduler'}">active</c:if>">
							<em class='fa fa-genderless nav-icon'>
							<p><la:message key="labels.menu_scheduler_config" /></p>
						</a></li></c:if>

    * Specifically the new controller watches the API server for scheduled pods. It processes each pod and ensures that any volumes that implement the volume Attacher interface are attached to the node their pod is scheduled to.