Our customer is one of the largest software provider with more than 75,000 employees worldwide, among them several thousand sales and pre-sales employees. Together with partners they are demoing the company´s products and solutions on a day to day basis. The customer was looking for a solution which would enable the automatic provisioning and easy access to multi-tiered and complex demo landscapes in a cloud environment. The solution should meet the following challenges:
- Responsibilities for infrastructure components were distributed across multiple individual departments using a variety of management tools
- Creation and provisioning of new, individual demo landscapes took several weeks. An on-demand creation and provisioning was not possible
- Pre-defined and constantly updated demo landscapes were shared by multiple sales employees, which meant that customer demos often interfered with each other
- Missing overview of available demo landscapes and creation of a “shadow IT”, e.g. deployment on internal systems or hosting on public clouds
- Performance problems due to missing scalability of the infrastructure resources at times of high demand
- High error rate and poor demo experience due to missing automation and standardization
Basing on a scalable cloud architecture and cloud portal, the customer is now able to monitor all master landscapes with over 1,000 systems in total, and to deliver ready-to-run application landscapes with just a click of a mouse to its sales and partner staff. Through the integration of all available resources hosted either internally or externally, the customer has complete transparency over existing, globally distributed systems and is able to ensure that KPIs (e.g. system performance, response time of systems) are met. Through scheduled start and stop operations, load peaks can be better distributed and the utilization of CPU and RAM is measurable.
- Reduction of deployment time from 2 months to 2 hours
- Provisioning of 400 systems for 30,000 users per month
- Provisioning of demo systems with up to 25 individual systems in a landscape
- Compliance with safety standards through automated lifecycle management (upgrade, patch, backup, restore)
- Reduction of manual organizational efforts of up to 95 percent through automatic distribution of templates in global development, test and productive landscapes including version management
- Discovery and clean-up of no longer required systems and landscapes in on- and off-premise environments provide saving potentials of up to 40 percent
The customer uses eCloudManager to manage and monitor infrastructure components in the private and public cloud. Leveraging Infrastructure as a Service workflows, the customer provides multi-tiered and ready-to-use demo systems. The integrated Landscape as a Service concept isolates systems as a logical grouping and makes them available via a Self-Service portal. The underlying lifecycle management controls the individual steps during a system lifecycle and ensures smooth IT operations using current security standards.
The app delivers four main components to address the challenges:
- Backend: central controller of the entire cloud environment, including internal resources which are available worldwide or distributed across public cloud resources. In addition, the backend enables the creation of system and landscape templates in a service catalog.
- Admin UI: monitoring and management of all infrastructure and application resources, event and error tracking and resolution. Administrators automate the creation of test and QA environments, control the distribution of new templates and define SLAs and service prices.
- Self-Service cloud portal: fully customizable portal for on-demand usage of systems and landscapes by sales employees and partners. The service is available and users have immediate access. A consumption report about the provided service is available via the Self-Service portal.
- Public cloud integration: provisioning of landscapes either in the public cloud or hosted by service providers. Users have complete transparency over SLAs and decide in which cloud environment the landscape should be deployed.