Mapping files for job status (PRISMAdirect to JMF)

The job status in PRISMAdirect is represented by two items: InternalJobState and CommunicationState. The mapping file for job status maps these PRISMAdirect specific values to custom values defined by the customer.

The JDF client can request the job states by sending a QueueStatus query. In response to the query, the job states are sent to the JDF client in a response message or by using signals.

Structure of the mapping file

The structure of the mapping file is quite simple. By default, each PRISMAdirect job state to an equal job state for the JDF client for both the InternalJobState and CommunicationState. For example:

<Mappings>

<CommunicationState>

<StatusMapping PAValue="Incoming">Incoming</StatusMapping>

<StatusMapping PAValue="Accepted">Accepted</StatusMapping>

<StatusMapping PAValue="Resubmitted">Resubmitted</StatusMapping>

<StatusMapping PAValue="Failed">Failed</StatusMapping>

</CommunicationState>

<InternalJobState>

<StatusMapping PAValue="Uploading">Uploading</StatusMapping>

<StatusMapping PAValue="Exported">Exported</StatusMapping>

<StatusMapping PAValue="Closing">Closing</StatusMapping>

<StatusMapping PAValue="Closed">Closed</StatusMapping>

</InternalJobState>

</Mappings>

The attributes of the mapping file are:

Limitation

• A state cannot be mapped to a custom job state if no StatusMapping is available for that state. In this case, the job state of PRISMAdirect is returned to the JDF client.

Customise the mapping file

For each JDF endpoint, you can change the mapping file to map the PRISMAdirect job states to custom values. This also means that you can translate the job states into the language of the customer. For example:

• The PRISMAdirect job state "New" is equal to the customer's job state "Unprocessed". Change:

  <StatusMapping PAValue="New">New</StatusMapping>

  into:

  <StatusMapping PAValue="New">Unprocessed</StatusMapping>.

• Translate the job states for the customer: Change:

  <StatusMapping PAValue="Ready">Ready</StatusMapping>

  into:

  <StatusMapping PAValue="Ready">Bereit</StatusMapping>.

1. Determine for which JDF endpoint the mapping file must be changed.

2. Open the concerning mapping file. You can find the files on the server of PRISMAdirect in the following location: <disk drive>:\ocestorage\Asset\JMF Endpoints\<name of endpoint>.

3. Change the mapping file.

4. Upload the edited mapping file for the concerning JDF endpoint in the "Configuration" workspace.

   At upload, the files are loaded from disc and kept in memory as long as the JDF endpoint is running. Just changing the mapping files in the folder on the server is not enough.