Because Meridian data is stored on a server, Meridian relies heavily on network performance. Therefore, the local area network bandwidth between all Meridian client and server computers must be 100 Mbps or higher to ensure adequate performance. The bandwidth between Meridian servers (application servers, database servers, web servers, and other servers used by Meridian) should be 1 Gbps or higher (preferably optical links and very reliable). There should be no switches, routers, hubs, or network cards slower than 100 Mbps at any point between Meridian computers. Just as important as speed is the latency (delay) of the network, which should be under 5 milliseconds between all LAN client computers and the Meridian application server. A latency of less than 300 ms is required when using application links in Remote mode over wide area networks. If the latency is higher, we recommend using Offline mode instead.
Real-time bandwidth, latency, and Meridian application server responsiveness can be measured with the Diagnostics command in PowerUser.
If you use more than one Windows server or more than a few Windows workstations, we recommend implementing a Windows domain structure. We highly recommend installing Meridian only on a member server, not a domain controller. You might also need to configure security delegation as described in Security Delegation.
Meridian relies heavily on the DCOM protocol. By default, DCOM communicates over a very wide port range (1024 to 65535). The Meridian desktop clients always start a DCOM session with a request on the TCP port 135 of the Meridian application server. If a response is received, DCOM handles further communications and determines which port will be used. It's essential to ensure that DCOM is running with TCP/IP only. If possible, delete all other protocols except TCP/IP if you are not using them. If you only have a restricted number of ports to use, refer to the Microsoft MSDN site for the current recommendation for the minimum number of ports to allocate. Additional information about Windows port requirements can be found at Service overview and network port requirements for Windows.
The following table lists the default TCP port numbers that Meridian relies upon. Some of the ports are configurable as described elsewhere in this guide. Other ports may be used by some third-party applications, particularly AutoVue. For information about the ports used by AutoVue, refer to the AutoVue Client/Server Deployment Installation and Configuration Guide.
| Port | Description |
Remarks |
|---|---|---|
|
25 |
SMTP email notifications |
Used by EDM Server and Enterprise Server to send notification emails. |
| 80 | HTTP (PowerWeb) |
Used by the PowerWeband Explorer clients for HTTP connections. |
| 135 | DCOM port negotiation |
Used by PowerUser, WebAccess, and Enterprise Server to connect to EDM Server and License Server. |
| 443 | HTTPS (PowerWeb) |
Used by the PowerWeband Explorer clients for HTTPS connections. |
| 445 | Server Message Block (SMB) |
Used by EDM Server and Enterprise Server to exchange files. |
| 587 | SMTP SSL email notifications |
Used by EDM Server and Enterprise Server to send notification emails. |
| 1024 to 65535 | DCOM communication |
Used by PowerUser, WebAccess, and Enterprise Server to connect to EDM Server and License Server. |
| 8080 | Meridian Enterprise |
Used by EDM Server to connect to Enterprise Server. |
| 8450 | BlueCielo Connector SSL |
Used by PowerUserand Publisher for AutoVue integration. |
| 8686 | Meridian Enterprise |
Used by EDM Server to connect to Enterprise Server. |
| 8900 | BlueCielo Connector |
Used by PowerUser and Publisher for AutoVue integration. |
