Storing job information

Information related to the jobs is stored in the database, if the input and output queues are configured to store job information. This job information is showed in Reporter and can be used as criteria to search for jobs.

If the job stores documents in the Collector archive, document metadata can also be used as search criteria in Reporter.

The information listed below can be stored when you run a job.

Content type

The MIME application type of the output document, for example, application/pdf. The content type is determined by the driver used.

Creation date

Date and time when the output document is created.

Job description

To store a description of the input job, you must use the SetJobDescr scripting function.

Document size

The size of the output document in bytes.

Document type

To store a document type, you must configure a document type resource in the resource set. See the Document type and metadata documentation.

Error code

The error code for the last processing of the job. Possible values are No errors, Processed with errors and Processed with warnings.

Expiry date

The expiry date defines when the job deletion thread for the runtime repository is allowed to delete successful or failed jobs in the runtime repository.

The date is derived from settings made in Design Center, in the Configure Platform dialog box – Generic layer mode.

External job ID

To store the ID of jobs received from external applications, you must use the SetExtJobId scripting function. If a job ID is included in the external input job, you can use variables and scripting to retrieve the value.

Initiation time

For input jobs, the date and time when incoming data is received, is stored as initiation time.

For output jobs, the date and time when processing of the output documents is started is stored as initiation time.

Job no

A number that uniquely identifies the job within the application domain.

Latest queue

The name of the latest queue for the output job.

Latest queue event

The latest queue event for the output job. Possible values are listed below.

Data dequeued	The job is removed from the queue.
Data enqueued	The job is placed in the queue.
Data requeued	The job is resent and placed in the queue.
Fail over	The StreamServer that processed the job went down for some reason. A new job is created and another StreamServer is taking over the new job.
Data failed	The job processing failed and the job is placed in the queue for a retry.

Last error message

The last error text generated during processing of the job.

Last processed time

Last date and time when the job was processed.

Marked for archive

Indicates if the job generates documents that should be archived in the Collector archive.

Next queue

The current queue for the output job.

Processing state

A temporary state while the StreamServer is processing the job. Possible values are listed below.

N/A	Processing has not started, or has finished.
Idle	The StreamServer has finished processing a request, and is waiting for a new request.
Holding	An output job related to the input job is processed.
Processing	The StreamServer is processing the job.
Resending	The StreamServer is processing the resent job.
Cancelling	The job has been canceled by an administrator.
Removing	The job, or its related document, is being deleted.
Archiving	Documents are being stored in the long term storage.

Job receiver

To store the job receiver, you must configure the receiver in the physical layer of the output connector runtime configuration.

Job sender

To store the job sender, you must configure the sender on the runtime job.

Status

The result when the StreamServer has finished processing the job. Possible values are listed below.

N/A	The job is not processed, or processing is ongoing.
Completed	Job processing is complete, with or without errors.
Cancelled	Job processing was canceled by an administrator.
Aborted	Job processing failed due to errors.
Removed	The job was deleted.
Failed over	Job processing has failed and the job is taken over by another StreamServer.

Times accessed

The number of times the StreamServer has processed the job.

Times to attempt

The number of times the StreamServer should attempt to process the job. The default value is 1.

To change this value, you must configure the retries setting in the queue configuration.