For detailed, complete lists of components as well as installation instructions, see the following Navigator release notes articles:
- 10.4.0 E-fix for multiple platforms
- 10.4.0 E-fix for Linux RHEL
- 10.4.0 E-fix for Windows
- 10.4.0 E-fix for AIX 6.1
See also the Navigator v10.4.1.1 hot fix section at the end of this article.
Redesigned Security Manager Now Available
In addition to the existing web Security Manager, we offer a newly designed implementation of the Security Manager. Both the existing application and the new one can be used interchangeably.
To access the new Security Manager, use a web application (navxwsm) and you can continue to access the original (apodwsm). The Security Manager quick access icon in Navigator will default to the original Security Manager, but can be changed.
See the E-fix for multiple platforms link above for v10.4 installation information.
See Navigator Security Manager for details about the new version of Security Manager.
Solace support
We now support Solace Pubsub+ through the REST API and through viewlets in the user interface. The focus of the initial release was on the REST API, which offers full functionality for managing Solace PubSub+. The viewlets in Navigator are view-only and intended to provide visibility into what data is being collected. Future releases will add full functionality to the viewlets as well.
Transfer dashboard ownership from inactive users
The Dashboard Ownership Management feature is intended to manage the dashboards of inactive users before the users’ accounts are deleted. You can use it to change the ownership of an inactive user's dashboard, assigning it to a different user.
See Dashboard Ownership Management for details.
Freeze viewlet columns
By freezing columns in a viewlet, you can keep important columns on the left side of the viewlet no matter how far you scroll to the right, without changing your schema.
See Manage Frozen Columns for details.
Filter viewlet by specific columns
By managing filtered columns in a viewlet, you can tailor the use of the Filter by box to your specific needs. Instead of using it to filter viewlet data by all columns only (its default behavior), you can choose one or more specific columns to apply the filter to.
See Manage Filtered Columns for details.
New global and user settings
Several new options have been added to the Settings dialog. See User Settings Field Descriptions for a complete list of settings and their descriptions.
Global settings:
- Refresh interval minimum (sec.). To conserve system resources, you can now prevent users’ viewlets from being refreshed too frequently by establishing a minimum value for refresh intervals. When you change this setting, all user-defined refresh intervals that fall below it are set to the threshold from Global Settings; the updated interval goes into effect the next time the user logs in.
- Session timeout. For security reasons, user sessions are set to terminate after a defined period of inactivity (known as the “session timeout”). The default value is 600 seconds (10 minutes). If a user’s session has been idle for 10 minutes, the Extend Session dialog is displayed, and the user can either click Continue to extend the user session or Log Out to exit the application.
User setting:
- Collapse all viewlets on login. This option to have all viewlets displayed as collapsed at login can be set at the global or user level. If you do not have this option enabled, then the next time you log in, viewlets will revert to their previous state. Note that Workspace dashboard viewlets are not subject to this setting.
Streaming queues supported
New attributes have been added to support streaming queues. Use the Queue Create Window Storage Tab to enter details. You can specify the Stream Queue Name (the name of the queue to deliver streamed messages to) and the Stream Queue QoS, which can be set to Best Effort (this default setting avoids affecting delivery of the original message) or Must Duplicate (a problem with delivery of the streamed message can prevent delivery of the original message).
How to Create a Queue.
New "Force Refresh" viewlet mode
When you know you'll need to force a refresh of viewlet data several times in a row, you can turn on Force Refresh mode, which allows you to perform a number of consecutive forced refreshes for a viewlet.
See Force Refresh (Viewlet) for more information.
Search object attribute names or values from console
When using the Show Object Attributes feature to view object attributes in the console pane, you can now also search the attribute list to find specific names or values. Enter part or all of the attribute name or value in the box provided. The first record that matches the value you entered is highlighted. You can then browse through matches using the right and left arrows.
Viewlet schemas now support secondary sort option
See Schemas in Navigator for schema instructions, which include how to set up a secondary sort column for a schema.
New Kafka viewlets
Three new (Confluent) Kafka viewlets are supported:
- Schemas
- Schema subject
- Schema subject version
Delete IIB Message Flows, Sub Flows, and Resources
You can delete IIB Message Flows, Sub Flows, and Resources have been created directly on the server.
See Delete IIB Message Flows, Sub Flows, and Resources.
Navigator v10.4.1.1 hot fix
Make object attributes for TIBCO EMS Brokers Easier to Read
TIBCO EMS object attributes that were previously displayed in bytes only are now displayed in megabytes and gigabytes as needed. Abbreviations are derived from the International System of Units (SI) and are used as follows:
Size |
Displayed in Units |
Label |
up to 1 MB |
bytes (B) |
No label |
Up to 1 GB |
megabytes (MB) |
MB |
1 GB or greater |
gigabytes (GB) |
GB |
This change affects the display of the following six attributes:
- EMS Log File Size (EXIA_EMS_LOG_FILE_SIZE)
- EMS Pending Message Size (EXIA_EMS_PENDING_MSG_SIZE)
- EMS Message Memory (EXIA_EMS_MSG_MEMORY)
- EMS Message Memory Pooled (EXIA_EMS_MSG_MEMORY_POOLED)
- EMS Sync Database Size (EXIA_EMS_SYNC_DB_SIZE)
- EMS Async Database Size (EXIA_EMS_ASYNC_DB_SIZE)