Example of logging for Jasper/SDM connection test success through xFlow Insights
search cancel

Example of logging for Jasper/SDM connection test success through xFlow Insights

book

Article ID: 247834

calendar_today

Updated On: 05-13-2025

Products

CA Service Desk Manager CA Service Management - Service Desk Manager

Issue/Introduction

When one enables extended logging in both Jasper and SDM, the following will be observed when testing the sdm_ds datasource for connectivity from Jasper to SDM, either by using the connectivity test function in Jasper, or in the logging example given, Insights is invoked from xFlow.

Environment

CA Service Management 17.1 and higher with Jasper integration

Resolution

The following testing was done in a non-prod instance, where both SDM and Jasper Services were recycled, and no JDBC related entries were initially found in the SDM slump connection listings immediately after restart. 

Overall integrated architecture (non-SSL) and logging activated:  

Server 1:  Service Desk and xFlow server (17.4 release)

insight microservice:  KB Article 45002

SDM logging:  Ran the following from an Admin Command Prompt on the SDM Server

pdm_logstat -n boplgin TRACE
pdm_logstat -f sqlclass.c TRACE
pdm_logstat -n domsrvr TRACE


Logs of interest:

SDM:  C:\Program Files (x86)\CA\Service Desk Manager\log\stdlog.X
xFlow:  C:\Program Files\CA\xFlow\APPS\logs\insightMS_debug.log

 

Server 2:  Jasper Server (Jasper 9.0 release)

Jasper/JDBC logging:  KB Article 247835

Logs of interest:
C:\Program Files\Apache Software Foundation\Tomcat 9.0\webapps\jasperserver-pro\WEB-INF\logs\jasperserver.log
Optional:  C:\Program Files\Apache Software Foundation\Tomcat 9.0\logs\localhost_access_log.20XX-01-01.txt



When connecting to the Insights app on xFlow and running a report from Insights, the following will present in the jasperserver.log:

20XX-01-01T17:31:37,293 DEBUG DalJdbcDriver,http-nio-8080-exec-7:145 - URL: jdbc:sdm:bop:@[SDM-XFLOW SERVER]:2100;impersonateUserUuid=ED4A390065CBF14CA4DB4033EE1AF4DF, properties: password:********;user:[SERVICE DESK USER];
20XX-01-01T17:31:37,369 DEBUG DalJdbcDriver,http-nio-8080-exec-7:179 - In DalJdbcDriver: logged in
20XX-01-01T17:31:37,369 DEBUG DalJdbcDriver,http-nio-8080-exec-7:183 - username=[SERVICE DESK USER], impersonateUserUuid=ED4A390065CBF14CA4DB4033EE1AF4DF, roleId=null
20XX-01-01T17:31:37,790 DEBUG DalJdbcDriver,http-nio-8080-exec-7:244 - token: 753772544


Of interest is "753772544" which is the token that Jasper obtains as part of the integration.


The localhost_access_log.20XX-01-01.txt will show a corresponding record of that access.  [SDM-XFLOW SERVER IP ADDRESS] is the IP Address of the SDM/xFlow server.

[SDM-XFLOW SERVER IP ADDRESS] - - [01/Jan/20XX:17:31:05 +0000] "GET /jasperserver-pro/rest_v2/organizations/casm_insights/users/[SERVICE DESK USER] HTTP/1.1" 200 370
[SDM-XFLOW SERVER IP ADDRESS] - - [01/Jan/20XX:17:31:06 +0000] "PUT /jasperserver-pro/rest_v2/organizations/casm_insights/users/[SERVICE DESK USER]/attributes HTTP/1.1" 200 176
[SDM-XFLOW SERVER IP ADDRESS] - - [01/Jan/20XX:17:31:06 +0000] "PUT /jasperserver-pro/rest_v2/organizations/casm_insights/users/[SERVICE DESK USER] HTTP/1.1" 200 370


On the SDM Server, the stdlog will show:

