> #### Accessing and reviewing Operational views

> The NameServer Operational views display information about the NameServer's current running status.

> To display and review runtime information about the NameServer instance:

> 1. Display the NameServer main page for the instance that you want to start. See the "Accessing OpenEdge resource information" section for the detailed procedure.
> 2. Click Status in the Operational Views section to display the Operational Status page:

> This view is comprised of a single Summary section that displays at the top of the view. followed by multiple AppService sections, one for each registered Application Service (AppService) that this NameServer recognizes.

> ##### Operational Views content examination

> In general, the summary section data pertains to the resource as a whole; each Application Services detail section focuses primarily on data for an individually registered broker. The total values displayed in the Summary section are derived by adding the unique values that display in each unique AppService section. However, there are some situations in which the request- related counts between these sections might not correlate. See the description of the Total client requests received and Total client requests rejected fields in Table 5–3 for details, and the Requests Received and Requests Directed fields in Table 5–4 for details.

> Table 5–3 briefly describes each of these fields displayed on the Summary section.

> ##### Summary section

> In the Summary section, the Number of Brokers field displays a total of all the brokers currently registered with a specific resource. The number of unique brokers identified in each of the separate AppService detail sections equals the number displayed in the Number of Brokers field.

> Table 5–3 identifies and describes all the Summary fields and their display-only details. Most of the values that display on this page are originally defined in the `ubroker.properties` file.

> Table 5–3: Summary details on the Operational Status page
> This field... | Displays the...
> --- | ---
> Host | NameServer's host machine name.
> Port | Number of the UDP Port that the NameServer uses to listen for client connection requests and registration messages from AppServers, and Transaction Servers.
> Timeout | A value, in seconds, that indicates how often the NameServer checks for WebSpeed or AppServer broker instances that have timed out. When a WebSpeed or AppServer broker instance registers with a NameServer, the instance indicates how often it will send "keep-alive" messages by setting a registration retry value (a property setting in the `ubroker.properties` file). Once a NameServer determines that it has not received a "keep-alive" message from a broker instance within the broker's registration retry time, the NameServer automatically unregisters the instance.
> Start time | Date and time stamp when the NameServer started. Any time the NameServer is restarted, this field will be updated to display the NameServer's most recent start time.
> Number of AppServices | Number of Application Services associated with this NameServer instance. The count associated with this display field matches the number of Application Services listed in the detailed AppService sections in this view.
> Number of Brokers | Number of brokers in the broker pool that are currently registered with this NameServer instance, directing client connection requests to a requested Application Service. A broker might register more than one Application Service with a NameServer instance. Therefore, it might appear several times in the AppServices detail section. However, the broker will only count as 1 towards the total number of brokers recorded in this field.
> Total client requests received | Total number of client requests received by the NameServer since it was started. Any time the NameServer is restarted, this field will be reset to display a request total relative to the NameServer's most recent start time.
> Total client requests rejected | Total number of times that a client requested a broker for an Application Service that the NameServer had no knowledge of and therefore a client could not be matched up with a registered broker. This value identifies real-time client requests. Data related to any requests that the NameServer passes to NameServer Neighbors with which it typically works are not captured in this total. Any time the NameServer is restarted, this field will be reset to display a count relative to the NameServer's most recent start time.

> ##### Application Services detail section

> For each Application Service (AppService) currently identified to the NameServer, there is a unique table of displayed values that appears on the Operational Status page. Table 5–4 briefly describes each of these fields. Also, note these additional points about the relationship of these fields as they relate to each other and to data presented in the Summary section:

> - An individually registered broker can support multiple Application Services. Therefore, you might see several AppService detail sections associated with a NameServer instance, but only a small total number reported in the Number of Brokers field in the Summary section.
> - In an Application Services detail section, the value displayed in the Requests Received field reflects a total number of requests for this service. However, each broker identified as supporting a client request to an Application Service maintains its own individual Requests Directed total.
> - If an active broker goes down or is unavailable, any AppService detail sections uniquely associated with that broker will no longer display. If the broker re-registers, its total Requests Directed count will be reset to zero.

> Table 5–4 identifies and describes the fields and their display-only details that appear in each AppService section of the Operational Status page. Many of these values originate from the configuration settings stored in the `ubroker.properties` file.

> Table 5–4: NameServer details on the Operational Status page
> This field... | Displays the...
> --- | ---
> Requests Received | Number of client requests received for this Application Service. This count is maintained when one or more brokers are registered to support the Application Service. The count is reset when the Application Service is first identified to the NameServer.
> Broker | Name of the broker that is capable of fulfilling the connection between the requesting client and the Application Service. When more than one broker is servicing the same Application Service, each new broker's data is appended to the individual AppService details section.
> Host | Broker's host machine name and numeric address.
> Weight | Priority weight assigned to the Unified Broker instance for the purpose of load balancing.
> Requests Directed | Total number of client connection requests for the Application Service as directed by the NameServer to the broker instance. This count is maintained while the broker remains registered. If the broker is stopped or timesout, the broker's count is reset to zero when the broker next runs. There is a separate counter for each Application Service that the broker supports.
> UUID | Unique number for the Unified Broker instance.
> Port | TCP/IP port number that the broker listens on to pick up client connection requests.
> Timeout | Amount of time, in seconds, that elapses between the "keep alive" messages that the broker sends to the resource as part of a broker's registration retry entry process.

Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095