MySQL Enterprise Certification for Technology Providers

MySQL Partner Program

Become a MySQL Partner Now!

Certifying your technology to work with MySQL Enterprise has benefits to both your company and your customers. Certification enables you to provide your customers with the confidence that they are deploying a production-ready, enterprise-grade solution. As well, you will be able to further differentiate your offering from those of your competitors by affirming that your product has been tested and confirmed to work with MySQL Enterprise. Additionally, you have the added benefit of knowing that when your customer deploys your solution with MySQL Enterprise, the database is fully supported thru monitoring and advisory services, rapid software up-dates, 24x7 support, and much more.

Today, achieving MySQL Enterprise Certification for your technology could not be easier. To certify your technology, you will need to:

Join the MECA program
Test and certify your product with MySQL Enterprise
Post the tested and supported version of your product on your MECA partner product page, and send the completed certification document to partner@mysql.com. Once the document is approved the certification document will be posted on your product page and the certified for MySQL Enterprise logo will show next to your product in the product directory.
Focused advertising of MySQL Enterprise - Reference "MySQL Enterprise [tested version]" as the supported database from MySQL (not "MySQL" or "MySQL Community Edition") in your marketing (e.g., product sheets, specifications, web site, customer announcements,… )

… and the MySQL Alliances team will help you in accomplishing these steps.

Step 1: Join the MECA program

To enroll in the MECA Program, visit http://partner-portal.mysql.com/, where you can apply for membership in the program, create a company profile for the MySQL Solutions Directory, subscribe for MECA Program Modules, and much more.

Step 2: Test your product with MySQL Enterprise

The MySQL Enterprise Certification program is a quick and easy self-certification program that will mark your application as a product that is compatible with the MySQL Enterprise Database Server product and related MySQL software tools. By clearly identifying ISV/IHV with robust products, this program creates awareness and increased business opportunities for MECA partners. Have your application become MySQL Enterprise Certified and you'll increase your product's visibility and provide an additional level of assurance to your customers.

This document describes the procedures that ISV/IHVs are required to follow for the rights to use a MySQL Enterprise Certified Program Logo. An application may carry the applicable MySQL Program Logo once it has passed certification testing as described in these procedures and the ISV/IHV has indicated agreement with the MySQL Enterprise Certified Partner Program Agreement. Such an application may continue to carry the MySQL Program Logo for so long as the application's certification status remains valid and the Agreement remains in effect. Sun reserves the right to change these procedures without notice.

The MySQL Enterprise Certification Procedures for ISV Applications and IHV platforms are intended to provide Technology Partners with a basic structure for ensuring that their applications run successfully using MySQL Enterprise binaries. Since the certification process is a self-certification process, Sun does not guarantee that a MySQL Enterprise Certified application works correctly and Sun accepts no responsibility or liability for any such application. It is the responsibility of the partner to determine, write, and execute a series of tests (the "test suite") that provide assurance that the application works properly when MySQL Enterprise is the installed database management system.

Platforms

ISV/IHV applications that comply with these Procedures for MySQL Enterprise Certification may be certified for any one of the following platforms:

32-bit Solaris
64-bit Solaris
32-bit Unix/Linux
64-bit Unix/Linux
32-bit Windows
64-bit Windows

Initial Certification

The first MySQL Enterprise binaries were released for MySQL Enterprise version 5.0.28. ISV/IHV applications that comply with these MySQL Enterprise Certification Procedures for ISV/IHV Applications will be certified for the MySQL Enterprise binary that is current at the time the Technology Partner executes the test suite and certifies to MySQL the error-free operation of the Technology Partner application.

Ongoing Certification/Recertification

A Technology Partner application that has earned the right to carry the MySQL Enterprise Certified Program Logo may continue to do so even when Sun releases a Monthly-Rapid Update (MRU), or maintenance, version, of MySQL Enterprise. An application may also continue to carry the MySQL Program Logo when the Technology Partner releases an interim version of the application. However, to keep its certification current, the Technology Partner must put its application through the certification process and recertify in the following circumstances:

A major new version of MySQL Enterprise is released. (A major new version is denoted by an increment in the first or second digit of the MySQL Server version number; e.g. 5.1, 6.0, 6.1 and so on). That is, applications that are certified for MySQL 5.1.30 will not need to recertify when MySQL 5.1.31 is released but will need to recertify for MySQL Enterprise 6.0 and MySQL Enterprise 6.1 when they are released.
A major new version of the application is released by the Technology Partner.
The application is released on a platform for which the application was not previously certified.

Sun does, however, encourage Technology Partners to rerun the certification test suite each time either Sun or the vendor releases any new versions of their respective software.

Step 3: Post the tested and supported versions on your MECA partner page

Once you have completed the certification you should have the following information:

The MySQL Enterprise version tested
Your product version used for the test
The platform (i.e. operating system/environment) upon which the testing was done (Linux, Windows, etc)

It is the responsibility of the Technology Partner to specify the platform and the MySQL Enterprise version for which the application has been certified. Depending how restrictive or open you want the certification to be, you can specify a narrow set of versions (e.g. MySQL Enterprise 5.1.38 on RHEL4, 32 bit Intel) or a broader set (e.g. MySQL Enterprise 5.1.38 and higher on RHEL4, 32 bit) if your tested configurations will work without errors on other platforms.

