Maintenance mode is automatically entered while this job is running.During this time, other users can not log on.(There is also an option not to switch to maintenance mode.)
Specify the job parameter dir.The origin folder is export.
If you do not specify the job parameter dir, the data_XXX folder of the newest date in the export folder will be imported.However, the data_init and data_build folders are excluded.If the corresponding folder does not exist, the import process will not be performed.
In addition, folders once imported will be skipped the next time.This is a measure to prevent accidents importing the same folder twice.(A file called ".autoimport" is prepared in the folder imported by the job.This is a marker.)
For models not to be imported by jobs, specify the model name using job parameter exclude.
For example, if you import a job schedule (jfcjobschedule) model, an operation mistake is assumed that the job schedule whose job name is RegularImport is erased.In this case, troubles can be avoided by specifying jfcjobschedule as the job parameter exclude.
You can specify more than one parameter to specify for the job. The parameters that can be specified here are as follows.
|Parameter name||Required||Description||Description example|
|dir||Specify the name of the folder to be imported.The starting point is export.If this parameter is not specified, the folder with the latest date (and the folder which has not been imported by the job yet) existing in the export folder is selected.For compressed files, give ".zip".||data_20141225000000.zip|
|target||If you write a model name (English) with a space separator, only this model will be imported.If this parameter is not specified, all models are eligible.||customer support|
|exclude||If you write a model name (English) with a space separator, you exclude this model from the import.||staff product|
|drop||Normally, the import process involves table deletion and recreation processing.But if you set this option to false, we will use the existing table as it is.However, when operating, it is necessary to consider separately deleting existing data in SQL delete statement in advance.When this specification is omitted, it is treated as true.||true|
|maintenance||When executing this job, specify whether to switch to maintenance mode.Default is "true" (maintenance mode is applied).||false|
|maintenanceOption||Specify how to respond to the account that was logged on when switching to maintenance mode.[Optional]||Logout: Force logout of the account logged on before job execution.
Fail: If there is an account logged on before job execution, cause the job to fail.
(Default): Switch the mode while leaving the logged on account unchanged.
You can temporarily disable the job.
Multiple job execution can not be performed.
If you make a job start every minute, if execution of this job is not completed in 1 minute, a new job will not be executed.
If there are many data to be imported, the web browser may time out before the processing is completed normally by operation from the "Import Export" screen.To make this correspondence, I will explain how to use the immediate execution function of import job.
In the import job, the two models "juser" and "jprincipal" are alwaysNot covered.