You can manage JDF endpoints in the "Configuration" workspace. Each JDF endpoint listens for and reacts to messages received over HTTP from the JDF clients. One JDF endpoint uses two mapping files:
One file to map the JDF ticket and its values to PRISMAdirect ticket items.
One file to map the job status used by PRISMAdirect into the job status used by the JDF client.
By default, each JDF endpoint uses default mapping files. You can create and use custom mapping files. You can find the default mapping files on the server of PRISMAdirect in the following location:<disk drive>:\ocestorage\Asset\JMF Endpoints.
PRISMAdirect also offers default mapping files for DSF, Pressero and uniFLOW . You can find these files on the server of PRISMAdirect in the following location:<disk drive>:\ocestorage\Asset\Import Service Mappings. This folder contains the files that map ticket items from the concerning application to ticket items of PRISMAdirect. To map the status, use the default mapping file in the following location:<disk drive>:\ocestorage\Asset\JMF Endpoints
For each JDF endpoint:
PRISMAdirect creates a folder containing the mapping files. The mapping files are XML files. Each JDF endpoint can use a different set of mapping files. You can find the files on the server of PRISMAdirect in the following location: <disk drive>:\ocestorage\Asset\JMF Endpoints\<name of endpoint>.
You can change the mapping files of a JDF endpoint. When you have changed the mapping files, you must upload the files again 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.