We provide data dump required for install, but not for sample data.

BMC Helix Innovation Suite containers use Linux operating system. The container host systems must have Linux operating system as the kernel is shared between the host and container.

It is theoretically possible to run a Linux virtual machine on a Windows host and deploy Kubernetes across the virtual machine and run Linux containers. However, BMC does not recommend such deployment architecture and does not provide deployment sizing guidelines for such configurations.

BMC Helix Innovation Suite containers are based on Docker and they leverage Kubernetes orchestration layer.

Yes.

For more information, see Downloading the installation files.

That is correct ! we are bringing all Service Management applications on one converged platform.

For more information, see Downloading the installation files.

Yes, The same Deployment Engine setup ( Jenkins) can be used to deploy different environments of the same version, such as dev, QA, and production.

For more information, see Setting up the deployment input configuration file.

Yes, The same Deployment Engine setup ( Jenkins) may be used to deploy multiple instances of the same version.

For more information, see Setting up the deployment input configuration file.

Yes, The same Deployment Engine setup ( Jenkins) can be used to deploy patches and updates; hence may be retained or recreated when needed.

For more information, see Setting up the deployment input configuration file.

Yes, Multiple BMC Helix ITSM and Helix Platform namespaces can use same Helix Logging Namespace. Only one helix logging namespace is recommended per cluster.

For more information, see Setting up the installation environment.