When you update IXIA CCMS Desktop, you must update the packages in the Test environment and test them before deploying them to the Production environment.
Because CCMS Desktop packages are self-contained, multiple instances can be
used concurrently. Therefore, you can make and test a wide range of changes (binaries,
config, deployment, and so on) without affecting the Production instances of CCMS Desktop.
-
Download the package or plugins that changed.
-
Update and test in the Test environment:
-
Locate the staging area that you created for the
initial deployment.
-
In the staging area, update the CCMS Desktop packages for the Test
environment.
For example, you might replace the plugins with newer
versions.
-
Record the changes so that you can repeat them later
for the Production environment packages.
-
Deploy the packages for the Test environment.
-
Ask the users who have Test environment packages to
perform tests in the Test environment.
The level and type of testing depends on the type of
changes that were made. The testing could be for specific changes you
made to CCMS Desktop,
regression testing, functional testing, bug fixes, and so on.
-
Iterate if necessary.
-
Update and deploy the packages for the Production environment.
-
In your staging area, update the CCMS Desktop packages for the
Production environment by repeating the steps you made with the Test
environment packages.
-
Deploy the packages for the Production
environment.
