Autoform DM - Virus Checker Exceptions

Prev Next

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

Folders

Purpose

Location

Example

Installation folder

As installed

C:\Program Files\Formpipe Software\AUTOFORM DM\Server_10.x.x\

Archive folder

Configured in Server Settings

C:\ARCHIVE

Chunks folder

Usually within Archive folder

C:\ARCHIVE\chunks

Temp folder

Default windows directory

C:\Windows\Temp

Note:

Autoform DM related temp files are prefixed with PDM_

Ports (standalone)

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

Purpose

Location

Example

HTTPS

Incoming

443

HTTP Management

Incoming

9990

Database connection

Outgoing

1433

SMTP (if emailing is configured)

Outgoing

25

Secure SMTP (if emailing is configured)

Outgoing

465, 587

LDAP server

Outgoing

389

LDAPS server

Outgoing

636

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 Type

Default Port

MS SQL Server

1433

Oracle

1521

PDC / SDC

Interfaces / Interface selection

  • management

    • default interface: 0.0.0.0 (IPv4 wildcard).

    • 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).

  • multicast

    • the multicast address chosen during installation.

Ports

Purpose

Wildfly Interface

Default Port

Protocol

Overridden by

Obeys port offset?

HTTP Management

management

19990

TCP

jboss.management.http.port

✘

Native Management

management

19999

TCP

jboss.management.native.port

✘

HTTP

wildcard

8080

TCP

jboss.http.port

✔

HTTPS

wildcard

8443

TCP

jboss.https.port

✔

mcmp-management

public

8090

TCP

jboss.mcmp.port

✔

modcluster

multicast

23364

UDP

–

✘

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:

Purpose

Wildfly Interface

Default Port

Protocol

Overridden by

Obeys port offset?

HTTP Management

management

19990

TCP

jboss.management.http.port

✘

Native Management

management

19999

TCP

jboss.management.native.port

✘

HTTP

wildcard

8080

TCP

jboss.http.port

✔

HTTPS

wildcard

8443

TCP

jboss.https.port

✔

ajp

public

8009

TCP

jboss.ajp.port

✔

jgroups-udp

public

55200

UDP

–

✔

multicast

45688

UDP

–

✘

modcluster

multicast

23364

UDP

–

✘

jgroups-udp failure-detection

private

54200

UDP

–

✔

iiop

unsecure

3528

TCP

–

✔

iiop-ssl

unsecure

3529

TCP

–

✔

Was this page helpful? Let us know at knowledgebase.feedback@lasernetgroup.com