[Deprecated] JBoss Enterprise Application Platform

>**NOTE:** This data connector depends on a parser based on a Kusto Function to work as expected [**JBossEvent**](https://aka.ms/sentinel-jbosseap-parser) which is deployed with the Microsoft Sentinel Solution.

>**NOTE:** This data connector has been developed using JBoss Enterprise Application Platform 7.4.0.

1. Install and onboard the agent for Linux or Windows

Install the agent on the JBoss server where the logs are generated. > Logs from JBoss Server deployed on Linux or Windows servers are collected by **Linux** or **Windows** agents.

Choose where to install the Linux agent:

Install agent on Azure Linux Virtual Machine

Select the machine to install the agent on and then click **Connect**.

Install agent on a non-Azure Linux Machine

Download the agent on the relevant machine and follow the instructions.

Choose where to install the Windows agent:

Install agent on Azure Windows Virtual Machine

Select the machine to install the agent on and then click **Connect**.

Install agent on a non-Azure Windows Machine

Download the agent on the relevant machine and follow the instructions.

2. Configure the logs to be collected

Configure the custom log directory to be collected

1. Select the link above to open your workspace advanced settings 2. Click **+Add custom** 3. Click **Browse** to upload a sample of a JBoss log file (e.g. server.log). Then, click **Next >** 4. Select **Timestamp** as the record delimiter and select Timestamp format **YYYY-MM-DD HH:MM:SS** from the dropdown list then click **Next >** 5. Select **Windows** or **Linux** and enter the path to JBoss logs based on your configuration. Example: - **Linux** Directory: >Standalone server: EAP_HOME/standalone/log/server.log >Managed domain: EAP_HOME/domain/servers/SERVER_NAME/log/server.log 6. After entering the path, click the '+' symbol to apply, then click **Next >** 7. Add **JBossLogs** as the custom log Name and click **Done**

3. Check logs in Microsoft Sentinel

Open Log Analytics to check if the logs are received using the JBossLogs_CL Custom log table. >**NOTE:** It may take up to 30 minutes before new logs will appear in JBossLogs_CL table.