Converter Services › How to Configure the CFB Server › CFB Server Control Client

CFB Server Control Client

The CFB Server Control Client allows the system administrator to interactively see what is happening in any CFB Server. The Control Client is an interactive task that connects to any CFB Server through a published (or well known) socket to display connection status and control active connections.

The default configuration of the CFB Server accepts connections only from the local host IP address. The CFB Server properties can be changed to accept connections from other IP addresses, allowing the Control Client to connect to a Server at a remote IP address.

The Control Client uses a command line interface. The localhost can be in IPv4 or IPv6 format. To start the Control Client, open a command window and enter the following command:

java -cp <CA-Gen-Root>\classes\jcfb##.jar 
    com.ca.genxx.jcfbserv.control.ControlServer 
    localhost:8900

Note: xx refers to the current release of CA Gen. For the current release number, see the Release Notes.

The controlCommand.jar file must be in the current directory.

Localhost:8900 is the control port on the CFB Server in this example.

The basic format of the command is:

Dis[play] [port]

The Control Client cannot modify the state of any resource in the CFB Server.

The following commands are available for the Control Client.

• Help—lists all available commands.
• Quit—terminates the Control Client.
• Display—shows two or more lines for each listening port. The first line is the name of the server, the port number, and number of active connections.
  • Control—the server that handles the display command request.
  • Listener—the server that handles TCP/IP CFB requests from clients.
  • Request Processor—the server that connects to the EJB server for each request.

  The second line displays server statistics of connections (successful and failed). One additional line is displayed for each active session. It contains:

  • Connection ID—listening port requesting port pair.
  • Status—COK for active connections.
  • Bytes sent and received for connections on listening ports.
  • Time connection has been alive.
  • The name of the connection.

  Request Processor EJB connections do not show performance statistics.

• Display port—shows the status of the identified resource where the server is listening. Examples of what is displayed follow:
  • Command Reader OK.
  • Control[8900] serving 1 active connections.
  • Since host start 1 connections succeeded. 0 failed.
  • 8900:1360 COK 0 0 0 0 0sec XC[8900:1360]
  • Listener[8901] serving 0 active CFB connections.
  • 0 connections succeeded. 0 connections failed.
  • Listener[8902] serving 0 active CFB connections.
  • 0 connections succeeded. 0 connections failed.
  • Request Processor Thread-2 active 10sec. idle 300sec.
  • Processed 0 request, of which 0 failed, processed 0 responses and 0 errors.