Prerequisites
Prior to installing Evident ClearStone Live, ensure the following prerequisites are met:
- ECSL Collector Deployment
- If the monitored processes are running on a different network than the ECSL server, consider deploying a remote ECSL Collector that is within the same network. The benefit would be to reduce network overhead across multiple network segments and improve overall collection latency.
- If the processes are J2EE containers, consider deploying the Evident JMX Proxy Servlet web application. This provides a HTTP based interface to collect data from the J2SE container and avoids using standard JMX over RMI, which tends to be slow. Furthermore, HTTP is generally open on most hosts and networks, whereas RMI may not be.
- If the processes are standard Java processes, configure the ECSL Collector to perform remote JMX monitoring.
- ECSL Operational Cache
- The OpCache is limited to the available physical memory across the ECSL core server(s). With more physical memory ECSL, can retain the more real-time performance data and events for longer periods of time. Typically, the OpCache is used to store the most recent 24 hours of real-time.
- Consult Evident Software regarding the sizing of the OpCache to ensure the amount of physical memory is adequate for the monitoring of the environment.
- Database Requirements
- An Oracle 10g/11g relational database is required for storing historical data for ChronoGraphs.
- Customers are required supply a separate database instance running on a database-grade server.
- For production, the DBA should ensure the database instance is properly configured with table spaces to achieve optimal performance.
- ECSL includes tools for creating the database schema and ETLs necessary for the data warehouse.
- Notifications
- ECSL supports email and SNMP trap alerts.
- For email alerts, the administrator must have a SMTP host and list of email addresses subscribing to the alerts.
- For SNMP traps, the administrator must have one or more SNMP trap destinations available.
- For additional custom alerting interfaces, this can be supported via a custom notification plugin.
Deployment
Installation Options
The ECSL installation consists of deploying the core software on one or more servers. The product can be deployed across multiple servers to scale out data storage and load balancing the real-time data processing. Optionally, customers can deploy remote Collectors and Management Plugin Servers to collect and manage the remote applications. During the installation process, the administrator is presented with the following options for the core ECSL platform:
- Collector
- Pipeline Server
- User Interfaces
- Management Plugin Server
- ChronoGraph (license specific)
During the installation process, the ECSL license activates additional features (i.e. ChronoGraphs) during the product installation.
Management Packs
Evident Software provides Management Packs for ECSL that are designed for supporting specific managed systems (i.e. caching platforms, middleware systems, messaging systems, etc.). A management pack includes features that are tailored to that type of manage system. A management packs is comprise of the following combination of components:
- Information Model(s) that represents the data definition of the managed system
- Pipeline plugins and extensions for specialized processing / handling of the managed system data
- UI extensions for updated visualizations of the managed system data
- ChronoGraph templates for history reporting of the managed system data
- Management plugins provide operations for managing the monitored system
For example, the Oracle Coherence Management Pack includes the following additional components:
- Oracle Coherence Information Model
- Pipeline Plugins and Extensions for handling Coherence data
- Real-Time Console for Oracle Coherence
- Chronograph templates for Coherence historical reporting
- Management Plugin for managing Coherence clusters and data
During the ECSL installation process, the following core modules are available for installation.
Installation Modules |
Components |
| Collector |
Collector |
Pipeline Server |
Operational Cache
Pipeline Engine
License Server |
User Interfaces |
Data Services
Real-Time Dashboard |
| Management Plugin Server |
Plugin Server
Operations Proxy |
ChronoGraph (optional) |
Clearbase Publisher
ChronoGraph Builder & Viewer |
Default |
Web Documentation |
Depending on the deployment model, the product can be deployed on a single server or across multiple servers to support large scale environments. The following table illustrates common deployment models for the product.
# of Servers |
Installation Options |
Description |
1 |
Server #1:
- Collector
- Pipeline Server
- User Interfaces
- Management
Plugin Server
-
ChronoGraph |
The most basic deployment model is where all the modules are installed on a single server. This model requires the target installation server to have sufficient local resources (CPU cores and physical memory) to run the product. It assumes the server is co-located on the same network as the monitored environment. |
2 |
Server #1 (remote):
-
Collector
- Management
Plugin Server (optional)
Server #2:
- Pipeline Server
-
User Interfaces
-
ChronoGraph |
In environments where the monitored JVMs are on a different network, then a dual server deployment model is recommended. This model allows users to deploy a remote Collector to collect data from the local environment. This reduces the network overhead and expedites data collection within the same network segment. The optional Management Plugin Server can also be coresident with the Collector to enable remote management of the local environment.
Server #1 is remote ECSL JMX Collector and the Management Plugin Server (optional) deployed in a remote network where the monitored JVMs are.
Server #2 the ECSL core server that is deployed in a management/test network. The network communication between the servers is over a specific TCP port (i.e. 30200) on Server #2. Server #2 is consists of all the ECSL components except for the Collector.
Note: The management plugin server requires multicast for this deployment model. If multicast is prohibited between the servers, please consult Evident Software for additional instructions. |
3 |
Server #1 (remote):
-
Collector
- Management
Plugin Server (optional)
Server #2:
- Pipeline Server
Server #3:
- User Interfaces
-
ChronoGraph |
In larger environments where the ECSL requires additional resources for processing and memory storage, the ECSL deployment can be distributed across multiple servers. This model allows for the product to expand beyond the physical memory limits of single or dual server deployment models.
Both server #2 and #3 will provide for a shared distributed Operation Cache for the system. Server #2 will performed most of the data processing. Whereas server #3 is used for data presentment.
The additional benefit of distributing the Pipeline Server and the User Interfaces is for load balancing, scaling, and redundancy. A server that is installed with just the Pipeline Server is responsible for processing the real-time data from the monitored cluster and updating the OpCache. The other server running the User Interfaces components is dedicated to serving the users connected with the Real-Time Dashboard and ChronoGraph features.
Note: The management plugin server requires multicast for this deployment model. If multicast is prohibited between the servers, please consult Evident Software for additional instructions. |
Base on the desired deployment model, follow these guidelines for installation of the software on the target platforms.
- For installations supporting Oracle Coherence, a valid ECSL license is required for the Coherence Management Pack.
- For deploying ECSL on a single server, choose to install all options.
- For deploying ECSL with a remote collector, perform these steps:
- Start with the deployment of the Collector and Management Plugin Server (optional) on server #1.
- On the ECSL core server, choose the Pipeline Server, User Interfaces, and ChronoGraph (if licensed).
- For deploying multiple ECSL servers, perform these steps:
- Start with the deployment of the Collector and Management Plugin Server (optional) on server #1.
- Next, deploy the first ECSL core server by choosing the Pipeline Server option.
- Lastly deploy the second ECSL core server by choosing the User Interfaces and ChronoGraph option(s).
- For this deployment model, ensure the two ECSL core servers are same network segment.
- The ChronoGraph module requires a separate Oracle database server.
- Once the ECLS product has been installed, the next step is deploying specific management packs for the managed environment. Please consult the documentation for each of the available Management Packs.
Installing on MS Windows Platforms
- Ensure the server meets the system requirements as described in the System Requirements section.
- Obtain a valid license file from Evident Software.
- Installation must be performed by a user with Administrator rights on the target host.
- Upload the installer (install.exe) and the license file to the server.
- Run install.exe on the command line or using Windows file explorer.
- The installer will prompt for the target installation directory on the server. The designated drive requires at least 2GB of disk space.
- The installer will prompt the user for the ECSL license file. Please provide the name of the licensee and the absolute path where the license file is located. Once all the information has been specified, click on the Install License button to install the license key and then proceed using the Next button.
- Following the license registration, the installer will prompt for the acceptance of the Electronic User License Agreement for the software.
- Base on the deployment model as noted above, select the modules as required. After the module selection is completed, continue with the installer. It will deploy the product in the specified directory.
- On the ECSL core server(s), the installer creates two Windows services entries for Evident ClearStone Live and the Evident ClearStone OpCache Manager. The Evident ClearStone Live service depends on the Evident ClearStone OpCache Manager service. Both are set to auto start upon a server restart.
- If the Collector is deployed on a remote host, the installer creates a single Windows service (Evident ClearStone Live for Java 4.x.).
- For additional server deployments, repeat the same steps choosing the appropriate options to deploy.
- Once the service is running, proceed with Setup and Configuration.
Installing on Linux or Solaris
- Ensure the server meets the system requirements as described in the System Requirements section.
- Obtain a valid license file from Evident Software.
- Upload the installer (install.bin) and license file to the server.
- Where possible, install the product as a user with root privileges. If the installation is executed by a user without root privileges, then the installer will warn the user of this restriction. It will proceed to install, however it will not deploy the startup scripts for the Evident ClearStone Live services in the /etc/init.d directory. The ownership can be changed from root to another user after the installation is completed.
- Open up a shell and run the installer. The installer runs in console mode.
# sh install.bin
- It will prompt for the target installation directory on the server. The designated drive requires 2GB of disk space. The directory will automatically be created.
- When the installer prompts for the license file, enter the name of the licensee and the absolute path where the license file is located. Once all the information has been specified, the installer will validate the license and continues with the installation is accepted.
- Following the license registration, the installer will prompt for the acceptance of the Electronic User License Agreement for the software.
- The installer will prompt for the modules to install. Base on the deployment model as noted above, enter "yes" for the modules as desired.
- Once all the modules are selected, the installer will proceed to install the software.
- Assuming the installation was executed as a user with root privileges, the installer will create additional startup scripts that will run the software on the host.
- On the server where the Pipeline Server or User Interfaces is installed, the installer creates the following startup scripts:
- /etc/init.d/evidentws (Evident ClearStone Live daemon)
- /etc/init.d/evidentocm (Evident ClearStone OpCache Manager daemon)
- On the remote server where the Collector is deployed, the installer creates a single startup script:
- /etc/init.d/evidentws (Evident ClearStone Live daemon)
- For additional server deployments, repeat the same steps choosing the appropriate modules to deploy.
- Assuming the installation was executed as a user with root privileges, it is recommended to change the file ownership of the installed software and startup scripts. Follow these steps:
- Stop the service(s):
# /etc/init.d/evidentws stop
# /etc/init.d/evidentocm stop
- If required, create a new user group for the new user account (i.e. evident).
- Create a new user (i.e. evident) using User Administrator tool or useradd command. Specify the new user group is desired.
- Change the ownership of the files where the product was installed to the new user. For example:
# chown -fR evident:evident /opt/evident/ECSL
- Login or su to the new user (i.e. evident) and start the services:
# su - evident
$ /etc/init.d/evidentocm start
$ /etc/init.d/evidentws start
- Once the processes are running, proceed with Setup and Configuration.
Installing on Apple Mac OS X
- Ensure the server meets the system requirements as described in the System Requirements section.
- Copy the installer (install.app) to the host where the Evident ClearStone Live software is to be installed.
- If possible, install the product as a user with root privileges. If the installation is executed by a user without root privileges, then the installer will warn the user of this limitation. It will proceed to install, however it will not deploy the startup scripts for the Evident ClearStone Live services (the services can be started manually, see Step #10 below).
- Double-click on the install icon from the Finder to launch the Evident ClearStone Live installer and follow the directions provided by the installer.
- If you get and error that specifies that "you do not have sufficient permissions to install services on this machine", click-on the Next button and proceed with the installation.
- The installer will prompt for the target installation folder on the Mac. The designated drive requires 2GB of disk space. The default installation is in /Applications/ClearStone_Live/ directory, but you may select a different folder from the default Applications folder, if needed, by selecting the Choose button.
- The installer will proceed to prompt for the license file. When prompted, provide the Customer Name of the license key and the absolute path where the license file is located (you can browse using the "..." button). Once all the information has been specified, click on the Install License button to install the license key and then proceed using the Next button.
- Following the license, the installer will prompt for the acceptance of the Electronic User License Agreement for the software.
- After the feature selection is completed, continue with the installer. It will deploy the product in the designated installation Folder. Click on the Done button once Evident ClearStone Live has been installed successfully.
- If you received the "you do not have sufficient permissions to install services on this machine" message in Step #5, you can manually start the services using the instructions below or install the services from an account that has root privileges as stated below.
Evident OpCache Manager
These instructions assume Evident ClearStone Live is installed in the default location, /Applications/ClearStone_Live. To start the Evident OpCache Manager manually, open the Mac OS X Terminal application from the Application --> Utility folder and perform the following steps from a command prompt:
- $ cd /Applications/ClearStone_Live/services/EvidentClusterManager/bin
- $ ./evidentocm.sh start
To install and start the Evident Opcache Manager service, log in as root and perform the following steps from a command prompt:
- # cd /Applications/ClearStone_Live/services/EvidentClusterManager/bin
- # cp evidentocm.plist /Library/LaunchDaemons
- # launchctl load /Library/LaunchDaemons/evidentocm.plist
- # launchctl start com.evidentsoft.ocm
Evident ClearStone Live
To start Evident ClearStone Live manually, perform the following steps from a command prompt:
- $ cd /Applications/ClearStone_Live/tomcat/bin
- $ ./evidentws.sh start
To install and start Evident ClearStone Live as a service, log in as root and perform the following steps from a command prompt(*):
- # cd /Applications/ClearStone_Live/tomcat/bin
- # cp evidentws.plist /Library/LaunchDaemons
- # launchctl load /Library/LaunchDaemons/evidentws.plist
- # launchctl start com.evidentsoft.ws
|