--- title: "Log4J Installation Instructions" slug: "log4j-installation-instructions" updated: 2026-10-06T14:03:23Z published: 2026-10-06T14:03:23Z canonical: "documentation.lakesidesoftware.com/log4j-installation-instructions" --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.lakesidesoftware.com/llms.txt > Use this file to discover all available pages before exploring further. # Log4J Installation Instructions ## Prerequisites - Minimum Version: Requires SysTrack 10.1 or later. ## Notes - After this DEX Pack is installed, it may take up to 24 hours for data to appear. - If you update or reinstall this DEX Pack, you must reassign any Views created below to the SF_Log4J Role and reapprove the log4j Action. ## Installation Steps To install this DEX Pack, complete the following steps: 1. [Import the Kit](/documentation/docs/log4j-installation-instructions#import-kit). 2. [Enable the log4j Action](/documentation/docs/log4j-installation-instructions#enable-collection-extensions). 3. [Create the Log4J View](/documentation/docs/log4j-installation-instructions#log4j-view). 4. [Assign the Log4J View to the Log4J Role](/documentation/docs/log4j-installation-instructions#assign-the-log4j-view-to-the-log4j-role). 5. [Assign the Log4J Role to Relevant Configurations](/documentation/docs/log4j-installation-instructions#import-log4j-role). ### Import the Kit There are two ways to import the DEX Pack to SysTrack: - Import the pack directly from the Kits page in SysTrack. See the [Import Online Kits](/documentation/docs/import-online-kits) guide for more information. - Import a local file downloaded from the [DEX and Kit Downloads](/documentation/docs/dex-packs-dex-and-kit-downloads) page. Click the **Download Kit** link for the pack and follow the [Import Local Kits](/documentation/docs/import-local-kits) guide to finish the import. ### Enable the log4j Action 1. Verify you have unlocked the tenant next to your username. 2. In **Configure**, click **Automations and Collection Extensions** on the left. 3. Select **Action Governance**, then click the **Pending Approval** tab. 4. Find the **log4j** Action and select the checkbox next to it. 5. Click **Approve**, then confirm. The action moves to the **Actions** tab and is enabled automatically. > [!NOTE] > **NOTE**: In SysTrack Cloud, the user who imported the Kit may not be allowed to approve its actions. If the checkbox is unavailable, ask another user with Action Governance – Management permission to approve the action. ### Create the Log4J View This DEX Pack requires you to make a View for the relevant SF_Log4j Role. To create the new View: 1. Navigate to **Configure** > **Views**. 2. Click the **padlock icon** in the upper-right to enable editing. 3. Click the **plus icon** to add a new View. 4. Fill in the **Settings** as follows or follow them as per the screenshot from the kit. 1. **View Name:** **SF_Log4j** 2. **Existing Category:** **General** 3. **Expires in:** **30 Days** 4. **When Expired:** **Overwrite Data** 5. Do NOT check **When overdue by 1 day (s)**. 6. Set the **Refresh** drop-down to **Daily**, **Inside**, **24x7**, and **Every Day**. 7. Copy the [SF_Log4j SQL Query](/documentation/docs/log4j-installation-instructions#sflog4j-sql-query3), and paste it into the box under **SQL Selection** > **Generic**. 8. Click **Test SQL**. A **Success** message should appear at the top of the screen. If the test is not successful, the query may have been copied incorrectly. 5. Click **Create View** at the top-right. #### SF_Log4j SQL Query ```sql SELECT T0.WGUID, GETUTCDATE() AS VWTIME, Add_Date AS RunTime, S0.STRVALUE AS FULLPATH FROM DYNI_log4j AS T0 INNER JOIN SASTR_DYN AS S0 ON T0.FullName = S0.STRINGID ``` ### Assign the Log4J View to the Log4J Role To assign the new View: 1. Navigate to **Configure** > **Roles**. 2. Use the drop-down at the top to select the **SF_Log4J** Role. 3. Click **Views**, then check the box next to **SF_Log4j**. 4. Click **Save Changes** at the top-right. ### Assign the Log4J Role to Relevant Configurations This solution requires you to assign the SF_Log4J Role to the relevant Configurations: 1. Navigate to **Configure** > **Configurations**. 2. Click the **padlock icon** in the upper-right to enable editing. 3. Use the drop-down at the top to select a relevant Configuration, or create a new Configuration. 4. Assign the **SF_Log4J** Role to the Configuration by dragging it from **Available Roles** to **Assigned Roles**. 5. Click **Save Changes** at the top-right. 6. Repeat this process for any other relevant Configurations.