Reconfiguring xDeTECH Services

Configuration properties are stored in files in the config directory of each service. The service must be restarted for any changes to these services to take effect.

Open a terminal window and log in to a session on the container.
List running processes: ps -ef | grep sentinel Example output shows three java processes, from top to bottom: VCDx, VGSx and VGSx tester. The process id (PID) is the leftmost number listed.

root 8582 8578 8 Oct27 pts/44 06:01:13 java --add-opens java.base/java.lang=ALL-UNNAMED -cp /sentinel-vcdx/config:/sentinel-vcdx/lib/* -Djava.library.path=/sentinel-vcdx/bin:/sentinel-vcdx/bin/DaonReplayTelephonyTI:/sentinel-vcdx/bin/DaonVoiceCloningTelephony:/sentinel-vcdx/bin/DaonVoiceQC -Ddaon.dir=/sentinel-vcdx -Ddaon.logs.dir=/sentinel-vcdx/logs -Dlog4j.formatMsgNoLookups=true com.daon.sentinel.SentinelVoiceCloneReplayApplication root 8893 8889 0 Oct27 ? 00:10:32 java -jar SentinelVoiceGatewayServices-0.0.0.1-SNAPSHOT.jar --spring.config.location=file:/sentinel-vgsx/config/application.properties root 10213 10209 0 08:22 pts/43 00:00:35 java -jar sentinel-vgs-tester-0.0.1-SNAPSHOT.jar --spring.config.location=file:/sentinel-vgsx-tester/config/application.yml

Kill the process you want to reconfigure: kill -9 {PID} where PID represents the Process ID. To kill VGSx in the example above, use kill -9 8893
Change to the config directory for the service: cd {service-folder}/config where service-folder is one of sentinel-vcdx, sentinel-vgsx or sentinel-vgsx-tester
Update the configuration file, either application.properties or application.yml , using a console editor of your choice (example vi ). Alternatively, copy the file from the container, edit it on your desktop and copy it back.
Change directory to the bin directory of the updated service. For example: cd sentinel-vgsx/bi
Restart the service as a background task: ./startup.sh &
Check the service is running. You can check the service logs listed in the directory structure above, and ping the service to be sure.
1. List running services: ps -ef | grep sentinel
2. Ping the services:

For VCDx: curl localhost:8099/actuator/health Returns:

{ "status": "UP", "components": { "livenessState": { "status": "UP" }, "readinessState": { "status": "UP" } }, "groups": [ "liveness", "readiness" ] }

For VGSx: curl localhost:8080/pingReturns:

{ "system": "SentinelVgsx", "id": "1", "systemTime": "2023-11-02T16:30:01.590+0000", "sentinelVersion": "1.0.0", "buildVersion": "1", "receivedInitFromSIPRECStack": false, "lastCallReceived": "2023-11-02T16:29:58.076+0000", "analysisServiceAvailable": true, "acceptsNewActionCommands": true }

For VGSx Tester: curl localhost:8081/pingReturns:

{ "system": "Sentinel VGS Tester", "systemTime": "2023-11-02T16:30:57.236+00:00", "buildVersion": "1.0.0" }

Check the service logs. Logs are stored in the service’s logs directory. You can type cat {log name} to see that the service has started up without errors.

Last updated on