Table of Contents
This chapter briefly describes the basic concepts and features of SysMaster and pre-installation tasks for installing SysMaster.
SysMaster is an integrated management solution for monitoring the performance of various system resources that are distributed on multiple servers. SysMaster provides an integrated monitoring environment for monitoring the entire IT system, including web server, WAS, TP-Monitor, application server, etc. (provider group), through a more intuitive screen where the user can monitor various types of resources from a single view.
SysMaster also provides real-time monitoring through Web Admin for more efficient resource management and measurements against failure. It efficiently manages performance of the overall system resources, quickly detects and handles errors, and systematically manages system performance using various statistical reports. SysMaster supports various forms of management environment that can be easily customized by the user according to the user's needs.
This guide refers to SysMaster monitoring target group as a Provider and each monitoring unit and instance as a Resource.
The following are the main features of SysMaster.
Manages performance of various resources.
Supports action plans for performance issues and failures.
Not dependent on hardware or OS.
Provides customizable Web Admin environment.
Provides custom management functions.
Provides various monitoring screen styles.
Provide search and reporting functions for statistical information.
The following items must be checked before installing SysMaster.
SysMaster is provided in the Standard edition and Enterprise edition. Check the specifications of each version before installing the product.
| SysMaster Version | Requirement |
|---|---|
| Standard | JDK: 1.6 |
| DB: H2DB | |
| WAS: Tomcat7 | |
| Enterprise | JDK: 1.5 ~ 1.7 |
| DB: Tibero 4, Tibero5, Oracle 10g~11g | |
| WAS: JEUS 6.0.0.6-b216(built-in WebtoB) |
SysMaster's master server engine is Tomcat and its repository DB is H2DB.
SysMaster's master server has the following constraints in using an embedded H2DB.
It is recommended to limit the number of target monitoring containers to 5 or less (50TPS/Container).
It is recommended to limit the data retention time to under 12 hours (in seconds).
Tx-view analysis and trend analysis might be difficult for a high volume of transactions or data.
When a high volume of transactions occurs or the amount of accumulated data increases, the embedded H2DB must be replaced with a commercial enterprise DBMS such as Tibero or Oracle.
Although there are no functional issues with installing the Master, Agent, and DB on the same machine using the same account, it is highly recommended that you install each on a different machine using a different account. The machine's performance specification should be considered for load distribution for monitoring targets like WAS, DB, etc.
The root(super user) account or the account of the target resource must be used to install the Agent. Otherwise, an authentication error may occur during operation. If the resource account is used, the Agent must be installed for each resource account.
The following are the database(File DB) resource requirements.
Disk space for database
1GB of disk space is required for operation in using a File DB. Disk space must be secured in advance based on the number and type of supported resources and the site policy. In general, at least 1GB of disk space is recommended for each resource.
Disk space for Master, Agent, and Web UI
The account of the target machine must acquire at least 512 MB of disk space.
License file and other license-related library files are needed to start the SysMaster Master Server. For more information about obtaining SysMaster licenses, contact TmaxSoft's sale representative or engineer, or contact TmaxSoft directly using the contact information at the beginning of this document.
The following are the software and hardware requirements for SysMaster.
| Category | Requirement |
|---|---|
| Platform | IBM AIX 5L 32/64bit, IBM AIX 6L 32/64bit |
| HP-UX 11 32 /64bit, HP-UX 11 32/64bit ia64 | |
| Solaris 7 ~ 10 32/64bit, Solaris 32(x86)bit | |
| Linux Kernel 2.x/2.x ia64 | |
| Windows XP/7/8, Server 2003/2008/2012(32/64bit) | |
| Master | JDK 1.6 |
| More than 1024MB of memory recommended (Min 512MB) | |
| Min 1GB hard disk space | |
| Agent | JDK 1.5 ~ 1.6 |
| More than 512MB of memory recommended (Min 256MB) | |
| Min 512MB hard disk space | |
| Web UI | JRE 1.6 |
| More than 512MB of memory recommended (Min 256MB) | |
| Min 512MB hard disk space | |
| Supported browsers: IE10 or later, and Chrome | |
| Database | H2DB(Basic) |
| Oracle 10g, 11g, 12c | |
| Tibero 4, Tibero 5 |
SysMaster Master Server includes a built-in H2DB. When a high volume of transactions occurs or the amount of accumulated data increases, the embedded H2DB must be replaced with a commercial enterprise DBMS such as Tibero or Oracle.
The following are the resource requirements for the monitoring targets.
Supported JDK versions for WAS: Java 1.4 ~ 1.6
Supported WAS WAS
| Resource | Supported Version |
|---|---|
| JEUS | 4.x ~ 7.x (JEUS 4.2.4.6 and later can be configured to collect pool information) |
| WebLogic | 8.x ~ 10.x |
| Oracle AS | 9.x ~ 10.x |
| Other | WebSphere : 5.x – 7.x |
| Tomcat : 6.x - 7.x | |
| Resin : 4.x | |
| JBoss AS : 6.x - 7.x | |
| Jetty 8.x |