Please find below instructions to activate the new dynamic logging feature included in Ephesoft v3128 and above.

Instructions:

Changes required to activate dynamic logging when application is started using startup.bat file.

1)      Stop Ephesoft server.

2)      Open startup.bat file available in JavaAppServer\bin\* folder in a text editor.

3)      Append below parameters to JAVA_OPTS line:

Dcom.sun.management.jmxremote

Dcom.sun.management.jmxremote.port=8900

Dcom.sun.management.jmxremote.authenticate=false

Dcom.sun.management.jmxremote.ssl=false

Dcom.sun.management.jmxremote.local.only=false

4)      Resultant line will looks somewhat like below.

set JAVA_OPTS=-Djava.library.path=F:\\Ephesoft\\Application/native –Djava.io.tmpdir=F:\\Ephesoft\\JavaAppServer/temp –Ddcma.home=F:\\Ephesoft\\Application –Duser.language=enDuser.country=US -Xms1024m -Xmx1024m -Xss512k –XX:MaxPermSize=1024m –XX:PermSize=1024m –Dcom.sun.management.jmxremoteDcom.sun.management.jmxremote.port=8900 –Dcom.sun.management.jmxremote.authenticate=false –Dcom.sun.management.jmxremote.ssl=false –Dcom.sun.management.jmxremote.local.only=false

5)      Please ensure all the parameters are added in a single, new line should not be added after each parameter.

6)      Start Ephesoft Server by executing startup.bat file.

Changes required to activate dynamic logging when application is started using Ephesoft Enterprise service.

1)      Stop Ephesoft server.

2)      Open service.bat file available in JavaAppServer\bin\* folder in a text editor.

3)      Append below parameters to ++JvmOptions:

Dcom.sun.management.jmxremote;

Dcom.sun.management.jmxremote.port=8900;

Dcom.sun.management.jmxremote.authenticate=false;

Dcom.sun.management.jmxremote.ssl=false;

Dcom.sun.management.jmxremote.local.only=false;

4)      Resultant line will look somewhat like below.

“%EXECUTABLE%” //US//%SERVICE_NAME% ++JvmOptions “-XX:MaxPermSize=1024m;-Djava.io.tmpdir=%CATALINA_BASE%\temp;-Djava.util.logging.manager=org.apache.log4j.LogManager;-Djava.util.logging.config.file=%CATALINA_BASE%\lib\log4j.properties;-Djava.library.path=D:\\Ephesoft\\Application/native;-Ddcma.home=D:\\Ephesoft\\Application;-Duser.language=en;-Duser.country=US;-Dcom.sun.management.jmxremote;-Dcom.sun.management.jmxremote.port=8900;-Dcom.sun.management.jmxremote.authenticate=false;-Dcom.sun.management.jmxremote.ssl=false;-Dcom.sun.management.jmxremote.local.only=false” —JvmMx 2048

5)      Please ensure all the parameters are added in single, new line should not be added after each parameter.

6)      Reinstall Ephesoft Enterprise service by executing install-ephesoft-services.bat batch file available at JavaAppServer home location.

7)      Start Ephesoft Server using Ephesoft Enterprise service.

Above changes need to be done manually as this feature was introduced as part of patch release and patch installer don’t modify JavaAppServer configurations. Above changes will not be required to be done manually in next full installer i.e 4.0.

After doing above changes, Ephesoft server is ready to change logging level dynamically. Following are steps need to be followed to change logging level dynamically.

1)      Open jConsole utility available in Jdk bin folder.

2)      Select Remote process radio box and enter <ServerIP>:8900  in text box below to that.

3)      A new window as shown below, will appear on successful connection to Ephesoft Jmx port.

4)      Now select Mbean tab and expand Ephesoft tree node.

5)      On above shown screen, under Attributes node, we can find all the loggers available in Ephesoft.

6)      Under Operations, we have two methods exposed which will help to get current logging level and set logging level for a logger. Please refer to below screenshots.

7)      To get current Log level for a logger, Enter logger name in text box and click on getLogLevel button next to it. A pop will appear with log level information.

8)      To set Log level for a logger, provide logger name as p0 value and log level as p1 value and click then on setLogLevel. A pop will appear with message “Method invoked successfully”.

Was this article helpful to you?

wikiadmin

Comments are closed.