Once you have successfully completed the certification testing, we encourage you to share the results with our ecosystem. A template for the white paper certification document is available on your homepage in the partner portal. When the test data and the white paper are submitted to partner@mysql.com the MECA program manager will review the documentation. Once the documentation is approved, the program manager will send the Enterprise Certified Logo to the technology partner, and approve the partner as a certified partner in the partner directory.

Step 4: Focused advertising of MySQL Enterprise

Upon completion of the above steps, you may use the MySQL Enterprise Certified logo while referring to “MySQL Enterprise [tested version]” as the supported database from Sun in your product sheets, specifications, web site, customer announcements, etc.

You may not use the terms “MySQL” or “MySQL Community Edition”, which refer to unsupported versions and fall outside the partner program.

Use of the MySQL Enterprise Certified Logo is subject to the terms described in these Instructions, the Program Guide and the MySQL Trademark Policy posted on the MySQL AB Web site (www.mysql.com, the "Web site").

The Technology Partner's certification is specific to the application for which certification testing has been completed and does not apply to or benefit any other application, company or organization. Technology Partner may continue to use the MySQL Enterprise Certified Logo for so long as the tested application’s certification status remains valid and this Agreement remains in effect.

Technology Partner may not display or use the MySQL Enterprise Certified Logo in a manner that suggests that the Technology Partner is a representative of MySQL AB, or that Technology Partner or the application tested for certification is affiliated with, or endorsed by, MySQL AB. Moreover, everywhere Technology Partner uses the MySQL Enterprise Certified Logo, the name of Technology Company and the application tested for certification, must appear more prominently than, and clearly distinguished from, the MySQL Enterprise Certified Logo.

To obtain the MySQL Enterprise Certified logo, or for more information on how to become MySQL Enterprise Certified, email partner@mysql.com.

Technical Requirements

To obtain MySQL Enterprise Certified status for an application, the following technical requirements must be met:

The Technology Partner must write a test suite which verifies that the application they wish to certify for MySQL Enterprise certified status (the "candidate application") works properly with MySQL Enterprise. Since this program is a self-certification program, Sun imposes no rules or requirements on the type of tests that must be included in the test suite; it is expected that the Technology Partner will certify using an in-house testing process which assures the Technology Partner that the candidate application is production-ready and fully compatible when using MySQL Enterprise. It is not expected that the test suite shall verify that the candidate application works with all aspects and features provided by Sun; it is expected that the test suite shall verify that the candidate application works properly with all Sun-provided aspects and features that are relevant to the application.
The Technology Partner must start the MySQL Server with the general query log option enabled (i.e. mysqld --log[=file_name]) and run the test suite for the candidate application. This ensures that all connections and SQL statements sent to the server by the candidate application will be logged. The log can later be used to help verify that there were no errors generated.
The Technology Partner's test suite for the candidate application must run without errors, using the then-current MySQL Enterprise binary. Sun undertakes no responsibility for verifying that the test suite runs without errors; this is solely the responsibility of the Technology Partner.

MySQL Test Software

The MySQL Enterprise distribution includes a software testing program which the Technology Partner ("you") may use to run certification tests instead of, or in addition to, your own tests. The MySQL test software, called mysql-test, can be found on a subdirectory called mysql-test, under the directory where you have installed the MySQL Enterprise package. Sun does not represent that the mysql-test software will adequately test or certify your application, and you accept all risks associated with using such test software.

The mysql-test software comes with numerous test cases already written. These tests check the ability of the MySQL Enterprise Server to process requests correctly and are not intended to check the performance of a candidate application. If you wish to utilize the MySQL test software to augment your own test processes, use the following procedure:

Start the MySQL Enterprise Server with the general query log enabled.
Run the candidate application, using either your own test suite or passing a series of requests from the application to the MySQL Enterprise Server.
Convert the statements written to the MySQL Enterprise general query log during the test process into a test suite file acceptable to the MySQL test software.
Run the MySQL test software, as follows.

How to run the MySQL Test Software

As stated above, the mysql-test software comes with numerous test cases already written; it will not be necessary to execute these tests to certify your application. To execute only your test suite, run the software as follows (all instructions assume the use of a Linux operating system):

% mysql-test-run test-file-name

Replace test-file-name with the name of your test suite file. The file must have an extension of .test. The README file in the mysql-test directory contains detailed information on invoking the MySQL test software and the test case language.

The mysql-test-run command sets up the environment needed to call the mysql-test program. mysql-test will read the test case language text and start managers, create connections, send queries to the MySQL Enterprise Server, and so on.

The test case language is a mixture of SQL statements and commands understood by the mysql-test program. Any commands not understood by the program are assumed to be SQL statements and are sent to the MySQL Enterprise Server. The base principle is that the test script compares the output produced when the test file is run with the expected result. To add and run a test file, follow these steps:

Go to the mysql-test directory:
% cd mysql-/mysql-test
Copy your test suite file to the mysql-test/t subdirectory; the result is a file called:
mysql-test/t/<test-file-name>.test
Create an empty result file:
% touch r/.result
Run the test:
% ./mysql-test-run
If the tests do not produce the expected result, the MySQL test software creates a file called r/<test-file-name>.reject. The first time you run a new test file, a .reject file is always produced, since the .result file has no expected results.
Examine the .reject file, to determine whether the tests ran successfully. If they did not, correct any problems and then rerun the tests.
Once all tests in the test file run successfully, copy the contents of the .reject file to the .result file, so that each time the test is run in the future, the mysql-test program can compare the new test results with the expected results shown in the .result file.

For more information about using the mysqltest program run:

% mysqltest --help