Changing Tomcat Logs Directory

Tomcat has a set of 7 log files, not including the application logs that the applications it hosts, write. The default location to which Tomcat writes its logs is $CATALINA_HOME\logs, which is set during installation. There may be instances when you would need to change the location to which Tomcat writes its logs to. This may be applicable in different cases -

1. In small to medium scale installations, where the default directory has got full and you need to write to another location
2. In large scale installations, wherein you are maintaining a separate share (SAN/NAS) for logging and would want to change to a new partition as matter of a set policy

The change of directory is not as simple as it may seem for all log types. There is not much available on the net for this, so I dissected the issue in detail and have written a paper on the same. Please refer to the below link for details:
Changing Tomcat Logs Directory

Documentum Upgrade & Migration Using Selective Data Copy – A Whitepaper

Introduction

This whitepaper developed by me is a new concept to Upgrade or Migrate Documentum systems using only a subset of data from the source repository. The source would generally be the current production server and the target would be a new or an old system. I developed this concept while working on an Upgrade Project for DCTM from 6.5 SP1 to 6.7 SP1. The requirement was unique, in that the Non Production systems were to be carved out from the existing live Production environment, however only with a subset of the documents. The concept was developed due to the limitation of storage space on the new Non Production systems. Note that this was a cross platform upgrade/migration exercise which needed extra steps not covered in this whitepaper.

Target Audience

1. Documentum Administrators
2. Documentum Solution Architects and Designers
3. Documentum Developers

When to use

This methodology could be used in the following scenarios:

1. DCTM Upgrades when a new target system needs to be created from a source but storage space is a constraint on the target.
2. Migration Activities when a target system needs to be built with a source’s data subset.
3. Reverse synching Non Production systems with Production data subset on a regular operational basis.

For complete details please view my whitepaper available on the link below:

A Whitepaper on How to Upgrade/Migrate Documentum Systems Using Selective Data