Difference between revisions of "Configuring MySQL to Run on a Separate Server"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 8: Line 8:
<li>Direct the database server to the application server:
<li>Direct the database server to the application server:
   <ol type="a">
   <ol type="a">
   <li>Edit <tt>longjump_installation/tomcat/conf/server.xml</tt></li>
   <li>Edit <tt>{platform_installation}/tomcat/conf/server.xml</tt></li>
   <li>Replace <tt>url="jdbc:mysql://{domain}/relationals"</tt> with<br/>  <tt>url="jdbc:mysql://IP_address_of_database_server/relationals"</tt></li>
   <li>Replace <tt>url="jdbc:mysql://{domain}/relationals"</tt> with<br/>  <tt>url="jdbc:mysql://IP_address_of_database_server/relationals"</tt></li>
   <li>Save the file</li>
   <li>Save the file</li>

Revision as of 17:22, 7 June 2011

Configuring MySQL to Run on a Separate Server

This procedure sets up database connection pooling between the two servers.

  1. Enable permissions on MySQL, so web servers can access the database server:
    GRANT ALL ON *.* to 'root'@'web_server_IP_Address' IDENTIFIED BY 'password'
  2. Direct the database server to the application server:
    1. Edit {platform_installation}/tomcat/conf/server.xml
    2. Replace url="jdbc:mysql://{domain}/relationals" with
      url="jdbc:mysql://IP_address_of_database_server/relationals"
    3. Save the file
    4. If the Application server is currently running, then Restart the Application Server.

Learn More: http://dev.mysql.com/doc/refman/5.1/en/replication-solutions-backups.html