|
|
The different modules of Web NMS are initiated and managed by corresponding processes defined in NmsProcessesBE.conf and NmsProcessesFE.conf. When Web NMS is started, these configuration files are read and the processes are started. You can prevent a process from getting initiated by commenting it's definition i.e Process name and arguments list, in the conf file.
This section explains the various processes related to Management Protocols.
com.adventnet.nms.ms.NMSMServer
Functionality
Starts the Management Server.
Declaration
java com.adventnet.nms.ms.NMSMServer
[-debug 0,1,2,3]
Process com.adventnet.nms.ms.NMSMServer
ARGS -debug 0
Arguments and Description
| Argument | Description |
|---|---|
|
-debug |
Specifies the level of logging in the Management Server. The values could be from 0 to 3 where, 0 means No logging 1 means logging up to Management Server Level 2 means logging up to XML Level 3 means logging up to Provider Level |
Dependencies
Mandatory Process Dependencies
com.adventnet.nms.topodb.DBServer - Only when the com.adventnet.nms.topodb.DBServer process is activated, would the com.adventnet.nms.ms.NMSMServer process begin.
com.adventnet.nms.sas.NMSSAServer
Functionality
To start the SAS which provides communication for applets which are unable to connect directly to managed devices due to security limits
Declaration
# java com.adventnet.nms.sas.NMSSAServer
[SAS_DEBUG true/false]
[SAS_PORT port]
[APPLET_DIRECTORY applet_directory]
[WEBSERVER_ROOT directory]
[RESTRICT_SOCKETS true/false]
[FILE_OUTPUT true/false]
[SERVER_CLIENT class]
[SESSION_CLIENT class]
[LOG_CLASS class]
[REGISTER_CLIENT class]
Process com.adventnet.nms.sas.NMSSAServer
Arguments and Description
| Argument |
Description |
|---|---|
|
SAS_DEBUG |
This option enables the debug and prints the packet dumps. Default value : False |
|
SAS_PORT |
This option allows you to specify the port in which the SAS can start. Writes the port number to the SASPort.html file. Default : 0 (Any free port) |
|
APPLET_DIRECTORY |
This option allows you to specify the directory in which the SASPort.html file will be written. By default it is the current directory. The SASUsers sub-directory, which is used to save data from the applets should be created under the directory specified. - Default value : Empty string |
|
WEBSERVER_ROOT |
Specifies the root directory of the Web server. Default value : Empty string |
|
RESTRICT_SOCKETS |
This option allows socket access only to SNMP UDP ports 161 and 162. Default value : False |
|
FILE_OUTPUT |
This option enables/disables file output access Default value : False |
|
SERVER_CLIENT |
Implementation class for SAServerClient. Default value : null |
|
SESSION_CLIENT |
Implementation class for SASessionClient. Default value : null |
|
LOG_CLASS |
Implementation class for SASLogInterface interfaces. Default value : null |
|
REGISTER_CLIENT |
This option can be used to set the user's implementation of the interface "RegisterClient". This interface can be used by the API users to receive the traps coming from different agents. Default value : null |
Dependencies
Other Process Dependencies
SASServerFE and NMSSAServerFE - SASServerFE is a proxy forwarder for SAS in FE. Unless SAServer is started in the BE, there is no need to have its counterpart in FE. Hence, these processes are inter-dependent.
com.adventnet.nms.tl1.NMSTAServer
Functionality
NMSTAServer is a wrapper of the TAServer. This process enables the running of the TAServer as a part of Web NMS server in the same JVM.
TAServer enables the TL1 Craft Interface to communicate with the TL1 NEs in an applet client environment. TAServer is a part of the TL1 API 4.0 product bundled in Web NMS. The TL1 Craft Interface and other TL1 functionalities will not function, if TAServer is not enabled.
Declaration
java com.adventnet.nms.tl1.NMSTAServer
Process com.adventnet.nms.tl1.NMSTAServer
ARGS NULL
Dependencies
This process is a standalone process and does not depend on any other NMS processes.
com.adventnet.nms.util.SnmpCorbaServer
Functionality
On starting this process, the northbound API will be provided for doing SNMP operations, like GET, GET BULK, SET etc.
Declaration
java com.adventnet.nms.util.SnmpCorbaServer
[propertyfiles]
Process com.adventnet.nms.util.SnmpCorbaServer
ARGS ORBInitialPort 1050
Arguments and Description
| Arguments | Description |
|---|---|
|
ORBInitialPort |
The port wherein the CORBA Server is running. |
Dependencies
None
com.adventnet.nms.telnet.telnetwindow.CLIFactoryBinder
Functionality
This process enables the client to access the CLI API and enables the access to the CLI API operations.
Declaration
java com.adventnet.nms.telnet.telnetwindow.CLIFactoryBinder.
Arguments - Null
Dependencies
None
com.adventnet.nms.fe.ms.MServerFE
Functionality
This process is a forwarder for management server packet over the common NMS socket.
Declaration
java com.adventnet.nms.fe.ms.MServerFE
Arguments - Null.
Dependency
com.adventnet.nms.topodb.DBServer
com.adventnet.nms.fe.sas.SAServerFE
Functionality
This process is the FE SAServer proxy forwarder. It accepts all SAS Client requests and forwards them to the SAServer running in either FE or BE. If the SAServer is started in FE, then it forwards the requests to FE, otherwise it forwards them to BE
Declaration
java com.adventnet.nms.fe.sas.SAServerFE
Arguments - Null.
Dependency
NmsSAServerBE or NmsSAServerFE
SASServerFE is a proxy forwarder for SAS in FE. Unless SAServer is started in the BE, there is no need to have its counter part in FE. Hence, these processes are inter-dependent.
com.adventnet.nms.fe.tas.TAServerFE
Functionality
This process is a forwarder in the FE for the NMSTAServer process running on the BE. It forwards all the requests from the client to the BE server.
Declaration
java com.adventnet.nms.fe.tas.TAServerFE
Arguments - Null.
Dependency
com.adventnet.nms.tl1.NMSTAServer
|
|