|
Home > Archive > SQL Anywhere database > October 2005 > Silent Install or merge modules?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Silent Install or merge modules?
|
|
|
| Hello..
We are fairly new to "automatic" ASA installation and would like to install
it quietly during the installation of our app...nothing new really. We've
seen the docs on how to install ASA using the "merge modules" and "silent
install" techniques, but we haven't seen info about why you would choose
approach or the other...is one method easier/newer/better than the other?
Is the choice forced by installation technology (i.e. installer X cannot do
"silent install") or is it just a matter of convenience/preference?
Any thoughts appreciated...
Steve
| |
| Mike Emery 2005-10-31, 8:23 pm |
| In general we recommend that you use a silent install unless you have a
specific reason not to. The merged modules are provided in case you want to
customize to a degree not provided by the standard setup. The only problem
is that there are several things which we take care of in the installer
which you will have to set up manually if you decide to use the merged
modules. We also don't provide direct support for merged module issues as
far as I know.
The silent install option provides enough customizability for most people,
and it has the bonus of being very simple to work with. You can set up both
the initial install, and EBF installations using the silent install
mechanism.
--
-Mike Emery
Product Support Analyst
iAnywhere Solutions
"Steve" < bhiggins@toolboxsoft
ware.com> wrote in message
news:43668af7$1@foru
ms-1-dub...
> Hello..
>
> We are fairly new to "automatic" ASA installation and would like to
install
> it quietly during the installation of our app...nothing new really. We've
> seen the docs on how to install ASA using the "merge modules" and "silent
> install" techniques, but we haven't seen info about why you would choose
> approach or the other...is one method easier/newer/better than the other?
> Is the choice forced by installation technology (i.e. installer X cannot
do
> "silent install") or is it just a matter of convenience/preference?
>
> Any thoughts appreciated...
>
> Steve
>
>
>
| |
|
| Mike,
Thanx for the response... very helpful. I can see now that silent install is
more of an "in house" sybase method, which has the benefits of being
supported, etc.
Question for you or whomever....
I've seen that a silent install needs a "response file" ( perhaps wrong
terminology...sorry) that we can define to hold pre-determined answers to
typical install questions.
If that's the case, can silent install deal with variable answers to install
prompts? i.e what if someone need to install to the F: drive instead of the
C:drive, etc?
Thanks again...
Steve
"Mike Emery" <mike.emery@ianywhere.com> wrote in message
news:4366955a@forums
-1-dub...
> In general we recommend that you use a silent install unless you have a
> specific reason not to. The merged modules are provided in case you want
> to
> customize to a degree not provided by the standard setup. The only problem
> is that there are several things which we take care of in the installer
> which you will have to set up manually if you decide to use the merged
> modules. We also don't provide direct support for merged module issues as
> far as I know.
>
> The silent install option provides enough customizability for most people,
> and it has the bonus of being very simple to work with. You can set up
> both
> the initial install, and EBF installations using the silent install
> mechanism.
>
> --
> -Mike Emery
> Product Support Analyst
> iAnywhere Solutions
> "Steve" < bhiggins@toolboxsoft
ware.com> wrote in message
> news:43668af7$1@foru
ms-1-dub...
> install
> do
>
>
| |
| Mike Emery 2005-10-31, 8:23 pm |
| As far as I know, there is no easy way to change small things like that.
One option would be to record several different installs, and play them back
depending on what situation you are in (e.g. drive space left). Another
more complicated option is to alter the .iss file itself. The file is human
readable, and if you were to make a small regular expression I'm sure you
could easily change the drive letter.
--
-Mike Emery
Product Support Analyst
iAnywhere Solutions
"Steve" < bhiggins@toolboxsoft
ware.com> wrote in message
news:4366a023$1@foru
ms-1-dub...
> Mike,
>
> Thanx for the response... very helpful. I can see now that silent install
is
> more of an "in house" sybase method, which has the benefits of being
> supported, etc.
>
> Question for you or whomever....
> I've seen that a silent install needs a "response file" ( perhaps wrong
> terminology...sorry) that we can define to hold pre-determined answers to
> typical install questions.
> If that's the case, can silent install deal with variable answers to
install
> prompts? i.e what if someone need to install to the F: drive instead of
the
> C:drive, etc?
>
> Thanks again...
>
> Steve
>
> "Mike Emery" <mike.emery@ianywhere.com> wrote in message
> news:4366955a@forums
-1-dub...
want[color=darkred]
problem[color=darkre
d]
as[color=darkred]
people,[color=darkre
d]
We've[color=darkred]
" silent[color=darkred
]
choose[color=darkred
]
other?[color=darkred]
cannot[color=darkred
]
>
>
|
|
|
|
|