Integrity ALM Installation - Existing Environment

[mattia]

Hello,

Currently our MKS installation activates only Requirements and Tasks as work items.

Our MKS server manages the repositories, Build for miscellaneous big projects and a ~big number of users (arround 2000).

My Question:

It is possible to install the ALM of MKS without disturbing the current environment?

What is the risk: to perturb the current users/projects/workflow?

This Question is very important for me:

What about the estimated Time to install and use the first ALM with default ALM template?

Thanks in advance

Miled Attia

[jgorsline]

No, you cannot install the ALM solution onto an existing environment without disturbing it. The ALM installation makes a great number of big changes and cannot be uninstalled.

As per your other post, I would recommend a test environment to work with ALM.

As for time, I have set up test servers and installed ALM on top of them from scratch (VM->OS->Integrity->ALM) in less than an hour start to finish, so it is not a difficult process.

[DanR. · Accepted solution]

I will second that. We currently have 2 Integrity Servers. One for production and one for test. The ALM does make a good deal of changes. As Jeremy stated, I would recommend you install it on a seperate Integrity server. We are not presently using it, but it provides good examples of how it could be used.

[KaelLizak]

I would also add that you should make sure the ALM solution is actually the one you intend to work with, since most current generation solutions cannot co-exist together.

We recommend that you contact PTC Integrity Support or PTC Integrity Services to discuss your solution requirements before installing any given solution.