# Configuring Acceptors

Author: Eike Stepper

The acceptors of a CDO Server are configured in the cdo-server.xml file. Here's an example:

| cdo‑server.xml |  |  |  |
`<?xml version="1.0" encoding="UTF-8"?> <cdoServer> <acceptor type="tcp" listenAddr="0.0.0.0" port="2036"/> <!-- other acceptors and repositories --> </cdoServer>`

The following sections describe the various elements and properties.

Table of Contents

1 | Element acceptor
2 | Element negotiator

## 1 Element acceptor

Defines an `IAcceptor` instance. Please refer to the Net4j Signaling Platform documentation for details about acceptors and connectors.

The `type` attribute corresponds to the type of an acceptor factory that is contributed via the `org.eclipse.net4j.util.factories` extension point with a product group of `org.eclipse.net4j.acceptors`.

The remaining attributes depend on the specified `type` attribute value. The following values are possible with the shipped distribution (subject to user-supplied extension):

- tcp: `ITCPAcceptor` for fast, new I/O based socket connections. The following additional attributes are recognized:
  - listenAddr: The network address the server socket shall be bound to. A value of `"0.0.0.0"` is the default (whole attribute can be omitted) and tells the socket to listen on all available addresses.
  - port: The network port the server socket shall be bound to. A value of `2036` is the default (whole attribute can be omitted).
- ssl: Similar to tcp but with transport-level security (TLS).
- ws: `IWSAcceptor` for WebSocket-based connections over HTTP.
- jvm: `IJVMAcceptor` for JVM internal (non-socket based ) connections.

## 2 Element negotiator

Defines an `INegotiator` instance to be used by the enclosing acceptor element. Please refer to the Net4j Signaling Platform documentation for details about negotiators and the pluggable security concept that can be used for authentication and authorization on the transport-level.

The `type` attribute corresponds to the type of a negotiator factory that is contributed via the `org.eclipse.net4j.util.factories` extension point with a product group of `org.eclipse.net4j.negotiators`.

The remaining attributes depend on the specified type attribute value. The following values are possible with the shipped distribution (subject to user-supplied extension):

- challenge: Negotiator for simple yet effective and cryptographically secure challenge/response-based negotiations. The following additional attributes are recognized:
  - description: The absolute path to a file in the local file system that contains the credentials of the users in the form `user-id: password`.

Copyright (c) 2004-2026 Eike Stepper (Loehne, Germany) and others.
All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html