Service environment details
This section describes the following topics:
The types of environments provided will vary by Helix subscription service. Please refer to the information detailed in the BMC Helix Core services table for which environments are provided by a particular service.
- Development / Tailoring
- Quality Assurance (QA)
Separate customer environments are provisioned for your BMC Helix services. Application updates flow from the development/tailoring environment through QA before going live in production. These environments contain the most recent generally available (GA) version of the products and out-of-the-box content (including services, templates, requests, catalogs, and so on), pre-installed from a golden image. Following the solution build and test, the environment is moved to QA so that the customer can perform the required user acceptance testing prior to going live. For services where a QA environment is not provided, user acceptance testing is performed in the development environment.
|Development / Tailoring||Creation of customer-specific integrations, workflow, and data configurations|
|Quality Assurance (QA)||Release, testing, and validation of your custom application components prior to live operation|
|Production||Operation of your BMC Helix processes which are available to end users|
Additional environments for training, secondary testing, and other activities are available for an additional monthly fee. See BMC Helix additional environment option for more information.
Environments are available to customers at all times and do not require a request to be created for provisioning. Customer data is not co-mingled with other customer data or between environments.
Services are hosted and delivered from secure data center facilities. For BMC Cloud locations, BMC provides highly available network connectivity across two physically disparate data centers within a metropolitan area, allowing for an active-active configuration for the production environment at the web and application layers. Backup data is stored at a separate third location or zone, but always within the same country. AWS and Azure facilities use availability zones; these zones are distinct locations within a region that are engineered to be isolated from failures in other availability zones.
Customer environments are controlled, monitored, and managed by BMC SaaS Operations (BMC Cloud locations also include the underpinning application and infrastructure aspects of the service). Areas of focus include hosting, storage, network, application software, and the connectivity between the cloud and the customers' premises. Additionally, the service includes the management of standard operational activities such as data and system backup, and recovery.
Full application access is provided to customers for their development environment only. Access to the QA and production environments is restricted.
Non-production environments, including development, QA and any additional environments purchased, are not scaled to the same specification as the production system and therefore are not capable of processing production-level workloads. Non-production systems are not configured for high availability but are scaled to sufficiently handle the following workloads:
- Development: up to 50
- QA: up to 50
Environment naming conventions
BMC employs standard naming conventions for its customer environments depending on how the environment is to be used. Environment naming conventions are listed under the Activation activities page for each service.
Hi, for Helix Operations Management (Monitor) Do we have three environments too?
Yes, see https://docs.bmc.com/docs/display/public/helixsubscriber/BMC+Helix+Operations+Management+activation.
Gerardo Sumano When you follow the link provided by Martha you will find that for BMC Helix Operations Management we are only providing two environments.
One Production instance and One Dev instance.
Log in or register to comment.