Skip to content

Installation

Download

Download the plugin from the customer portal. The portal embeds your personal license key directly into the jar at download time, so there is nothing to install or copy separately; the jar is all you need.

Installing on the POS

  1. Put popup-message-plugin.jar into the plugin directory of the POS: <CCO installation directory>/POSPlugins/AP/
  2. Restart the POS.
  3. In the configuration UI of the POS, open the plugin settings and select the UDF field the messages should come from. That is the setting UDF to use, e.g. udfString1 (see Configuration).

The same jar runs on SAP Customer Checkout 2.0 FP21 (on-premise) and on the Cloud Edition 3.0 up to FP2602; there is no variant to choose.

Verifying the installation

After the restart, the plugin writes a license banner with product name and version to the POS log at startup. For a functional test, book an article that has a message maintained: the warning must appear (see Usage); if it does not, the FAQ helps.

Adding a license key manually (special case)

Normally there is nothing to do; the key is inside the downloaded jar. In case you need to swap in a key (for example one you received from support) without downloading the jar again:

  • Put the key in a file named license-popup-message-plugin.key next to the jar (that is, also in POSPlugins/AP/). An existing, non-empty key file takes precedence over the key embedded in the jar.
  • It is enough to copy the complete contents of the LICENSE.txt from the portal download into the file; the plugin finds the key line in it by itself.
  • An empty key file does no harm; the embedded key then remains in effect.

Without a valid license the plugin disables itself with a clear notice (log entry and a banner on the POS), but it never blocks the POS startup or other plugins. Details in Operations.