Deploying the engine

The connectivity engine is the piece that talks to S/4. It runs in your landscape, not ours — which is the whole point, and also why this is the one part of onboarding that involves your platform team.

Do you need it#

Only if something you bought reads live S/4 data. That is 3 of our products, plus any screen you bind to S/4. Everything that works against FSA alone needs none of this.

If you are not sure, check your entitlements — the table there marks which ones require it.

What it is#

A single long-running service you deploy into your own SAP BTP Cloud Foundry space. It holds your S/4 connection, translates between the extension and your S/4 services, and answers the browser.

• One deployment serves every product and every screen in your tenant. There is not one per product.
• Your credentials stay yours. They are configured on your own application, in your own subaccount.
• It is stateful and long-running, so it belongs on Cloud Foundry rather than on a serverless platform.

What it does once it is up is described on the engine page, and the request paths are drawn on how it works.

What you will need#

• An SAP BTP subaccount with Cloud Foundry enabled, and a space you can push an application to.
• The Cloud Foundry CLI, and permission to use it against that space.
• An S/4 system exposing the OData services you want, reachable from that space — see connecting to S/4.
• Your engine licence, which we issue separately from the extension licence. It is what allows the engine to start.

The shape of a deployment#

1. Take the bundle. We provide a self-contained artifact — no dependency tree to install, no build step on your side.
2. Push it to your Cloud Foundry space with the CLI. It comes up healthy immediately, but not yet functional: the health and readiness endpoints answer so the platform is satisfied, while everything else refuses until it is configured and licensed.
3. Configure it— your S/4 connection details and your engine licence, set as application configuration through your platform's own mechanism. Nothing sensitive goes into a file we send you.
4. Restart it and check the readiness endpoint. It should report the licence as active. If it does not, it says why.
5. Point the extension at it — one URL, which we set for your tenant.

What we send you#

• The bundle, and a manifest describing how to run it.
• Your engine licence.
• A step-by-step runbook with the exact commands and settings.
• A person to ask, for the first one.

Keeping it current#

The engine is yours, so updating it is a push you make when you want it — not something we do to you. We tell you when a version matters and why. Health and versions covers how to tell what you are running.

Its licence renews itself on a short lease in the background. If it cannot reach us it keeps serving until the current lease runs out, so a network problem is not an outage — the full behaviour is on the security page.