Extract the Oozie configuration files to a temporary directory. The files are located in the configuration_files/oozie directory where you decompressed the companion files.

Add the following property to the oozie-log4j.properties file:

log4j.appender.oozie.layout.ConversionPattern=%d{ISO8601} %5p %c{1}:%L - SERVER[${oozie.instance.id}] %m%n where ${oozie.instance.id} is automatically determined by Oozie.

Oozie runs a periodic purge on the shared library directory. The purge can delete libraries that are needed by jobs that started before the installation. To minimize the chance of job failures, you should extend the oozie.service.ShareLibService.purge.interval and oozie.service.ShareLibService.temp.sharelib.retention.days settings.

Add the following content to the the oozie-site.xml file:

<property>
<name>oozie.service.ShareLibService.purge.interval</name>
<value>1000</value>
<description>
How often, in days, Oozie should check for old ShareLibs and LauncherLibs to purge from HDFS.
</description>
</property>

<property>
<name>oozie.service.ShareLibService.temp.sharelib.retention.days</name>
<value>1000</value>
<description>
ShareLib retention time in days.
</description>
</property>

Modify the configuration files, based on your environment and database type as described in the following sections.