This document covers the following topics:
Note:
To allow the stopping of an NPR service while the TCP/IP connection
to the Broker is down, an automatic setting of the environment variable
ETB_TIMEOUT was added in NPRETB and NPRMGR. If
ETB_TIMEOUT is already set before execution of
NPRETB respectively NPRMGR, it remains unchanged. Otherwise it will be set to
60 seconds. This avoids a hang of the Broker stub during a disconnected TCP/IP
connection, and allows the stopping of npretb in such a situation.
This section covers the following topics:
The NPRMGR utility offers a command-line-oriented interface that allows the user to:
Start servers in its local system
Stop servers both in its local system and in remote systems
Query the status of the server of a service Go to Top
To invoke the utility from the UNIX shell
Invoked the command
$ nprmgr
Once invoked, the utility shows the prompt NPRMGR> to show that it is ready to accept commands.
To execute a single command and then exit the utility
Invoke NPRMGR in the following way:
$ nprmgr <command>
The input of NPRMGR can be redirected from a text file.
To obtain online help for the utility
Type HELP at the NPRMGR prompt.
Or:
Invoke NPRMGR in the following way:
$ nprmgr help
Below Additional information available: a list of
subtopics is displayed. To get more information on a particular subtopic enter
the first character(s) that uniquely identify it and press Enter.
To exit the utility
Type QUIT,
Q, Control+D, or your
terminal EOF sequence at the NPRMGR prompt.
The commands are not case sensitive, but service identifiers are.
More specific commands are described in the following subsection.
| Syntax | Description |
|---|---|
start service <service name> |
This command starts the server of a service on the local machine. |
The specified value for <service name> is compared to the section identifiers (i.e <npr identifier>) of the npr.ini file and it must correspond to a valid service definition in the EntireX Broker parameterization file.
If the server is detected to be already active, the command will not be executed. Even if NPRMGR says the server has been started, the server may fail to initialize itself.
You can use the display service command to check for the successful activation of a server.
| Syntax | Description |
|---|---|
display service [<service name>] |
This command allows you to check whether a server is running for a service or not. If you omit the parameter <service name>, the command results in a status report for all service names defined in the npr.ini file. |
If Entire Net-Work is operative, this command can detect services in any node of the network. Otherwise, this command will only detect servers running on the local machine.
| Syntax | Description |
|---|---|
stop service <service name> |
This command stops the server process that is serving requests for a given service. |
To be able to execute this command
If Entire Net-Work is operative, you must log on to the server.
NPRMGR will ask you for a user ID and password. Even if the login succeeds, the server may refuse to be stopped because the user is not authorized.
Or:
If Entire Net-Work is down, then the user under which
you are executing NPRMGR must be authorized to stop the service.
You will not be required to enter a user name or password. In this situation, the server process may last up to 30 seconds before actually stopping.
Note:
Although every user is authorized to start a server, only the
administrator (as specified in the npr.ini file) and the
root user are allowed to stop an active system server process.