Centralizing CWCLIent Operations

From TDiWiki

Jump to: navigation, search

CWCLIent may be installed and configured on a UNIX server so that it listens for incoming telnet connections to a specific port. This configuration enables administrators to install and setup CWCLIent on one machine and access it from anywhere on the network.


The first step in centralizing CWCLIent is installing it on the UNIX machine on which you want it to run.

NOTE: If you have installed ConsoleWorks on this machine, you do not need to also install CWCLIent, as it is included in the ConsoleWorks installation process. Please see the CWCLIent User's Guide for instructions on how to install CWCLIent.


The next step is to pick a network port number for CWCLIent to listen on. Because ConsoleWorks defaults to listening on port 5176, the following instructions will use 6176 as the port number for CWCLIent. You should use a port number that is valid for your environment.

Run the following command on the UNIX server and verify that no other process is listening on the port you chose: 

# netstat -an | grep 6176

#


The third step is to edit the /etc/services file and add the following line to the file:

cwclient          6176/tcp                         # cwclient telnet listener

NOTE: The "cwclient" service name, "6176/tcp" port number, and "# cwclient telnet listener" comments must be separated by tabs and not spaces.


The fourth step differs, depending on whether you're configuring CWCLIent on a UNIX server that runs inetd (Solaris, AIX) or one that runs xinetd (linux).

FOR SYSTEMS THAT USE INETD

Edit the /etc/inetd.conf file and add the following line to the file:

cwclient    stream    tcp    nowait    root    /opt/TDIcnwrks/bin/cwterm    cwterm -inetd

NOTES:

  • The "cwclient" service name, "stream" socket type, "tcp" protocol, "nowait", "root" user, "/opt/TDIcnwrks/bin/cwterm" server program, and "cwterm -inet" server program arguments need to be separated by tabs, not spaces.
  • "/opt/TDIcnwrks/bin/cwterm" server program might be in a different location than the one here, depending on your platform and installation directory.
  • In addition to "-inet", other cwterm parameters such as "-port=5176" and "-server=<fully qualified domain name>" may be specified

FOR SYSTEMS THAT USE XINETD

cd to the /etc/xinetd.d directory and create a file named cwclient. The file should contain the following:

service cwclient
{
    disable = no
    flags = REUSE
    socket_type = stream
    wait = no
    user = root
    server = /opt/ConsoleWorks/bin/cwterm
    server_args = -inetd
    log_on_failure += USERID
}

NOTES:

  • "/opt/ConsoleWorks/bin/cwterm" server program might be in a different location than the one used here, depending on your platform and installation directory.
  • In addition to "-inet" other cwterm parameters such as "-port=5176" and "-server=<fully qualified domain name>" may be specified on the same line.


The fifth step is to restart the inetd/xinetd daemon so it will read in the new configuration and start listening for incoming connections to CWCLIent.

Solaris: 

# inetconv

cwclient -> /var/svc/manifest/network/cwclient-tcp.xml

Importing cwclient-tcp.xml ...Done

# svcadm restart inetd

#

Linux: 

# /etc/init.d/xinetd restart

Stopping xinetd:                                           [  OK  ]

Starting xinetd:                                           [  OK  ]

#

AIX: 

# refresh -s inetd

0513-095 The request for subsystem refresh was completed successfully.

#


The final step is to ensure that port 6176 is being listened to: 

# netstat -an | grep 6176

     *.6176               *.*                0      0 49152      0 LISTEN

#


Now you can telnet to port 6176 of the server you just set up from any machine on your network and get your CWCLIent prompt. 

#  telnet cwclienthost 6176

Trying...

Connected to cwclienthost.tditx.com.

Escape character is '^]'.



ConsoleWorks>

Retrieved from "http://wiki.tditx.com/index.php/Centralizing_CWCLIent_Operations"
Personal tools