Note | ||
---|---|---|
| ||
|
Please follow the below instructions to enable fmq loggings logging at the component level:
- Delete the jar named "slf4j-nop-1.7.5.jar" from the location %FIORANO_HOME%/extlib/apacheds/lib.
- Ensure that the jar named "slf4j-api-1.7.5.jar" is present at %FIORANO_HOME%/extlib/slf4j.
- Configure the log4j log4j2.properties file in the location present at %FIORANO_HOME%/fmq/bin in the following manner:
- Uncomment the line log4j.logger.
Ensure that the following lines are uncommented:
Code Block logger.ClientLoggerServices.name=Fiorano.FMQ.Services.ClientRootLoggerServices.FMQClientLoggerServices logger.ClientLoggerServices.level=OFF
,FILE- Modify the log level from "OFF" to "
ON- ALL" in the above-mentioned line.
'FILE' denotes that the logs Logs are written to the log.out
file file specified in the following line:
Code Block appender.FMQClientLoggerAppender.fileName=log.out
Tip The log.out file can be found in the present working directory of the component which is %FIORANO_HOME%/runtimedata/PeerServers/
<profileName><profileNumber>/FPS/run/components/<ComponentName>/
<Version><VersionNumber>.
To change the name of the file
name, modify the value of the following variable:
Code Block log4j.appender.FILE.File(=log.out)
.
- Add 'log4jthe log4j2.properties' file and 'the log4j-slf4j-log4j12impl-12.717.52.jar' jar jar to the classpath by performing the following the stepsactions:
- In eStudio, navigate to Service Repository view (Window > Show View > Service Repository).
- Expand the corresponding category and right-click the required component > Edit > Deployment, and click Add under the Resource table.
- Go to %FIORANO_HOME%/extlib/slf4j, double-click the 'log4j-slf4j-log4j12impl-12.717.52.jar'.Save jar and save the changes.
Add the 'log4jlog4j2.properties' file file from the location %FIORANO_HOME%/fmq/bin in the same waymanner.
Info The file and the jar get added to the classpath.
Note |
---|
If any changes are made in the |
...
log4j2.properties file, |
...
the same |
...
needs to be updated in the classpath (repeat |
...
Step 4 above) of the component as well. |