Language: Deutsch · English

Connection

KONZEPT DEVELOPER / ADMINISTRATOR UPDATED: JUL 2026 APPLIES TO NUCLOS 4.2026.X

Menu Administration → Connection. With connections you integrate a Nuclos server more deeply into its system landscape via so-called Nuclos interfaces – e.g. phone systems, SMS services or any system reachable via Java (including RESTful services).

Interface vs. connection

• An interface is a server extension (in Java, as a JAR) that runs permanently and, e.g., receives events from a phone system – comparable to a hardware driver. It is normally based only on the Nuclos API (backward compatibility).
• A connection is the concrete use of an interface with its parameters (host, port, user …). An interface can be configured as a connection any number of times; additionally Nuclos users can be linked to connection accounts.

Integration via rule

An interface's events are integrated into the business logic via a communication rule (in the rule manager). Contexts:

• PhoneCallNotificationContext / PhoneCallRequestContext – for telephony. With the request context a user can dial a number directly from Nuclos (attribute type PhoneNumber, stored account – then the dial number button appears).
• GenericNotificationContext – universal, works with a key-value map.

Developing interfaces

The API knows two types: PhoneCall (phone systems) and GenericNotification (special cases). If an interface implements PhoneCall, it can be swapped when changing systems without touching the business logic. The freely usable com-interface-template serves as a template; specifying the Java package in comport-template-server-beans.xml is important.

Related pages