From LMC, click the System tab.
From the System section, select System Status.
Click System Health.
From LMC, access the System Health dashboard. For more information, see Accessing the System Health dashboard.
The following indicators show the overall health of the LDD system:
Overloaded—The indicator changes color depending on the overload condition of the system:
Green—No servers are overloaded, and all servers are operating at normal capacity.
Yellow—One or more servers are overloaded, but at least one server is not. Overloaded servers operate at diminished capacity until they are no longer overloaded.
Red—All servers are overloaded and operating at diminished capacity.
Task / Hour—Shows the current hourly task rate, based on tasks done in the past minute.
Threshold Exceptions—Shows the hourly rate of tasks that exceed the threshold time set for each job on each server, based on tasks done in the past minute.
To view the performance data for an individual server, from the Server Health section, select the address of the server from the list. The following data is shown for overall server performance:
Task Count—Shows the number of jobs running on the server over time.
Overload Events—Shows the hourly rate of overload events. An overload event occurs when the number of tasks exceeds the configured design load and ends when the number of tasks reaches the configured recover load.
The following task-specific data is shown for the task selected from the list:
Task / Hour—Shows the current hourly task rate for the selected task, based on tasks done in the past minute.
Threshold Exceptions—Shows the hourly rate of the task that exceeds the threshold time set for the selected task, based on tasks done in the past minute.
To view a specific performance graph, from the Server Health section, click the graph. To return to the view of all graphs, click the graph again.
Notes:
URL | Method | Headers key | Value | Body | Description |
|---|---|---|---|---|---|
Where is the IP address of the load balancer. | POST | Accept | application/json or application/xml | data type application/json | This API lets you specify a list of servers, and the API can be called to each one of the LDD servers to get a status of each server. The API returns a payload that contains each server and the corresponding status of each server. This payload must be returned in a JSON response format. Note: Depending on the LDD installation type, send a JSON array with the IP address or host name. For example, . |
Where is the IP address of the load balancer. | GET | Accept | application/json or application/xml | This API provides the results of the existing "SystemHealth" MBean "Overloaded" method in XML or JSON format. | |
Where is the IP address of the load balancer. | GET | Accept | application/json or application/xml | This API provides the results of the existing "SystemHealth" MBean "Overloadedeventsperhour" method in XML or JSON format. |
A server that meets recommended requirements can process 30 concurrent jobs from clients. If a server is faster than the recommended system, then raise the limit on concurrent jobs for that server to increase system capacity. If a server is slower than the recommended system, then lower the limit on concurrent jobs to maintain system reliability.
The adjustment sets the baseline design load for the server, and the recover load is set at 80 percent of the design load. If jobs running on the server exceed the design load, then the load balancer reduces job submissions to the server until the recover load is reached.
To change the limit on concurrent jobs, do the following for each server:
From LMC, access the System Health dashboard. For more information, see Accessing the System Health dashboard.
From the Server Health section, select a server address.
Adjust the Concurrently Running Task Limit slider to the preferred limit for the server.
Click Apply.
The ideal job distribution depends on the following:
Hardware
Network environment
Solution being run
When all servers in the system are approximately equal, server loads must be optimal without manually tuning the load balancer. If servers are unequal, then the least powerful machine determines the overall throughput. To increase the overall job capacity of the system, assign a load-balancing factor to each server. This configuration routes more traffic to more powerful machines and helps prevent overloading.
Each load balancer distributes jobs to servers in proportion to the load-balancing factors that are assigned to each server. For example, in a system with three servers with load-balancing factors of 10,10, and 20, do the following configuration:
The first two servers must each receive 25 percent of jobs.
The third server must receive 50 percent of jobs.
To determine the optimal proportions for load-balancing factors, run performance tests on each server. Some factors such as memory, number of processors, or CPU speed may suggest an initial value for the load-balancing factor to add more system capacity.
To assign a load-balancing factor to each server, do the following:
From LMC, access the System Health dashboard. For more information, see Accessing the System Health dashboard.
From the Server Health section, select a server address.
Adjust the Load Factor slider to the preferred load-balancing factor for the server.
Click Apply.
The load balancer is composed of three different Tomcat load-balancing workers that separately manage LMC sessions and job submissions from e-Task 3, e-Task 2, and e-Task printers. The adjustment affects the e-Task 3, e-Task 2, and e-Task load balancers, but not the LMC load balancer.
When using more than one server in a system, you can assign some servers to run LMC only and other servers to only process jobs.
When using a configuration 1-N, X-N, or X-Y-N system with the recommended hardware, we recommend doing the following:
Install the server component on the RAID 1 array where the operating system is installed on the load balancer computer. Configure it to run LMC only.
Configure the servers that are installed on dedicated computers to only process jobs.
From your web browser, launch JK Status Manager by using the URL . is the IP address of the computer where the load balancer is installed.
Server information and the worker status for each of the three load-balancing workers appear. Each server in the system is listed as a worker in each Balancer Members list.
For each server that must only process jobs, stop the associated worker on the adminloadbalancer load-balancing worker. Do the following:
From the “Worker Status for adminloadbalancer” section, click E beside the server name.
Stop the activation.
Click Update Worker.
For each server that must run LMC only, stop the associated worker on the clientloadbalancer and adaptorloadbalancer load balancing workers. Do the following:
From the “Worker Status for clientloadbalancer” and "Worker Status for adaptorbalancer" sections, click E beside the server name.
Stop the activation.
Click Update Worker.
Notes:
When using three or more servers, reducing the chunk size may increase the speed of device discovery and policy updates.
From LMC, click the Services tab.
From the Services list, select General.
From the Tasks list, select Parameters.
In the ChunkSize field, enter a new value. When using three or more servers, a value as low as is sufficient.
Click Apply.