You can view the default and user-defined cluster groups, what servers belong to those groups, and what applications are deployed to those groups.

1. In the left pane, click the Domain node, where Domain refers to the name of your Oracle Stream Analytics domain.
2. In the right pane, click the Cluster Groups/Server tab.

   The Cluster Groups/Server tab appears as Figure 17-1 shows.

   Figure 17-1 Cluster Groups/Server Tab

   
   Description of "Figure 17-1 Cluster Groups/Server Tab"
3. Use the Cluster Groups/Server tab to examine the server and application contents of various cluster groups.

   For example:

   • Group testgroup contains two servers (WLEvServer-1 and WLEvServer-2) and one application (helloworld) as Figure 17-1 shows.

   • Group WLEvServer-1 contains one server (WLEvServer-1) and no applications. The helloworld application listed under its Applications node belongs to group testgroup, not to server WLEvServer-1.

   • Group WLEvServer-2 contains one server (WLEvServer-2) and one application (fx). The fx application was deployed to server WLEvServer-2. The helloworld application listed under its Applications node belongs to group testgroup, not to server WLEvServer-2.

Using Oracle Stream Analytics Visualizer, you can view all cluster topologies regardless of cluster implementation. You can also view cluster group properties and server instance properties.

1. In the left pane, click the Domain node, where Domain refers to the name of your Oracle Stream Analytics domain.
2. In the right pane, click the Cluster tab.
3. In the right pane, click the Topology tab.

   The Topology tab appears as Figure 17-2 shows.

   Figure 17-2 Cluster Topology Tab

   
   Description of "Figure 17-2 Cluster Topology Tab"

   This tab shows all cluster groups regardless of the cluster implementation.

   Within a cluster group, the primary server is identified by the icon that Figure 17-3 shows. In Figure 17-2, the primary server is CEPServer1.

   Figure 17-3 Primary Server

   

   For information on the various tools along the top of the topology canvas, see Manage the Cluster Topology Diagram.

4. To view the properties for a given group, click on the group in the Group List.
5. To view the properties for a given server instance, click on the server instance in the Group List.
6. To view details on a given server instance, click the Group Member tab and select the server instance as Figure 17-4 shows.

   Figure 17-4 Group Member Tab

   
   Description of "Figure 17-4 Group Member Tab"
7. Use the Group Member tab to customize the group table:

   • To change the order of columns, click on the column name in the cache chart and drag left or right.

   • To change the sort order of a column, click the triangle to the right of the column name in the cache chart.

Using Oracle Stream Analytics Visualizer, you can view an Oracle high availability cluster topology. You can also view cluster group properties and server instance properties.

Using Oracle Stream Analytics Visualizer, if you are using Oracle Coherence clustering, you can view Oracle Coherence cluster topologies, cluster group properties, and server instance properties.

1. In the left pane, click the Domain node, where Domain refers to the name of your Oracle Stream Analytics domain.
2. In the right pane, click the Coherence tab.
3. In the right pane, click the Topology tab.

   The Topology tab appears as Figure 17-10 shows.

   Figure 17-10 Oracle Coherence Cluster Topology Tab

   
   Description of "Figure 17-10 Oracle Coherence Cluster Topology Tab"

   This tab shows all cluster groups that the Oracle Coherence clustering implementation manages.

   For information on the various tools along the top of the topology canvas, see Manage the Cluster Topology Diagram.

4. To view the properties for a given group, click on the group in the Group List.
5. To view the properties for a given server instance, click on the server instance in the Group List.

Using Oracle Stream Analytics Visualizer, you can compare a combination of properties for any and all nodes in an Oracle Coherence cluster. For a selected node in an Oracle Coherence cluster, you can view a select list of properties.

1. In the left pane, click the Domain node, where Domain refers to the name of your Oracle Stream Analytics domain.
2. In the right pane, click the Coherence tab.
3. In the right pane, click the Multi-Nodes Monitor tab.

   The Multi-Nodes Monitor tab appears as Figure 17-11 shows.

   Figure 17-11 Multi-Nodes Monitor Tab

   
   Description of "Figure 17-11 Multi-Nodes Monitor Tab"
4. Use the Multi-Nodes Monitor tab to customize the group table:

   • To change the order of columns, click on the column name in the cache chart and drag left or right.

   • To change the sort order of a column, click the triangle to the right of the column name in the cache chart.

