Cisco Cisco Prime Optical 10.3 Developer's Guide
Cisco Prime Optical 10.3 GateWay/CORBA Programmer Reference Guide
413
Compliance
Prime Optical-defined.
Prime Optical-defined.
3.15 session::Session_I
The Session_I interface provides capabilities for managing the client-server connection. It
enables either a client or a server to detect communication loss with the associated party. There
are two Session_I objects for each communication session between an NMS and an EMS. One
Session_I object is maintained on the NMS and the other Session_I object is maintained on the
EMS. The Session_I object maintained on the EMS is actually an EmsSession_I, while the
Session_I object maintained on the NMS is actually an NmsSession_I (both inherit from
Session_I).
Each Session_I object is responsible for pinging the other Session_I object periodically to detect
communication failures. Prime Optical invokes this method on NmsSession_I every five
minutes. If this call raises an exception, Prime Optical assumes the session is no longer
connected and deletes all resources allocated to it.
Attributes
enables either a client or a server to detect communication loss with the associated party. There
are two Session_I objects for each communication session between an NMS and an EMS. One
Session_I object is maintained on the NMS and the other Session_I object is maintained on the
EMS. The Session_I object maintained on the EMS is actually an EmsSession_I, while the
Session_I object maintained on the NMS is actually an NmsSession_I (both inherit from
Session_I).
Each Session_I object is responsible for pinging the other Session_I object periodically to detect
communication failures. Prime Optical invokes this method on NmsSession_I every five
minutes. If this call raises an exception, Prime Optical assumes the session is no longer
connected and deletes all resources allocated to it.
Attributes
This attribute contains a reference to the Session_I on the NMS/EMS associated with the object.
This attribute can be checked to verify the NmsSession_I/EmsSession_I association is still valid
(particularly in case of communication failures).
This attribute can be checked to verify the NmsSession_I/EmsSession_I association is still valid
(particularly in case of communication failures).
3.15.1 endSession
Synopsis
Description
This interface enables a controlled disconnect between parties.
Parameters
None.
Throws
None.
Compliance
TMF-defined.
This interface enables a controlled disconnect between parties.
Parameters
None.
Throws
None.
Compliance
TMF-defined.
3.15.2 ping
Synopsis
Description