Extended ECM support
Extended ECM and xECM support for estates already live

Extended ECM and xECM only earn their keep when the link between content and the line of business system stays honest. When a connector fails quietly, users work around it. By the time someone raises a ticket, two systems of record already disagree.
Nuca supports OpenText estates across the UK, Ireland, DACH and the wider EU. We support live Extended ECM estates as part of an OpenText managed service. We monitor and administer the OpenText side, including xECM connectors into SAP and other line of business systems, and we treat OTDS and the database as part of the same incident, not a handoff. Platform, business and database administration sit under one coordinated support model, for a fixed monthly fee scoped to your estate. Your SAP and line of business teams keep their domains. We keep the content platform and the join between systems stable in production.
We do not sell greenfield xECM implementations, consulting programmes or custom build. If the estate is already live and short of senior OpenText capacity, that is the work we take.
If a second pair of eyes would help, book a free 45-minute continuity check call.
After go live, the risk moves to quiet connector failure
Implementation programmes end. The connector work does not. After go live, the risk often shifts from project milestones to quiet failure: a job that stops telling you the truth, a document that never arrives in SAP or another line of business system, or a permission change that only shows up when a user cannot open a record. Users invent workarounds. Two systems of record drift apart before anyone raises a ticket.
Day to day run for a live Extended ECM estate means watching the OpenText side of those joins, owning the incident when the content platform and the line of business system disagree, and keeping OTDS and the database in the same diagnostic picture. That is operational support for an estate already in production, not a new programme.
Connectors we stay close to: SAP and other line of business systems
We stay close to the OpenText side of xECM connectors into SAP and other line of business systems. Monitoring, administration and incident ownership sit with the same team that runs Content Server, OTDS and the database underneath. When a connector symptom appears, we do not bounce it between an application queue and a database queue.
Your line of business teams keep ownership of their stacks. We keep the content platform and the join stable.

Where ArchiveLink and document access sit in the same estate
Many live Extended ECM estates also depend on ArchiveLink and related document access paths into SAP. Those paths sit in the same production picture as the xECM connectors: content must be findable, retrievable and consistent with what the line of business system expects. When archive retrieval or document access fails quietly, the business feels it as a process fault, not as an OpenText ticket.
We treat ArchiveLink joins that exist on your estate as part of the OpenText operational run, alongside the connectors and the content platform. We do not rebuild archiving programmes. For archive-specific managed run, see also Archive Server managed service.
Platform, OTDS and database as one diagnostic surface
Connector faults rarely live in one neat layer. Authentication through OTDS, platform behaviour and database round trips under OpenText workloads often share the same incident. We treat platform, OTDS and the database as one diagnostic surface so the fault is diagnosed once, rather than handed between queues that each see only part of the picture.
That matches how Nuca runs Content Server estates more broadly across the OpenText platform and the database underneath. Monitoring and alerting run around the clock. Critical-incident response follows the tier you choose. For a deeper companion read, see OpenText ECM database administration and Content Server managed services.

Working with your SAP and line of business teams without owning their stack
Your SAP and line of business teams keep their domains. We do not take over their stack, their change calendars or their functional ownership. We work with them when an incident crosses the join: we bring the OpenText evidence, they bring the line of business evidence, and the fault gets owned rather than bounced between two correct-looking status pages.
That boundary matters. Nuca complements the specialists you already have. We relieve the OpenText operational load on live Extended ECM and xECM estates. We do not replace the people who know your SAP and other line of business landscapes, and we do not compete with the vendor path those teams already use for their own platforms.
How this sits next to OpenText vendor support and Current Maintenance
Nuca is not a substitute for OpenText as the product vendor. Licences, releases and Current Maintenance stay on the vendor path. Nuca's role is the live Extended ECM run: the OpenText side of connectors into SAP and other line of business systems, OTDS, and incidents that cross platform and database.
Your SAP and line of business teams keep their stacks. We work beside vendor support. For the dates that apply to your release, rely on OpenText's published lifecycle materials; this page does not restate them. xECM for SAP 21.4 and Current Maintenance and OpenText support for legacy versions are practical companion reads for planning.
Planning around OpenText Current Maintenance dates for your release
OpenText publishes a lifecycle for each release, and Current Maintenance is one period in it. Planning around that period for your Extended ECM or connector release is part of keeping a live estate honest. You still need monitoring, incident ownership and a clear upgrade or bridge path while the vendor lifecycle for that version changes.
For SAP-integrated estates, xECM for SAP 21.4 and Current Maintenance is a practical companion read. OpenText support for legacy versions covers the wider path for mixed-version estates.
Scope: run and recover, not greenfield xECM programmes
On this page, we mean running and recovering live Extended ECM and xECM estates. We do not sell greenfield xECM implementations, consulting programmes or custom build. We do not take large transformation programmes that belong with OpenText Professional Services or a systems integrator. If the estate is short of senior OpenText capacity after go live, that is the work we take: monitor, administer, recover, and keep the joins honest in production.
The managed service is a fixed monthly fee scoped to your estate. Coverage sits on-premise and private cloud only. Your implementation partner keeps the build relationship. For the wider service model and tier depths, see OpenText managed services.
How we support Extended ECM and xECM
| Tier | What it covers on a live Extended ECM / xECM estate | Response |
|---|---|---|
| Tier 1 Platform | OpenText side of the estate: platform, connectors, OTDS and database kept production-stable. Monitoring and alerting around the clock. | Critical-incident response in core hours. |
| Tier 2 Platform + Business | Everything in Tier 1, plus the business-administration layer. | Critical-incident response 24×7×365. Monitoring around the clock. |
| Tier 3 Full Lifecycle | Everything in Tier 2, plus full lifecycle: upgrades, migrations and a named Technical Account Manager. | Critical-incident response 24×7×365. Monitoring around the clock. |
Around-the-clock monitoring is included at every depth. Tier 1 Platform fits estates that already handle business administration internally. Interim Cover fits a temporary administrator gap: three-month minimum, then rolling monthly. Pricing for the managed service is a fixed monthly fee scoped to your estate. See OpenText managed services.
Spot a connector that has stopped telling you the truth, then book a free call
Signs that a connector has stopped telling you the truth are often quiet. Users work around missing documents. Two systems of record disagree on a key field. A job reports success while the business process stalls. By the time someone raises a ticket, the workaround has become normal and the join is no longer trusted.
Start with the 15 estate self-checks if you want a structured self-review. They are a free self-check resource, not a Nuca review, and you can run them without us. If you want a second view on a live Extended ECM estate, book a free 45-minute continuity check call. No system access and no log upload. We help you see whether the OpenText side of the connectors, OTDS and the database need a standing service, interim cover, or simply a clearer ownership model with the teams you already have.

If you want the findings in writing after the call, the Estate Continuity Review is the paid next step: two weeks on your live Extended ECM estate, five senior days, review only, fixed price agreed in advance and credited against the work that follows. Start with the free 45-minute continuity check call (no system access, no log upload) via book a free 45-minute continuity check call.
Further reading: xECM for SAP 21.4 and Current Maintenance, OpenText support for legacy versions, OpenText ECM database administration.
FAQ
If a second pair of eyes would help, book a free 45-minute continuity check call.
No system access and no log upload. For a self-review first, use the 15 estate self-checks. No other meeting ask.
