Application status is not correctly displayed.

Administration
1

Hi all

We enable us to see status of third-party applications by SCI.
We have a problem.
'Stopped’status is displayed on SCI though these applications work normally.
FYI:
・LCA version is 6.5.000.23.
・SCS and LCA are installed on different server through WAN.

Following is SCS log.

hostname: REventAppLiveStatusChanged… APP_STATUS_STOPPED, mode= , app=APP_A, PID=2196
‘hostname’: NotifyApp: status= APP_STATUS_STOPPED mode= pid=2196 {162, APP_A}
07:29:28.550 Standard hostname APP_A GCTI-00-05064 Application terminated due to internal condition

App{162,APP_A} status changed to APP_STATUS_STOPPED mode= , [prev=APP_STATUS_RUNNING]

07:29:28.551 Trace ctioksvp SCS GCTI-43-20620 [Application APP_A]: LiveStatus changed to APP_STATUS_STOPPED from APP_STATUS_RUNNING
Nothing to do on STOPPED/UNKNOWN for ‘APP_A’.
hostname: REventAppLiveStatusChanged… APP_STATUS_STOPPED, mode= , app=APP_A, PID=2196
hostname: REventAppLiveStatusChanged… APP_STATUS_STOPPED, mode= , app=APP_A, PID=2196
hostname: REventAppLiveStatusChanged… APP_STATUS_STOPPED, mode= , app=APP_B, PID=2056
‘hostname’: NotifyApp: status= APP_STATUS_STOPPED mode= pid=2056 {161, APP_B}
07:29:29.550 Standard hostname APP_B GCTI-00-05064 Application terminated due to internal condition

App{161,APP_B} status changed to APP_STATUS_STOPPED mode= , [prev=APP_STATUS_RUNNING]

07:29:29.550 Trace ctioksvp SCS GCTI-43-20620 [Application APP_B]: LiveStatus changed to APP_STATUS_STOPPED from APP_STATUS_RUNNING
Nothing to do on STOPPED/UNKNOWN for ‘APP_B’.
hostname: REventAppLiveStatusChanged… APP_STATUS_STOPPED, mode= , app=APP_B, PID=2056
hostname: REventAppLiveStatusChanged… APP_STATUS_STOPPED, mode= , app=APP_B, PID=2056
ADDP: closing 21 - timed out (9000 msec), remote socket [400]

Could you please tell us the solution?

2

Hi,

LCA use the so-called command-line matching mechanism. It means that LCA monitors list of running processes and compares these with 3rd party application properties defined in Genesys configuration. There are several “issues” related to that mechanism so please check following:

  • the combination of , and has to correspond to parameters in the configuration. If it doesn’t LCA tells you the application is stopped.
  • if the command line parameters are too long than LCA shouldn’t be able to recognise status of the application. Some operating systems like Solaris, doesn’t returns full length of application command line so the comparison done by LCA fails in that case.

The way how LCA controls third-party applications is described in “Framework 6.5 Management Layer User’s Guide”.

Hope it helps you.

René

2 Likes