Configuring your MiNiFi Java agent

After you install the MiNiFi Java agent, you need to update the configuration files.

If you are configuring a MiNiFi Java agent, the configuration file is conf/bootstrap.conf.

From the MiNiFi home directory, open the configuration file.
Configure the agent class so that you can logically group MiNiFi Java instances according to their functionality.
```
c2.agent.class={AGENT_CLASS}
```
note
Leading and trailing whitespaces are accepted for Agent Class names so consider this when configuring agents.
Configure the agent ID. If you do not specify an agent ID, MiNiFi generates a unique ID per agent instance.
```
c2.agent.identifier={AGENT_ID}
```
Set the c2.enable property to true to inform MiNiFi that run time flow instructions will be received from EFM.
```
c2.enable=true
```

Configure your EFM server endpoint:

c2.rest.url=http://{EFM_SERVER_IP}:10090/efm/api/c2-protocol/heartbeat
c2.rest.url.ack=http://{EFM_SERVER_IP}:10090/efm/api/c2-protocol/acknowledge

Configure your heartbeat interval:

c2.agent.heartbeat.period={HEARTBEAT_INTERVAL}

Configure the config directory to be used by MiNiFi:
```
c2.config.directory=./conf
```

Configure C2 runtime properties:

c2.runtime.manifest.identifier=minifi
c2.runtime.type=minifi-java

Configure MiNiFi to recognise the changes in the config.yml file during publishing:

nifi.minifi.notifier.ingestors=org.apache.nifi.minifi.bootstrap.configuration.ingestors.FileChangeIngestor
nifi.minifi.notifier.ingestors.file.config.path=./conf/config-new.yml
nifi.minifi.notifier.ingestors.file.polling.period.seconds=5