A comprehensive guide to the administrative features and functions for the IXIA CCMS.
The maintenance tasks required to keep the components running smoothly may fall under the responsibility of one or more individuals in your enterprise.
In an on-premise deployment, maintenance involves user connection, configuration changes, coordinating system upgrades and backups, and possibly developing outputs.
When you experience a data loss or significant error that forces you into data recovery, use your latest backup and perform a restore.
Follow these procedure in cases where you need to uninstall a component.
This section contains general information about the IXIA CCMS configuration.
Although you can perform some basic administration functions in IXIA CCMS Web using the Administration page, you must configure some CCMS Web features elsewhere.
The Content Repository contains your DITA content, images, resources, snapshots, taxonomies, DTDs, and system configuration.
You can customize Darwin Information Typing Architecture (DITA) functionality within IXIA CCMS.
This section contains information and instructions for the configuration of roles, groups, users, and access rights.
This section describes how to configure or customize IXIA CCMS to use the IXIA Dynamic Release Management module functionality.
Localization requires configuration.
You can enable secure connections to the IXIA TEXTML Server.
In a dedicated SaaS deployment, maintenance involves configuration changes, coordinating upgrades, and possibly developing outputs.
In an IXIA CCMS on-premise deployment that implements Single Sign-On (SSO), users who sign in to the company's identity provider also automatically sign in to CCMS Web. SSO does not impact connections to CCMS Desktop.
When you upgrade or make changes to IXIA CCMS, ensure you test them on a non-production environment.
How you test a modification depends on the component and type of modification you made.
Generating and managing backups of your data is a fundamental task for those responsible for maintaining servers and component content management systems.
If you can stop IXIA TEXTML Server, you can replace the Content Store files with copies from your backup without needing to uninstall the existing Content Store.
The procedure for installing a Content Store from a backup depends on how you want it installed and the total number hosted on IXIA TEXTML Server.
The procedure for restoring IXIA CCMS Output Generator depends on if you need to reinstall the entire component or just replace files in an existing service.
Restoration of IXIA CCMS Scheduler depends on whether you need to reinstall the entire component or to replace files in an existing service.
You can restore IXIA CCMS Web by reinstallation.
For Windows platforms, use the Control Panel to uninstall the IXIA TEXTML Server service.
The second task when you update a build is to delete an instance of IXIA TEXTML Server running on Linux if it is no longer required.
You can uninstall IXIA CCMS Web using the command prompt.
You can uninstall IXIA CCMS Output Generator.
You can uninstall IXIA CCMS Scheduler.
You can uninstall a local instance of IXIA CCMS Desktop from a user's machine by deleting all the files for it.
When you upgrade or make changes to IXIA CCMS, test them in a non-production environment.
Importing large, non-DITA files, such as videos, can impact memory requirements and performance of the IXIA CCMS. Manage large file imports and regularly confirm they are not slowing system performance.
Follow the specific troubleshooting procedure for a given task.
IXIA CCMS Customer Support staff are available to answer your questions. We welcome your comments.
