GLU.Engine Settings

The GLU.Engine Settings interface provides analysts with the capability to define a set of parameters utilised by the GLU.Engine during operation. These settings regulate the GLU.Engine’s interaction with the operational environment.

To configure the settings, activate the ‘GLU Engine Settings’ button and select the desired environment to specify the settings for.

Choose the GLU.Engine required and the GLU.Engine Settings page will open on the General tab. 

Navigate the tabs and choose the settings to change. The following settings can be changed:

• General settings:
  • Server Port
  • switch spring JMX Enabled
  • switch jolokia debug Mode Active
  • switch Management Endpoint Shutdown Enabled
• Logging level and parameters
• Docker settings:
  • switch on docker usage and distribution
  • all associated docker parameters if docker is switched on
• Provision customised settings for the GLU.Engine
• Adjust the JVM settings which the GLU.Engine utilises

General tab

The Server Port or Management Port (used interchangeably) in the context of JMX metrics refers to the port number used for communication between JMX client applications and the JVM (Java Virtual Machine) management interface. JMX (Java Management Extensions) is a Java technology that provides a standard way to monitor and manage Java applications and resources. The JMX Management Port allows remote monitoring and management of a running Java application through JMX client applications. JMX client applications can use the Management Port to connect to the JVM and retrieve information about the application, such as memory usage, thread counts, and performance metrics, as well as perform management operations, such as garbage collection and thread dumps. The Management Port is specified as a command line argument when starting the JVM and its default value is typically set to 9010.

The Server Port field can be set to control which port the GLU.Engine Management APIs use. The server port must be unique for each GLU.Engine running on a server therefore it is important to change the server port if you plan to run multiple GLU.Engines on the same server. If you don’t change the port for each such GLU.Engine, you’ll have conflicts when trying to startup the GLU.Engine. 

The Management Endpoint JMX Domain is used to set the URL for the JMX Domain.

Use the tick boxes to: 

• switch Spring JMX to be enabled, this will enable JMX Metrics to be available on the set JMX Domain via the Server Port.
• switch Management Endpoint shutdown to be enabled. (This setting exists to provide an extreme level of security for the shutdown of GLU.Engines, if enabled then the API will work and you can shutdown the GLU.Engine from the API call. Shutdown API Call)

Note that if your Application Settings have the path for logs set to a sub-folder within the GLU.Engine folder if / when you deploy a new build you will lose / over-write your logs if you’ve not moved them. So in Application Settings, the recommendation is to set the path to a folder outside the GLU.Engine folder. 

For the details on setting the name of the Log file GLU.Engine Log Name.

Logging tab

For details on log levels settings see GLU.Engine Logging Levels.

For details of each of the settings in the log tab please refer to  GLU.Engine Logs.

Docker tab

It is possible to switch on the use of Docker and set the Docker settings which are used to push a docker container to a container registry. All fields are mandatory. 

For some container registry systems like Azure when the  docker image repository doesn’t exist, then it will be created when GLU pushes to the container registry. 

For more information on the docker settings please refer to GLU.Engine running in Docker.

Custom Settings tab

Where required it may be necessary to set up customer parameters for using with the GLU.Engine. If this is required these settings can be configured in this tab.

JVM tab

The JVM Arguments are set to the default arguments for running the Java Virtual Machine which runs the GLU Engine, however with access to these settings it is possible to refine the settings as required to optimise the performance of the GLU.Engine. 

Please refer to  GLU.Engine – Performance-Level Settings for details of how the changes will affect the GLU Engine.

The JVM Arguments will be applied to docker as well if the GLU.Engine is to be hosted in docker. The following extract shows how the JVM settings can be viewed using the docker exec command. Use command docker ps to view the containers:

root@ip-172-31-52-133:~# docker ps
CONTAINER ID   IMAGE                                       COMMAND                  CREATED         STATUS         PORTS                                                                  NAMES
4e71043cef89   gluglobal/glu_data:1.0-SNAPSHOT             "java '-Djava.securi…"   5 minutes ago   Up 5 minutes   9088/tcp, 9195/tcp                                                     data_autoTest.1.4g03oc84p4kbt5b1a8waj5n3y
5

docker exec -u 0 {CONTAINER ID} ps -ef to see the java call.

root@ip-172-31-52-133:~# docker exec -u 0 4e71043cef89  ps -ef | grep java
    1 root       0:55 java -Djava.security.egd=file:/dev/./urandom -XX:+PrintGCDetails -Xloggc:gc.log -Xms2g -Xmx2g -XX:+UseG1GC -XX:MaxGCPauseMillis=250 -XX:+UseStringDeduplication -XX:G1HeapRegionSize=32 -XX:G1ReservePercent=15 -XX:InitiatingHeapOccupancyPercent=30 -XX:MetaspaceSize=100M -jar /glu_data-1.0-SNAPSHOT.jar --logging.config=./engine/config/loggingSetting.xml
root@ip-172-31-52-133:~#