Upgrade the base package

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

The packages folder, %packagesfolder%, represents the folder of the instance of Eclipse that you must update as part of your distribution strategy.

Table 1. Possible distribution strategies

Method

Description

Using a network share and batch file

Place all the packages on a network share such as \\servername\sharename and make sure 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 personal computer (PC). If you use a remote access solution, follow this process on the servers.

Using an automated tool to push the application

Use a product such as Microsoft SCCM to deploy applications automatically to users.

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' PCs.

Manual deployment

Create a zip file for each package.

For the installation and each update of CCMS Desktop, create a new zip file and have your users download and unzip the file on their PCs. If you are using a remote access solution, follow this process on the servers.
  1. Go to the 7.3 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 use a secure connection (SSL) to connect to IXIA TEXTML Server, make sure that you have a backup copy of %packagesfolder%\jre\lib\security\cacerts, since the upgrade overwrites it.
  5. If you customized version of eclipse.ini, make sure you have a backup copy of %packagesfolder%\eclipse.ini, since the upgrade overwrites it.
  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
      Note: NEVER execute this file! Use start-ccms.bat instead.
    • 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 to copy and overwrite %packagesfolder%\jre\lib\security\cacerts with the new version.
  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: You can define default values for a new workspace.
  11. Re-integrate your customized values into the new version of set-instance-client.bat, which changed in version 7.3, by taking the following actions:
    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, such as ActionStart or ActionUpdate, to the appropriate section.