Factors that influence the number of packages
You need a separate package for each category of users based on a variety of factors.
| Factor | Detail |
|---|---|
| Local install or access via Remote Desktop/Citrix | You might need a separate package for these target
machines:
In some cases, you can share a package across workstations and remote access servers by using settings in the customization batch file. For details, see Edit the customization batch file. |
| CCMS admin role | You need a separate package for those who have CCMS administrator roles vs those who do not. The package for users who administer the CCMS solution contains two extra plugins that end users should not have. |
| Support for different XML editor capabilities | CCMS Desktop supports two editions of Oxygen XML editing software: Author and Editor. If you want to support both editions, you need a separate package for each. |
| Testing new versions or configurations | You need a separate package for users who will help test new versions of IXIA CCMS or changes to its configuration. This separate package enables the users to work on the Test version of CCMS Desktop while continuing to work on the current production system. |
| Extra components or tools | If you have users, such as graphic designers, who require other Eclipse plugins, you need a separate package for those users. These plugins are not supplied by MadCap Software but can be installed in the same packages to simplify the deployment. |
| Platform | If you have users on multiple operating systems, you need a separate package for each. |