How To - Use `unisrvcntr [start|stop|status] <service(s)>` command to manage CA iGateway and CA Directory services.

Document created by Chandru_V Employee on Oct 8, 2015Last modified by Lenn Thompson on Apr 20, 2016
Version 2Show Document
  • View in full screen mode

As you may already know, CA Embedded Entitlements Manager (EEM) relies on the CA iTechnology iGateway and CA Directory services. On Windows based installs, one can monitor the status of these services from Microsoft Services Console, but on UNIX/Linux platforms, it requires one to run multiple commands to check if iGateway and Directory services are active. 

The KB article at the URL below describes ways to check the status of the iGateway and Directory services:

http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec577022.aspx

 

However, some may like to be able to monitor/manage CA iGateway and CA Directory using the [unifstat | ustat | unisrvcntr | unistart | unishutdown | unicycle] commands on Linux and UNIX platforms, much like managing CA WCC or CA WAAE services.


A couple of scripts that enable this functionality have been attached to this document.

  • S99igateway (manages CA iGateway service)
  • dxserver (manages CA Directory service)

 

I have tested these scripts on Linux (RHEL 6.x and SuSE 11.3 64bit) and Solaris 10 (SPARC) systems running CA EEM 12.0.7.57 and CA EEM 12.51.2.11 [DXserver r12.0 SP13 (build 8091) and r12.0 SP10 (build 6892)].

On AIX and HP-UX systems, the dxserver script may fail due to missing pgrep command (used to retrieve the PID(s) for the status report).

So, how to put these scripts to use?

 

1. Download and move these scripts to the CA EEM host(s).

 

2. Place these scripts under /etc/init.d/ on Solaris or Linux hosts ( /sbin/init.d/ in case of HP-UX and /etc/rc.d/ or /etc/rc.d/init.d/ in case of AIX ) directory:

      Example from Solaris 10 host:

IMPORTANT:

* Backup/rename/move existing dxserver and S99igateway scripts, BEFORE copying.

* Change permission to grant execute (`chmod u+x /etc/init.d/S99igateway /etc/init.d/dxserver`)

 

3. Ensure the DXHOME variable setting in the new dxserver file is set to a valid location. CA Directory may be installed under /opt/CA/SharedComponents/CADirectory/dxserver or /opt/CA/Directory/dxserver

 

The following command may help to identify the correct $DXHOME path if the default "dsa" owns the CA Directory installation.

4. Execute one of these commands to view the status of CA Directory and CA iGateway services:

    `ustat` or `unifstat` or `unisrvcntr status`

 

5. Execute one of these commands to restart services:

    `unicycle dxserver S99igateway` or `unisrvcntr restart dxserver S99igateway`

 

6. Similarly, one the following commands to stop|start services;

    To stop:  `unishutdown <service(s)>` or `unisrvcntr stop <service(s)>`

    To start:  `unistart <services(s)>` or `unisrvcntr start <services(s)>`

 

Backout procedure:

To back-out the changes, simply restore the original dxserver or S99igateway files.


DISCLAIMER:

The sample scripts provided here are not supported under any CA Technologies standard support program or service. All scripts are provided “AS IS” without warranty of any kind. CA Technologies further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample scripts and documentation remains with you. In no event shall CA Technologies, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if CA Technologies has been advised of the possibility of such damages.

Attachments

Outcomes