Free trial
Vivansa home

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 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.

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?

You no longer face the difficulty with proprietary CSI programming.

Developing CSI-based interfaces using the proprietary CSI API is known to be complex and involves (hard to find) specialist knowledge and experience. lxr.CCN removes this barrier by offering a standard Web Service-based interface that completely hides the complexity of CSI programming and underlying protocols. Applications Platforms no longer require to use the CSI stack; all is managed by lxr.CCN. Developers can apply state-of-the-art practices. Your National Administration gains staffing flexibility and reduces costs while maintaining (or evolving) EU applications or developing new ones.

euro_symbol

You strongly reduce maintenance costs due to EU applications sharing the same connector.

lxr.CCN allows to harmonise and rationalise the way EU applications connect the CCN Network. This means that your administration is no longer constrained to maintain a large variety of – sometimes outdated – technology stacks per EU application. Instead, lxr.CCN provides a Web Service-based shared access point for all EU applications. As a result, EU applications are decoupled from the complexity of handling CSI interfaces individually. Overall, this means a strong reduction of maintenance costs and higher scalability.

mediation

You prepare the future and facilitate the potential transition towards CCN2.

lxr.CCN has the potential to play the role of EU applications dispatcher between the current CCN Network and the forthcoming CCN2 (to be seen as a major upgrade of the current CCN Network proposing new services on top of existing CSI-based services which will be kept). This means that lxr.CCN offers a straightforward way for National Administrations to execute the gradual transition of current EU applications (NCTS, VIES, EMCS, etc.) to the CCN2 Network, should such change be decided by DG TAXUD and National Administrations.

0
Customs Administrations using lxr.CCN into production, 5 others currently evaluating it.
0+
Trans-European Systems making use of lxr.CCN.
0+
messages processed by lxr.CCN every day.

Vivansa releases the NJCSI version of lxr.CCN

commentNo Comments
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

commentNo Comments
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

commentNo Comments
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…