Parameters
In summary, all parameters of the Communication Forward Manager and their meaning are described in the following table. In the delivered standard of the DMZ server, all of these are contained in the configuration file ./etc/startup_dmz.xml (possibly commented out). As far as possible, default values that make sense are maintained.
|
Parameter |
Function |
Allowed values [Default] |
|
setForwardHost |
Address of (inner) Lobster_data machine and port number of Message Service. |
IP or host name and port [Port: 8020] |
|
handleEmptyFiles |
Handling of empty (0 bytes) files. |
0=skip, 2=transfer,1=delete [0] |
|
isdnNumber |
Only for OFTP via ISDN. |
Telephone number |
|
keepMessages |
Lead time in minutes, how long undelivered messages are stored (also see backupDir). |
[120] |
|
backupDir |
Directory that stores a backup of sent files. Empty path/lead time < 1 deactivates backup. |
|
|
noForwardRulesForFtp |
Path to property file that defines for which FTP/SSH/OFTP users no forwarding should take place. |
[ftp_user_rules.properties] in [./etc/admin/datawizard/] |
|
traceOftp |
true: Creates a trace file during receipt of OFTP data. |
true|false [false] |
|
otherDMZ |
See section DMZ Cluster. |
|
|
retryInterval |
Number of seconds to wait before a retry. See: retryNumber. |
1-n [30] |
|
retryNumber |
Defines the number of tries if Lobster_data sends data via DMZ. |
1-n [3] |
|
keystorePassword |
Empty or password for keystore. If own certificates are used, the password for the keystore is needed. |
Password, maybe encrypted. No longer necessary due to the use of the Authentication Service. |
|
serverName |
If servlets are not being installed on the standard server Main server, the desired HTTP server needs to be entered here. |
[Main server] |
|
servletContext |
If a different path needs to be used, please enter the URI here. See section Forwarding HTTP Requests Inwards. |
[/forward] |
|
servletPath |
Filter, means all requests to servletContext are filtered. |
[/*] means no filter |
|
addStandardServlets |
If true, forwarding for triggers, requests and AS2 to Lobster_data are set up. See section Forwarding HTTP Requests Inwards. |
true|false [false] |
|
streamingSize |
Specified in MB, from when the payload of a message is no longer attached to the message and Lobster_data.3 fetches payload via FTP or SFTP from DMZ. |
0-n [10] |
|
maxSize |
Specified in kB. Defines max. size of payloads after which they are not forwarded. Value 0 means no limit. |
0-n [0] |
|
handleAS2 |
If true, the local AS2 service is used; false forwards AS2 messages. See section AS2 on DMZ Server. |
true|false [false] |
|
usePersistentMessageForAS2 |
If true, unsuccessfully forwarded AS2 messages are MDN acknowledged with a negative MDN and forwarded to Lobster_data later; false sends an NDN. |
true|false [false] |
|
retainFiles |
Specified in days, how long backups are stored. If 0, no backup is created. |
0-n [0] |
|
checkInnerIS |
If activated, a check is executed every n minutes if the inner IS reacts. If not, a mail is sent to the specified address. |
[not active] |
|
x400Cmd |
Only necessary, if UAFI is used for X.400. DEPRECATED. |
Path to UAFI program. No longer necessary. |
|
forwardUnknownFiles |
If no profile is found, using false will prevent the forwarding. |
true|false [true] |
|
stopServices |
If true, communication services are terminated before stopping the IS. No longer necessary if factory.xml has been created correctly. |
true|false [true] |