CommandTXNPoller

CommandTXNPoller

This application manages the Integration Daemon application directly; it:

  • Initializes transaction queues for EV-P4 communication
  • Initializes message queues for command line interaction
  • Starts the threads for EV interface and P4 Interface
  • Provides for startup, shutdown, status, and configuration commands to both EV and P4 interfaces.

This is the primary application to initiate as a daemon for EV-P4 integration. Under normal circumstances you will not need to run this utility.

Command Line Options for CommandTXNPoller

The following options are available for invoking CommandTXNPoller:

Option Values Significance
-f File Name Specify a file containing command lines (default is none)
-l Log Level Specify the level for logging daemon events (default is 6)
-q Queue Name Specify the message queue name for interprocess communications (default is “P4Commands”)

Note: the file containing commands (specified with the -f option) has one command per line, e.g. 

e:start
p:start

EVP4CommandLine

This application runs as a separate application from the Integration Daemon to provide a simple command-line, interactive interface to the CommandTXNPoller. It uses the JMS message queue functions to issue commands to, and read responses from the CommandTXNPoller.

There are four commands possible to the EVP4CommandLine:

  • START
  • STOP
  • STATUS
  • QUIT

The START, STOP and STATUS commands must be directed to one of the interface threads, either ExtraView or Perforce. To direct a command to an interface, the command is prepended with “E:” (for ExtraView) or “P:” for Perforce. Thus, to issue a status command to Perforce, one would type:

P:STATUS

START Command

This command is used to start the polling for the interface to which the command is directed. Thus, “E:START” starts the ExtraView interface polling for historical issue modifications that may be communicated to Perforce, and “P:START” starts the Perforce polling for changes or job modifications that may be communicated to ExtraView.

STOP Command

This command is used to stop the polling for the interface to which the command is directed. The polling is immediately terminated, possibly leaving some transactions in the intermediate queues in an unprocessed state.

STATUS Command

This command is used to determine the current state of the interface to which the command is directed. The possible states are:

  • INIT: the thread is initialized, but the polling is not started
  • RUN: the thread is running and the polling is active

The STATUS command takes one additional parameter on the command line: the name of a message queue that is used for receiving the status response from CommandTXNPoller. The returned status text is displayed on standard out. After issuing the status command to CommandTXNPoller, the command waits for 10 seconds for a response; if no response is received in 10 seconds, the command terminates; if a response is received, the command terminates after displaying the response.

QUIT Command

This command is not directed at any particular interface, but rather affects the CommandTXNProcessor itself. The QUIT command immediately terminates the CommandTXNProcessor and stops all processing of the child ExtraView and Perforce interface threads. The QUIT command should only be used when the daemon is quiescent, such as after a STOP on both interface threads.