mySQL Installation with my own INI File

[Zero-G.]

Hey
I use the new Version 15. and I want to create an Installation, which should install mySQL for me.
I took the mySQL Plugin. But I don't found Information, of how I can use my own complex my.ini file for Startup!
Is there any Information about this

THX a lot

[Adam]

Hi

We ship MariaDB but used to do MySQL. We shipped all of the loose MySQL files and created the service manually (SC CREATE). The installer also installed my.ini to $WINDIR$ which can be edited after Apply Install (if using Windows Installer).

Cheers
Adam

[Zero-G.]

Thx for your reply
This was my first aproach as well. - But the Problem there is, that you can't run a Script any more, because the installer says, that the mySQL Plugin is missing...

THX for more tips to this

[FrancescoT]

Dear Zero-G,

Please verify that you have installed all InstallAware features during package setup.

Hope this helps you.

Regards.

[Zero-G.]

Hey
Maybe, I have been unclear.
The following Situation:
When I use InstallAware's Plugin of mySQL, I can't find a way, how I can implement my own "my.ini" file, with extra Settings (This was the main question, how I can get this working)

The solution would be to NOT use the plugin of InstallAware, install the files manually -> This works, but then I can't run a Script, because InstallAware tells me, that I haven't installed the Plugin.

Can you see the confusions!?

THX

[FrancescoT]

I'm not a MYSQL expert, but I really don't understand the error relation you are reporting.

Supposing that you with the same IA script first run the "my.ini" file (as you do manually) and just after the IA MySql plugin, this last one fails?

Regards

[Zero-G.]

Hey
The Problem is as follows: If you don't specify the ini file at the Moment, where you Register the Service, then mySQL searches (and automaticly takes) the first file, which is found.
In the following direction:
Root Path (e.g. C:\)
Windows Path (e.g. C:\Windows)
and THEN the Installation path.

The Problem is, that the most "Standard" Installation give there ini file to on of the first places. - So, if found, the one of a Prior Installation could be taken - I hope, I don't have to explain, what happens then....

This is the reason, why I have to explicit set the ini file at Installation of the Service!

THX

[Adam]

It just sounds to me like you haven't installed the MySQL plugin when you installed InstallAware.

I do not install MySQL as a pre-requisite, but I can still run a script using the "My SQL" plugin.

[Zero-G.]

Hey
Where to get this plugin?

THX

[FrancescoT]

As I already said ... try to verify that you have installed all InstallAware features.

Regards

[Zero-G.]

Hey
Thanks for all answers. - I finished it right now. And I will share my solution here with all of you, maybe someone will Need this help.
I got the mySQL Server from the mySQL Internet site. - as MSI package. (you can find Solutions on Google, how to unpack an msi file with command line Tools)
This files I add through the files Dialog to my "TARGETPATH"
Creating the ini file also works fine by using the Dialog mechanism.
Then Switch to the MSI Code window and search the INI entries. - below them, enter the code (with your Needs!)

Code: Select all

        
        Run Program $TARGETDIR$\bin\mysqld.exe --install VOpt --defaults-file="$TARGETDIR$\my.ini" (WAIT)
        Set Variable PROGRESS to 25
        Run Program NET START VOpt (WAIT)
        Set Variable PROGRESS to 50
        Run Program $TARGETDIR$\bin\install.bat  (WAIT)
        Set Variable PROGRESS to 75
        Configure Windows Firewall - add port opening 3306 TCP

2 Interesting things
1) I don't got it working, that the Service "VOpt" starts up with the built in Service control plugin. - This is, why I did it by "Run Program"
2) create an install.bat file in the same Folder, where the "mysql.exe" file is in. And let the script run through this install.bat file. - I didn't get it working with the direct command. - I just put the command to the Batch file

Code: Select all

mysql -uroot -P3306 < Script.sql

And here is Point 3 - which is one of the most important ones: IA Tells you, when importing a script use ANSI Charset. - When using mySQL Script with the way I did above, you have to take care that your script is formated in UTF8 Character Format (you can also find frewweare Tools on Google, which do that. - I used PSPad)

So, I hope someone of you could Need this.

Have a nice weekend

[FrancescoT]

Many thanks for sharing it!

Regards