Cisco Cisco Workload Automation 6.3 Installation Guide
84
Installing a CWA Java Client
Configuring the CWA Java Client
You can view the CWA Java Clients connected to the CWA Master at any time along with the information on whether any
of the Java Clients is slow in communicating with the Master. If a Java Client connection is slow, a super admin user can
terminate that connection.
of the Java Clients is slow in communicating with the Master. If a Java Client connection is slow, a super admin user can
terminate that connection.
Note: This feature is available only on the CWA Java Client.
To view slow CWA Java Client connections
1.
Log on to the CWA Client.
2.
From the Navigator, choose Master Status.
3.
Click the Connections tab.
The Queued Messages column indicates the queued messages for each connection. A fast client should ideally show
close to “0” queued messages or show a decreasing amount of queued messages over time.
close to “0” queued messages or show a decreasing amount of queued messages over time.
Configuring the Monitoring of Slow CWA Java Client Connections
You can enable monitoring of the CWA Java Client connections to the CWA Master and be alerted when a slow
connection is detected.
connection is detected.
To configure the frequency of checking for slow CWA Java Client connections
1.
Open the master.props file that resides in the config directory on the Master machine.
2.
Add this configuration property to master.props:
Client.SlowConnectionCheckInterval=<time_in_seconds>
where
<time_in_seconds>
is how often CWA Java Client connections will be checked. To make sure that the
monitoring process is not overly intrusive on the operations of the CWA Master, set to 60 seconds or more.
When a slow CWA Java Client is detected, the system event “Client Connection Slow” is triggered. A CWA Client
connection is considered to be slow if the client has received less than 95 percent of the messages from the CWA
Master over the duration of the client session. You can optionally change this tolerance threshold as described in the
next step.
connection is considered to be slow if the client has received less than 95 percent of the messages from the CWA
Master over the duration of the client session. You can optionally change this tolerance threshold as described in the
next step.
3.
(Optional) You can change the tolerance threshold for what is considered to be a slow connection using the following
configuration property in master.props to any value other than 95 (such as 99 – meaning 99 percent):
configuration property in master.props to any value other than 95 (such as 99 – meaning 99 percent):
Client.SlowConnectionThreshold=95
4.
(Optional) You can set up an action event when a slow connection is encountered. For example you could associate
an Email Action to the “Client Connection Slow” System Event to get email notifications. See the “Events” chapter
in the Cisco Workloade Automation User Guide for how to do this.
an Email Action to the “Client Connection Slow” System Event to get email notifications. See the “Events” chapter
in the Cisco Workloade Automation User Guide for how to do this.
Controlling the Java Client Access
CWA provides a “whitelisting” mechanism for allowing Java Client access to the Master based on the Java Client’s
subnet mask, IP address, and/or user ID. This lets you restrict Master access by Java Clients that are unauthorized or that
are on a slow network. For example, you might want to safeguard the Master from running out of memory due to a Java
Client with a slow downloading speed which can cause a backlog in the Master memory.
subnet mask, IP address, and/or user ID. This lets you restrict Master access by Java Clients that are unauthorized or that
are on a slow network. For example, you might want to safeguard the Master from running out of memory due to a Java
Client with a slow downloading speed which can cause a backlog in the Master memory.
Java Client Access Configuration Parameters
To support the Java Client whitelisting feature, CWA provides three parameters that control which Java Client IP
addresses and users are allowed to access the Master. These parameters are specified in the master.props file:
addresses and users are allowed to access the Master. These parameters are specified in the master.props file:
TESClient.SubnetMaskList—Specifies the list of one or more subnet mask(s) which comprises the Java Client IP
addresses that are allowed to access the Master.
addresses that are allowed to access the Master.