To allow the Adapter for TMF 814 to communicate with each vendor’s EMS and the domain managers, the adapterConnections.xml file must be edited. This file can be found in the adapter's conf directory. For Cisco, this is

BASEDIR/smarts/conf/tmf814Cisco

For Ciena, this is

BASEDIR/smarts/conf/tmf814Ciena

Open the adapterConnections.xml file using sm_edit. Appendix A, “Understanding the sm_edit Utility,” provides instructions on using sm_edit.

Only the parameters in Configuration parameters for connection to Cisco and Ciena EMSs and should be customized. Other parameters should be kept at default values. These parameters are found under the “connect to the Cisco EMS” and “connect to the Ciena EMS” sections and use the connect action.

Table 1. Configuration parameters for connection to Cisco and Ciena EMSs

Parameter

Description

otm.basedir

Installation path of OTM. Must end with “/OTM”.

connectionType

A string describing the type of connection, e.g., TMF814.

ems.instanceName

EMS instance name. (This is the name of the EMS that will be created on the domain manager.)

ems.emsType

A string describing the EMS type, e.g., CiscoCtm.

ems.interfaceClass

The Java class that contains the specific vendor EMS interface implementation.

For Cisco:

com.vmware.smart.optical.tmf814.ciscoCtm.CiscoCtmEmsInterface

For Ciena:

com.vmware.smart.optical.tmf814.cienaOnctr.CienaSnmEmsInterface

ems.sessionFactory

The EMS session factory (provided by customer).

For Cisco:

Cisco Systems/CTM_78.EmsSessionFactory

For Ciena:

CIENA/LightWorks_ON-Center.EmsSessionFactory

ems.sessionFactoryBackup

The backup EMS session factory (provided by customer).

ems.userName

The EMS user name (provided by customer).

ems.password

The EMS password (provided by customer).

ems.nameServerIors

URL that resolves to the IOR file for one or more name servers. A valid URL must be provided. The URL is passed to the local CORBA ORB.corbaloc::160.45.110.41:38693/StandardNS/NameServer-POA/_root

Note:

Note that the URL is system-specific when a “file:” URL is specified. A Win32 filename should be specified like “file:///c:/a/b/c.ior” using forward slashes and three slashes between “file:” and the drive letter.

Examples (from JacORB documentation):

corbaloc::160.45.110.41:38693/StandardNS/NameServer-POA/_root

file:c/:/NS_Ref

http://www.x.y.z/~user/NS_Ref

ems.emsTracerFile

If the default tracer file directory needs to be specified, it can be added after the "/logs" in the desired path.

ems.logToFilePath

Full path and filename of adapter log.

ems.discovery

To use the TMF814 Adapter for discovery and event processing, set “on”.

For event processing only, set to “off”.

The parameters listed in Configuration parameters for connection to Cisco and Ciena EMSs are used to connect to the SONET/SDH server. Only the parameters in Configuration parameters for connection to OTM domain managers and should be customized. Other parameters should be kept at default values. These parameters are found under the “connect to SONET,” “connect to PDH” and “connect to WDM” sections and use the otmConnect action.

Note:

“Connect for SONET” indicates High-order SONET/SDH.

“Connect for PDH” indicates Low-order SONET and SDH.

Table 2. Configuration parameters for connection to OTM domain managers

Parameter

Description

connectionName

Connection name (can be any string, e.g., “SONET-1”)

connectionType

OTM-SDH-TOPOLOGY,

OTM-PDH-TOPOLOGY, or

OTM-WDM-TOPOLOGY

connectionSyncher

For a High Order SONET/SDH connection:

com.vmware.smart.ce.jablOtmInterface.connection.otmSonetSyncher

For a Low Order SONET/SDH (PDH) connection:

com.vmware.smart.ce.jablOtmInterface.connection.otmPdhSyncher

For a WDM connection:

com.vmware.smart.ce.jablOtmInterface.connection.otmDwdmSyncher

icDomain

The domain name (given by the -n argument of sm_server)

managedEms

The name of the managed EMS

pingFrequency

Frequency, in seconds, in which the adapter sends pings to the domain manager.