Setting Up A Client Enterprise Stage Environment (CESES)
Quick FAQ on building a stage environment for your next big project. This article applies to Enterprise clients only.
What is it?
The CESES is a complete or partial copy of your Enterprise implementation.
Why is its function?
Its primary function is to allow you, and us, to test modifications to symmetric and asymmetric web services between our two systems. For example, any modification to SSO, UDSM, or TMS APIs requires thorough testing prior to introduction to the production Env. A modification release without proper testing may result in corrupt data and potential security issues.
Its secondary function is to test client-specific features and enhancements. For example, a cross-implementation branding re-skin which requires content migration is a type of project which requires a CESES even though it is not technically an integrated feature.
Are there different scopes of CESES?
Yes. There are 3.
- Master Node CESES - A replicated Master Node only. Rarely used, but cost effective if the testing is only on features which affect the Master Node. An example would be upgrades to the Enterprise Directory feature (which only resides on the Master Node).
- 4-Node CESES - A replicated environment for your Master Node and 3 Nodes of your choice. It is sufficient in testing all Enterprise API functionality involving data and content traversal. This is our most popular CESES.<
- All-Node CESES - A replicated environment for your entire implementation. Rarely used. A good usage would be for a branding change. Another example would be stress-testing of traversal APIs.
How do I pick which one is right for my project?
The 3 choices vary in cost and complexity. 1 being the simplest and least expensive. 3 being the most complex and expensive. Depending on the testing objectives of your project, your Magnet Account Lead would be able to recommend the least costly solution which will cover all the testing permutations required for release.
What are the costs?
The cost may vary from one implementation to another. However, the general guideline is as follows: 20,30,40 production hours for 1,2,3 respectively.
How long is the CESES supported?
A CESES is active for 90 days after completion of the project it was built to test. For example, say Client X would like to alter SSO. The project is scheduled to begin on Jan 1st and take 60 days to complete. This would mean that the CESES for this project will be set up by Dec. 31st and taken down around May 31st.
What if the project is delayed and an extension is needed?
A 30 day courtesy extension is given upon request from client. After that, the CESES Nodes are added to the Client’s Node Count (for license assessment purposes).
What if I have more than one project - do I need 2 separate CESES?
No. We encourage you to plan ahead and leverage your CESES. We recommend working on one project at a time. The only point that is important to us is to be noticed about all projects, their timeline, and their scope prior to the request of the CESES.
For additional information about setting up a CESES for your next project, please inquire with your Magnet’s Account Lead.
|
|
 |
