Parameter‌s for Class 'CommunicationForwardManager‌'

In summary, all parameters of the CommunicationForwardManager and their meaning are described in the following table. In the default installation of the DMZ server, all of these are contained in the configuration file ./etc/startup_dmz.xml (possibly commented out). As far as possible, meaningful default values are used there.

Parameter

Function

Allowed Values [Default]

setForwardHost

Address of (inner) Lobster_data server and port number of the MessageService.

IP or host name and port. Default: 8020

handleEmptyFiles

Handling of empty files (0 bytes).

0=skip, 2=transfer,1=delete. Default: 0

isdnNumber

Only for OFTP via ISDN.

Telephone number.

keepMessages

Retention time in minutes, of how long undelivered messages are kept (see also backupDir).

Default: 120

backupDir

Directory that stores backups of sent files. An empty path or keepMessages < 1 deactivates backup.

Default: No Backup.

noForwardRulesForFtp

Path to property file that defines for which FTP/SSH/OFTP users no forwarding should take place.

Default: ./etc/admin/datawizard/ftp_user_rules.properties


traceOftp

true creates a trace file on OFTP reception.

true|false. Default: false

otherDMZ

See section DMZ Cluster.

retryInterval

Number of seconds to wait before a retry. See also parameter retryNumber.

1-n. Default: 30

retryNumber

Defines the number of tries if Lobster_data sends data via DMZ server.

1-n. Default: 3

keystorePassword

Empty or password for keystore. If local certificates are used, the password for the keystore is needed.

Password, possibly encrypted. No longer necessary due to the use of the AuthenticationService.

serverName

If servlets are not being installed on the standard server Main Server, the desired HTTP server needs to be set here.

Default: Main Server

servletContext

If a different path should be used, please enter the URI here. See section Forwarding HTTP Requests Inwards‌.

Default: /forward

servletPath

Filter, i.e. all requests to servletContext are filtered.

Default: /* (i.e. no filter)

addStandardServlets

If true, forwarding for triggers, requests and AS2 to Lobster_data is set up. See section Forwarding HTTP Requests Inwards‌.

true|false. Default: false

streamingSize

Specification in MB from when on the payload of a message is no longer passed on in the message and Lobster_data fetches the payload from the DMZ server via FTP or SFTP.

0-n. Default: 10

maxSize

Specified in kB. Defines max. size of payloads after which they are not forwarded. Value 0 means no limit.

0-n. Default: 0

handleAS2

If true, the local AS2 service is used. If false forwards AS2 messages. See section AS2 on DMZ Server.

true|false. Default: false

usePersistentMessageForAS2

If true, unsuccessfully forwarded AS2 messages are acknowledged with an MDN and forwarded to Lobster_data later. If false, an NDN is sent.

true|false. Default: false

retainFiles

Specifies in days how long backups are kept. If 0, no backups are created.

0-n. Default: 0

checkInnerIS

If activated, a check is executed every n minutes to see if the inner Integration Server reacts. If not, an email is sent to the specified address.

true|false. Default: Not active (commented out).

x400Cmd

(Only necessary if UAFI is used for X.400. DEPRECATED.)

(Path to UAFI program. No longer necessary.)

forwardUnknownFiles

If no profile can be found, false will prevent the forwarding of files.

true|false. Default: true

stopServices

If true, communication services are terminated before the Integration Server is stopped. No longer necessary if the file ./etc/factory.xml has been created correctly.

true|false. Default: true