Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Please check whether you have libxml2 installed in your system.
  2. Download mod_proxy_html.c from from 
    Newtab2
    aliashttp://apache.webthing.com/
    urlhttp://apache.webthing.com/
  3. Now build mod_proxy_html with apxs, apxs -c -I/usr/include/libxml2 -i mod_proxy_html.c
  4. You need to load the following modules, so add the following entries in [/etc/httpd/conf/httpd.conf].

    Code Block
    themeConfluence
      LoadModule proxy_module modules/mod_proxy.so 
      LoadModule proxy_http_module modules/mod_proxy_http.so 
      LoadModule headers_module modules/mod_headers.so 
      LoadModule deflate_module modules/mod_deflate.so 
      LoadFile /usr/lib/libxml2.so 
      LoadModule proxy_html_module modules/mod_proxy_html.so
  5. Add the following configuration in your Apache configuration file [/etc/httpd/conf/httpd.conf]

...

They have similarities (in which they both differ from server-side scripts used for monitoring): they both make use of a HTTP service, a database and both use a web-browser for reporting. However, important differences are:

  • SQL DM for MySQL is distributed with a perpetual license and is not bundled with anything else. But other MySQL Monitoring Tools are available only as part of a larger support package with periodical license terms.SQL DM for MySQL needs no installation (of 'agents') on the server where the MySQL servers are running. Other does.
  • SQL DM for MySQL 'has everything in itself' - the webserver, the database, the MySQL client. It does not depend on the existence of other webservers, runtimes/Virtual Machines (like JAVA) and needs no separate database install. Other monitoring tools requires a full JDK (java), a TOMCAT server and a MySQL server instance for itself. Due to this simplified architecture install, configuration and first of all maintenance and upgrade is much simpler with SQL DM for MySQL. Download packages and disk storage required are much smaller with SQL DM for MySQL.

...

20. SQL DM for MySQL throws an error when trying to connect to MySQL.

Please go through through 

Newtab2
aliasError when trying to connect to MySQL
urlhttp://faq.webyog.com/category/7/connection-issues.html
. The same applies to SQL DM for MySQL as the client code is exactly the same in both programs. Observe however that everything related to HTTP-tunneling with SQLyog is not relevant for SQL DM for MySQL.

...

Four ways:

  • Website Intercom 
    Newtab2
    aliashttps://www.idera.com/
    Post in our Forums
    urlhttps
    http
    ://www.idera.com/
  • Post in our Forums 
    Newtab2
    alias http://community.idera.com/
    url http://community.idera.com/
  • Create ticket: ideramysqlsupport@idera.com
  • SQL DM for MySQL UI intercom

...

Code Block
themeConfluence
sudo monit reload


TOP



Scroll pdf ignore
Newtabfooter
aliasIDERA
urlhttp://www.idera.com
Newtabfooter
aliasProducts
urlhttps://www.idera.com/productssolutions/sqlserver
Newtabfooter
aliasPurchase
urlhttps://www.idera.com/buynow/onlinestore
|
Newtabfooter
aliasSupport
urlhttps://idera.secure.force.com/
|
Newtabfooter
aliasCommunity
urlhttp://community.idera.com
|
Newtabfooter
aliasResources
urlhttp://www.idera.com/resourcecentral
|
Newtabfooter
aliasAbout Us
urlhttp://www.idera.com/about/aboutus
|
Newtabfooter
aliasLegal
urlhttps://www.idera.com/legal/termsofuse
IDERA Website | Products | Buy | Support | Community | About Us | Resources | Legal