5. Use the Multi-Nodes Monitor tab to compare any combination of the properties that Table 17-1 lists for any nodes in an Oracle Coherence cluster:

   • Expand a group and check one or more nodes.

   • Drag a property from the Drag Property to Watch area to either graph to watch that property or, select a property and click Add to Left or Add to Right.

     You may specify at most one property per graph.

   • A line is drawn for each selected node. The legend below the graph distinguishes graph data for each selected node by color.

   • To watch a different property, drag a new property and drop it onto the graph or, select a new property and click Add to Left or Add to Right.

   • To change the scale of a graph, drag the slider next to the vertical axis.

   Table 17-1 Properties You Can Watch on the Multi-Nodes Monitor Tab

   Property	Description
   Memory Available	The total amount of free memory (in MB) for the selected node.
   Memory Max	The total amount of memory available (in MB) for the selected node.
   Packets Sent	The total number of Oracle Coherence packets sent by the selected node.
   Packets Received	The total number of Oracle Coherence packets received by the selected node.
   Buffer Receive Size	The total number of Oracle Coherence received packets that the selected node can buffer.
   Buffer Publish Size	The total number of Oracle Coherence published packets that the selected node can buffer.

6. To view more details for a particular node, click the Node Detail View tab.

   The Node Detail View tab appears as Figure 17-12 shows.

   Figure 17-12 Node Detail View Tab

   
   Description of "Figure 17-12 Node Detail View Tab"
7. Use the Node Detail View tab to compare the properties that Table 17-2 lists for a selected node:

   • Select a node from the Nodes pull-down menu.

     The properties for the selected node are shown in the Nodes Properties list.

   • A line is drawn for the selected node.

   • To change the scale of a graph, drag the slider next to the vertical axis.

   Table 17-2 Properties You Can Watch on the Node Detail View Tab

   Property	Description
   Memory Available	The total amount of free memory (in MB) for the selected node.
   Memory Max	The total amount of memory available (in MB) for the selected node.
   Packets Sent	The total number of Oracle Coherence packets sent by the selected node.
   Packets Received	The total number of Oracle Coherence packets received by the selected node.

Using Oracle Stream Analytics Visualizer, you can monitor a wide variety of Oracle Coherence cache parameters and graphically compare parameter values to locate and diagnose performance and operational problems.

1. In the left pane, click the Domain node, where Domain refers to the name of your Oracle Stream Analytics domain.
2. In the right pane, click the Coherence tab.
3. In the right pane, click the Cache Chart tab.

   The Multi-Nodes Monitor tab appears as Figure 17-13 shows.

   Figure 17-13 Cache Chart Tab

   
   Description of "Figure 17-13 Cache Chart Tab"
4. Use the Cache Chart tab to view any combination of the columns that Table 17-3 lists for one or more selected caches:

   • Check one or more caches in the cache chart.

   • To add a column to the cache chart, check the column in the Columns list.

   • To remove a column from the cache chart, uncheck the column in the Columns list.

   • To change the order of columns, click on the column name in the cache chart and drag left or right.

   • To change the sort order of a column, click the triangle to the right of the column name in the cache chart.

   Table 17-3 Columns and Properties for the Cache Chart Tab

   Property	Description
   Cache Name	The name of the cache.
   # of Objects	The total number of objects in the selected cache.
   Cache Hits	The total number times an Oracle Coherence cache client has accessed the selected cache.
   Cache Misses	The total number times an Oracle Coherence cache client has accessed the selected cache and failed to find the desired object.
   Cache Prunes	The total number times Oracle Coherence has reached its maximum size and had to delete some objects to return to a configured smaller size for the selected cache.
   Store Writes	The total number of times Oracle Coherence has written to the selected cache's backing store.
   Store Reads	The total number of times Oracle Coherence has read from the selected cache's backing store.
   Node Id	The node identifier for the selected cache.
   Store Failures	The total number of times the selected cache's backing store has failed to service an Oracle Coherence Store Write or Store Read.
   Average Hit Millis	The average time (in milliseconds) taken by Oracle Coherence to find an object in the selected cache.
   Average Get Millis	The average time (in milliseconds) taken by Oracle Coherence to retrieve an object from the selected cache.
   Average Miss Millis	The average time (in milliseconds) taken by Oracle Coherence to determine that an object does not exist in the selected cache.
   Average Put Millis	The average time (in milliseconds) taken by Oracle Coherence to add a new object to the selected cache.
   Cache Hits Millis	The total time (in milliseconds) taken by Oracle Coherence to find an object in the selected cache.
   Cache Misses Millis	The total time (in milliseconds) taken by Oracle Coherence to determine that an object does not exist in the selected cache.
   Cache Prunes Millis	The total time (in milliseconds) taken by Oracle Coherence to delete some objects from the selected cache to return to a configured smaller size after having reached its maximum size.
   Store Read Millis	The total time (in milliseconds) taken by Oracle Coherence to read from the selected cache's backing store.
   Store Write Millis	The total time (in milliseconds) taken by Oracle Coherence to write to the selected cache's backing store.
   Total Gets Millis	The total time (in milliseconds) taken by Oracle Coherence to retrieve objects from the selected cache.
   Total Puts Millis	The total time (in milliseconds) taken by Oracle Coherence to add new objects to the selected cache.

