Skip to content

Compiling and Deployment

Jump to bottom Edit New page
Daniel Moldovan edited this page Jan 31, 2014 · 4 revisions

The “MELA” directory contains a MELA Maven "pom" project. The project has a set of Maven modules: MELA-AnalysisService, MELA-DataService, MELA-Common and MELA-DataCollector. MELA-DataService is responsible of collecting monitoring information from existing monitoring systems, and storing it in a local monitoring repository.

The MELA-AnalysisService is a Web Application queries monitoring data from the MELA-DataService, structures and analyzes it. MELA-Common contains the common data model used by the other two modules. MELA- DataCollector currently contains scripts for installing Ganglia and configuring it to work with MELA automatic structure detection.

MELA-DataCollector compiles and packages using Maven in a “tar.gz” archive, containing scripts for installing Ganglia, and configuring it for supporting automatic service structure detection. MELA-Common compiles in jar.

MELA-AnalysisService and MELA-DataService have two maven profiles: the standard profile compiles them in shaded .jar files. The “Release” profile also produces for each project a “tar.gz” archive containing the jars, necessary configuration files, and scripts for running them. To compile the modules using Maven, from the MELA main directory, running "mvn clean install" or "mvn clean package" will compile all MELA Modules. Running "mvn clean install –P Release” or "mvn clean package –P Release” activates the Release profile which also produces the project’s “ tar.gz” distribution.

Running

Both MELA-DataService and MELA-AnalysisService must run for obtaining the complete system functionality. MELA-DataService can also run standalone, during which it will collect data. MELA-AnalysisService just processes already collected data and provides services for setting the monitored service structure, metric composition rules (see writing metric composition rules and application specific configuration), and service requirements, which affect the way MELA-DataService structures collected data.

MELA-DataService

Configuration

  • Configure if required the options presented in "./dataServiceConfig/Config.properties" .
  • Configure the data sources from which data is to be collected in "./dataServiceConfig/dataSources.conf" =
  • If necessary the default metric composition rules, service structure and service requirements can be configured by modifying the files in "./dataServiceConfig/default"

Compile and Run

  • If compiled with "mvn clean package -P Release", extract the "tar.gz", perform necessary configurations, and start the MELA-DataService using the provided script by executing "mela-data-service start". With "mela-data-service stop" the MELA-DataService can be shut down.
  • If compiled with the standard profile, run from the target directory the MELA-DataService as any simple jar with "java -jar ./MELA-DataService_version"

MELA-AnalysisService

Configuration

  • Configure if required the options presented in "./config/Config.properties".

Compile and Run

  • If compiled with "mvn clean package -P Release", extract the "tar.gz", perform necessary configurations, and start the MELA-AnalysisService using the provided script by executing "mela-analysis-service start". With "mela-analysis-service stop" the MELA-AnalysisService can be shut down.
  • If compiled with the standard profile, run from the target directory the MELA-AnalysisService as any simple jar with "java -jar ./MELA-AnalysisService", as it is packaged with an embedded Apache Tomcat 7.

As MELA-AnalysisService is packaged with an embedded Apache Tomcat 7, it will try to start on a standard HTTP 8080 port. If that port is occupied, change the "mela-analysis-service" script to include in the java -jar ./MELA-AnalysisService -httpPort=port", or add "-httpPort=port" if running from command line.

Add a custom footer
Add a custom sidebar
Clone this wiki locally