In this section: |
This section provides detailed descriptions of new configuration and monitoring features.
How to: |
You can map users to groups using a custom FOCEXEC.
The Change Groups Provider pane opens.
How to: |
You can kill the agents associated with a connected user ID from the Data Agents pages of the Web Console or from the command line.
In the Web Console, look for a row for the agent in the Data Services Agents pane that is currently connected to the desired user ID, then right-click that row and select Kill Agents With The Same User ID, as shown in the following image.
To kill agents from the command line, the syntax is:
edastart -killuser <userid>
In addition, for the z/OS platform, a z/OS operator MODIFY command can also be used, as follows:
/F <server_jobname/started tast>,-killuser <userid>
How to: |
A server administrator can enter a custom message that will be displayed for a new user connection to the server when the server is in Quiesce mode.
To define a custom message that will be delivered from a quiesced server:
You will be asked if you want to disable new connections.
Note: This feature is only available to a user having server admin privileges.
How to: |
The max_connections_per_user property for a Data Service specifies the maximum number of connections to the Data Service allowed for each user. When a user exceeds the maximum number allowed, additional connections requested by that user are refused, and the server displays the following message:
Connection refused due to the max_connections_per_user (n)
being exceeded
where n is the number of allowed connections.
You have the option to queue user connections that are refused by the server, using the queue_max_user_conns property on the Data Service Properties page. That option is available only if the Queuing property for the Data Service is on.
The Properties page for the selected Data Service opens.
In the following image, Queuing is turned on, max_connections_per_user is set to 3, and queue_max_user_conns is enabled.
Advanced parameters have been added for multiple cluster nodes. The parameters include:
These parameters work on the cluster node level and override the values defined in the CLM node.
WebFOCUS |