5. Use the Cache Chart tab to compare any combination of the properties that Table 17-3 lists for one or more selected caches:

   • Check one or more caches in the cache chart.

   • Drag a property from the Drag Property to Watch area to either graph to watch that property or, select the property and click Add to Left or Add to Right.

     You may specify at most one property per graph.

   • A line is drawn for each selected cache. The legend below the graph distinguishes graph data for each selected cache by color.

   • To watch a different property, drag the new property and drop it onto the graph or, select a different property and click Add to Left or Add to Right.

   • To change the scale of a graph, drag the slider next to the vertical axis.

Using Oracle Stream Analytics Visualizer, you can view and modify a variety of Oracle Coherence parameters to fine tune Oracle Coherence performance.

1. In the left pane, click the Domain node, where Domain refers to the name of your Oracle Stream Analytics domain.
2. In the right pane, click the Coherence tab.
3. In the right pane, click the Tuning tab.

   The Tuning tab appears as Figure 17-14 shows.

   Figure 17-14 Tuning Tab: Cache Tuning

   
   Description of "Figure 17-14 Tuning Tab: Cache Tuning"
4. To tune parameters and invoke operations for caches, select the Cache Tuning accordion tab and select a cache as Figure 17-14 shows.

   Table 17-4 lists the properties you can view and tune for the selected cache. All properties are based on Oracle Coherence http://download.oracle.com/otn_hosted_doc/coherence/340/com/tangosol/net/management/Registry.html.

   Table 17-4 Cache Tuning: Properties

   Property	Description
   Cache Name	The name of the selected cache (read-only).
   Service	The service associated with this cache (read-only).
   Batch Factor	The BatchFactor attribute is used to calculate the `soft-ripe` time for write-behind queue entries. A queue entry is considered to be `ripe` for a write operation if it has been in the write-behind queue for no less than the QueueDelay interval. The `soft-ripe` time is the point in time prior to the actual `ripe` time after which an entry will be included in a batched asynchronous write operation to the CacheStore (along with all other `ripe` and `soft-ripe` entries). This attribute is only applicable if asynchronous writes are enabled (that is, the value of the QueueDelay attribute is greater than zero) and the CacheStore implements the storeAll() method. The value of the element is expressed as a percentage of the QueueDelay interval. Valid values are doubles in the interval [0.0, 1.0]..
   Queue Delay (Milliseconds)	The number of seconds that an entry added to a write-behind queue will sit in the queue before being stored via a CacheStore. Applicable only for WRITE-BEHIND persistence type.
   Expiry Delay (Milliseconds)	The number of milliseconds that the MBeanServer will keep a remote model snapshot before refreshing.
   Flush Delay (Milliseconds)	The number of milliseconds between cache flushes. Value of zero indicates that the cache will never flush.
   Refresh Factor	The RefreshFactor attribute is used to calculate the `soft-expiration` time for cache entries. Soft-expiration is the point in time prior to the actual expiration after which any access request for an entry will schedule an asynchronous load request for the entry. This attribute is only applicable for a ReadWriteBackingMap which has an internal LocalCache with scheduled automatic expiration. The value of this element is expressed as a percentage of the internal LocalCache expiration interval. Valid values are doubles in the interval[0.0, 1.0]. If zero, refresh-ahead scheduling will be disabled.
   Requeue Threshold	The maximum size of the write-behind queue for which failed CacheStore write operations are requeued. If zero, the write-behind requeueing will be disabled. Applicable only for WRITE-BEHIND persistence type.
   High Units	The limit of the cache size measured in units. The cache will prune itself automatically once it reaches its maximum unit level. This is often referred to as the `high water mark` of the cache.
   Low Units	The number of units to which the cache will shrink when it prunes. This is often referred to as a `low water mark` of the cache.

   To apply changes, click the Save button.

   To discard changes, click the Cancel button.

   Table 17-5 lists the operations you can invoke for the selected cache.

   Table 17-5 Cache Tuning: Operations

   Operation	Description
   Reset Statistics	Reset the cache statistics.

