Component Configuration › Log Files Configuration › Configuring Log File Cleanup

Configuring Log File Cleanup

By default the cleanup action for each component is configured to run on the logbase directory. If the log files are redirected to another directory, modify the cleanup configuration for successful Archive or Delete actions.

Define cleanup actions in the LocalConfig xml-element in the configuration files. For all CAMM components, define the cleanup actions in the respective configuration files:

• MultiController: LocalConfig-mc.xml
• LocalController: LocalConfig-lc.xml
• Delivery Service: LocalConfig-ds.xml
• Subcomponents (ENGINE/PRESENTER): TemplateConfig-subcomponent.xml

  Note: You can find the TemplateConfig-subcomponent.xml file in the <camm.base>/LC directory.

The following examples describe two sample cleanup configurations.

Example: Cleanup configuration file (Delete action) for the Delivery Service component

<LocalConfig>

<Description>Configuration for Delivery Module</Description>

	…

	…

	<CleanUps>

		<!-- SAMPLE  DELETE  ACTION -->

		<CleanUp>

			<CleanUpName>Delete</CleanUpName>

			<CleanUpAction>delete</CleanUpAction>

			<CleanUpTarget>${apphome}/.local</CleanUpTarget> <!-- Directory Name -->

			<Parameter>

				<ParameterName>expire</ParameterName>

				<ParameterValue>7d</ParameterValue> <!-- 1y0m3d1h -->

			</Parameter>

			<Parameter>

				<ParameterName>includeDir</ParameterName>

				<ParameterValue>true</ParameterValue><!-- true/false -->

			</Parameter>

			<Parameter>

				<ParameterName>recursive</ParameterName>

				<ParameterValue>true</ParameterValue><!-- true/false -->

			</Parameter>

			<Parameter>

				<ParameterName>match</ParameterName>

				<ParameterValue>^[\d]+\.xml$</ParameterValue> 

				<!-- Regular Pattern -->

			</Parameter>

		</CleanUp>

Example: Cleanup configuration file (Archive action) for the Delivery Service component

		<!-- SAMPLE  ARCHIVE  ACTION -->

		<CleanUp>

			<CleanUpName>Archive</CleanUpName>

			<CleanUpAction>archive</CleanUpAction>

			<CleanUpTarget>${logbase}</CleanUpTarget> <!-- Directory Name -->

			<Parameter>

				<ParameterName>expire</ParameterName>

				<ParameterValue>7d</ParameterValue> <!-- 1y0m3d1h -->

			</Parameter>

			<Parameter>

				<ParameterName>includeDir</ParameterName>

				<ParameterValue>true</ParameterValue><!-- true/false -->

			</Parameter>

			<Parameter>

				<ParameterName>recursive</ParameterName>

				<ParameterValue>true</ParameterValue><!-- true/false -->

			</Parameter>

			<Parameter>

				<ParameterName>match</ParameterName>

				<ParameterValue>CAMM-.*\.log</ParameterValue> 

				<!-- Regular Pattern -->

			</Parameter>

			<Parameter>

				<ParameterName>achiveHome</ParameterName>

				<ParameterValue>${logbase}</ParameterValue> <!-- folder path -->

			</Parameter>

			<Parameter>

				<ParameterName>achivePrefix</ParameterName>

				<ParameterValue>Archive-</ParameterValue> <!-- prefix string -->

			</Parameter>

			<Parameter>

				<ParameterName>achiveSuffix</ParameterName>

				<ParameterValue>.zip</ParameterValue> <!-- suffix string -->

			</Parameter>

		</CleanUp>

	</CleanUps>

<LocalConfig>

You can include any of the cleanup actions in the component configuration file. The Generic Executor performs all the cleanup actions. The Generic Executor stores cleanup files in the {camm.base }/GE_<User>/cleanup directory, where camm.base is the CA Mediation Manager installation directory. Once the component configuration file is modified, restart the related component so that the modified configurations can take effect.