Neptune DXP deployments

The REST and OData API connectivity mechanisms described here can be packaged and deployed across your technical landscape without any re-implementation required in the target Neptune DXP environment. Using Neptune DXP’s Deployment function, your various development, test, staging or production instance can be integrated in a deployment and allow for the progressive propagation of your APIs through to production. Let’s consider a simplified landscape operating three environments:

APIs developed or imported into the API Designer are organised into packages along with any associated artefacts, for example, database tables or scripts, to enable their transfer between environments. Packages, subject to an optional approval mechanism, can be propagated across the landscape, following pre-defined routes between the various environments. In this case, a development Neptune DXP application or microservice environment may define a route to a test environment. In turn in the test environment may target the production environment as the next step to complete the propagation path from development to production. More elaborate integrated landscapes can be organised, including an environment for staging, quality testing, or sandbox instances to test your APIs in an isolated fashion.