In normal operation, an active profile automatically starts as soon as its Input Agent receives data (time-driven or via event). Lobster_data saves the data in a backup and then generates a so-called job. See also sections Profiles and Jobs and especially Phase 1 (introduction).

Additionally, there is the possibility to start a profile manually. This is the purpose of the restart dialogue. It can be opened here in the Control Center under Logs/Overview and also in the following places. See also system variable VAR_SYS_RESTART.

• Via the context menu of a profile in the profile overview.

• In a mapping test via the upper menu bar of a profile.

(1) Search period.

(2) Log Selection only shows the one archive file of the job to be restarted. Archive Files shows all archive files of the profile for the selected period. Unknown Files shows the files from area Unresolved.

(3) List of all archive files found for the profile (whose job was restarted).

(4) If this checkbox is set, the restarted job will not be considered for any defined checkpoints of the profile.

(5) If this checkbox is set, the started job will be treated as a test run. That means that

• the system variable VAR_IS_TEST is set to true (and VAR_IS_NOT_TEST to false) (see also item 9) and

• in phase 6, only those Response Routes are considered that have the checkbox Only at test set.

Note: Both items only apply for Upload file and not for Start cron (6). Button Upload file is only shown for profiles that have no time-driven Input Agent.

(6) If the profile to be restarted has a time-driven Input Agent, it can be restarted with this button. Archive files are not taken into account. If a profile is to be restarted with one or more specific archive files (which creates new jobs), the context menu should be used (see screenshot below). If the profile to be restarted has an event-driven Input Agent, you can manually upload a file here and start a job.

Note: If a profile with a time-driven Input Agent is not active, the Input Agent will be executed, but the inactive profile will not process the received data. If another profile has the same Input Agent and is active, this profile might be able to accept the data instead (see section Input Agents That Are Forced to Receive All the Data) or the data is stored in the Unresolved area. In this case, there will be an entry in the Control Center under General Messages.

(7) For profiles with an Input Agent of type OFTP, the fetching of files (pickup) can be started here.