Alcatel NMS MP:Installation Instructions

From GEANT2-JRA1 Wiki

Contents

1 In this release
- 1.1 Overview
- 1.2 Specifics
2 Installing the Java version of Alcatel NMS Measurement Point Service

In this release

This document is included within the distribution in .txt format (/doc/install-notes directory)

Overview

The Measurement Point Service for Alcatel NMS provides a Web Service interface to some of the data available via the IOO interface on Alcatel NMS. It requires the installation of Open Source Apache Axis (www.apache.org/axis/) as well as an application server such as Tomcat. Standard installation of this software involves automatic download and installation of Tomcat and Axis. Its main configuration file is in XML format and it needs to be stored inside an xml database which can support XPath queries. Currently perfSONAR framework supports only eXist (http://exist.sourceforge.net/) and hence this NMS Measurement Point needs the installation of eXist XML database.

Currently, the software is in its beta1 state (public trial).

Specifics

The current release supports the following functionality
- Retrieval of keys and capability information. Keys are useful to retrieve data efficiently
- Retrieve of data for SES, ES, UAS, BBE. Sample requests and responses are available within the distribution (/schema/example-instances/nmsTypeMP directory)
- Capability to test many individual components and also the installed Web Service with the help of ant scripts (/ant/nmsmp/nmsTypeMP-test-targets.xml)

The current release does not support the following functionality
- Specification of time interval. The Default start time is current time - 2hrs and Default end time is current time - 2hrs 15 mins
  - The assumed default time is reported back in the response
- No authentication or resource protection mechanisms

Please be aware that
- You need to have the Alcatel NMS and IOO interface to be able to retrieve data via this service
- You need to have an a/c on the IOO interface system which should be configured into the service properties
- You can however test the key part or use the sources as reference for other implementations
- Sometimes the NMS might not provide data. This is normal as NMS has other greater priorities than to make data available for retrieval via its IOO interface
- You should expect to see exceptions when the NMS cannot return data or if there are errors in request.
- Thrown exceptions are usually fairly helpful. Fault codes will be used in future

Installing the Java version of Alcatel NMS Measurement Point Service

These instructions are also available in format for offline reading. They are included in the distribution in .txt format as well (/doc/install-notes directory).

Step 1. Installing Software Dependencies

Instructions below will help you to download and install required additional software in order to install and run the perfSONAR Measurement Point Software.

Step 1.1 - Installing Java Development Kit (JDK) 2 Platform

We recommend version 1.5 which has been tested. Current code will not compile on version 1.4.
In your server choose a directory and download and extract Java 2 Platform from http://java.sun.com/j2se/1.5.0/download.jsp

Step 1.2 - Installing Apache Ant

Apache Ant is a Java-based build tool. You will need it to proceed with other steps which are using Ant scripts.
Download Ant from http://ant.apache.org/bindownload.cgi and install.

Step 1.3 - Installing Tomcat and Axis

perfSONAR Web Service requires an Application Server (Jakarta Tomcat)and a SOAP implementation (Apache Axis) to be installed on the system. There are two ways to install these packages. If you already have Tomcat and Axis installed, please read the following section to see if you need to install another instance of Tomcat and Axis. Later sections provide more information about the available options to install Tomcat and Apache Axis.

If you already have Jakarta Tomcat and Apache Axis Installed
If you have Jakarta Tomcat and Apache Axis already installed and used for other perfSONAR services, you will unfortunately need to install and run another instance of Jakarta Tomcat and Axis. We are working on removing this constraint for our future releases.

A second instance of tomcat will require some changes to Tomcat's configuration file to make sure that it listens to different ports for incoming requests and for shutdown requests. The section below on Changing Jakarta Tomcat's port numbers should help you in this task.

Changing Jakarta Tomcat's port numbers

Please click here to read about changing Tomcat's port numbers while installing a perfSONAR service.

If your existing Tomcat and Axis is for "non-perfSONAR" purposes
Please continue with step 1.4. $PERFSONAR_TOMCAT in the following sections should be seen as the complete path to your tomcat installation (i.e. the directory which contains the bin, log, conf, etc directories of tomcat. Example: /home/loukik/jakarta-tomcat-5.0.28)

Install Tomcat and Axis manually
Download and install Jakarta Tomcat from <a href="http://tomcat.apache.org/">here</a>. perfSONAR services should work fine with version 4.1 and 5.x. If you are using the latest version of tomcat, make sure you choose a stable release (example: 5.0.28) and not beta releases. Once installed you can verify the installation by following instructions provided in section 5 - Post Installation checks below.

Once Tomcat is installed, download and install Apache Axis from <a href="http://ws.apache.org/axis/java/releases.html">here</a>. perfSONAR Services should work fine with version 1.2. Make sure you chose a final release (and not beta). Installing Axis is very easy. Once you have downloaded the axis tar file, unzip and untar the file. Inside the untarred axis directory (/axis-1.2 for example), you will find the webapps/axis directory. Copy this axis directory to $PERFSONAR_TOMCAT/webapps directory. Thats it!!! Axis might need some additional JARs to be placed in its directory but this is not a big task and perfSONAR should help you take care of it. You can validate the installation by following instructions in section 5 - Post Installation Checks below.

Install Tomcat and Axis using perfSONAR scripts
To ease the installation procedure, perfSONAR provides an easier way to install Jakarta Tomcat and Apache Axis. In order to make use of these scripts, continue with the next steps below and when you get to step 2.3 please make sure you go through it.

Step 1.4 - Installing XML Database

NMS Measurement Point Service requires eXist XML Database to work. Following instructions should help you install eXist. If you already have eXist installed, go to step 1.4.5 to create a new group and a new user. More than one service can use the same eXist XML Database to store xml files. They only need some configuration (which is explained later)

  1.4.1 Download the application from http://exist.sourceforge.net/

  1.4.2 Install the database

           java -jar eXist-{version}.jar

       It will run GUI installer. Select the path for installation 
       (for example $EXIST_HOME=/usr/local/exist).

  1.4.3 In order to change eXist database server port, edit $EXIST_HOME/bin/startup.sh
       and change OPTIONS line:


           OPTIONS="-Dexist.home=$EXIST_HOME"

           to

           OPTIONS="-Dexist.home=$EXIST_HOME -Djetty.port=8680"

           (8680 port is only an example)
 
  1.4.4 Run the database


           $EXIST_HOME/bin> startup.sh
 

  1.4.5 Run client tool to create a database group and database user (screenshot)

           $EXIST_HOME/bin> client.sh
       
       You will need to provide the correct hostname, port number and password for admin in order to login to the database
 
       After login, use the Menu of this client: Tools->Edit users  (screenshot)

       In the Groups section there is an icon to create a new Group which will prompt for the group name. 
       
       Enter the group name as nmsTypeMPConfig

       Examples of fields required to create a new user:

           Username: nmsTypeMP
           Password: password
           Assigned group: NMSTypeMPConfig

        (Presented password is only an example and should be changed for security reasons!)

Step 2 - Getting perfSONAR software

You can download a tar file containing the last get sources from CVS (step #2.1) or download a snapshot tar file (step #2.2). Step 2.3 will help you in automatically downloading and installing tomcat and axis distributions with the help of perfSONAR Scripts as mentioned in Step 1.

Step 2.1 - Snapshot

Step 2.1.1 Download a snapshot tar file from download page
- Download either the sources or binaries. The sources obviously need compiling before actual service deployment
- Untar the gzip file (src or bin) by using the following command in the directory where you downloaded the tar file.

> tar -xvzf perfSONAR-NMS_MP-src-beta1.tar.gz 
                       or 
> tar -xvzf perfSONAR-NMS_MP-bin-beta1.tar.gz

From now on $PERFSONAR will refer to the path where ant directory is located.
 (For example:  /home/loukik/perfSONAR-NMS_MP-bin-beta1/sonar/perfsonar)

We suggest that you set $PERFSONAR environment variable for this. In unix (standard shell types), you can do so by using the following commands

> cd perfSONAR-NMS_MP-src-beta1/sonar/perfsonar
                      or
> cd perfSONAR-NMS_MP-bin-beta1/sonar/perfsonar

> export PERFSONAR=`pwd`

You can verify in unix by typing

> echo $PERFSONAR

Step 2.2 - CVS

Please skip this step if you have downloaded tarballs as instructed in Step 2.1
The latest version of NMS Measurement Point is available from perfSONAR CVS.
If you don't have CVS in your system then you have to install it (http://ximbiot.com/cvs/)
You can download all sources including perfSONAR code using Ant build file linked below. It will also download from the Internet and install Jakarta Tomcat and Axis
You can download perfSONAR code to any directory you choose in your server. CVS by default will create and download files into ./sonar/perfsonar. The rest of this document assumes that perfSONAR full directory name is under $PERFSONAR e.g./opt/dev/jra1-project/sonar/perfsonar. To download sources copy file Build.xml to your directory and enter:

$PERFSONAR/ant> ant -f Build.xml

To find detailed guidelines on how to download and install individual components point your browser to detailed software installation guidelines.

Step 2.3 - Install Tomcat and Axis automatically using perfSONAR Scripts

This step will help you install Tomcat and Axis with the help of perfSONAR scripts. If you have already installed Tomcat and Axis (either manually in Step 1 or it was already installed) please skip this step.
Change to the ant directory ($PERFSONAR/ant)

> cd $PERFSONAR/ant

Type the following command to install Tomcat and Axis

$PERFSONAR/ant> ant webservice-container-download

The above command will download and install tomcat and axis onto the server and into the directory two levels before the $PERFSONAR directory (i.e. just under the directory into which you untarred the distribution). You will be prompted to provide alternative URLs from where Tomcat and Axis can be downloaded. If you don't have any alternative URL to provide, simply press enter for the prompts. Ant will then use the default URLs configured by us.

From now on, $PERFSONAR_TOMCAT will refer to the path where tomcat is installed. (For example: /home/loukik/perfSONAR-nmsTypeMP-bin-beta1/jakarta-tomcat-5.0.28). We suggest that you set an environment variable for this as well

> cd $PERFSONAR
> cd ../../

This will take you to the perfSONAR-NMS_MP-bin-beta1 or perfSONAR-NMS_MP-src-beta1 directory.

> cd jakarta-tomcat-5.0.28
> export PERFSONAR_TOMCAT=`pwd`

You can validate the environment variable by using the following command

> echo $PERFSONAR_TOMCAT

Once installed, Tomcat will run on the default port 8080. You can change this by altering the tomcat config file (server.xml) under conf directory. See Step 1.3 for more information.

IMPORTANT!! Make sure you validate your tomcat and axis installation using instructions given in Step 6.1 and 6.2. Failure to have a valid tomcat axis installation will fail the service installation.

Step 3. Configuring the Measurement Point Service

Step 3.1 - NMS configuration file

For Measurement Point to work you need to create your own XML file describing measurement data available. This configuration file is used by NMS MP to provide capability information and also to provide keys for accessing data from Alcatel NMS.

If this is your first configuration of NMS MP service then you can use the sample NMS MP configuration file ($PERFSONAR/schema/example-instances/sonar/nmsTypeMP/nmsTypeMP-store-beta1.xml). In this case you don't have to change anything for now and can go directly to Step 3.2. Once the service is setup and tested, you can alter the configuration file to suit your needs.

To create or edit your own NMS MP configuration, you can use the sample document (link given above) as a guide and tailor this file according to your NMS keys and capabilities.

Step 3.2 - Properties files setup

It is required to manually edit two files and use ant to automatically create a third file. This process if quite easy and the files that need modification provide clear clues as to where these changes need to be made. The following steps which give the property name and an example value should help you through the process. The const.properties file is well documented and all the properties are easy to find.

3.2.1 Change directory to $PERFSONAR/ant directory

> cd $PERFSONAR/ant

set log4j properties by typing

$PERFSONAR/ant> ant set-log4j-properties

3.2.2 In the same ant directory, change the following properties in 'const.properties' file

  # set the following property value as the directory where tomcat has been installed
  tomcat.home=/home/loukik/perfSONAR-NMS_MP-bin-beta1/jakarta-tomcat-5.0.28

  # set the following property to the directory where axis has been installed
  axis.home=/home/loukik/perfSONAR-NMS_MP-bin-beta1/jakarta-tomcat-5.0.28/webapps/axis

  # set the following property to the host name of the server where the service is being installed
  target.server=mu.dante.org.uk

 # set the following property to the port number on which tomcat is listening. default is 8080
  target.port=8080

 # for the property below, you can derive the information from the above information (target.server and target.port).
    Typically http://targer.server:target.port/axis/services/AdminService
   adminService=http://mu.dante.org.uk:8090/axis/services/AdminService

 # jdk path location - java 1.5 needed. Make sure the path below is the actual path and not a symbolic link
   jdk_path=/net/dante-sw/opt/jdk1.5.0_01

3.2.3 Change to $PERFSONAR/conf directory

> cd $PERFSONAR/conf

change the following properties in 'service.properties' file

3.2.3.1 Alter the following general properties

  # IP Address of machine on which the web service has been hosted
   service.r.location=193.63.211.10

  # Web Service access point - standard installation requires hostname and port number change only
   service.r.access_point.address=http://mu.dante.org.uk:8080/axis/services/MeasurementPointService

  # location of log4j and sax parser config files- IMPORTANT!!!!!!
  # The ones below are important entries, please make sure you change them appropriately.
  # In the examples below /home/loukik/perfSONAR-NMS_MP-bin-beta1/sonar/perfsonar is $PERFSONAR directory 
  # Only these bits need to be changed. The rest can remain the same for standard installation.
  service.log.log4j.config=/home/loukik/perfSONAR-NMS_MP-bin-beta1/sonar/perfsonar/conf/log4j.properties
  service.sax_parser.config=/home/loukik/perfSONAR-NMS_MP-bin-beta1/work/sonar/perfsonar/src/objects.config

3.2.3.2 Uncomment (by removing #) the below lines

  #service.r.description=MP service capable of communicating with Alcatel NMS IOOinterface
  #service.mp.message_types=MetadataKeyRequest,SetupDataRequest
  #service.mp.class_name=org.perfsonar.service.measurementPoint.nmsType.NMSTypeMPServiceEngine
  #service.r.access_point.description=beta deployment
  #service.r.version=beta1

3.2.3.3 Alter the following Alcatel MP Specific properties

 The properites below are for the xml db configuration. 
 For standard installation, only the host name and port number will require changes

  component.mp.nms.xmldb.db_uri=xmldb:exist://mu.dante.org.uk:8094/exist/xmlrpc/db/NMSTypeMPConfiguration
  component.mp.nms.xmldb.db_username=NMSTypeMP
  component.mp.nms.xmldb.db_password=password

 The properties below are for NMS server IOO Interface configuration. The changes are specific to your NMS IOO Configuration. 

  service.mp.nms.NMS_Servers=nms1.mil.it.geant2.net,nms2.mil.it.geant2.net
  service.mp.nms.NMS_Servers_Port=3002
  service.mp.nms.NMS_Servers_IOO_Password=password

 The property below provides the link to the config file that will be put into the xml database. 
 The default value of this property contains a link to an example of such a config file. 
 which is present in the schema directory. You can leave it for test purposes but once you have built your own config. file, 
 place the complete path to your config file here. Everytime you make changes to the config file, you will also 
 need to run the ant targets to put the config file on the xml database using instructions provided in Step 4.2.1

 service.mp.nms.conf_file=schema/example-instances/sonar/nmsTypeMP/nmsTypeMP-store-beta1.xml

Step 4. Preparing the Measurement Point Service

If you have downloaded the src release or if you are using the cvs checkout, you will need to build the service first. IMPORTANT!! If you have downloaded the binaries, you should skip Step 4.1 and go to Step 4.2.

Step 4.1 - Compilation

In order to compile all sources and create jar files that you can deploy, execute the following command in the ant directory

Change to $PERFSONAR/ant directory

> cd $PERFSONAR/ant

$PERFSONAR/ant> ant build-nmsTypeMP

Step 4.2 - Applying configurations

4.2.1 Upload XML Config into XML Database

In order to upload the NMS config file into the xml database, run the following command in the $PERFSONAR/ant directory. This will initialize the xml database, remove existing NMS config file and store the new NMS config file. You have already configured the location of the xml file in service.properties in Step 6.3.3. IMPORTANT!!!: Every time the location or the content of the xml config. file changes, this step needs to be repeated.

Change to $PERFSONAR/ant directory

> cd $PERFSONAR/ant

$PERFSONAR/ant> ant xmldb-init-nmsTypeMP

4.2.2 Bootstrapping via Jakarta Tomcat

The tomcat properties need to be set to point to the perfsonar properties file. In a standard installation process, this can be achieved by running the following command in $PERFSONAR/ant directory.

Change to $PERFSONAR/ant directory

> cd $PERFSONAR/ant

$PERFSONAR/ant> ant set-tomcat-properties

During this process, ant will ask for confirmation of the location of tomcat and different configuration files. Press the Return button if the location value is correct. If it is wrong, it is possible that the information has been configured wrongly in const.properties. Please double check using step 3.2.2 above.

Step 5. Deploying the Web Service

Step 5.1 - Running Tomcat

Change to the $PERFSONAR_TOMCAT/bin directory

> cd $PERFSONAR_TOMCAT/bin

Execute the following command in order to launch Tomcat

$PERFSONAR_TOMCAT/bin> ./startup.sh

Or restart Tomcat if it has been running previously

$PERFSONAR_TOMCAT/bin> ./shutdown.sh

$PERFSONAR_TOMCAT/bin> ./startup.sh

Step 5.2 - Deploying your web service

What remains to be done is to deploy the web service in Tomcat. Execute the following command

Change to $PERFSONAR/ant directory

> cd $PERFSONAR/ant

$PERFSONAR/ant> ant deploy-nmsTypeMP

Change to the $PERFSONAR_TOMCAT/bin directory

> cd $PERFSONAR_TOMCAT/bin

Restart Tomcat (to include missing jars)

$PERFSONAR_TOMCAT/bin> ./shutdown.sh

$PERFSONAR_TOMCAT/bin> ./startup.sh

Step 6 Post-installation checks

Step 6.1 - Validate Jakarta Tomcat installation

After installing the web application and dependencies, you should make sure that the server is running the web application.
If Tomcat is not running then execute the startup file to run Tomcat:

$PERFSONAR_TOMCAT/bin> ./startup.sh

Check to see if you get a Tomcat welcome page at http://hostname:port/ The hostname is the DNS entry of the host where tomcat was installed and port is the port on which Tomcat is running.

Step 6.2 - Validate Axis installation

If standard Axis installation procedure was followed then check at http://hostname:port/axis to see if you see an Axis welcome page. Remember that Tomcat should be running.
If your are able to get welcome page, look for the Validation link. The validation page says what Axis has to say about the installation. If it says that Needed libraries are missing and you haven't reached step 5.2 yet, continue with the installation. Step 5.2 should fix the problem. If you are validating the page after finishing the installation (after step 5.2), contact support.
If welcome page is not displayed (but Tomcat has been properly installed and Tomcat welcome page ahs been shown), check in the Tomcat directory to see where Axis was installed. Check the tomcat logs in $PERFSONAR_TOMCAT/logs/catalina.out to see if there are errors. Contact support if there are errors that you think you can't fix by yourself.

Step 6.3 - Testing service installation

If the service has been installed at the following URL http://hostname:port/axis/services/MeasurementPointService, just pointing the browser to this URL should show you a page saying that a service is running at that URL and it can be invoked. This should return something like

'''MeasurementPointService'''<br> Hi there, this is an AXIS service!<br> Perhaps there will be a form for invoking the service here...

Step 7. Testing

Step 7.1 - Running sample requests

It is presumed that you have completed all steps before. Now you can check whether Measurement Point deployment has been successful.
Testing involves retrieving metadata and keys from the config file. The example config file and some ant targets should help you test the service for this functionality easily. However, you will not be able to test the service for providing measurement data. This is because you will need to modify the example config file or build your own config file. This process is explained in step 8. The current step only helps to check if you have installed the service properly.

Testing requires some changes to the ant target located in $PERFSONAR/ant/nmsmp directory. By default, the ant target looks like the example below

<target name="test-nms-service" description="Tests the given Service Installation using SOAP Messages">
        <java classname="org.perfsonar.client.testHarness.SOAPClient"
                classpathref="classpath"
                fork="true">
 
                <!-- Change the argument value below to specify the Web Service to test -->
                <arg value="http://mu.dante.org.uk:9011/axis/services/MeasurementPointService"/>
 
                <!-- Choose a request file -->
                <arg value="${basedir}/schema/example-instances/sonar/nmsTypeMP/KeyRequest-emptyMetadata.xml"/>
 
                <!--
                <arg value="${basedir}/schema/example-instances/sonar/nmsTypeMP/DataRequest-exampleMetadata-noKey.xml"/>
                <arg value="${basedir}/schema/example-instances/sonar/nmsTypeMP/KeyRequest-exampleMetadata.xml"/>
                -->
 
                <!-- Response is stored below -->
                <arg value="${basedir}/schema/example-instances/sonar/nmsTypeMP/Server-test-response.xml"/>
 
        </java>
 </target>

If you have decided to use test nms configuration file in the service then you will only have to change the service location in the ant target. In the ant target look for the argument <arg value="http://mu.dante.org.uk:9011/axis/services/MeasurementPointService"/>. Replace the value of the argument with your service url. For standard installation, only the host name and port number will have to be changed.

When using the example config file, you can also choose between KeyRequest-emptyMetadata.xml and KeyRequest-exampleMetadata.xml. However, DataRequest-exampleMetadata-noKey.xml will not work for example config file since it involves data fetching and the NMS won't be able to give you data for the example content given (which is valid for GEANT2 only). You can use this file by changing its contents only if you have uploaded your own config file (see step 8).

After you make the changes to the service url,

Change to the $PERFSONAR/ant directory

> cd $PERFSONAR/ant

$PERFSONAR/ant> ant test-nms-service

Step 7.2 - Using your own requests

If you want to test against your modified config file, follow the next points
- Make sure you have uploaded your config file into the xml database. Step 8 explains how to do this.
- First put relevant values in the request file(s). You can choose between any of the following request files.
  - If you want to test retrieve of metadata (one key) stored in the example MP config file

$PERFSONAR/schema/example-instances/sonar/nmsTypeMP/KeyRequest-exampleMetadata.xml

- - If you want to retrieve data for just one metadata without specifying any key

$PERFSONAR/schema/example-instances/sonar/nmsTypeMP/DataRequest-exampleMetadata-noKey.xml

- - If you want to retrieve data by only using a key

$PERFSONAR/schema/example-instances/sonar/nmsTypeMP/DataRequest-withKey.xml

- To test your service with the request execute the following command in $PERFSONAR/ant directory

> cd $PERFSONAR/ant
$PERFSONAR/ant> ant test-nms-service

If you change something in the code of the web service or update using CVS you have to compile again and redeploy it in Tomcat. Then execute the following commands and restart Tomcat

$PERFSONAR/ant> ant undeploy-nmsTypeMP
$PERFSONAR/ant> ant deploy-nmsTypeMP
$PERFSONAR_TOMCAT/bin> shutdown.sh
$PERFSONAR_TOMCAT/bin> startup.sh

If you change something only in configuration files you have to restart Tomcat

$PERFSONAR_TOMCAT/bin> shutdown.sh
$PERFSONAR_TOMCAT/bin> startup.sh

Step 8. Building your own config file

You can test your service with the example service config file loaded inside the xml database to make sure the installation is alright. Once this is done, you are now ready to build and upload your own config file. Follow the steps below to do so.

Using the example config file ($PERFSONAR/schema/example-instances/sonar/nmsTypeMP/nmsTypeMP-store-beta1.xml) as a template, build your own config file.
- Every config file has n (where n>0) chains.
- Each chain consists of one or more metadata elements and one data element. For now, consider that there is only one metadata element in one chain.
- The data element contains a key which provides access to the data (or helps in making a measurement). In case of NMS, this key contains a wavelength description parameter which can be used to easily communicate with the IOO interface of NMS
- Everything inside the metadata element describes the data element/key and thus eventually the data. Refer to the example config file to see what can be used in the metadata
- Make sure you use namespaces and prefixes correctly
- A wrong config file can cause uncertain behaviour
- Any ideas for auto-generation of the config file will be appreciated

Once you have the config file ready, replace the existing example config file with the new one (You might want to back up the example config file somewhere in case your config file doesn't work)

Once you have repaced the example config file with your own config, put it up on the database by using Step 4.2.1

Alter the example request files according to the values in config file

Test the service using Step 7.2

Step 9. FAQ and Additional Information

FAQ

Additional Information

Checking tomcat logs for some errors

Axis Validation page and adding missing jars

How to deploy and undeploy the service?

In $PERFSONAR/ant directory
> ant deploy-nmsTypeMP 
> ant undeploy-nmsTypeMP

Other XML Database Utilities
- List resources in the XML db

In $PERFSONAR/ant directory
> ant xmldb-list-nmsTypeMP-resources

- To check if NMS type MP Config exists in XML Database

In $PERFSONAR/ant directory
> ant xmldb-check-nmsTypeMP-config
It does not confirm that the resource is present.

- To delete NMS Type MP Config from XML Database

In $PERFSONAR/ant directory
> ant xmldb-remove-nmsTypeMP-config

- To store NMS Type MP Config into the XML Database

In $PERFSONAR/ant directory
> ant xmldb-store-nmsTypeMP-config

Back to Alcatel NMS Measurement Point Page

Retrieved from "http://wiki.perfsonar.net/jra1-wiki/index.php/Alcatel_NMS_MP:Installation_Instructions"

Views

Personal tools

Log in

Search

Toolbox