Skip to content

Configure the Repro List Processing

When using PLOSSYS 4 (p4) as a backend system, the PLOSSYS 4 (p4) connector interprets jobs by default as set collations for PLOSSYS 4. The jobs are generated as set collations and sent to the stargate.

Alternatively, you can activate the repro list processing in the PLOSSYS 4 (p4) connector. This means the connector interprets jobs as repro lists. Then, the jobs are generated as repro lists and sent to the configured gate directory, by default, rlipdmgate.

When using PLOSSYS Output Engine (p5) as a backend system, repro lists can be printed if the list file includes HREF file locations for each included document. SEAL Operator then separates the repro list into different print jobs, locates the files and sends them to the PLOSSYS Output Engine system.

For how to use the repro list processing, refer to Import Repro List Files.

Activate the Repro List Processing

This way you activate the repro list processing in the PLOSSYS 4 (p4) connector:

  1. Export the complete configuration of SEAL Operator from Consul to a YAML file. This ensures that you edit the current configuration.

    operator config export <filename>.yml --insecure

  2. Edit the exported file <filename>.yml.

  3. In the env section, specify the following key for the seal-operator-p4 service in the operator-p4 section:

    env:
  service:
  ...
    operator-p4:
      tag:
        any:
          ...
          TARGET_CONTENT_TYPE: application/rli
  ...

  4. Save the <filename>.yml file.

  5. Re-import the file to Consul.

    operator config import <filename>.yml --insecure

  6. Check the imported value, for example for TARGET_CONTENT_TYPE:

    operator config get TARGET_CONTENT_TYPE --service operator-p4 --insecure

Change the Target Gate

By default, rlipdmgate is used as target gate for the repro list processing. To change the target gate, execute the following steps:

  1. Specify the following node-p4rest key as system variable:

    • RLIGATE: optional, name of the target directory for the rli and rlist repro list files without path

    • On Windows:

      1. Open the Windows System dialog and select Advanced System Settings.

      2. In the System Properties dialog, select Environment Variables.

      3. Add RLIGATE to System Variables.

    • On Linux:

      1. Add RLIGATE to the following file:

        /opt/seal/etc/node-p4rest.env

    Example - set system variable on Linux

    RLIGATE=<gate_name>

  2. Restart the following service:

    • node-p4rest

Specify Job Parameters

There are 3 keys to influence repro list processing with the PLOSSYS 4 connector.

  • TARGET_FILE_KEY: optional, key where to put the names of local files. Default PLS_ORIG_NAME

  • RLI_JOBNAME_KEY: optional, key in repro list files to be used as job name. Default name. If it does not exist, PLS_PLOTID, PLS_ORIG_NAME and a self-generated UUID are used in this order.

    Hint - case-sensitive

    name is case-sensitive, so, for example, if a Name key is contained in the repro list, it is not used.

  • USER_NAME_KEY: optional, key to store the name of the logged-in user. By default, no user name is set in a repro list passed to PLOSSYS 4. If you want the name of the logged-in user to be set in the repro list, specify the repro list key where to put the user name, for example PLS_USERNAME.

To change any of these keys, execute the following steps:

  1. Export the complete configuration of SEAL Operator from Consul to a YAML file. This ensures that you edit the current configuration.

    operator config export <filename>.yml --insecure

  2. Edit the exported file <filename>.yml.

  3. In the env section, specify the keys you need for the seal-operator-p4 and seal-operator-server services in the operator-p4 and operator-server sections:

    env:
  service:
  ...
    operator-p4:
      tag:
        any:
          ...
          TARGET_FILE_KEY: <plossys_key>
          USER_NAME_KEY: <plossys_key>
  ...
    operator-server:
      tag:
        any:
          ...
          RLI_JOBNAME_KEY: <rli_key>
  ...

  4. Save the <filename>.yml file.

  5. Re-import the file to Consul.

    operator config import <filename>.yml --insecure

  6. Check the imported value of a key you have set, for example TARGET_FILE_KEY:

    operator config get TARGET_FILE_KEY --service operator-p4 --insecure

Import Repro List Files

