In some use cases it might be useful to not have the JRJOBIMPORT table in the JobRouter database, but in an external database or even in a different database system. If the tasks are to be started by for example trigger of specific tables in another database system, it might be difficult to write data in the task table of the JobRouter database.
If this is the case, you can create JobRouter import connections (see admin manual) to other databases. The JRJOBIMPORT table has to be created in these databases.
The JobServer service monitors all data sources and imports instances from all task tables. This allows you to create interfaces to other systems with little effort.
