Skip to main content
Skip table of contents

Enabling Client Logging for components

Installer Path

  • UNIX: $FIORANO_HOME
  • Windows: %FIORANO_HOME%

Please follow the below instructions to enable fmq logging at the component level:

  1. Delete the jar named "slf4j-nop-1.7.5.jar" from the location %FIORANO_HOME%/extlib/apacheds/lib. 
  2. Ensure that the jar named "slf4j-api-1.7.5.jar" is present at %FIORANO_HOME%/extlib/slf4j.
  3. Configure the log4j2.properties file present at %FIORANO_HOME%/fmq/bin in the following manner:
      1. Ensure that the following lines are uncommented:

        CODE
        logger.ClientLoggerServices.name=Fiorano.FMQ.Services.ClientRootLoggerServices.FMQClientLoggerServices
        logger.ClientLoggerServices.level=OFF
      2. Modify the log level from "OFF" to "ALL" in the above-mentioned line.
      3. Logs are written to the log.out file specified in the following line:

        CODE
        appender.FMQClientLoggerAppender.fileName=log.out

        The log.out file can be found in the present working directory of the component which is %FIORANO_HOME%/runtimedata/PeerServers/<profileNumber>/FPS/run/components/<ComponentName>/<VersionNumber>.

      4. To change the name of the file, modify the value of the following variable:

        CODE
        log4j.appender.FILE.File(=log.out)
  4. Add the log4j2.properties file and the log4j-slf4j-impl-2.17.2.jar jar to the classpath by performing the following actions:
    1. In eStudio, navigate to Service Repository view (Window > Show View > Service Repository).
    2. Expand the corresponding category and right-click the required component > Edit > Deployment, and click Add under the Resource table.
    3. Go to %FIORANO_HOME%/extlib/slf4j, double-click the log4j-slf4j-impl-2.17.2.jar jar and save the changes.
    4. Add the log4j2.properties file from the location %FIORANO_HOME%/fmq/bin in the same manner.

      The file and the jar get added to the classpath.

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.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.