01/01 17:31:37.76 [SDM-XFLOW SERVER] boplgin                 5884 TRACE        sys_kpi.c              672 Inserted session with id 753772544 into session_history
01/01 17:31:37.77 [SDM-XFLOW SERVER] sqlagt:select41         6184 MILESTONE    sqlclass.c            1063 The following statement took 1 milliseconds: Clause (SELECT session_log.id FROM session_log WHERE session_log.id = ?) Input (<int>753772544)
01/01 17:31:37.77 [SDM-XFLOW SERVER] boplgin                 5884 TRACE        bplaccess.c           7711 New session (753772544) started for userid ([SERVICE DESK USER])
01/01 17:31:37.78 [SDM-XFLOW SERVER] domsrvr                 8140 TRACE        sec_mgr.c             3221 Using existing UserCntInfo [SERVICE DESK USER] (0x000001CBCBF70170) for DomSession 753772544-cnt:ED4A390065CBF14CA4DB4033EE1AF4DF (0x000001CBCB9C8410); refcount 0; UserCntInfo count 2
01/01 17:31:37.78 [SDM-XFLOW SERVER] domsrvr                 8140 TRACE        sec_mgr.c             5242 Created primary DomSession 753772544-[SERVICE DESK USER] (000001CBCB9C8410); DomSession count 5
01/01 17:31:38.29 [SDM-XFLOW SERVER] boplgin                 5884 TRACE        bplaccess.c           6098 Queuing (REPORTS) Session_Object 753772544 for delete in 300 seconds


In the above, we see the same 753772544 mentioned as an access token in Jasper reporting, now showing as a session ID in the SDM stdlog.

The insightMS_debug.log logging will show:

DEBUG 20XX-01-01 17:31:36 [           AsyncHttpClient-3-2] ChannelManager                   268 Adding key: http://[JASPER-SERVER]:8080 for channel [id: 0xc19cd1a9, L:/[SDM-XFLOW SERVER IP ADDRESS]:51573 - R:[JASPER-SERVER]/[JASPER SERVER IP ADDRESS]:8080]
DEBUG 20XX-01-01 17:31:36 [           AsyncHttpClient-3-2] SecondaryKeyCalculator            76 calculate: returning secondaryKeys = TreeMap(Origin -> List(http://[JASPER-SERVER]:8080))
DEBUG 20XX-01-01 17:31:36 [     AsyncHttpClient-timer-1-1] DefaultChannelPool               348 Entry count for : http://[JASPER-SERVER]:8080 : 5
DEBUG 20XX-01-01 17:31:36 [     AsyncHttpClient-timer-1-1] DefaultChannelPool               302 Adding Candidate expired Channel [id: 0x558b4ad3, L:/[SDM-XFLOW SERVER IP ADDRESS]:51574 ! R:[JASPER-SERVER]/[JASPER SERVER IP ADDRESS]:8080] isIdleTimeoutExpired=false isRemotelyClosed=true isTtlExpired=false

 

Furthermore, if one views the slump connection listings, one will find an entry like this to be present:

dal_jdbc_driver_[JASPER-SERVER]                                          5    55 Tue Jan 01 17:31:37 20XX

 

stdlog will present with:

01/01 17:31:37.47 [SDM-XFLOW SERVER] domsrvr                 8140 MILESTONE    bpremref.c             326 Registering client @|dal_jdbc_driver_[JASPER-SERVER]


To view the above, one would run the command slstat on the given [SDM-XFLOW SERVER].  The above entry would not be present in SDM immediately after restart and before the Jasper data source test.  The above entry will only appear in the slstat output if you run a report in Insights.  Opening Insights alone may not cause the process to generate in SLUMP.

Additional Information

The jasperserver.log will expose a token integer value, which will match the SDM stdlog session id for the corresponding timeframe (logging needs to be enabled for both).

The Jasper Server's localhost_access_log and insightMS_debug.log can be used to verify the SDM Server and the Jasper Server involved in the integration.  

Certain log entries were omitted from this KB article for purposes of brevity and clarity.

Powered by Wolken Software