Separate logging for schema operations

You can configure Pega Platform to save a log of schema operations to a file other than the PegaRules log file. Operations performed using the Schema Tools landing page, including Pega Cloud schema operations (this makes it sound like on-premises environments can use schema tools, which you said they can't. Also, try to stay away from "Schema Tools Landing page" and try to write it more about why and how they would want to do it.), can be logged to a separate file from the PegaRules log file. To enable logging to a separate file, add the following appender to the prlog4j2.xml file (Move this last sentence to a new paragraph and keep the short description short. Also, I feel like we should tell them how to add the appender. Do they navigate to the file and open it? How do we tell them to modify files like this in other places?) .

<RollingRandomAccessFile name="RollingRandomAccessFileDBOPERATIONS" fileName="${sys:pega.tmpdir}/PegaDBOPERATIONS.log" filePattern="${sys:pega.tmpdir}/PegaDBOPERATIONS-%d{MM-dd-yyyy}-%i.log.gz">
	<PatternLayout>
		<Pattern>%d [%20.20t] [%10.10X{pegathread}] [%20.20X{app}] (%30.30c{3}) %-5p %X{stack} %X{userid} - %m%n</Pattern>       
	</PatternLayout>
	<Policies>
		<TimeBasedTriggeringPolicy />
		<SizeBasedTriggeringPolicy size="250 MB"/>
	</Policies>
	<DefaultRolloverStrategy max="20"/>
</RollingRandomAccessFile>

<Logger name="SchemaDesignerLogger" level="info" additivity="false">
	<AppenderRef ref="RollingRandomAccessFileDBOPERATIONS"/>         
</Logger>