| Author |
Message
|
| jeevan |
 Posted: Mon Mar 31, 2008 10:59 am Post subject: Automating MQ installation /configuration |
 |
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
I am exploring silent installatino feature of MQ. I started with generating a ini files instead of installing the whole product. I issued the follwing command:
| Quote: |
Msiexec /i IBM WebSphere MQ.msi" c:\mqm\install.log TRANSFORMS="1033.mst" ONLYINI="yes" AGREETOLICENSE="yes" ADDLOCAL="Server" |
It just brings up an MSI windows but does not do anyting. Did I miss anything else?
I hope, this should go ahead start asking questions which will be eventually be recored in an silent file ( not sure whether I should mention a file name or it generates automatically as default file name) |
|
| Back to top |
|
 |
| jeevan |
| Posted: Mon Mar 31, 2008 3:21 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
One more thing, I am consufuse while reading the doc. At one point it says:
| Quote: |
Msiexec /i "path\MSI\IBM WebSphere MQ.msi" /l*v c:\install.log /m mif_file
TRANSFORMS="1033.mst" AGREETOLICENSE="yes" ADDLOCAL="Server"
|
And in another place, it says:
| Quote: |
To invoke the Msiexec command using a response file, enter the following command at a command line:
Msiexec [parameters] USEINI="reponse_file"
|
Does it mean when I invoke MSI with USEINI do I need to mention .msi file or not ?
I am not sure response file and msi file are mutually exclusive? If not, why they have similar parameters?
When I tried invoking the command without .msi file, it an winodws pops up with follwoing errors:
This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package
Any help would be greatly appreciated |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Mar 31, 2008 11:56 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Jeevan,
Try this:
Msiexec /i "<path to MSI>\IBM WebSphere MQ.msi" /qn /l*v "<temp dir path>\<log file name>" USEINI="<path to ini file>\<ini file name>"
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| jeevan |
| Posted: Tue Apr 01, 2008 7:16 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| exerk wrote: |
Jeevan,
Try this:
Msiexec /i "<path to MSI>\IBM WebSphere MQ.msi" /qn /l*v "<temp dir path>\<log file name>" USEINI="<path to ini file>\<ini file name>" |
It does not work either. The other parameters are optional. The msi and ini file are the main configuration files.
thanks anyway |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Apr 01, 2008 11:17 am Post subject: Re: Automating MQ installation /configuration |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| jeevan wrote: |
| It just brings up an MSI windows but does not do anyting. Did I miss anything else? |
With the "ONLYINI" switch, unless you have an *.ini file for it to read I would expect that it would appear to hang.
I've found the /i switch to be very sensitive to the path and MSI file name not being enclosed in quotes (and from your post it looks like one is missing from the beginning Msiexec /i IBM WebSphere MQ.msi"), especially if there are spaces in the directory name where the MSI file is.
It's possible either the path is incorrect, or possibly the file is corrupt. Have you tried to run it from the command line while in the MSI directory?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| jeevan |
| Posted: Tue Apr 01, 2008 12:15 pm Post subject: Re: Automating MQ installation /configuration |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| exerk wrote: |
| jeevan wrote: |
| It just brings up an MSI windows but does not do anyting. Did I miss anything else? |
With the "ONLYINI" switch, unless you have an *.ini file for it to read I would expect that it would appear to hang.
I've found the /i switch to be very sensitive to the path and MSI file name not being enclosed in quotes (and from your post it looks like one is missing from the beginning Msiexec /i IBM WebSphere MQ.msi"), especially if there are spaces in the directory name where the MSI file is.
It's possible either the path is incorrect, or possibly the file is corrupt. Have you tried to run it from the command line while in the MSI directory? |
Let me explain how my setup is. I have mq binary ( installation stuff), .ini and msi files all in the same directory.
I use ONLYINI at the beg, but I tried virtually everthing afterward.
I used simplest parameters
Msiexec /i "c:\mq6.0\IBM WebSphere MQ.msi" c:\mqm\install.log TRANSFORMS="1033.mst" ADDLOCAL="Server"
This is a simplest parameters. But it still does not work. It pops up an msi windows and do nothig. Not a hang as such.
Thanks a lot |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Apr 01, 2008 12:28 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Anything in EventViewer? Specify a log file and see if anything is printed in it.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| chaitralip |
| Posted: Thu Apr 03, 2008 2:06 am Post subject: |
|
|
Novice
Joined: 16 May 2007
Posts: 24
|
instead of using INI file you can try doing the below. It works for me
MSiexec /i "\<Path to MSI>\IBM WebSphere MQ.msi" /q /L*v "<LogPath>\<logname>" PGMFOLDER="C:\WebSphereMQ" DATFOLDER="C:\WebSphereMQ" LOGFOLDER="C:\WebSphereMQ\log" ADDLOCAL="Server" LAUNCHWIZ=0 AGREETOLICENSE="yes" REMOVEFEATURES="yes" /q |
|
| Back to top |
|
|
|
|
