search cancel

Cleaning up the SDM Install directory

book

Article ID: 134628

calendar_today

Updated On:

Products

CA Service Desk Manager

Issue/Introduction

What are the locations within the CA Service Desk install directory in which content may be safely removed?

Environment

Release:  CA Service Desk Manager (all versions)

Resolution

When looking through SDM installs, one often finds these to be large sources of unnecessary content that can be deleted safely:


* Diagnostic output.  Under NX_ROOT\diag\rpt directory, one may find multiple CAZ files from previous executions.  These can be deleted, as they were usually requested by Support to examine the given install at the time of generation and serve no further purpose, especially if the associated ticket that the given diagnostic output was executed for has long been resolved.


* Log materials.  There are often logs at these locations which can be archived safely:


- NX_ROOT\bopcfg\www\CATALINA_BASE\logs

This has the 'localhost_access_log' files that are written with Tomcat accesses.  


- NX_ROOT\log\mail_nxd

Mail notification logging is held here.


- NX_ROOT\log\maileater_nxd

Maileater logging, which can be removed as needed.


- NX_ROOT\log

The main SDM log folder.  One may find visualizer_log.log, older stdlog files that had been remamed (there should be just 10 stdlog files at any given time here).  Boplogging or pdm_trace log outputs, and the interval logging, which may not even be active and can all be archived.


* Old and outdated customisations.

The NX_ROOT\site\mods folder is where the SDM customisations are kept.  One can often find backups or copies of custom directories of various naming conventions here, which can all be removed safely.  Best practice when asked to backup a set of customisations is to copy the given custom file/folder AWAY from the above location to another drive or location from the SDM install directory.