IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Pre-deployment phase > Sizing the Tivoli Monitoring hardware
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Locating and sizing the portal client
There are three deployment options for the portal client; Browser client, Desktop client, and Java Web Start client.
The portal client has three different deployment alternatives which are described in Table 1 below.
Portal client deployment considerations
Portal client Advantages Disadvantages Browser client
- Does not need to be installed on client machine.
- Centralized administration.
- Workspaces can be referenced using URLs.
- Longer initial download.
Desktop client
- Fastest startup and performance.
- Needs to be installed on each client machine.
- Requires maintenance to be installed individually on each client machine.
- Mismatch of versions between portal server and the client is not permitted.
Java Web Start client
- Similar performance to desktop client.
- Supports multiple JREs.
- Centralized administration.
- Longer initial download.
The memory required by the portal client depends on the size of the monitoring environment and on the Java heap size parameters. The default maximum Java heap size for the desktop client is 256 MB on 32-bit platforms and 512 MB on 64-bit platforms. For a large monitoring environment, the portal client can be expected to use between 300 and 600 MB of memory.
Parent topic:
Sizing the Tivoli Monitoring hardware