Skip to main content

Autoform DM - Virus Checker Exceptions - Knowledgebase / Autoform DM / Autoform DM FAQs - Formpipe Support Portal

Autoform DM - Virus Checker Exceptions

Authors list


This page lists the exceptions configuration which must be applied to any installed virus checker to limit interference with the Autoform DM process.


Folders

PurposeLocationExample
Installation folderAs installedC:\Program Files\Formpipe Software\AUTOFORM DM\Server_10.x.x\
Archive folderConfigured in Server SettingsC:\ARCHIVE
Chunks folderUsually within Archive folderC:\ARCHIVE\chunks
Temp folderDefault windows directoryC:\Windows\Temp



Autoform DM related temp files are prefixed with PDM_


Ports (standalone)

These ports listed below apply to services in which DM connects to:


PurposeLocationExample
HTTPSIncoming443
HTTP ManagementIncoming9990
Database connectionOutgoing1433
SMTP (if emailing is configured)Outgoing25
Secure SMTP (if emailing is configured)Outgoing465, 587
LDAP serverOutgoing389
LDAPS serverOutgoing636


The following lists the default port bindings for each type of node in a cluster and what interfaces they use.

For example, for DM the *HTTP* port will be affected by the port offset, and will use the wildcard interface, which by default is the IPv4 wildcard ‘0.0.0.0’.

Refer to the server logs to see what ports and bindings have been used – messages at server startup along the lines of the following will be present:

HTTP listener default listening on 0.0.0.0:8180
 

Ports (cluster)

Database Server

The database port should be open for the inbound connections. Default port lists:


Server TypeDefault Port
MS SQL Server1433
Oracle1521

 

PDC / SDC

Interfaces / Interface selection
  • management
    • default interface: 0.0.0.0 (IPv4 wildcard).
    • overridden by: jboss.bind.address.management.

 

Ports

PurposeWildfly InterfaceDefault PortProtocolOverridden byObeys port offset?
HTTP Managementmanagement9990TCPjboss.management.http.port

 

LB

Interfaces / Interface selection
  • management
    • default interface: 127.0.0.1 (IPv4 loopback).
    • controlled by: jboss.bind.address.management.
  • public
    • default interface: Any network interface that:
      • supports multicast.
      • and is up and configured.
      • and is NOT the loopback interface.
  • wildcard
    • default interface: 0.0.0.0 (IPv4 wildcard).
  • multicast
    • the multicast address chosen during installation.

 

Ports

PurposeWildfly InterfaceDefault PortProtocolOverridden byObeys port offset?
HTTP Managementmanagement19990TCPjboss.management.http.port
Native Managementmanagement19999TCPjboss.management.native.port
HTTPwildcard8080TCPjboss.http.port
HTTPSwildcard8443TCPjboss.https.port
mcmp-managementpublic8090TCPjboss.mcmp.port
modclustermulticast23364UDP

 

DM

Interfaces / Interface selection
  • management
    • default interface: 127.0.0.1 (IPv4 loopback).
    • overridden by: jboss.bind.address.management.
  • public
    • default interface: Any network interface that:
      • supports multicast.
      • and is up and configured.
      • and is NOT the loopback interface.
  • wildcard
    • default interface: 0.0.0.0 (IPv4 wildcard).
  • private
    • default interface: 127.0.0.1 (IPv4 loopback).
    • overridden by: jboss.bind.address.private.
  • unsecure
    • default interface: 127.0.0.1 (IPv4 loopback).
    • overridden by: jboss.bind.address.unsecure.
  • multicast
    • the multicast address chosen during installation.

 

Ports:

PurposeWildfly InterfaceDefault PortProtocolOverridden byObeys port offset?
HTTP Managementmanagement19990TCPjboss.management.http.port
Native Managementmanagement19999TCPjboss.management.native.port
HTTPwildcard8080TCPjboss.http.port
HTTPSwildcard8443TCPjboss.https.port
ajppublic8009TCPjboss.ajp.port
jgroups-udppublic55200UDP
multicast45688UDP
modclustermulticast23364UDP
jgroups-udp failure-detectionprivate54200UDP
iiopunsecure3528TCP
iiop-sslunsecure3529TCP

Helpful Unhelpful

Share