Cisco Cisco Prime Optical 10.3 Entwickleranleitung
Cisco Prime Optical 10.3 GateWay/CORBA Programmer Reference Guide
640
Decode an IOR file:
Check if the naming service is running:
The /opt/CiscoTransportManagerServer/openfusion/bin directory contains nsMgrTool, dior, and
server utility tools.
6.11 Configuring GateWay/CORBA
You can configure the following GateWay/CORBA properties in the Prime Optical client
Control Panel.
Control Panel.
Step 1
From the Domain Explorer, choose Administration > Control Panel.
Step 2
In the Control Panel, click GateWay/CORBA Service. Configure the following
properties:
properties:
If GateWay/CORBA is running, changes to the config file do not take effect
dynamically. You must restart GateWay/CORBA for the changes to take effect.
Enable Encryption for username and password:
This property defines whether to encrypt the username and password used for the
GateWay/CORBA client.
Heartbeat for Notification Channel (min): 0
This property is the rate at which the notification service is checked. A zero entry
means not to check the notification service.
Enter the maximum number of simultaneous sessions: 4
This property is the number of GateWay/CORBA sessions that can be active at
the same time. The range is from 4 to 25 sessions.
Enter the maximum events per consumer: 10000
GateWay/CORBA uses this property to set the MaxEventsPerConsumer
administrative QoS parameter of the notification channel. The notification server
uses this property to bound the maximum number of events in a given channel
that are allowed to queue at any given time. The default value is 0, where the
notification server does not impose a limit on the maximum number of events that
can be queued. If no limits are imposed on the queue, the notification server might
run out of memory if a client behaves incorrectly. The server must keep all events
in memory until they are consumed by all registered consumers.
Any change to this value should be made with extreme caution. If you set the
uses this property to bound the maximum number of events in a given channel
that are allowed to queue at any given time. The default value is 0, where the
notification server does not impose a limit on the maximum number of events that
can be queued. If no limits are imposed on the queue, the notification server might
run out of memory if a client behaves incorrectly. The server must keep all events
in memory until they are consumed by all registered consumers.
Any change to this value should be made with extreme caution. If you set the
value too low, the NMS will not receive all notifications. If you set the value