devan05

CA Tuesday Tip: Managing the DLP Infrastructure Service

Discussion created by devan05 Employee on Jul 19, 2011
CA DLP Tuesday Tip by Andrew Devine, Snr. Support Engineer for 19 July 2011

If you need to stop or restart the CA DLP infrastructure, you can do so using the wgninfra service.

To stop the infrastructure Run this command:

[font=Times New Roman]net stop wgninfra[font]

To restart infrastructure Run this command:

[font=Times New Roman]net start wgninfra[font]

The following command executed from a command prompt in the %wgninstall%\system directory can be used to check a DLP connection:

wgninfra -exec wigan/infrastruct/serviceutil/ConnectionManager Check {parameters}


This command tests the connection between a machine and its CMS or any other machine.

parameters

none - Check connection to CMS and output status to command log.

machine_name - Check connection to machine and output status to command log.

Example:

[font=Times New Roman]wgninfra -exec wigan/infrastruct/serviceutil/ConnectionManager Check MyMachine[font]

Note: The command log can be found in the %wgndatadir%\log directory.

The following are examples of the expected results encountered in different scenarios:

Wgninfra Service Suspended:

Jul 19, 2011 12:50:52 PM Checking Connection to MyMachine
Jul 19, 2011 12:50:52 PM Reply from machine: -- listing properties --serverip=10.119.48.103  servername=MyMachine
Jul 19, 2011 12:50:52 PM Socket connected, trying user service
Jul 19, 2011 12:50:52 PM Infrastructure Disabled
Jul 19, 2011 12:50:52 PM Checked

Wgninfra Service Running:

Jul 19, 2011 12:51:35 PM Checking Connection to MyMachine
Jul 19, 2011 12:51:35 PM Reply from machine: -- listing properties --serverip=10.119.48.103  servername=MyMachine
Jul 19, 2011 12:51:35 PM Socket connected, trying user service
Jul 19, 2011 12:51:35 PM Infrastructure Running OK
Jul 19, 2011 12:51:35 PM Checked

Wgninfra Service Disabled:

Jul 19, 2011 12:53:08 PM Checking Connection to MyMachine
Jul 19, 2011 12:53:11 PM wigan.infrastruct.WgnException: Server not responding
at wigan.infrastruct.serviceutil.Ping.PingIt(Ping.java:442)
at wigan.infrastruct.serviceutil.Ping.PingIt(Ping.java:306)
at wigan.infrastruct.serviceutil.ConnectionManager.Check(ConnectionManager.java:596)

Alternatively Microsoft Windows ships with a SC (Service Check) command and this can be used to confirm a running or non running service. Please note that STATE should be in caps as it is case sensitive.

[font=Times New Roman]SC query wgninfra | Find "STATE"[font]


The following are the expected results:

Wgninfra Service Stopped:

STATE :1 STOPPED

Wgninfra Service Running:

STATE :4 RUNNING

The SC command does not work with a suspended service as the service is still seen as running

Outcomes