5. To tune parameters and invoke operations for cluster nodes, select the Node Tuning accordion tab and select a node as Figure 17-15 shows.

   Figure 17-15 Tuning Tab: Node Tuning

   
   Description of "Figure 17-15 Tuning Tab: Node Tuning"

   Table 17-6 lists the properties you can view and tune for the selected cache. All properties are based on Oracle Coherence http://download.oracle.com/otn_hosted_doc/coherence/340/com/tangosol/net/management/Registry.html.

   Table 17-6 Node Tuning: Properties

   Property	Description
   Node Name	The name of the selected node (read-only).
   Buffer Publish Size	The buffer size of the unicast datagram socket used by the Publisher, measured in the number of packets. Changing this value at runtime is an inherently unsafe operation that will pause all network communications and may result in the termination of all cluster services.
   Buffer Receive Size	The buffer size of the unicast datagram socket used by the Receiver, measured in the number of packets. Changing this value at runtime is an inherently unsafe operation that will pause all network communications and may result in the termination of all cluster services.
   Burst Count	The maximum number of packets to send without pausing. Anything less than one (for example, zero) means no limit.
   Burst Delay (Milliseconds)	The number of milliseconds to pause between bursts. Anything less than one (for example, zero) is treated as one millisecond.
   Logging Level	Specifies which logged messages will be output to the log destination. Valid values are: 0 only output without a logging severity level specified will be logged 1 all the above plus errors 2 all the above plus warnings 3 all the above plus informational messages 4..9 all the above plus internal debugging messages (the higher the number, the more the messages) -1 no messages
   Logging Format	Specifies how messages will be formatted before being passed to the log destination. The value of the message-format element is static text with the following replaceable parameters: {date} the date/time format (to a millisecond) at which the message was logged {version} the Oracle Coherence exact version and build details {level} the logging severity level of the message {thread} the thread name that logged the message {member} the cluster member id (if the cluster is currently running) {text} the text of the message
   Logging Limit	The maximum number of characters that the logger daemon will process from the message queue before discarding all remaining messages in the queue. Valid values are integers in the range [0...]. Zero implies no limit.
   Multicast Threshold	The percentage (0 to 100) of the servers in the cluster that a packet will be sent to, above which the packet will be multicasted and below which it will be unicasted.
   Resend Delay (Milliseconds)	The minimum number of milliseconds that a packet will remain queued in the Publisher`s re-send queue before it is resent to the recipient(s) if the packet has not been acknowledged. Setting this value too low can overflow the network with unnecessary repetitions. Setting the value too high can increase the overall latency by delaying the re-sends of dropped packets. Additionally, change of this value may need to be accompanied by a change in SendAckDelay value.
   Send Ack Delay (Milliseconds)	The minimum number of milliseconds between the queueing of an Ack packet and the sending of the same. This value should be not more then a half of the ResendDelay value.
   Traffic Jam Count	The maximum total number of packets in the send and resend queues that forces the publisher to pause client threads. Zero means no limit.
   Traffic Jam Delay (Milliseconds)	The number of milliseconds to pause client threads when a traffic jam condition has been reached. Anything less than one (for example, zero) is treated as one millisecond.

   To apply changes, click the Save button.

   To discard changes, click the Cancel button.

   Table 17-5 lists the operations you can invoke for the selected node.

   Table 17-7 Node Tuning: Operations

   Operation	Description
   Reset Statistics	Reset the cluster node statistics.

6. To tune parameters and invoke operations for nodes, select the Node Tuning accordion tab and select a node as Figure 17-16 shows.

   Figure 17-16 Tuning Tab: Service Tuning

   
   Description of "Figure 17-16 Tuning Tab: Service Tuning"

   Table 17-8 the properties you can view and tune for the selected cache. All properties are based on Oracle Coherence http://download.oracle.com/otn_hosted_doc/coherence/340/com/tangosol/net/management/Registry.html.

   Table 17-8 Service Tuning: Properties

   Property	Description
   Service Name	The name of the selected service (read-only).
   Request Timeout (Millis)	The default timeout value in milliseconds for requests that can be timed-out (for example, implement the com.tangosol.net.PriorityTask interface), but do not explicitly specify the request timeout value.
   Task Hung Threshold (Millis)	The amount of time in milliseconds that a task can execute before it is considered hung. Note that a posted task that has not yet started is never considered as hung.
   Task Timeout (Millis)	The default timeout value in milliseconds for tasks that can be timed-out (for example, implement the com.tangosol.net.PriorityTask interface), but do not explicitly specify the task execution timeout value.
   Thread Count	The number of threads in the service thread pool.

   To apply changes, click the Save button.

   To discard changes, click the Cancel button.

   Table 17-9 lists the operations you can invoke for the selected service.

   Table 17-9 Service Tuning: Operations

   Operation	Description
   resetStatistics	Reset the service statistics.

You use the topology tools to manage the topology diagram of your cluster topology.

This section describes the various tools along the top of the Topology canvas as Figure 17-17 shows.

Figure 17-17 Cluster Topology Tools

Description of "Figure 17-17 Cluster Topology Tools"