You can import Repro List Files either via Drag & Drop or via URL parameter.

Via Drag & Drop

In SEAL Print Client, drag & drop the repro list file to the list panel (My Lists) or any PLOSSYS panel.

Via Web Server

To import a repro list to SEAL Operator, you can use a Web server which provides the repro list. Add the URL of the repro list as parameter to the URL when calling the PLOSSYS 4 Panel in your web browser:

https://<operator_server>:3000/import?open-panel=operator-p4&list=<repro_list_url>

Example - import via Web server

https://my-operator-host.example.com:3000/import?open-panel=operator-p4&list=http:%2F%2Fmy-repro-host.example.com:9125%2Ftest.rli

Hint - Content-Type application/rli

Ensure that the Web server which provides the repro list sets Content-Type to application/rli in the response header!

Logging

Messages concerning the list import are logged into the following log files:

  • Windows: %PROGRAMDATA%\SEAL Systems\log\seal-operator-server.log

  • Linux: /var/log/seal/seal-operator-server.log

Example of a Repro List

Example - repro list referring local files for PDM

[PROGRAM]
    VERSION             "01.00"
    PLOT_DIREKT         "Y"
    LOG_LEVEL           "diag"

[PROCESSING]
    PROCESS_GOOD        "pass"
    PROCESS_MISSING     "pass"
    PROCESS_UNKNOWN     "pass"

[JOBINFO]
    JOBID               "Project X, Job 0000001"
    PLOTTER             "LaserJet"
    FORMAT              A3
    MEDIUM              PA
    COPIES              1
    SET_COPIES          1
    STAMP_0             "Only for information"
    COVER_MESSAGE_1     "Local documents for project X. This is only for information. Documents are not released yet."
    COVER_MESSAGE_2     "Due-date: 26.12.2019"
    COVER_MESSAGE_4     "!!! Only for internal use !!!"

[SENDER]
    USER                "johndoe"
    CREATOR             "johndoe"
    REALUSER            "johndoe"
    CREATENODE          "SERVER1"
    FULLNAME            "John Doe"
    DESCRIPTION         "Lead developer"
    EMAIL_DIS           "john.doe@example.com"
    ADDR_DIS_1          "%FULLNAME%"
    ADDR_DIS_2          "Development"
    ADDR_DIS_3          "%EMAIL_DIS%"
    ADDR_DIS_4          ""

[RECEIVER]
    janedoe

[janedoe]
    PRINT_COVER         "Y"
    PRINT_RECEIPT       "Y"
    PRINT_TRAILER       "Y"
    DRAWLIST            "Y"
    PRINT_DRAWING       "Y"
    DEPARTMENT          "Manufacturing"
    EMAIL_REC           "Jane.Doe@example.com"
    ADDR_REC_1          "Jane Doe"

[jackdoe]
    PRINT_COVER         "Y"
    PRINT_RECEIPT       "Y"
    PRINT_TRAILER       "Y"
    DRAWLIST            "Y"
    PRINT_DRAWING       "Y"
    DEPARTMENT          "Sales and Distribution"
    EMAIL_REC           "Jack.Doe@example.com"
    ADDR_REC_1          "Jack Doe"

[REPRO_LIST_FORMAT]
    RECEIVER            #0
    Nummer              #1
    Blatt               #2
    Index               #3
    Status              #4
    Titel               #5
    PLOTTYPE            #6
    LOCALFILE           #7

[REPRO_LIST]
##10000001#001#01#test#Overview#PDF#pdmtest_local.pdf
##20000002#002#02#test#Statistics#PDF#pdmtest_local.pdf
##30000003#003#03#test#Roadmap#PDF#pdmtest_local.pdf

Hint - HREF value

When using repro lists with a PLOSSYS Output Engine backend system LOCALFILE reference is not needed. Instead the list needs to contain HREF file locations. For example

...
    [REPRO_LIST_FORMAT]
    RECEIVER            #0
    Nummer              #1
    Blatt               #2
    Index               #3
    Status              #4
    Titel               #5
    PLOTTYPE            #6
    HREF                #7
...
Back to top