Upgrading the base packages

IXIA CCMS Desktop is built of the base Eclipse package and a set of drop-ins developed by MadCap Software. To upgrade CCMS Desktop, you begin be upgrading the base Eclipse packages.

The packages folder (%packagesfolder%) represents the folder of the instance of Eclipse that needs to be updated as part of your distribution strategy. The following tables summarizes some possible distribution strategies:

Table 1.
Method Description
Using a network share and batch file

Place all the packages on a network share such as \\servername\sharename and ensure users have read permission to the share.

For the installation and each update of IXIA CCMS Desktop, update the folder and then have users click on a batch file that installs the software on their machines. If using a remote access solution, the system administrator follows this process on the servers.
Using an automated tool to push the application

A product such as Microsoft SCCM can be used to deploy applications automatically to users' machines.

For the installation and each update of CCMS Desktop, the person responsible for the deployment software captures the changes and pushes the application to users' machine.
Manual deployment

A zip file can be created for each package.

For the installation and each update of CCMS Desktop, you create a new zip file and users download and unzip the file to their machines. If you are using a remote access solution, an administrator follows this process on the servers.
  1. Go to the 7.2 area of the MadCap Software Downloads site:
    https://cms.ixiasoft.com/downloads/CCMS_7.2/
  2. Click the CCMS_Desktop folder.
  3. Download the latest version of the Eclipse package.
    The zip file is named eclipse-4.7.3_win32_x86_64_7.1.x.zip, where x is the latest build.
  4. If you are using a secure connection (SSL) to connect to IXIA TEXTML Server, ensure that you make a backup copy of %packagesfolder%\jre\lib\security\cacerts as it will be over written during the upgrade process.
  5. If you have customized version of eclipse.ini, ensure you make a backup copy of %packagesfolder%\eclipse.ini as it will also be over written during the upgrade process.
  6. In the folder %packagesfolder% delete the following folders and files
    Folders:
    • Configuration
    • Features
    • Ixiasoft
    • Jre
    • P2
    • Plugins
    • Readme

    Files:

    • .eclipseproduct
    • artifacts.xml
    • citrix.txt.orig
    • eclipse.exe
    • eclipse.exe NEVER execute this - instead use start-ccms.bat
    • eclipse.ini
    • eclipsec.exe
    • krb5.ini.empty
    • login.conf
    • preferences.properties.orig
    • set-instance-client.bat.orig
  7. Extract the Eclipse package zip file into %packagesfolder%.
  8. If you are using a secure connection (SSL) to connect to TEXTML Server, use the previous backup copy (from step 2) and overwrite %packagesfolder%\jre\lib\security\cacerts with it.
  9. If you have a customized instance of eclipse.ini, compare your backup copy and the current one in the folder %packagesfolder% and merge your customization.
  10. If you use preferences.properties compare the %packagesfolder% \preferences.properties.orig with %packagesfolder% \preferences.properties and merge the changes.
    Note: Default values can be defined for a new workspace.
  11. Re-integrate your customized values into the new version of set-instance-client.bat, which changed in version 7.2, by doing the following:
    1. Rename your existing set-instance-client.bat to set-instance-client-old.bat.
    2. Copy the new set-instance-client.bat.orig to set-instance-client.bat.
    3. Compare set-instance-client.bat and set-instance-client-old.bat.
      1. Merge your customization for the environment variable
      2. Move the code of each action (ActionStart, ActionUpdate, etc.) to the appropriate section