Professional Documents
Culture Documents
A160428-CE EMS Admin Guide-HFR-v1.4
A160428-CE EMS Admin Guide-HFR-v1.4
Administration
Version 1.4
NOTICE
This document contains proprietary and confidential material of HFR, Inc. Any unauthorized, reproduction, use or
disclosure of this material, or any part thereof, is strictly prohibited. This document is solely for the use of HFR
employees and any authorized customers or partners. HFR, Inc. reserves the right to make changes in the
specifications at any time and without notice.
1. Document Information
This document describes method of using CE-EMS for Admin user.
Revision History
References
Page 2
HFR, Inc.
2. Table of Contents
HFR CE-EMS Guide Administration .............................................................................................................................................. 1
References .................................................................................................................................................................................. 2
4. Discovery........................................................................................................................................................................................... 41
Page 3
HFR, Inc.
6. Monitor/Management ................................................................................................................................................................ 53
Page 4
HFR, Inc.
9. Appendix A. ..................................................................................................................................................................................... 64
Page 5
HFR, Inc.
Page 6
HFR, Inc.
4. Click “Next”
5. The License Agreement screen is displayed. Select "I accept the License Agreement" to proceed
further installation process.
6. Click “Next”
7. Select “English” language of HFR CE-EMS.
Page 7
HFR, Inc.
8. Click “Next”
9. In the next screen, select “Advanced” to install all the components including Back-End,
Standalone Front-End and Distributed Poller.
12. Screen to specify the destination directory to install “Back-End Server” is displayed.
13. Click “Next” to install “Back-End Server” to the specified destination in, or click “Browse” to
install to a different location.
14. The installation details like “Installation Directory” and “Product size” are displayed in next
screen.
15. Click “Next” to start installation process or “Back” if there are any changes in the destination
location.
Page 9
HFR, Inc.
Page 10
HFR, Inc.
1. After installing CE-EMS, copy the patch file (.nar file) at <CE-EMS BE HOME>.
2. Go to <CE-EMS BE HOME>/bin/developertools.
3. Execute the DeploymentWizard by the following command:
Ø sh DeploymentWizard.sh
Page 11
HFR, Inc.
Page 12
HFR, Inc.
Page 13
HFR, Inc.
9. Click “Next”.
Page 14
HFR, Inc.
Page 15
HFR, Inc.
#!/bin/sh
#$Id: compileJSP.sh,v 1.5 2007/06/20 12:13:17 venkatramanan Exp $
# This script is used to generate classes for jsp files.
if [ $# -ne 0 ]
then
echo "Error: Run the script without any option"
echo "Usage ComplileJSP.sh"
exit 1
fi
cd ..
. ./setEnv.sh
JDK_HOME=/usr/java/jdk1.7.0_71
export JDK_HOME
JAVA_HOME=$JDK_HOME
export JAVA_HOME
if [ ! -f $JDK_HOME/bin/javac -o -z "$JDK_HOME" ]
then
echo "error: javac not found. Please configure JDK_HOME environment variable in $0 file."
exit 1
fi
Page 16
HFR, Inc.
The Command or Console mode is an Interactive and Non-GUI based installation mode. The user
can install CE-EMS through the command prompt.
1. Edit the DB_CLASSPATH variable (which is by default set to postgresql driver) in setEnv.sh file
under <CE-EMS Home> directory to set the JDBC Driver for Oracle. Set the JDBC Driver path to
ojdbc7.jar.
Below box is “setEnv.sh” file. And you need to add red items.
...
SNMP_CLASSPATH=$NMS_CLASSES/AdventNetSnmp.jar:$NMS_CLASSES/SNMPDebugger.jar
EXAMPLE_CLASSES=$NMS_HOME/examples/classes
SAS_CLASSPATH=$NMS_CLASSES/AdventNetSAS.jar
#XML_CLASSPATH=$NMS_CLASSES/jaxp.jar:$NMS_CLASSES/xalan.jar
PGSQL_HOME=$NMS_HOME/pgsql
DB_CLASSPATH=$PGSQL_HOME/driver/postgresql_jdbc4.jar:$NMS_CLASSES/p6spy.jar:$NMS_HOME/c
onf:$NMS_CLASSES/log4j.jar:$NMS_CLASSES/ojdbc7.jar
…
2. If the CE-EMS Server is already started, then do a proper and normal shutdown of Oracle. Do
not terminate the process abruptly.
3. Un-comment the following lines and comment out the PostgreSQL database configuration lines
in the hibernate.cfg.xml file.
Page 17
HFR, Inc.
Page 18
HFR, Inc.
Page 19
HFR, Inc.
B. Click “Next”
C. Next screen lists the usernames for whom the license file is authorized.
D. Select the username with which you want to register this installation copy.
E. Click “Finish”
8. Steps for Evaluation User
A. Click “Finish”
Page 20
HFR, Inc.
9. Now, the CE-EMS server will be started automatically on the specified port.
Page 21
HFR, Inc.
4. Click “Next”
5. The License Agreement screen is displayed. Select "I accept the License Agreement" to proceed
further installation process.
6. Click “Next”
7. Select “English” language of HFR CE-EMS.
Page 22
HFR, Inc.
8. Click “Next”
9. In the next screen, select “Advanced” to install all the components including Back-End,
Standalone Front-End and Distributed Poller.
12. Screen to specify the destination directory to install “Front-End Server” is displayed.
13. Click “Next” to install “Front-End Server” to the specified destination in, or click “Browse” to
install to a different location.
14. The installation details like “Installation Directory” and “Product size” are displayed in next
screen.
15. Click “Next” to start installation process or “Back” if there are any changes in the destination
location.
Page 24
HFR, Inc.
Page 25
HFR, Inc.
12. After installing CE-EMS, copy the patch file (.nar file) at <CE-EMS FE HOME>.
13. Go to <CE-EMS FE HOME>/bin/developertools.
14. Execute the DeploymentWizard by the following command:
Ø sh DeploymentWizard.sh
Page 26
HFR, Inc.
Page 27
HFR, Inc.
Page 28
HFR, Inc.
19. Click “Browse” and select new patch file in <CE-EMS FE HOME>.
And Click “OK”
Page 29
HFR, Inc.
Page 30
HFR, Inc.
#!/bin/sh
#$Id: compileJSP.sh,v 1.5 2007/06/20 12:13:17 venkatramanan Exp $
# This script is used to generate classes for jsp files.
if [ $# -ne 0 ]
then
echo "Error: Run the script without any option"
echo "Usage ComplileJSP.sh"
exit 1
fi
cd ..
. ./setEnv.sh
JDK_HOME=/usr/java/jdk1.7.0_71
export JDK_HOME
JAVA_HOME=$JDK_HOME
export JAVA_HOME
if [ ! -f $JDK_HOME/bin/javac -o -z "$JDK_HOME" ]
then
echo "error: javac not found. Please configure JDK_HOME environment variable in $0 file."
exit 1
fi
Page 31
HFR, Inc.
The Command or Console mode is an Interactive and Non-GUI based installation mode. The user
can install CE-EMS through the command prompt.
The following procedure explains two setups. The first setup where the back-end server and front-end
server are on different machines and the second the back-end server and front-end server are on the
same machine.
Assume the Back-End is running on a machine with DNS name "MachineBE". Install the Standalone
Front-End on the machine with DNS name "MachineFE".
By default, only the files required for Standalone Front-End Server installation, are
present in the “<CE-EMS FE Home>/conf “directory in "MachineFE". All the other
configuration files required for connecting to the database and other operations are
downloaded from "MachineBE" on the Standalone Front-End startup
Page 32
HFR, Inc.
Assume the Back-End is present in the same machine "MachineBE". The Front-End present in the
combo download does not require any changes for the BE_HOST and BE_PORT parameters. By
default, these parameters are set to "localhost" and "9090" respectively. In case the Front-End
server needs to be invoked as a separate process on the same machine as the Back-End server,
then some port values have to be changed in order to avoid clash of usage of ports.
If you want to run the front-end server as a separate process in the same machine where the back-
end server is running, the following ports have to be changed in <CE-EMS FE Home>/setEnv.sh.
• WEBSERVER_PORT : Change the port from 9090 to 9095(say)
• WEBCONTAINER_PORT : Change the port from 8009 to 8010(say)
• TOMCAT_SHUTDOWNPORT : Change the port from 8005 to 8006(say)
If you want to use any database other than PostgreSQL, the default database bundled with CE-EMS,
change the DB_CLASSPATH parameter in <CE-EMS FE HOME>/setEnv.sh present in "MachineFE" in
case of the standalone FE Server or the <CE-EMS FE Home>/setEnv.sh present in "MachineBE" in case
of the FE bundled with the BE.
1. Edit the DB_CLASSPATH variable (which is by default set to postgresql driver) in setEnv.sh file
under <CE-EMS FE Home> directory to set the JDBC Driver for Oracle. Set the JDBC Driver
path to ojdbc7.jar.
Below box is “setEnv.sh” file. And you need to add red items.
...
SNMP_CLASSPATH=$NMS_CLASSES/AdventNetSnmp.jar:$NMS_CLASSES/SNMPDebugger.jar
EXAMPLE_CLASSES=$NMS_HOME/examples/classes
SAS_CLASSPATH=$NMS_CLASSES/AdventNetSAS.jar
#XML_CLASSPATH=$NMS_CLASSES/jaxp.jar:$NMS_CLASSES/xalan.jar
PGSQL_HOME=$NMS_HOME/pgsql
DB_CLASSPATH=$PGSQL_HOME/driver/postgresql_jdbc4.jar:$NMS_CLASSES/p6spy.jar:$NMS_HOME/c
onf:$NMS_CLASSES/log4j.jar:$NMS_CLASSES/ojdbc7.jar
…
2. Un-comment the following lines and comment out the PostgreSQL database configuration lines in
the hibernate.cfg.xml file.
Page 33
HFR, Inc.
Page 34
HFR, Inc.
4. Click “Next”
5. The License Agreement screen is displayed. Select "I accept the License Agreement" to proceed
further installation process.
6. Click “Next”
7. Select “English” language of HFR CE-EMS.
Page 35
HFR, Inc.
8. Click “Next”
9. In the next screen, select “Advanced” to install all the components including Back-End,
Standalone Front-End and Distributed Poller.
12. Screen to specify the destination directory to install “Poller Server” is displayed.
13. Click “Next” to install “Poller Server” to the specified destination in, or click “Browse” to install
to a different location.
14. The installation details like “Installation Directory” and “Product size” are displayed in next
screen.
15. Click “Next” to start installation process or “Back” if there are any changes in the destination
location.
Page 37
HFR, Inc.
Page 38
HFR, Inc.
The Command or Console mode is an Interactive and Non-GUI based installation mode. The user
can install CE-EMS through the command prompt.
If you want to use any database other than PostgreSQL, the default database bundled with CE-
EMS, change the DB_CLASSPATH parameter in <CE-EMS Poller HOME>/setEnv.sh
1. Edit the DB_CLASSPATH variable (which is by default set to postgresql driver) in setEnv.sh file
under <CE-EMS Poller Home> directory to set the JDBC Driver for Oracle. Set the JDBC Driver
path to ojdbc7.jar.
Page 39
HFR, Inc.
Below box is “setEnv.sh” file. And you need to add red items.
...
SNMP_CLASSPATH=$NMS_CLASSES/AdventNetSnmp.jar:$NMS_CLASSES/SNMPDebugger.jar
EXAMPLE_CLASSES=$NMS_HOME/examples/classes
SAS_CLASSPATH=$NMS_CLASSES/AdventNetSAS.jar
#XML_CLASSPATH=$NMS_CLASSES/jaxp.jar:$NMS_CLASSES/xalan.jar
PGSQL_HOME=$NMS_HOME/pgsql
DB_CLASSPATH=$PGSQL_HOME/driver/postgresql_jdbc4.jar:$NMS_CLASSES/p6spy.jar:$NMS_HOME/c
onf:$NMS_CLASSES/log4j.jar:$NMS_CLASSES/ojdbc7.jar
…
2. Copy the DatabaseSchema.conf from <CE-EMS Poller Home>/conf/Oracle directory to <CE-
EMS Poller Home>/conf/ directory
3. Un-comment the following lines and comment out the PostgreSQL database configuration lines in
the hibernate.cfg.xml file.
Page 40
HFR, Inc.
4. Discovery
• Discovery Parmeter
• Discovery Criteria
• Re-Discovery Scheduler
• Network Configuration
• Node Configuration
• Refresh Node
Discovery Parameter
Discovery Configuration is about configuring the process of discovery based on entries in the seed.file
located in the <CE-EMS Home>/conf directory. Following configurations can be performed with ease
from the Runtime Administration page of Web Client.
• auto discovery of nodes and networks
2. Click Complete View > Discovery > Discovery Parameter node on the left-side tree of the
displayed page.
3. Alternatively, click Discovery Parameter link in the Discovery section on the right-side of the
client screen.
4. The Discovery Configuration Settings page is displayed. Each of the fields in this page is tabulated
below:
Field Description
Options, such as auto discovery, discovering local networks, enabling log
message generation, and rediscovering elements can be configured
Common
through the displayed page. For information on each of these options,
Parameters
refer to the General Configuration section in the Using Discovery
Configurator topic.
SNMP This section provides options to configure the discovery of SNMP devices.
Properties For information on each of these options, refer to the Protocol
Page 41
HFR, Inc.
ICMP Discovery: Select the check box to enable ICMP ping and un-
select to disable.
Ping Timeout: Specify the duration (in seconds) until when a device is in
the pinged state.
System Ping
Ping Retries: Specify the number of times a device is to be pinged.
Native Ping Timeout: Specify the duration (in seconds) for Native ping
until when a device is in the pinged state.
5. Click Submit button, if you want the configured values to take effect. Click Cancel button, to
cancel the configuration operation.
Discovery Criteria
You can configure the criteria based on which a device or network is to be discovered, at runtime.
2. Click Complete View > Discovery > Discovery Criteria node on the left-side tree of the
displayed page.
3. Alternatively, click Discovery Criteria link in the Discovery section on the right-side of the
client screen.
5. Select the Allow Criteria if you want the discovery to happen based on a criteria. Un-checking
the box will prevent the device or network from being discovered based on the set criteria.
6. Choose the criteria from the drop-down box and specify the corresponding value in the text field.
7. Click Add to add the value specified for the chosen criteria. The added value is listed in a tabular
format.
8. Click Modify if you want to modify the existing value of a chosen criteria. Click Delete to delete
the criteria.
For more information, refer to Criteria Based Discovery section in Using Discovery Configurator topic.
Page 42
HFR, Inc.
Re-Discovery Scheduler
You can configure the criteria based on which a device or network is to be discovered, at runtime.
2. Click Complete View > Discovery > Re-Discovery Scheduler node on the left-side tree of the
displayed page.
3. Alternatively, click Re-Discovery Scheduler link in the Discovery section on the right-side of the
client screen.
4. The Re-Discovery Scheduler page is displayed. Each of the fields in this page is tabulated below:
Field Description
Rediscovery To schedule the discovery of devices, click this option. The
Scheduler Rediscovery Scheduler is displayed.
5. Click Submit button, if you want the configured values to take effect. Click Cancel button, to
cancel the configuration operation.
Network Configuration
Networks and their elements are discovered automatically by CE-EMS and the discovery process is
carried out in a predetermined way. If you need to discover a network or node manually instead of
waiting for CE-EMS to discover it automatically, use the Add New Network and Add New Node
options.
2. Click Complete View > Discovery > Network Configurator node on the left-side tree of
the displayed page.
3. Alternatively, click Network Configurator link in the Discovery section on the right-side of
the client screen.
5. If you want to add a complete network, select Add Entire Network radio button. Enter a
valid IP Address in Network Address field and select the netmask (by default 255.255.255.0)
from Netmask combo box.
6. If you want to add a set nodes within a range of IP addresses, select Add Range of Nodes
radio button. Enter a valid staring IP Address of the range in Start IP Address field, enter a
valid ending IP Address of the range in End IP Address field and select the netmask (by
default 255.255.255.0) from Netmask combo box.
Page 43
HFR, Inc.
7. The Discovery Configuration options provided are optional. The significance of each of the
fields is given below.
Field Significance
Not to Discover
If this option is checked, the added network will not be discovered by
the above
CE-EMS.
Network
If this option is selected, the discovery of the network added starts
instantly.
Start Discovery
If the option is not selected, then the network is just added to the
database but discovery of that network is not performed.
If this option is selected, the network is added to the database and
discovery happens. The network and its elements are in managed state
Manage the as they are discovered.
Network If this option is not selected, the network is added in unmanaged state
to the database and discovery of that network will not be started.
Hence none of the network elements in the network will be discovered.
Initially some configurations are made related to discovery in the
Override the
seed.file using Discovery Configurator tool. A configuration could have
discovery
been made to restrict the discovery of certain IPs. But if you select this
configuration
option, those configurations are overridden and discovery is performed.
If you want this network to be discovered the next time CE-EMS Server
is started (after reinitializing), select this option. On doing so, the IP
Update the
that you mention is configured in the seed.file (discovery configuration
discovery
file present in <Web NMS Home/conf directory>) permanently. This
configuration
field is enabled for both Add Entire Network and Add Range of
Nodes options.
Is the nodes of If this option is selected, the discovery of the set of nodes, which are
the Network DHCP enabled, happens. This field is enabled for Add Range of Nodes
DHCP option and disabled for Add Entire Network option.
8. Once the Submit button is clicked, CE-EMS takes a while to discover the network. If you do not
want to wait for the discovery to be completed and want to proceed with other operations,
select Process in the background check box. By doing so, you can quit the current view and
work on other views while the discovery process is done in the background.
9. Click Submit button, if you want to discover the added network. Click Reset button, to reset
the adding network operation.
If the network IP that you have entered has already been added to the database and discovered by
CE-EMS, relevant message is displayed in the Network Configurator page.
Node Configuration
Page 44
HFR, Inc.
2. Click Complete View > Discovery > Node Configurator node on the left-side tree of the
displayed page.
3. Alternatively, click Node Configurator link in the Discovery section on the right-side of the
client screen.
5. Enter a valid IP Address in IP Address field and select the netmask (by default, 255.255.255.0)
from Netmask combo box.
6. The significance of each of the fields under SNMP Configuration and Discovery
Configuration is given below.
Field Significance
SNMP Configuration
Port number where the SNMP agent is running. By default, the
SNMP Port
port is 161.
By default, the value is public. When no value is set, then the
Community community value as configured in the seed.file is fetched and
substituted.
Enable V3 (User If you enable the discovery of SNMPv3 devices, then you need to
Name, Context specify the user name and context name in the corresponding
Name) field.
Discovery Configuration
Not to discover the If this option is checked, the added node will not be discovered by
above node CE-EMS.
Discover even if the
If this option is checked, even if the node is not alive when you
node is not
add it, CE-EMS adds a managed element for that node.
reachable
If this option is selected, apart from adding the node that you
have configured, all other devices in their parent network are also
Discover all the
discovered (if they were not discovered already).
devices in the
For example, if you add a device 192.168.1.5 with this option
parent network
checked, then all the devices in the 192.168.1.0 network are also
discovered.
Initially some configurations are made related to discovery in the
seed.file using Discovery Configurator tool. A configuration could
Override discovery
have been made to restrict the discovery of certain nodes. But if
configuration
you select this option, those configurations are overridden and
discovery is performed for those nodes also.
If you want this node to be discovered the next time the CE-EMS
Server is started (after reinitializing), select this option. On doing
Update discovery
so, the node that you mention is configured in the seed.file
configuration
(discovery configuration file present in <Web NMS Home>/conf
directory) permanently.
7. Once the Submit button is clicked, CE-EMS takes a while to discover the node. If you do not
want to wait for the discovery to be completed and want to proceed with other operations, select
Process in the background check box. By doing so, you can quit the current view and work on
other views while the discovery process is done in the background.
Page 45
HFR, Inc.
8. Click Submit button, if you want to discover the added node. Click Reset button, to reset the
adding node operation.
If the node IP that you have entered has already been added to the database and discovered by CE-
EMS, relevant message is displayed in the Node Configurator page.
Refresh Node
To rediscover a node in the network, use the Refresh Node option. A node or device could have been
down for a while or it would not have been discovered when you performed a manual discovery of that
node. In these cases, refresh the node manually to obtain its latest information.
To refresh a node
1. Click Admin module tab. The Admin page is displayed.
2. Click Complete View > Discovery > Refresh Node node on the left-side tree of the
displayed page.
3. Alternatively, click Refresh Node link in the Discovery section on the right-side of the client
screen.
5. Enter the name or IP address of the node to be refreshed in the Name of the Node field.
6. Select the netmask (by default, 255.255.255.0) from Netmask combo box.
7. Enter the port (by default, 161) where SNMP agent is running in SNMP Port field.
8. If you select the SNMP version as V3 in the combo box to enable the re-discovery of SNMPv3
devices, you need to specify the user name and context name in the corresponding field.
9. Click Refresh, if you want to re-discover the specified node. Click Reset button, to reset the
re-discovering the specified node operation.
Page 46
HFR, Inc.
5. Security Administration
• User Configuration
• Add User
• Add Multiple
• Change Status
• Delete
• Group Configuration
• Add Group
• Delete
• Modify Group
User Configuration
displayed.
5.1.4. Delete
To remove a user
1. Click Admin module tab. The Admin page is displayed.
2. Click Complete View > Security Administration > User Configuration node on the left-
side tree of the displayed page.
Page 48
HFR, Inc.
3. Alternatively, click the User Configuration link in the Security Administration section on the
right-side of the client screen.
4. The User Configuration page is displayed.
5. Select a user, by checking the check box of the user row.
6. Click Delete button.
7. Select Change Password button of User Information if you need to change that user's
password.
8. Enter the new password and re-enter the same password in New password and Re-type
password fields respectively.
9. The Modify password expiration field displays the number of days the password stays valid.
If this was not configured while creating the user, then 0 is displayed, which means the
password never expires. Modify the expiration period, if required, by selecting the check box
and entering a new value in the text field.
10. The Modify account expiration field displays the number of days the user account stays valid.
If this was not configured while creating the user, then 0 is displayed, which means the user
account never expires. Modify the expiration period, if required, by selecting the check box and
entering a new value in the text field.
11. On editing the required fields, click Submit. Click Cancel button, to cancel the user profile
modification.
12. Under Associated Groups section, the Group name section lists the group(s) in which the
user has already been enrolled. To add or delete new group(s), click Configure Group
button. Modify profile window for configuring the users pops-up. The Available groups field
lists the existing groups that the user has not been enrolled. Use the Remove and Add
options to remove the user from a group or enroll the user to a group. Press Ctrl key to
select multiple groups. Click Submit. Click Reset button, to reset the add/delete group
operation. Click Close button, to close the Modify profile pop-up window.
13. Under Permitted Operations section, the Name column lists the operations for which the
user is permitted and the Type column lists the type of permission for the corresponding
operation. To add or delete new operations and modify the permissions, click Configure
Operations button. Operations Tree window for configuring the users pops-up. The
Operation Tree Root lists all the existing operations that the user can be permitted. This
includes the operations inherited from the Group to which the user belongs. Use the Check box
options to include, exclude, and not authorize the operations for the user. Click Save. Click
Cancel button, to cancel the configuration.
Page 49
HFR, Inc.
Hints
• - Operation is authorized for the Group/User
Group Configuration
Hints
• - Operation is authorized for the Group/User
Page 50
HFR, Inc.
5.2.2. Delete
To remove a group
1. Click Admin module tab. The Admin page is displayed.
2. Click Complete View > Security Administration > Group Configuration node on the left-
side tree of the displayed page.
3. Alternatively, click the Group Configuration link in the Security Administration section on
the right-side of the client screen.
4. The Group Configuration page is displayed.
5. Select a group, by checking the check box of the group row.
6. Click Delete button.
To add or delete new user(s), click Assign Users button. Modify profile window
for configuring the users pops-up. The Available Users field lists the existing users
who have not been enrolled. Use the Remove and Add options to remove
the user from the group or enroll the user to the group. Press Ctrl key to select
multiple users. Click Submit. Click Reset button, to reset the add/delete users
operation. Click Close button, to close the Modify profile pop-up window.
8. Under Operations Settings section, the Name column lists the operations for which
the group is permitted, the Type column lists the type of permission for the
corresponding operation and the Scope Setting column lists whether any custom view
scope is set for this operation. To add or delete new operations and modify the
Hints
• - Operation is authorized for the Group/User
Page 51
HFR, Inc.
9. Under Custom View Scope section, the Authorized Scopes column lists the custom
view scopes authorized for this group.
o To add new custom view scopes, select Scope Name (module) from the combo
box and click Add New Scope button. Custom View Scope - Modify
page is displayed. Enter the name for the new custom view scope in Scope
Name field. In the Property Name combo box, select the required property
and enter the required value in the Property Value in the text field. Click Add
New button to add more properties and Delete icon against the properties to
remove them. Click Save. Click Cancel button, to cancel the configuration.
o To add or delete new custom view scope(s), click Assign Scope button.
Modify profile window for configuring the users pops-up. The Available
Scope field lists the existing scopes which have not been enrolled. Use the
Remove and Add options to remove the scopes from the group or
enroll the scopes to the group. Press Ctrl key to select multiple scopes. Click
Submit. Click Close button, to close the Modify profile pop-up window.
o To delete a custom view scope, select the scope(s), by checking the check box
of the scope row. Click Delete button.
o To modify custom view scopes, click on the Scope Name. Custom View Scope
- Modify page is displayed. Edit the name of the custom view scope in Scope
Name field. In the Property Name combo box, select the required property
and enter the required value in the Property Value in the text field. Click
More button to add more properties and Delete icon against the properties
to remove them. Click Save. Click Cancel button, to cancel the configuration.
Operation Configuration
Hints
• icon can be used for adding new operation
Page 52
HFR, Inc.
6. Monitor/Management
• WebNMS Details
• JVM Management
• Performance Status
WebNMS Details
Using the Web Client, you can view the details of the CE-EMS Server, such as information on fault
status, ports in use, discovery status and scheduler details. These details help you in ascertaining the
performance of the CE-EMS Server and thereby administer it appropriately. For example, to ascertain if
there are any threading issues, you can view the details of the schedulers.
2. Click the Complete View > Monitor/Management > WebNMS Details node on the left-side
tree of the client screen.
3. Alternatively, click WebNMS Details link in the Monitor/Management section on the right-
side of the client screen.
Information on the Events and Alerts in the queue that are to sent, traps that are yet to be processed, and the
time at which the last trap was received, is displayed.
Page 53
HFR, Inc.
Information on the ports that are currently occupied by CE-EMS is displayed. An example screen shot
is given below.
Information on the Discovery module that are currently registered by CE-EMS is displayed. An detail information
and example screen shot is given below.
Page 54
HFR, Inc.
JVM Management
Using the Web Client, you can view the details of the CE-EMS Server, such as information on back end
(BE) and front end (FE) servers, and the Clients. These details help you in ascertaining the
performance of the JVM of CE-EMS Server and thereby administer it appropriately
2. Click the Complete View > Monitor/Management > JVM Management node on the left-
side tree of the client screen.
3. Alternatively, click JVM Management link in the Monitor/Management section on the right-
side of the client screen.
Page 55
HFR, Inc.
4. Select the graphical display as either Line Graph or Area Graph by clicking the respective link.
5. Select the period of graphical data collected from the Select Period drop down list (Last 1 day,
Last Week and Last Month).
6. Click the Export JVM Details link of “Action” to export the JVM details from Web Client. The
JVMDetails.txt and JVMthreadDump.txt files are created and stored in <HFR CE-EMS FE
Home>/nmsanalyzer directory.
The following message appears on top of the page:
7. Click Report to WebNMS link of “Action” to upload the logs and other related CE-EMS files
from Web Client to AdvenNet.
The following message appears on top of the page:
Enter your Email address, Subject, and Message in the File Upload Form. Click Send
button to send the Email with CE-EMS server details in zip.gz format for debugging. The
debug<DD_MM_YYYY_HH_MM_SS>.zip.gz file is created and stored in <Web NMS
Home>/ directory.
Page 56
HFR, Inc.
The information on the machine where the Web NMS BE server is running is displayed. The
information, such as Host Name, Host Address, Server Started At, OS Name, Database Name,
Total Memory, and Free Memory is displayed. An example screen shot is given above.
CE-EMS JVM Monitoring collects, stores, and display the following System and Server
parameters as graphs by default:
For JVMs BE server
• CPU Utilization
• Memory Usage
• Number of threads spawned
• Data Collection Rate
• Status Polling Rate
• Trap Processing Rate
• Event Processing Rate
• Alert Processing Rate
A list of FE servers that are connected to the BE is displayed. It provides information on the
Host Name (where FE server is running), Host Address (IP address of the machine where FE
server is running), Server Mode (Primary or Secondary), Client Communication Mode, RMI
Registry Port, and Web Server Port.
CE-EMS JVM Monitoring collects, stores, and display the following System and Server
parameters as graphs by default:
For JVMs FE server(s)
• CPU Utilization
• Memory Usage
• Number of threads spawned
Page 57
HFR, Inc.
Client Host The Client host name that is connected to the BE.
The type of client connected to the BE. It includes
Client Type
Application, Applet, and Web Start Clients.
Client ID The Client's ID using which the client is being accessed.
Memory
The memory used by the client application.
Usage(%)
Option to terminate the client remotely in case of abnormal
Terminate
usage of resources.
CE-EMS JVM Monitoring collects, stores, and display the following System and Server
parameters as graphs by default:
For JVMs Client(s)
• CPU Utilization
• Memory Usage
• Number of threads spawned
Using the Web Client, you can view the details of CE-EMS module Performance. This helps you
in ascertaining the functioning of the module.
2. Click the Complete View > Monitor/Management > Performance Status node on the left-
side tree of the client screen.
4. Specify the node name for which you need to view performance statistics in Node Name field.
From this page, if you need to view performance statistics for any other node,
2. From Period drop-down box, choose the period for which you need to view performance
statistics. It includes Today, Last Week, Last Month, and Custom.
If Custom is selected in Period drop-down box, specify the Start Date and End Date, the
range between which you need to view the performance statistics.
Page 59
HFR, Inc.
7. Administrative Operations
• Shutdown Server
• Configuring MTEAP
2. Click the Complete View > Administrative Operations > Mail Server Settings node on the
left-side tree of the client screen.
3. Alternatively, click Mail Server Settings link in the Administrative Operations section on
the right-side of the client screen.
4. The Mail Server Settings page is displayed. This Screen contains the information regarding
Server Name, Server Port, User name, Password and Mail ID.
WebNMS Backup
To backup CE-EMS Database
1. Click the Admin module tab. The Admin page is displayed.
2. Click the Complete View or Admin Operations node on the left-side tree of the
displayed page.
4. A confirmation is asked. Click Yes. A backup of the available data is taken and stored in
files under the <HFR CE-EMS Home>/conf/backup directory.
2. Click the Complete View > Administrative Operations > Shutdown Server node on the
left-side tree of the client screen.
Page 60
HFR, Inc.
3. Alternatively, click Shutdown Server link in the Administrative Operations section on the
right-side of the client screen.
Page 61
HFR, Inc.
• MIB Browser
• Logs Monitor
• Audit Trails
2. Click the Complete View > Tools and Browsers > MIB Browser node on the left-side tree
of the client screen.
3. Alternatively, click MIB Browser link in the Tools and Browsers section on the right-side of
the client screen.
4. The MIB Browser page will get displayed on the right side of the screen.
2. Click the Complete View > Tools and Browsers > Logs Monitor node on the left-side tree
of the client screen.
3. Alternatively, click Logs Monitor link in the Tools and Browsers section on the right-side of
the client screen.
5. Select the latest updated lines and select a log file to view its details. Select the latest updated
lines from the Show Last __ lines of drop down list and the server log file listed in the drop
down list. Click View Logs button.
Page 62
HFR, Inc.
2. Click the Complete View > Tools and Browsers > Audit Trails node on the left-side tree of
the client screen.
3. Alternatively, click Audit Trails link in the Tools and Browsers section on the right-side of the
client screen.
5. Select the number of lines to be displayed from the Page Length drop down list and use the
First, Previous, Next and Last buttons to navigate through the audit pages.
7. Use Search button of “Actions” to search the audit entries based on the fields of the audit
entries. Select one of the options: Match any of the following, Match all of the following. Select
the field to be matched from the drop down list. Select the matching condition from the drop
down list. Enter the value of the field to matched. Click Search button.
Page 63
HFR, Inc.
9. Appendix A.
Page 64