HCL Connections 7 Component Pack with a linux virtual box on windows

HCL Connections Connections Forum
,
1

Hi everyone,

has somebody experience about a linux virtual box on windows?

Background: we have only windows machines and we wont to install the component pack for connections 7.

Thx.

Thomas

2

Hi Thomas,

have installed Connections v7 in a virtual box image running on Windows that I use as a test-system at the moment. But I have not installed any component pack right now. That test-system runs fine so far. Because Virtualbox is not the best Virtual environment I would not suggest to use such images in a production environment.

I hope that helps,

thanks, Thorsten

3

Hi Thomas,

I'd build several Connections environment on Linux inside Virtual Box on Windows 10. So far, they all ran fine.

Community-Pasted-Attachment-1642737663676.png635×424 24.8 KB

However, like what Thorsten said, base on the performance of Virtual Box, it is not suggested to run Connections as a Production on it.

Simply test environment would be fine to run on Virtual Box.

And if you plan to deploy Connections Component Pack on Virtual Box as well, that may require more resource of your desktop PC.

My Laptop: 8 core, 32G memory.

I tried to deploy CP inside Connections 7, and the VM image stuck at starting page.

Then, I tried to install CP on another image, and ran both Connections 7 and CP image at the same time, the these two image cause my laptop had no response.

So, from my experience, either you have a clean windows(with no other software running on it, and 32GB memory may be enough to run both ConnX 7 and CP. But the performance would be ugly)

Or you have a more powerful PC to run it would be much better.

Hope my post can help you a little bit.

Thanks

Rock

4

Hi,

so you're only using bare metal Windows servers without any virtualization? Otherwise I don't understand the problem because if you already do virtualization (which seems to be a standard for several years), you can just install linux servers directly by creating VMs in your hypervisor. Propably Hyper-V for you if you're MS focused, but it doesn't matter if you're using Proxmox, VMWare or any alternative.

If you're talking about already virtualized Windows servers, things are getting more complicated. Installing VMs on VMs is called nested virtualization. This is something which is not fully supported everywhere. Even if it's supported for your stack, it will increase complexity and cost performance since you're having two layer of virtualization before the container technology, which is the base for the k8s, which itself is the base for the CP. Nested virtualization in general is nothing i'd recommend for productive setups. Even for test environments it can be a pain.

5

Running Component Pack on "a" box is a huge challenge, because of the rather insane resource requirements. I guess in 10 years or so we laugh about 64 GB and 16 vCPU's, but currently very few machines have such specs and these are your minimal requirements to run the entire Connections stack including component pack on one machine.