Configure the Repro List Processing¶

By default, the PLOSSYS netdome (p4) connector interprets jobs as set collations for PLOSSYS netdome. The jobs are generated as set collations and sent to the stargate.

Alternatively, you can activate the repro list processing in the PLOSSYS netdome (p4) connector, that 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.

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

Activate the Repro List Processing¶

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

Export the complete configuration of SEAL Operator from Consul to a YAML file in order to ensure that the current configuration settings are used.
```
operator config export <filename>.yml --insecure
```

In the env section, specify the following key for the operator-p4 service:

TARGET_CONTENT_TYPE: PLOSSYS netdome-specific job format, here application/rli

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

Save the <filename>.yml file and re-import it to Consul.
```
operator config import <filename>.yml --insecure
```

Change the Target Gate¶

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

Open the Windows System dialog and select Advanced System Settings.
In the System Properties dialog, select Environment Variables.
Specify the following node-p4rest key as System Variables:
- RLIGATE: Name of the target directory for the repro list files (rli, rlist) without path
Restart the following service:
- node-p4rest

Change the PLOSSYS netdome Key Used for Storing the Names of the Local Files¶

By default, PLS_ORIG_NAME is used as PLOSSYS netdome key used for storing the names of the local files. For using another key, execute the following steps:

Export the complete configuration of SEAL Operator from Consul to a YAML file in order to ensure that the current configuration settings are used.
```
operator config export <filename>.yml --insecure
```

In the env section, specify the following key for the operator-p4 service:

TARGET_FILE_KEY: Key where to put the names of local files

env:
  service:
  ...
    operator-p4:
      tag:
        any:
          ...
          TARGET_FILE_KEY: <plossys_key>
  ...

Save the <filename>.yml file and re-import it to Consul.
```
operator config import <filename>.yml --insecure
```

Change the Repro List Key Used as Job Name in SEAL Print Client¶

By default, the name repro list key is used as key whose value is used as job name in SEAL Print Client. Unless name exists in the repro list file, 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 will not be used!

For using a key different to name, execute the following steps:

Export the complete configuration of SEAL Operator from Consul to a YAML file in order to ensure that the current configuration settings are used.
```
operator config export <filename>.yml --insecure
```

In the env section, specify the following key for the seal-operator-server service:

RLI_JOBNAME_KEY: Key in repro list files whose value is used as job name in SEAL Print Client

env:
  service:
  ...
    operator_server:
      tag:
        any:
          ...
          RLI_JOBNAME_KEY: <rli_key>
  ...

Save the <filename>.yml file and re-import it to Consul.
```
operator config import <filename>.yml --insecure
```

Pass the Name of the Logged-In User As Repro List Key¶

By default, no user name is set in a repro list passed to PLOSSYS netdome. 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 (e. g. PLS_USERNAME).

The key will be set in the default section and with any document section regardless of an already existent user name in the repro list. If this key already exists in the default section and/or with any document section, its value will be overwritten. Otherwise, the key will be added.

For specifying a key where to put the user name, execute the following steps:

Export the complete configuration of SEAL Operator from Consul to a YAML file in order to ensure that the current configuration settings are used.
```
operator config export <filename>.yml --insecure
```

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

USER_NAME_KEY: Key where to put the name of the logged-in user

env:
  service:
  ...
    operator_p4:
      tag:
        any:
          ...
          USER_NAME_KEY: <plossys_key>
  ...

Save the <filename>.yml file and re-import it to Consul.
```
operator config import <filename>.yml --insecure
```