You will first need to extract the configuration file and then modify it per your install/needs. The default will work for most as long as the Kafka instance is on the same machine/host. Normally you will want to at a minimum change the default kafka bootstrap server.
unzip obmp-psql-consumer-0.1.0-SNAPSHOT.jar obmp-psql.yml
You should have obmp-psql.yml
now in the current working directory.
vi (or sed) obmp-psql.yml
. The configuration file has inline documentation.
The configuration file is specified using the -cf option.
nohup java -Xmx2g -Xms128m -XX:+UseG1GC -XX:+UnlockExperimentalVMOptions \
-XX:InitiatingHeapOccupancyPercent=30 -XX:G1MixedGCLiveThresholdPercent=30 \
-XX:MaxGCPauseMillis=200 -XX:ParallelGCThreads=20 -XX:ConcGCThreads=5 \
-Duser.timezone=UTC \
-jar obmp-psql-consumer-0.1.0-SNAPSHOT.jar \
-cf obmp-psql.yml > psql-console.log &
The psql-console.log file will capture any console/STDOUT messages. This replaces the nohup.out file.
The normal consumer log file will default to current working directory as obmp-psql.log
. This
file will automatically be rotated and stored compressed under a date folder. See below on how to
customize the log4j configuration.
You can define your own log4j2.yml (yml or any format you prefer) by supplying
the -Dlog4j.configurationFile=<filename>
option to java when running the JAR.
Below is the default log4j2.yml
. Use this as a starting config.
Configuration:
status: warn
Appenders:
Console:
name: Console
target: SYSTEM_OUT
PatternLayout:
Pattern: "%d{yyyy-MM-dd HH:mm:ss} [%t] %-5level %logger{36} - %msg%n"
RollingFile:
name: file
fileName: "obmp-psql.log"
filePattern: "$${date:yyyy-MM}/obmp-psql-%d{MM-dd-yyyy}-%i.log.gz"
PatternLayout:
Pattern: "%d{yyyy-MM-dd HH:mm:ss} [%t] %-5level %logger{36} - %msg%n"
Policies:
SizeBasedTriggeringPolicy:
size: "75 MB"
DefaultRolloverStrategy:
max: 30
Loggers:
Root:
level: info
AppenderRef:
ref: file