Skip to Content

Ports used by MetaServices

Last modified by Admin on 2024/08/08 21:19

Introduction

This article lists all the ports used for MetaServices communication and describes them according to their purpose.

Web Services

The MetaServices use the Windows-httpsys component for communication. It created a listener on Port 81 by default and registers an additional URL with ISS on Port 80.

PortPurposeLink
3082Web Listener for Administration, Client Access via WebExtensions and MetaServices-AddInhttp://localhost:3082
80Web Listener using IIS on path /MetaServices. Can be used for Administration as well but was introduced to route client traffic from WebExtensions (SmartSearch) through RemoteConnector (Skins are marked with the suffix "RemoteConnector")http://localhost/MetaServices
443Web Listener for SSL using IIS on path /MetaServices. To activate SSL connections for this path a valid certificate has to be selected in ISS configuration. How-To can be found here.https://localhost/MetaServices
3445Web Listener for SSL traffic. To activate SSL connections a valid certificate has to be installed. How-To can be found here.https://localhost:3445

LDAP Access

All client components, such as WebExtensions, MetaServices AddIn, Event Controller, access the MetaServices using XML-requests on the beforementioned ports. It is possible though to separate the ESTOS LDAP server component from the MetaServices which always have to be installed on the SwyxServer directly.

PortPurpose
390Default LDAP port for ESTOS server used by MetaServices. This port is usually accessed only locally from the MetaServices service. In the scenario of a remote ESTOS installation the communication between the SwyxServer and ESTOS component will use this port or the configured port in ESTOS if changed (could be 389 or 712).