Ports Used

You must sometimes configure this application’s port availability on firewalls. Sometimes, excluding applications from firewall interference is all that is required (see Ports and Application To Exclude from Firewall). If you have remote mediation servers, see Remote Mediation Ports.

The following are some of the standard port assignments for installed components. These are often configurable (even for “standard” services like FTP or HTTP), so these are the typical or expected port numbers rather than guaranteed assignments. Also, see Protocol Flows for more about network connections.

[spacer]

Destination Port(s)

Service

File(s)

Notes

Used from Client

HTTP/S (Web Client)

80804

oware.webservices.port

[user.root]\oware\lib\owweb services.properties

appserver

Yes

84434, 5, 7

org.apache.coyote.tomcat4.CoyoteConnector (Apache)

[user.root]\oware\jboss-3.2.7\server\oware\deploy\jbossweb-tomcat41.sar\META-INF\ jboss-service.xml

app/medserver

No

Other Ports

n/a5(ICMP)

ping

 

MedSrv -> NtwkElement, NtwkElement -> MedSrv, ICMP ping for connection monitoring.

 

204, 5, 7 (TCP)

FTP Data Port

n/a

(Internally configurable), "MedSrv -> FTPSrv

NtwkElement -> FTPSrv"

medserver1

No

214, 5, 7 (TCP)

FTP Control Port

n/a

(Internally Configurable) "MedSrv -> FTPSrv

NtwkElement -> FTPSrv"

medserver1

No

224, 5, 7 (TCP)

SSH

n/a

MedSrv -> NtwkElement, secure craft access

medserver1

No

234, 5, 7 (TCP)

Telnet

n/a

MedSrv -> NtwkElement, non-secure craft access

medserver1

Yes

254, 5, 7 (TCP)

com.dorado.mbeans.OWEmailMBean (mail)

[user.root]\oware\jboss-3.2.7\owareconf\oware-service.xml

AppSrv -> SmtpRelay, communication channel to email server from Appserver

No

694, 5, 7 (UDP)

TFTP

n/a

(Configurable internally), F, MedSrv -> TFTPSrv

NtwkElement -> TFTPSrv

medserver1

No

1614, 5, 7

(UDP)

com.dorado.media tion.snmp.request.listener.port (SNMP), oware.media tion.snmp.trap.forward ing.source.port

[user.root]\oware\lib\owmediationlisteners.properties, [user.root]\oware\lib\owmediation.properties

MedSrv -> NtwkElement, SNMP request listener and trap forwarding source

medserver1

No

1624, 5 (TCP)

oware.media tion.snmp.trap.forwarding.des tination.port (SNMP)

[user.root]\oware\lib\owme diation.properties

NtwkElement -> MedSrv, SNMP trap forwarding destination port, medserver1

No

5144, 5 (UDP)

com.dorado.mediation.syslog.port (syslog)

 

NtwkElement -> MedSrv (mediation syslog port) medserver1

No

10984, 5, 7 (TCP)

org.jboss.naming.NamingService (JBOSS)

[user.root]\oware\jboss-3.2.7\owareconf\jboss-root-service.xml

AppSrv -> MedSrv

MedSrv -> AppSrv

user client ->AppSrv

user client ->MedSrv, (JBOSS naming service), app/medserver

Yes

10994, 5, 7 (TCP)

org.jboss.naming.NamingService (JBOSS)

[user.root]\oware\jboss-3.2.7\owareconf\jboss-root-service.xml

MedSrv -> AppSrv, user client -> AppSrv, user client -> MedSrv,

(JBOSS naming service & OWARE context server URL), app/medserver

Yes

10992, 4, 5, 7 (TCP)

OWARE.CONTEXT.SERVER.URL

 

 

 

 

 

 

 

[user.root]\oware apps\install props\lib\installed.properties

[user.root]\oware apps\install props\medserver\lib\installed.properties

MedSrv -> AppSrv, user client -> AppSrv. user client -> MedSrv. (JBOSS naming service & OWARE context server URL)

 

client

 

 

 

medserver1

Yes

1100 - 1101

 

 

 

 

11034, 5 (UDP)

jnp.reply.discoveryPort (JNP)

[user.root]\oware\lib\owappserver.properties

AppSrv -> MedSrv, AppSrv -> user client, (JNP reply discovery port), app/medserver

Yes3

11234, 5 (UDP)

jnp.discoveryPort (JNP)

[user.root]\oware\lib\owappserver.properties

MedSrv -> AppSrv, user client -> AppSrv, (JNP discovery port), app/medserver

Yes3

15214, 7 (TCP)

com.dorado.jdbc.database_name.oracle (JDBC)

[user.root]\oware apps\install props\lib\installed.properties

AppSrv ->OracleDBSrv, (JDBC database naming [Oracle])

database

No

18124, 7 (TCP)

RADIUS port

[user.root]\oware\jboss-3.2.7\server\oware\conf\login-config.xml

AppSrv -> RADIUS Srv, Appserver (RADIUS

client login enabled – optional)

No

25064, 5, 7 (TCP)

JMS - SONICMQ_CLIENT_PORT (JMS)

[user.root]\oware\lib\owapp server.properties

MedSrv -> AppSrv

user client -> AppSrv, (JMS - SonicMQ client port) app/medserver

Yes

25074, 7 (TCP)

JMS - SONICMQ_CONFIG_PORT

