Cisco Cisco Workload Automation 6.3 Installation Guide
83
Installing a CWA Java Client
Configuring the CWA Java Client
Configuring the CWA Java Client
As a thick client, the CWA Java Client can consume a considerable amount of resources of the CWA Master. You can
monitor and control CWA Java Client usage by:
monitor and control CWA Java Client usage by:
Limiting the Number of CWA Java Client Connections
You can control the number of users connected to the CWA Master via the CWA Java Client at any time. If the configured
maximum number of CWA Java Client connections is exceeded, additional requests are denied.
maximum number of CWA Java Client connections is exceeded, additional requests are denied.
Note: Configuring a maximum number of CWA Java Client connections does not limit the number of CWA Web Clients
connecting through the Client Manager, nor does it limit the number of super admin users using the CWA Java Client.
connecting through the Client Manager, nor does it limit the number of super admin users using the CWA Java Client.
To limit the number of 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:
TESClient.ConnectionLimit=<max_number_of_connections>
where
<max_number_of_connections>
is the maximum number of CWA Java Client connections allowed to the CWA
Master.
Restricting User Access via the CWA Java Client
You can control which users can connect to the CWA Master via the CWA Java Client.
Note: You cannot deny access to a super admin user.
To restrict user access via a CWA Java Client connection
1.
In the Navigator, choose Administration > Security Policies.
2.
Choose the Workgroups, LDAP Groups, or Interactive User and choose Edit.
3.
Check “Deny TES Client Access”.
4.
Save the security policy.
Viewing Slow CWA Java Clients
CWA Java Clients that are slow in consuming messages from the CWA Master can cause a Master process to consume
a huge amount of heap memory while trying to retain the pending messages.
a huge amount of heap memory while trying to retain the pending messages.