Features
Everything you need to run CCN in production.
lxr.CCN handles message exchange between the CCN network and your national applications while meeting the non-functional requirements that matter — availability, guaranteed delivery, security, logging and failover — all behind one standard Web Service.
Two branches
One connector, two supported branches.
lxr.CCN ships on two parallel, fully-maintained branches — so you can match it to your Oracle WebLogic environment. Both carry the same features.
2.x branch
Most widely deployedLatest: 2.8.3.1 · Oracle WebLogic 12c
The proven branch — in production across national administrations today, and still the most widely deployed. Runs on the CSI stack through the NJCSI compatibility wrapper, and remains fully maintained.
3.x branch
Native NJCSI · multi-threadedLatest: 3.1.0 · Oracle WebLogic 12.2.1+
A native re-implementation on the NJCSI stack. It removes the single-thread limitation of the legacy JCSI stack — the CCN message processor becomes multi-threaded, improving the performance of interactions with the CCN Gateway.
Both branches are fully maintained — the choice is yours:
- Stay on 2.x — keep your current installation and take the latest 2.x releases.
- Move to 3.x — migrate whenever it suits you (needs Oracle WebLogic 12.2.1+) for its multi-threaded performance.
The End-of-Support Matrix lists supported versions and dates; the release news covers what’s in each.
Reliability
Built for business-critical availability.
CCN connectivity is critical infrastructure. lxr.CCN is engineered for the non-functional requirements that come with it.
High availability
Supports business-critical national applications with high-availability requirements — built to keep CCN traffic flowing.
Guaranteed delivery
Message exchange between CCN and your applications with guaranteed delivery, not best-effort.
Clustering & failover
Run multiple connector instances (multi-instantiation) for clustering and failover.
Logging & monitoring
Full logging and monitoring of the message flow is built in, not bolted on.
Interfaces
Every CCN paradigm, as a Web Service.
Whatever the exchange pattern, your application calls a standard, loosely-coupled Web Service — SOAP for the CSI channels (asynchronous and synchronous), an HTTP proxy for the Intranet channel — and lxr.CCN maps it to CSI. Your development teams need no CSI knowledge — and wherever CSI expertise is needed, Vivansa’s support team has it covered.
CSI Asynchronous
Standard SOAP Web Service interfaces for asynchronous exchange:
- Submission
- Callback
- Delayed Callback
CSI Synchronous
Synchronous SOAP request/response, both directions:
- Synchronous Outgoing
- Synchronous Outgoing Callback
- Synchronous Incoming
- Synchronous Incoming Callback
HTTP over CCN Intranet
Standard HTTP proxy interfaces for the Intranet channel:
- lxr.CCN.HTTP client
- lxr.CCN.HTTP server
Operations
One connector, many applications, under control.
Serve every national application from a single connector, and tune how each one behaves against CCN.
Multi-application
Manage concurrent message exchange for several national applications at once — NCTS, EMCS and more — through one connector.
Secure transport
Traffic to and from CCN is secured at the transport layer with HTTPS and mutual TLS (mTLS) — the current CCN mechanism for message integrity and confidentiality.
Throttling & pacing
Configurable throttling and pacing for outgoing messages, so you control the load you put on CCN.
Message tracking
Operational tracking by message-id, with persistent storage and purge so history stays manageable.
Development & testing
Test without touching live CCN.
Integrate and validate on a developer workstation — no CCN Gateway, no risk to production traffic — then promote with confidence.
Loopback mode
Exercise your integration locally in loopback mode — no CCN round-trip required.
CCN simulator
Develop and test on a workstation against a built-in CCN simulator, without a live CCN Gateway.
Good to know before you go live: CCN provides no test gateways outside Member-State networks, so only National Administrations have access to a CCN Gateway. Vivansa validates every release against the simulator — but anything that exercises the CCN/CSI (NJCSI) library ultimately has to be verified on your own Gateway. Plan to validate a new release in your test / pre-production environment before Production, especially the 3.x branch (a native NJCSI re-implementation).
Administration
A web console for the SysOps.
Everything a CCN operator needs day to day, in one user-friendly web interface — take the tour.
Processors
2 / 2
Nodes running
18,204
Messages today
3
In queue
0
Failed · 24h
| Priority | Node | Status | Last heartbeat | Age (s) |
|---|---|---|---|---|
| 1 | ccn-node-01 | RUNNING | 2026-07-28 09:14:32Z | 4 |
| 2 | ccn-node-02 | STANDBY | 2026-07-28 09:14:30Z | 6 |
- Authentication & access control
- Message search, purge & archive
- Pending-message visibility
- Application configuration
- Partner-list configuration
- Configuration history
- Statistics
- Unavailability scheduling
Built by the team that has kept lxr.CCN in production at national customs and tax administrations since 2010.
See it against your own applications.
Start a free evaluation and connect lxr.CCN to your national applications — or talk to us about your CCN setup first.