[user.root]\oware\lib\owapp server.properties

AppSrv -> AppSrv

MedSrv -> AppSrv, (JMS - SonicMQ client port), app/medserver

No

25084, 7

JMS - SONICMQ_INTERBROKER_POR T (JMS)

[user.root]\oware\lib\owapp server.properties

AppSrv -> AppSrv, MedSrv -> AppSrv,

(JMS - SonicMQ interborker port), app/medserver

No

33064, 7 (TCP)

com.dorado.jdbc.database_name.mysql

[user.root]\oware apps\install props\lib\installed.properties

AppSrv -> MySQLSrv, (JDBC database naming [MySQL]) appserver)

No

31004, 5, 7 (TCP)

32004, 5, 7

org.jboss.ha.jndi.HANaming Service (JBOSS)

[user.root]\oware\jboss-3.2.7\owareconf\cluster-service.xml

AppSrv -> AppSrv,

user client -> AppSrv

AppSrv -> MedSrv MedSrv -> AppSrv user client -> AppSrv user client -> MedSrv (JBOSS HA JNDI HA Naming service [3100 is stub]

app/medserver

Yes3

4444

 

 

 

 

44454, 5, 7 (TCP)

org.jboss.invocation.pooled.server.PooledInvoker (JBOSS)

[user.root]\oware\jboss-3.2.7\owareconf\jboss–root-service.xml

AppSrv -> MedSrv

MedSrv -> AppSrv

user client -> AppSrv

user client -> MedSrv, app/medserver

Yes

44464, 5, 7 (TCP)

org.jboss.invoca tion.jrmp.server.JRMPInvoker (JBOSS)

[user.root]\oware\jboss-3.2.7\owareconf\jboss–root-service.xml

(AppSrv ->AppSrv, AppSrv -> MedSrv, MedSrv -> AppSrv, user client -> AppSrv, user client -> MedSrv) app/medserver

Yes

5988, 5989

WBEM Daemon (5989 is the secure port) defaults

 

You can add ports and daemons in monitored services. These are only the default. WBEM requires one port, and only one, per daemon.

No

6500-104, 5, 7 (TCP)

JBOSS

 

user client -> MedSrv (user client to mediation server cut-through)

Yes

78002(TCP)

org.jboss.ha.frame work.server.ClusterPartition (JBOSS)

[user.root]\oware\conf\cluster-service.xml

disabled - see UDP for same, (JBOSS HA frame work server cluster partition) TCP only

No

8009 (TCP)

org.mort bay.http.ajp.AJP13Listener

[user.root]\oware\jboss-3.2.7\server\oware\deploy\jbossweb-tomcat41.sar\META-INF\ jboss-service.xml

Obsolete -- appserver

No

8083 (TCP)

org.jboss.web.WebService (JBOSS)

[user.root]\oware\jboss-3.2.7\owareconf\jboss–root-service.xml

not used (JBoss web services)

appserver

No

80934, 5. 7 (TCP)

org.jboss.mq.il.uil2.UILServerILService

[user.root]\oware\jboss-3.2.7\owareconf\uil2-service.xml

MedSrv -> AppSrv, user client -> AppSrv (JBOSS mq il uil2 UIL Server-IL Server), app/medserver (Jboss JMS)

Yes

84432,4, 5, 7

org.apache.coyote.tomcat4.CoyoteConnector

[user.root]\oware\jboss-3.2.7\server\oware\deploy\jbossweb-tomcat41.sar\META-INF\ jboss-service.xml

user client -> AppSrv (Apache Coyote Tomcat4 Coyote connector), appserver

No

90014, 6, 7 (UDP)

mediation.listener.multi cast.intercomm.port

[user.root]\lib\owmediation listeners.properties

MedSrv <-> MedSrv (mediation listener multicast intercommunications port)

medserver3

No

313104, 6, 7 (TCP)

JBoss

 

AppSrv -> AppSrv

No

455664, 5 (UDP)

org.jboss.ha.frame work.server.ClusterPartition

[user.root]\jboss-3.2.7\owareconf \cluster-service.xml

AppSrv -> Multicast, (JBoss HA frame work server cluster partition), UDP only

No

540274,7

Process Monitor

[user.root]\oware\lib\pmstar tup.dat

mgmt client -> AppSrv, mgmt client -> MedSrv (process monitor local client for server stop/start/status) app/medserver

Yes

1 Remote mediation servers or application servers behaving as though they were mediation servers (single host installation).

2 Unused in standard configuration.

3 Client does not connect to medserver on this port.

4 This port is configurable.

5Firewall Impacting

6The most likely deployment scenarios will have all servers co-resident at the same physical location; as such, communications will not traverse through a firewall

7Bidirectional

 

To operate through a firewall, you may need to override default port assignments.

If you cluster your installation, you must disable multicast for communication through firewalls (to mediation servers or clients). See Disabling Multicast for more information.

[spacer]

To configure ports, open their file in a text editor and search for the default port number. Edit that, save the file and restart the application server and client. Make sure you change ports on all affected machines.

The mediation service also establishes a socket connection to client on ports 6500 to 6510 for cut through. Such connections are specified in the ezmediation/lib/ezmediation.properties file.

[user.root] = $OWARE_USER_ROOT

Remote Mediation Ports

You must open the following ports between application servers and remote mediation servers: 8443, 3306, 3200, 7800, 8009, 8080, 9001, 31310, 45566.