For each new customer deployment, Akamai Professional Services provisions two distinct environments:
Depending on the package you have purchased, a Staging environment may also be provisioned. All environments point to the Akamai platform’s production code, but non-production environments are hosted on separate application servers that are not scaled for production use.
Each Akamai environment consists of the following:
- Social Login application(s)
- Registration application
- User data storage
- API clients and settings
- Flow configurations
More information about these components can be found in the Registration Overview. Each environment may be configured for use with multiple properties and integration points.
After the project kickoff, Akamai will provide technical training to the customer’s team on how to use the Console and APIs for configuration and how the reference implementation is set up. Once Akamai has provided access to the Development environment and reference implementation, the customer is responsible for the following implementation tasks. All application configuration steps may be completed in the Console or by using Akamai APIs.
Once the customer has completed configuration on the Development environment and signed off on Configuration Acceptance Testing, Akamai will then provision the Production environment and promote the approved flow(s) and schema(s) from Development to Production. The customer will need to complete some configuration steps outlined above for the Production environment, as well as update production code that is either pointing to the Registration UI or making direct API calls on the back end (server-side) to use Akamai Production environment credentials. See the Production Launch Process section for more details.