lxr.CCN is a performing software connector to be used as a reliable “bridge” solution for EU Customs & Taxation applications that needs to connect the trans-European CCN Network. lxr.CCN offers to those applications a standard and loosely-coupled Web Service interface that hides the proprietary CSI interface to developers (no knowledge of CSI required anymore!). lxr.CCN also provides enhanced administration facilities that transform complex configuration tasks into a piece of cake.
NEED TO CONNECT EU APPLICATIONS TO THE CCN NETWORK?
FACING THE COMPLEXITY OF MAINTAINING MULTIPLE CSI STACKS?
THEN lxr.CCN IS WHAT YOU NEED.
lxr.CCN is “multi-application”, i.e. it can be shared by multiple national Customs/Excise applications (e.g. NCTS, VAT refund, MOSS, EMCS, SEED, ECS, ICS, etc.) connecting the CCN network. Both CCN/CSI and CCN Intranet channels are supported.
What value does lxr.CCN bring to you?
Customs Administrations using lxr.CCN into production, 5 others currently evaluating it.
Trans-European Systems making use of lxr.CCN.
messages processed by lxr.CCN every day.
BRUSSELS; February 1, 2021 — We’re happy to announce the release of lxr.CCN 2.7.0. This version integrates the support of NJCSI 5.0 and runs on Weblogic 12.2.1 and above. To make this change transparent to legacy applications, lxr.CCN 2.7.0 makes use of the JCSI/NJCSI wrapper (embedded in NJCSI 5.0). Therefore, the upgrade to lxr.CCN 2.7.0…
Update on lxr.CCN.HTTP and CCN Gateways 8.0
BRUSSELS; October 19, 2020 — To all lxr.CCN users: it has come to our attention that the latest version (8.0) of the CCN software (running on the CCN Gateways) has an adverse impact on the lxr.CCN connector functioning. The problem is that CCN 8.0 involves an Apache upgrade to version 2, which has the effect…
lxr.CCN : a solution to smoothly migrate JCSI applications
As announced by the DG TAXUD, the JCSI stack will be decommissioned soon (the current deadline is set 31-Mar-2021). This means that National Administrations running EU applications still using the JCSI stack will be required to migrate each of them to the (new) NJCSI stack, which can reveal a complex and costly activity. This migration…